Software Architecture

1
Software Architecture

• Encompasses significant decisions about
• organization of a software system
• the structural elements and their interfaces that
  will comprise the system, together with their
  behavior
• the composition of the structural and behavioral
  elements into progressively larger subsystems
• the architectural style that guides the
  organization elements and their interfaces,
  their collaborations, and their compositions
• Also concerned with
• usage, functionality, performance, resilience,
  reuse, comprehensibility, economic and
  technological constraints and trade-offs, and
  aesthetics.

2
Architecture

• Developed in iterations primarily during the
  elaboration phase
• starting with requirements, followed by analysis,
  design, implementation, and test, but focusing on
  the architecturally relevant use cases and other
  requirements
• first build works with application-general parts
  which are general for the domain in question and
  not specific for the system planned for
  development
• second build works with the application-specific
  aspect of the architecture - pick a set of
  architecturally relevant use cases
• When a stable architecture is in place, implement
  the complete functionality by realizing the rest
  of the use cases during the construction phase
• the use cases implemented during construction
  phase are mostly developed using customer user
  requirements as input.