During the course of the semester, each project group 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. Your group needs 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 project is divided into two phases:
• Phase 1 : SRS with high-level use cases (refer to SRS_ [login to view URL]) and analysis models
• Phase 2 : 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