HI5030 Systems Analysis and Design Group Assignment
Group Assessment
Cover Page
| Unit Details | Name | Systems Analysis and Design |
| Code | HI5030 | |
| Year, Trimester | 2023, Trimester 1 |
| Assessment Details | Name | Group Assignment |
| Due Date and Week | 07 / 05 / 2023, Week 7 04 / 06 / 2023, Week 11 |
| Group Student Details | Student ID | First Name | Family Name | Work Contribution |
| Group Submission Declaration | Integrity Declaration | Student ID | Full Name | Submission Date |
| We have read and understand academic integrity policies and practices and our assessment does not violate these. | ||||
Instructions
| Academic Integrity Information | Holmes Institute is committed to ensuring and upholding academic integrity. All assessment must comply with academic integrity guidelines. Important academic integrity breaches include plagiarism, collusion, copying, impersonation, contract cheating, data fabrication and falsification. Please learn about academic integrity and consult your teachers with any questions. Violating academic integrity is serious and punishable by penalties that range from deduction of marks, failure of the assessment task or unit involved, suspension of course enrolment, or cancellation of course enrolment. |
| Format Instructions | Most assessments must be in MS Word format with no spacing, 11-pt Calibri font and at least 2cm margins on all four sides with appropriate section headings and page numbers. You must name your file with the Unit Code and Group Number (e.g. “HI5004 Group 4”). Check that you submit the correct document as special consideration is not granted if you make a mistake. Student IDs need to be indicated on the cover page. Non-contributing students do not receive marks. |
| Penalties | All work must be submitted on Blackboard by the due date and time along with a completed Assessment Cover Page. Late penalties apply. Reference sources must be cited in the text of the report, and listed appropriately at the end in a reference list using Holmes Institute Adapted Harvard Referencing. Penalties are associated with incorrect citation and referencing. |
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
- 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:
- Local real estate agency system
- Internet shopping sites (clothing, shoes, books, music, or others)
- Warehouse management system
- Insurance purchase system (life, medical, homeowner, or others)
- Library circulation system
- Bank home loan management system
- Stockbroker trading system
- Airline booking management system
- Hospital system
- 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)
- Problem definition
- Issues
- Objectives
- Requirements
- Constraints
- Description of the proposed system
- Logical model design
- Data flow diagrams
Context diagram/Diagram 0/Diagram 1 [Diagram 1 is optional]
Descriptions of processes in each diagram
- Descriptions of outputs/inputs/performance/security or controls
- Specific requirements, if any (interface, operational, resource, performance, etc.)
Phase 2: System and database design (Physical model design) (Due Date – Week 11)
- User interface
Design an overall user interface consisting of screens, commands, controls, and features to enable users to use the system.
- How data will be input to the system?
- The physical layout for each input
- The input design and procedures
- How data will be output from the system?
- The physical layout for each output
- The output design and procedures
B. Object Oriented Modelling
- Class diagram
- Activity diagrams
- Sequence diagrams
- State chart diagram
C. Data design
Develop a physical plan for data organization, storage, updating, and retrieval.
- Database design
- Database tables with their attributes should be presented (however their implementations are not required)
- Primary key(s) should be identified in each table, if any
- Three steps of normalization should be included.
- Entity-relationship diagrams
- 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.