Please enable JavaScript.

Coggle requires JavaScript to display documents.

System Modelling (Abstraction (Idealisation (Contextual model (provides…

- - - - In ER diagrams -> Entities In UML -> Classes
      - Book
  - - - Assembled into composition -> book
  - - - provides background for other models
    - - High level detail about element with no regard to implementation
    - - More complete and robust -> still no implementation
    - - Implementation -> technology, physical location. Described to a point where solution can be built
- - - - Object changes in one model -> changes in all, views filtered
        
        Multiple views of the same model
        
        Views and Viewpoints
        
        Employ framework that defines set of viewpoints -> that define views to be used
    - - ----->
  - - - Current system
        
        As-Is/BASELINE
        
        Similar standards
        
        Notation
        
        Levels of abstraction
      - Proposed system
        
        To-Be/TARGET
- - - - What type of system the boundary represents.
      - Defines Actor and nature of interaction
    - - Summary goal (Kite Level)
      - User Goal (Sea Level)
      - Sub-goal (Fish level)
      - Very High level (Cloud level)
- - - - Misunderstandings, incorrect assumptions
      - Missing model elements
        
        Structure of models makes missing elements more obvious to identify and rectify
  - - - Automation of model development increasingly possible
        
        Reverse engineer model from existing system
        
        Model Driven Architecture (MDA)
        
        Employs and evolves UML
- - - - Sequence
      - Communication
      - Timing
      - Interaction Overview
- - - - What the system does or is required to do
    - - Abstract representation of the types of data objects and their structures & semantics -> meaning and integrity
    - - Triggers the system has to react to
- - - - Conceptual, Logical, or Physical
    - - Composition abstraction
- - - - Usefulness = intangible
- - - - What-if? scenarios
    - - Reveals
        
        New elements required
        
        Existing elements that need changing replacing
        
        Existing elements no longer required
        
        Existing elements remaining unchanged -> regressively test to ensure they're not compromised