Please enable JavaScript.

Coggle requires JavaScript to display documents.

Software architecture - Coggle Diagram

- - - - Control flow is implicit
      - Limits
        
        Implementation requires external control
        
        Does no provide interactive interface
        
        Concurrency is not supported and hence throughput remains low
        
        High latency
      - Applicable domain
        
        Data are batched
        
        Each sub-system reads related input files and writes output files
      - Benefits
        
        Each sub-system can be a stand-alone program working on input data and producing
        output data
        
        Simple divisions on sub-systems
    - - Control flow is explicit
      - Applicable Design Domain
        
        Whenever the system can be broken into a series of
        processing steps over data streams
        
        Whenever the data format on the data streams is
        simple and stable
        and easy to be adapted if it is necessary.
      - Benefits
        
        Concurrency
        
        Reusability
        
        Modifiability
        
        Simplicity
        
        Flexibility
      - Limits
        
        Not suitable for dynamic interactions
        
        Low Common Denominator
        
        Difficult to configure a P&F system dynamically
    - - Mostly for embedded systems
  - - - Applicable domain:
        
        Suit for large complex information system
      - Benefits:
        
        Easy to backup & restore
        
        Scalability and reusability of agents (components): easy to add new components
        
        Reduce overhead of transient data between components
      - Limitations:
        
        Data store reliability and availability is very important
        
        High dependency between data store and its agents (components)
        
        Overhead cost of moving data on network on distributed system
      - Control flow: Clients control the logic flow
        
        Data store is passive
        
        Clients are active
    - - Control flow: The flow of logic determined by the current data status
        
        Data store is active
        
        Clients are passive
      - Applicable domain
        
        Suitable for solving open-ended and complex problems (AI)
        
        Exhaustive searching is impossible and impractical
      - Benefits:
        
        Scalability: easy to add new knowledge source
        
        Concurrency: all knowledge sources can work in parallel
        
        Reusability of knowledge source
        
        support experimentation for hypotheses
      - Limitations:
        
        Tight dependency between the blackboard and knowledge source
        
        Difficult to make a decision
        
        Synchronization of multiple agents is an issues
        
        Debugging and testing is a challenge
  - - - 3 partitions:
        Message producers
        Message consumers
        Message service providers
    - - 2 partitions:
        Event sources
        Event listeners
      - Applicable domain
        
        Interactive GUI component communication
        
        Integrated Development Environment (IDE) tools
        
        Applications that require loose coupling between
        components
        
        Implementation of state machine
        
        When event handlings in the application are not
        predictable.
      - Benefits
        
        Framework availability
        
        Reusability component
        
        System maintenance and evolution
        
        Independency and flexible connectivity
        
        Possibility of parallel execution of event handlings
      - Limits
        
        Difficult to test and debug the system
        
        The event trigger cannot determine
        
        Tight coupling between event sources and their listeners
        
        Reliability and overhead of indirect invocations may be an issue
- - - - Elements: perform functions required by system
      - Connectors: enable communication among elements
      - Constraints: define how elements can be integrated
      - Attributes: advantages & disadvantages of structure
  - - - Reliability: Continue to keep operating over time not causing exception
      - Portability: Run on numerous platforms
      - Usability: How the user use system effectively and the ease of learn
      - Security: resist or block malicious or unauthorized attempts that affect the system
      - Testability: How well to perform tests
      - Maintainability: Easy to maintain and support changes cost-effectively
      - Availability: Raito of available system time to total working time
      - Flexibility: Ability of a system to adapt to future changes
      - Interoperability: Communicate or exchange data with other systems
      - Scalability: Handle demand for stress caused by increased usage without decreasing perfomance
      - Performance: response to actions within a period of time
- - - - Structural (Static): Show the hierarchy or structure of components or module of the system and show how they interact
        
        Class diagram
        
        Show a set of classes, interfaces and their relationship
        
        Object diagram
        
        Show set of objects and relationships which is the static instances
        
        Package diagram
        
        Represented by a tabbed folder such as namespace in .NET and packages in Java
        
        Composite Structure diagram
        
        Show internal structure of a classifier and interaction with environment
        
        Component
        
        Show a set of components and relationship that illustrates the static implementation view of system
        
        Deployment
        
        Describe the physical configuration of system
      - Behavioral (Dynamic): show the dynamic behavior of the objects in system
        
        Use case diagram
        
        An overview of use cases, actors and their communication with system
        
        Activity
        
        Representations of workflows of stepwise activities and actions
        
        State Machine
        
        Event-oriented diagram used for behavior of a part of a designed system through finite state transitions
        
        Sequence
        
        Time-oriented interaction diagram used for showing the chronological sequence of messages between objects
        
        Interaction Overview diagram
        
        Describes the control flow of the interaction
        
        Communication
        
        Message-oriented diagram summarizes how objects in the system receive and send messages. Equivalent to sequence diagram
        
        Timing diagram
        
        Is new in UML 2.0 combining the state diagram and time sequences to show the dynamic view of state change caused by external event over time
  - - - logical view: objects and their interactions
        
        Support by Interaction diagram, Sequence diagram, Communication diagram, State machine diagram & Activity diagram
      - process view: system activities, their concurrency and synchronization
        
        Support by Activity diagram
      - physical view: mapping of software into hardware, server and network
        
        Support by Deployment diagram
      - development view: software static structure within given development environment
        
        Support by Component diagram
      - scenario view: real world scenario
- - - - Static polymorphism: implement multiple method with the same name but different params which called method overloading
      - Dynamic polymorphism: A subclass can override a method which called method overriding