Please enable JavaScript.

Coggle requires JavaScript to display documents.

Software Architecture In Practice, 4th Edition Chapters 1,2 - Coggle…

- - - - Or the product of a small, cohesive and well
        communicated team of architects.
    - - To avoid the full implementation and
        integration of the system.
      - Achieved through the creation of
        a "skeletal" system.
        
        Communication paths are used,
        but functionality is minimal.
  - - - Each module should have a well-defined interface,
        through which it communicates with other components.
- - - - Connecting structures to each other
        
        Each structure gives a different
        view of the system.
        
        Structures are not independent of each other
        in spite that they give different perspectives
        of the systetm.
        
        The relations between these structures are vital for the reasoning about the systems key quality attributes.
      - Component and
        Connector Structures
        C&C
        
        Examples of
        
        C&C structures
        
        Interaction of elements
        with each other at runtime.
        
        Components: Can be units of computation,
        services, peers, clients, servers, filters, etc.
        
        Connectors: Communication vehicles.
        Pipes, process synchronization operators,
        call-return,etc.
      - Module Structures
        
        Examples of
        
        module structures
      - Allocation Structures
        
        Examples of Allocation
        structures
        
        They map the relationships between software
        to the system's non-software structures.
        
        Non-software structures.
- - - - And as an abstraction
        the levels of abstraction of the
        different structures should be consistent.
      - Leaves out specific details and extends others.