Please enable JavaScript.

Coggle requires JavaScript to display documents.

System Design, implementation, evaluation, deployment and maintenance…

- - - - Identifies what the modules are
      - How the modules should be
      - How the modules interact with each other
      - Avoids complexity
  - - - Architectural design
        
        UI Design
        
        Component Design
        
        Data Structure
        
        Algorithm Design
        
        Design algorithms for the functions
        
        Design the data storage
        
        Decompose subsystems into components
        
        Design Sub System interfaces
        
        Identify sub systems and their relationships
  - - - Bottom up and top down
        
        Functional Decomposition is the process of taking a complex process and breaking it down into its smaller, simpler parts.
        
        It takes more upfront thinking before coding can begin.
    - - Structured Analysis (SA) results in logical design, drawn as a set of data flow diagrams
      - Structured Design (SD) - transforms the logical design into a program structure drawn as a set of structure charts
    - - Identify Objects
      - Describe object properties and behaviours (attributes and methods)
      - Define their relationships
  - - - Avoid functionality overlap, divide the application into distinct features, minimise interaction points
    - - Each component/module should have a single responsibility (Cohesion)
      - Each method should do one job
      - Helps in component integration
    - - Implement once use everywhere
      - Do not duplicate code/functionality
      - Improves maintainability
    - - Assume requirements will change, so avoid designing the whole system completely
    - - an object should assume as little as possible about other objects
      - A component or object should not know about internal details of other components or objects
      - Avoids interdependency
    - - Inheritance creates dependancy
    - - Understand how the components will communicate with each other. Message Bus, RESTful etc.
    - - Define exceptions beforehand
      - Fail graecefully
      - User friendly error reporting
    - - Do not mix service logic (e.g. code related to membership, security. configuration etc) with business logic
  - - - Look at the problem from different angles to understand the problem
      - Evaluate possible solutions
        
        chose the most appropriate based on skills and resources
      - Model the solution
      - Repeat the process