Software Engineering Assignment
Purpose of the assessment - This assignment assesses the below Unit Learning Outcomes; students should be able to demonstrate their achievements in them:
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 Document and MS Access Prototype for your chosen project.
Projects Selection:
Student 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:
- Education
- Shopping
- Library
- Airline
- Financial
- Entertainment
Task - Once student 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.
Students have to submit:
1. The SRS Document (Templates are available on MOODLE):
a) Project introduction
b) Project Goals, objectives, stakeholders etc.
c) Functional and non-functional requirements
d) Technical assumptions and constraints
e) An appropriate diagrams e.g. storyboards, mock-ups etc.
Students should also pursue the following steps to complete SRS Document:
a) Required diagrams e.g. Use Case Diagrams, Context Diagram, ERD, DFD-L0 etc. (First Version)
b) Proper References.
c) Well written, properly formatted, correct grammar, no spelling mistakes etc. document.
d) Length of the document between six to eight A4 pages.
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.