Please enable JavaScript.

Coggle requires JavaScript to display documents.

SEI_SA _1, The important SA decision, How existed arhitecture influence,…

- - - - properties (not only API but some QA, but public sides) it is API +QA
      - set of structures (no "single page arhitecture", even "Hello world" - it is file, source code, need hardware, its performance, etc) There should be set of views.
      - abstraction (internal details is not architecture)
      - Every system has an Arhitecture
      - Box and lines are not arhitecture. It is just init point
      - Good architecture - meets goals
- - - - Referance Arhitecture
        
        Software Architecture
- - - - Create Systems using large independent components
      - Architecture enables templatte-based development
      - Create models, that is transferable across the system
- - - - PM, DM
      - SA
      - customer
      - marketers
      - Mainters
      - Stakeholders have a different concerns
      - Developers
      - Users of the System
    - - lifetime
      - ....
      - functionality
      - cost
    - - security
      - restore and backups
      - configuration
    - - From DEV organisation
      - From Customer organisation
        
        Strategic goals