Purpose
The purpose of the group system analysis and design project is to demonstrate students’ ability to apply the knowledge learned in this course to a real-world project.
Topics Suggestions
1. The system analysis and design project must be realistic and it will be done using techniques covered in this course. The list of topics suggested for this project is as follows:
1) Internet shopping sites (clothing, shoes, books, music, or others)
2) Local real estate agency system
3) Warehouse management system
4) Insurance purchase system (life, medical, homeowner, or others)
5) Library circulation system
6) Bank home loan management system
7) Stockbroker trading system
8) Airline booking management system
9) Hospital system
10) System for a toll road operator
2. The above list is meant to be suggestive and if you have an idea about a specific topic, please consult with me early to determine if it is suitable for the course.
Project Deliverables
The project requires students to perform two phases: (a) requirements analysis, (b) system and database design.
Title page (project name, author, and date)
Phase 1: Requirement analysis (Due Date – Week 7)
A. Problem definition
B. Issues
C. Objectives
D. Requirements
E. Constraints
F. Description of the proposed system
G. Logical model design
1. Data flow diagrams
Context diagram/Diagram 0/Diagram 1
[Diagram 1 is optional]
Descriptions of processes in each diagram
2. Descriptions of outputs/inputs/performance/security or controls
H. Specific requirements, if any (interface, operational, resource, performance, etc.)
Phase 2: System and database design (Physical model design) (Due Date – Week 11)
A. User interface
Design an overall user interface consisting of screens, commands, controls, and features to enable users to use the system.
1. How data will be input to the system?
a. The physical layout for each input
b. The input design and procedures
2. How data will be output from the system?
a. The physical layout for each output
b. The output design and procedures
B. Object Oriented Modelling
1. Class diagram
2. Activity diagrams
3. Sequence diagrams
4. State chart diagram
C. Data design
Develop a physical plan for data organization, storage, updating, and retrieval.
1. Database design
a. Database tables with their attributes should be presented (however their implementations are not required)
b. Primary key(s) should be identified in each table, if any
c. Three steps of normalization should be included.
2. Entity-relationship diagrams
3. Data file storage and access
D. System architecture
Determine the architecture of the system as Web-based interface, client/server architecture, Internet/Intranet interface, network configuration, etc.
