Architecting Software Solutions Introduction to Solution Architecture

Architecting Software Solutions Introduction to Solution Architecture

ATA/S-ARCHSS/OM/Introduction to Solution Architecture/v2.1
© 2011-24 National University of Singapore. All Rights Reserved.
Total slides: 40

Objectives

  • Understand what architecture is
  • Differentiate between enterprise architecture and solution architecture
  • Understand the role and responsibilities of an architect
  • Understand the quality attributes of a software system

Topics

  • Introduction to Architecture
    • Definition of Architecture
    • Importance of the architectural review
    • Enterprise Architecture and Solution Architecture
    • Architect’s role and responsibilities
  • Introduction to software quality attributes
    • The ISO 25010:2011 model

Definition of Architecture

  • Architecture Defined:
    • The fundamental organization of a system embodied in its components, their relationships to each other, and to the environment, and the principles guiding its design and evolution.
    • Definition is adapted from ANSI/IEEE Standard 1471-2000 and ISO/IEC/IEEE 42010:2011, which focus on architecture description for software-intensive systems.

Influences on Architecture

  • Influences on architecture include:
    • Solution Architect
    • Stakeholders
    • Organization
    • Architect’s Experience
    • Technical Environment
    • System Architecture

Benefits of the Architecture Review

  • Benefits derived from the architecture review include:
    • a) Identifying potential risks in the proposed architecture (88%)
    • b) Assessing quality attributes (e.g., scalability, performance) (77%)
    • c) Identifying opportunities for reuse of artifacts and components (72%)
    • d) Promoting good architecture design and evaluation practices (64%)
    • e) Reducing project costs caused by undetected design problems (63%)
    • f) Capturing the rationale for important design decisions (59%)
    • g) Uncovering problems and conflicts in requirements (59%)
    • h) Conforming to organization’s quality assurance process (55%)
    • i) Assisting stakeholders in negotiating conflicting requirements (43%)
    • j) Partitioning design responsibilities (40%)
    • k) Identifying skills required to implement the proposed architecture (40%)
    • l) Improving architecture documentation quality (40%)
    • m) Facilitating clear articulation of nonfunctional requirements (31%)
    • n) Opening new communication channels among stakeholders (31%)
    • Survey Reference: The statistics are gathered from systems architecture reviews for 86 responding organizations from the study "Software Architecture Review: The State of Practice" by Muhammad Ali Babar and Ian Gorton (IEEE Computer July 2009).

Definition of Enterprise Architecture

  • Enterprise Architecture Defined:
    • The organizing logic for business processes and IT infrastructure reflecting the integration and standardization requirements of the firm’s operating model.
    • A conceptual blueprint that defines the structure and operation of an organization.
    • The intent of enterprise architecture is to determine how an organization can most effectively achieve its current and future objectives.
    • It serves as the source of strategic direction and guidance for solution architecture.

Solution Architecture

  • Solution Architecture Defined:
    • Implementing Information and Communication Technology (ICT) projects requires analysis, design, and construction; the product is