Reference no: EM132368259 , Length: word count:3000
Assignment Specification
Any changes to due dates or other information relating to the project (or tutorial) will be advised via the topic FLO.
Project Overview
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 aProject 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_ template.doc) and analysis models
• Phase 2 : Expanded use case, andlevel 2 DFDfor 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.
Phase 1 Specification:
This document details the format and guidelines for phase 1, also known as Assignment 1,of the project.
Phase 1 has the following aims:
• To provide a forum for your group to practise its communication skills in promoting and sharing of ideas, formulating a group response, and submitting a completed group document;
• To enable thinking about what constitutes a software system and how to describe system requirements both as a user and as a developer;
• To investigate the use of several elicitation techniques to confirm and/or discover the user requirements for the system;
• To convert a broad statement of needs into a more structured requirements for the system;
• To document the formulated requirements in a structured format;
• To show main product features with a system context diagram (use case diagram and level 1 data flow diagram);
• To identify user classes (actors), and associated high level use cases;
• To appreciate the challenges in documenting requirements so that they can be effectively communicated to others.
Tasks
To produce the required document, the group must initially agree on what will be the standard document format, file naming conventions etc. Much of this should be resolved in the first group meeting.
Each member of the group is expected to take multiple of the following roles during this phase of the project work:
• collator - to put the various parts of the document together, including revised versions of parts. The document should be uniform in its presentation e.g. font and page layout.
• publisher - to put the final document together, to check the overall look and finish of the document.
• drafter - to draft the initial version of each part, to make any necessary modifications to it, and to do the initial proof reading (Reading out loud is always a good check.)
• proof reader - to check the syntax and content of parts, to provide editorial comments. All group members could make comments but this role involves a commitment to make comments and/or corrections.
Attachment:- Project Overview.rar