Reference no: EM132195886
Purpose of the assessment
- Define System requirement through requirement elicitation and workshops
- Explain the process for, and execute, verification and validation of system requirements
- Apply use case, data and process modelling techniques to specify system requirements
The purpose of this assignment is to produce and submit a consolidated FIRST VERSION of the Software Requirement Specification (SRS) Document and MS Access Prototype for your chosen project.
Form a team of exactly 5 people and write a Software Requirements Specification, based on a selected project.
Projects Selection:
Students can choose/select any website/application/system/software with enabled database component as a reference for their project from the following domains (industries) to investigate, analyse, and prototype:
- Bookings
- Library
- Rentals
- Education
- Entertainment
- Shopping
- Real Estate
- Financial
- ATM
Task:
Once students select their project, they need to do in-depth analysis for the project to complete Software Requirement Specification document and then develop MS Access prototype that relate to their selected project. Students need approval from lecture/tutor for their selected project.
Guidelines:
Follow the IEEE 830-1998 Recommended Practice for Software Requirements Specifications as your guide. Entire document reading is recommended before starting your project.
Format:
SRS document should follow the template of the IEEE standard.
Assignment SRS document should include the following:
1. The SRS Document Version 1.0 (Templates and guideline are available on MOODLE):
a) Introduction
b) Purpose
c) Scope
d) Glossary
e) References
f) Document Overview
g) Product Description
h) Functional and non-functional requirements
i) Technical assumptions and constraints
j) Context Diagram, Use Case Diagram, Entity Relationship Diagram (First Version)
2. The Access prototype should include (Reference, week 01 LAB DB File and available on MOODLE):
a) The prototype will have a splash page at the start.
b) All the tables and attributes properly documented and structured.
c) Enough functionality to see the prototype working.
d) The corresponding reading and writing forms for the tables.
3. An up to date copy of the Project Activity Journal where you show the weekly working of the group.
Attachment:- Assignment.rar