Please enable JavaScript.

Coggle requires JavaScript to display documents.

Architecture Description, Frameworks, View / Model, Hierarchy, Why?…

- - - - Contains
        
        Entities
        
        can appear in several artifacts
        
        discrete architectural element
        
        object reusable in artifacts
        
        definable using standard template
        
        EntityTypes
        
        Precursors
        
        stakeholder, business goal/objective, principle, standard
        
        Business
        
        business function, business process, org. unit, role, actor, service, location, time period
        
        Data
        
        Data entity, data event, data flow, data quality, data source, data store
        
        Applications
        
        Application, Use Case, automated service, data flow, component
        
        Infrastructure
        
        Computer, network, technology
      - can appear in several deliverables
      - A list, hierarchy, table, diagram, or model that names and relates entitites
        
        Artifact Types
        
        Precursors
        
        Goal or requirement traceability
        
        Process map
        
        Context diagram
        
        Goal or requirement hierarchy
        
        Business
        
        Business function structure
        
        Business process model
        
        Org. structure
        
        Location structure
        
        Business data model
        
        Business function dependancy matrix
        
        Data
        
        Data model
        
        Data lifecycle
        
        Data structure
        
        Business function CRUD matrix
        
        Application data CRUD matrix
        
        Data dissemination matrix
        
        Applications
        
        Application portfolio
        
        IS context diagram
        
        Busines-applications matrix
        
        Applications architecture diagram
        
        Application decomposition diagram
        
        Software layering diagram
- - - - comprises components, servies, reference models, and other items architext may want to reuse
      - categorised under Zachman framework and Enterprise Continuum
- - - - gap analysis
      - impact analysis
      - requirements traceability
      - cluster/affinity analysis
    - - Org unit to business function
      - Data entity or store to business function
      - data entity to data store
      - data entity or store to data quality
      - Application to platform technology
- - - - How? (function)
        
        What? (data)
- - - - focuses on description of an architecture as concrete artifact representing the abstraction that is software or system architecture
  - - - Stakeholders
        
        Security architect, technology architect, network manager
      - Concerns
        
        Systems must be protected from external threat
      - Model
        
        Infrastructure diagram showing firewalls
      - Regulator, contains rules, conventions, model kinds - control what the view should portray