Recent Question/Assignment

Any changes to due dates or other information relating to the project (or tutorial) will be advised via the topic FLO. I acknowledge the contribution of all previous lecturers in this topic to the project structure.
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 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_ template.doc) and analysis models
• Phase 2 : Expanded use case 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.
PHASE 2 (ASSIGNMENT 2) SPECIFICATION
During this phase the existing SRS Document completed in Phase 1 (Assignment 1) would normally be expanded 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 and data flow 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
Each group/individual 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 individual group members.
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
Each student must ensure consistency between the expanded use case and its DFD (as well as the analysis models presented in Appendix B).
• Appendix B Analysis Model
­ The group should provide an improved version of the use-case diagram for each user class defined in your requirements document.
­ The group should provide an improved version of level 1 data flow diagram. Each group member 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.
INDIVIDUAL WORK
Each group member is to complete a detailed description of 2 use cases, supplemented by a level 2 data flow diagram. At least one of these is to be a substantial or significant requirement. The structure to be used is the use-case format described in lectures. It is preferable if the functional requirements described are from different user classes, but this is not essential.
Clearly there needs to be consistency between individual’s work submitted in the group document (if done by a group). The authorship for each use case needs to be clearly identified to facilitate marking.
ASSESSMENT
Phase 2 submission will be marked for each individual student. Each student will receive a grade, not a mark, for this submission. The weighting distribution across the submitted components is outlined as follows:
Section 3:
­ Expanded use-cases [40%]
­ Level 2 Data flow diagram [30%]
Appendix B: [NGP]
Appendix C: [NGP]
Presentation: [15%]
Consistency: [15%]
NGP indicates that the section needs to exist in a proper form but does not contribute towards the marks.
SUBMISSION
The completed documents are to be submitted on FLO by Friday end of week 12.
Professor John F. Roddick
March 19, 2020