Saturday, August 13, 2016

Object Oriented Design - Lecture 2: Strategic Planning and Related Design

This post is the note of lecture 2 of the course "Object Oriented System Analysis and Design". Videos can be viewed at https://www.youtube.com/watch?v=ODeQ0rF59kI&index=3&list=PL6XklZATqYx9dj72MKG6wLYjljeB2odra.

Lecture 2

1. Planning method - strategic planning

  1. Definition of the technology architecture (infrastructure)
    1. the set of computing hardware
    2. network hardware/topology
    3. system software employed by the organization
  2. Application architecture
    1. information system, subsystem, supporting technology
      e.g. update the RMO system due to customer expectation, modern technological capability, etc.
      [What we have]
      1. Supply Chain Management System (SCM)
        (5 years old, Java/Oracle, tradeshow system will interface with SCM)
      2. Phone/Mail Order System
        (12 years old, Visual Studio/MS SQL, reached capacity, minimal integration)
      3. Retail Store System
        (order package solution, minimal integration)
      4. Customer Support System (CSS)
        (web-based system, etc)
    2. Information Diagram

2.Analysis, understand the details of the problem


  1. Gather detailed information (interviews, questionnaires, etc.)
  2. Define system requirements: modeling functional/non-functional requirements.
  3. Prioritize requirements.
  4. Develop user-interface dialogs.
  5. Evaluate requirements with users.

 Define system requirements (FURPS+)

  1. Functional requirements: APIs that should be implemented in the system.
  2. Non-functional requirements:
    1. Usability requirements: how easy it is to use the system (UI). (Need to consider whether the user can be trained.)
    2. Reliability requirements: reliable for the day and night? or just day?
    3. Performance requirements: response time, etc.
    4. Secure requirements: encryption, etc.
    5. + more other categories.

 Models and Modeling

  1. After collecting information, create models which can be:
    1. Textual models
    2. Graphical models -  diagram, schematic
      1. use case diagram
      2. class diagram
      3. sequence diagram
      4. common diagram
      5. state machine diagram
    3. Mathematical models

No comments:

Post a Comment