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
- Definition of the technology architecture (infrastructure)
- the set of computing hardware
- network hardware/topology
- system software employed by the organization
- Application architecture
- information system, subsystem, supporting technology
e.g. update the RMO system due to customer expectation, modern technological capability, etc.
[What we have]
- Supply Chain Management System (SCM)
(5 years old, Java/Oracle, tradeshow system will interface with SCM)
- Phone/Mail Order System
(12 years old, Visual Studio/MS SQL, reached capacity, minimal integration)
- Retail Store System
(order package solution, minimal integration)
- Customer Support System (CSS)
(web-based system, etc)
- Information Diagram
2.Analysis, understand the details of the problem
- Gather detailed information (interviews, questionnaires, etc.)
- Define system requirements: modeling functional/non-functional requirements.
- Prioritize requirements.
- Develop user-interface dialogs.
- Evaluate requirements with users.
Define system requirements (FURPS+)
- Functional requirements: APIs that should be implemented in the system.
- Non-functional requirements:
- Usability requirements: how easy it is to use the system (UI). (Need to consider whether the user can be trained.)
- Reliability requirements: reliable for the day and night? or just day?
- Performance requirements: response time, etc.
- Secure requirements: encryption, etc.
- + more other categories.
Models and Modeling
- After collecting information, create models which can be:
- Textual models
- Graphical models - diagram, schematic
- use case diagram
- class diagram
- sequence diagram
- common diagram
- state machine diagram
- Mathematical models
No comments:
Post a Comment