Assignment:
Overview
During the course of the semester, each student will develop a Software Requirement Specification for the requested system. The initial input to the requirements for that system will be provided in a Project Broad Statement of Needs. Students need to convert such a broad statement into more structured requirements for the system and describe them in written and graphical formats following the IEEE standard (tailored). This will inevitably involve dealing with challenges in documenting requirements for effective communication among stakeholders. Several elicitation techniques will be employed to confirm and/or discover the user requirements for the system. Where advice is needed on how to proceed, you should consult your tutor and lecturer who constitute the customers.
The Assignment is divided into two phases:
Phase 1 : 6 diagrams of SRS with high-level use cases (refer to SRS_ template.doc) and analysis models
Phase 2 : 6 diagrams of Expanded use case, activity diagram and level 2 DFD for selected use cases
Details of the document required are included in the phase specifications. These are based on the IEEE guidelines that provide an example structure for such documents. But, as it notes, this example structure is for information purposes only and is not part of the standard. This commonly occurs with standards, as it allows the standard to be tailored to different kinds of projects. The particular structure to be used in this project will be detailed in phase deliverables.
Submission
The completed documents are to be submitted online by the stated deadlines.
Phase 2 (Assignment 2) Specification:
During this phase the existing SRS Document completed in Phase 1 (Assignment 1) would normally be expanded and refined to a more detailed and refined form. However due to the limited time available, this phase focuses on more detailed analysis and specification of Section 3, resulting expanded process descriptions, data flow diagrams, and activity diagrams for the more significant use cases as well as the system level analysis models (updated Appendix B). An updated Issue list (Appendix C) will also be generate as parts of Phase 2 submission.
Deliverable:
Students will produce one document as the result of this phase. The document should include:
Title page: SRS Supplementary Submission
Should identify (name and type) the document and its author(s)
Table of Contents plus optionally list of tables and of figures
Section 3: Specific Requirements prepared by students.
For each* primary essential use-case (What the system must satisfy the requirements given), provide
Expanded use cases description, including key variations (Variations that are likely in reasonable circumstances).
Level 2 data flow diagram
Activity diagram
Each student must ensure consistency between the expanded use case, its DFD and Activity diagrams.
Appendix B Analysis Model
The students should provide an improved version of the use-case diagram for each user class defined in your requirements document.
The students should provide an improved version of level 1 data flow diagram. Student should ensure consistency between level 2 DFD for their particular functional requirement and the level 1 DFD.
Appendix C Issues List
As this is a dynamic list of the open requirements issues that remain to be resolved, it should be updated as necessary.
Work
The structure to be used is the use-case format described in lectures and is to be supplemented by a level 2 data flow diagram, and an activity diagram. It is preferable if the functional requirements described are from different user classes, but this is not essential.
Section 3:
Expanded use-cases [25%]
Level 2 Data flow diagram [25%]
Activity diagram [25%]
Appendix B: [NGP]
Appendix C: [NGP]
Presentation: [10%]
Consistency: [15%]