SOFTWARE ARCHITECTURE
DESCRIPTION

• This two-day course provides a solid grounding in the fundamental principles of Software Architecture (SA).
• Course provides in-depth coverage of effective software architecture documentation practices, effectively design and
• Analyze software architecture that meet the needs of the entire architecture stakeholder community.
• Software architecture has become a widely accepted conceptual basis for the development of nontrivial software in all application areas and by organizations of all sizes. However, the treatment of architecture to date has largely concentrated on its design and, to a lesser extent, its validation. Effectively documenting architecture is as important as crafting it; if the architecture is not understood (or worse, misunderstood), it cannot be analyzed
• Effectively or meet its goal as the unifying vision for system and software development.

o This course shows software architects how to produce a comprehensive documentation package for a software architecture that is useful to stakeholders. After attending this course, participants will have a better understanding of

• What is software architecture?
• How do you use software architectures in practice?
• What does a software architect do for an organization?
• What value does software architecture provide?
• Design decisions will lead to a software architecture that successfully addresses the desired system qualities (availability, performance, security, interoperability, and modifiability)
• Basic principles of sound technical documentation
• A stakeholder- and view-based approach to documenting software architectures
• Which views are available for documenting an architecture
• How to choose the set of views that will be most valuable to the architecture's community of stakeholders
• The information needed to document a view
• How to use formal and informal notations (including UML) to represent elements and relations in a view
• How to document a software interface and software behavior
• The information needed to document information that applies across views
• How do you know if a given software architecture is deficient or at risk relative to its target system qualities?

• Definition and overview of software architecture
• The architecture business cycle: what influences software architects and software architecture
• Understanding and achieving quality attributes
• Method for eliciting critical quality attributes, such as availability, performance, security, interoperability, and

• Method for evaluating software architecture based on a set of attribute-specific measures of the system
• Such as performance, availability, modifiability, and security
• Attribute-driven design
• Documenting software architecture
• Evaluating software architecture
• Architecture reuse
• Principles of sound documentation
• View types, styles, and views
• Advanced concepts such as refinement, context diagrams, variability, software interfaces, and how to document interfaces
• Documenting the behavior of software elements and software systems
• Choosing relevant views
• Building a documentation package using a seven-part template
• Life-cycle view of architecture design and analysis methods