Project Selection: The first step will be to select a project as the target for
Project Selection: The first step will be to select a project as the target for your requirements specification. This project will be used as the basis for each of the assignments throughout the course and should conform to the following guidelines:
<
<
Nontrivial: The selected project should be large enough to allow reasonable exercise of requirements-engineering processes.
<
Domain knowledge: You should be familiar enough with the organization or software category to allow focus on the requirements-engineering tasks without significant time required for domain education.
<
Accessibility: You should have access to the people and other information that is related to the organization or software because this will be an important part of the requirements-engineering process.
<
Select a software project that fits these requirements, and submit your proposal to your instructor before proceeding further with the assignments in the course. Approval should be sought within the first several days of the course. Your instructor will tell you how to submit this proposal and what notification will be given for project approval.
<
<
This week, you will submit your project proposal and have it approved. In addition, you will create the document shell for the final project deliverable that you will be working on each week. As you proceed through each project phase, you will add content to each section of the final document. Each week, you will work on the final section, Requirements Specification, to gradually complete this section for the final project deliverable.
<
<
Assignment Details:
<
<
Project proposal submitted to instructor for approval
<
Software Requirements Specification Document shell
<
Use Word
<
Title Page
<
This should include the course name and number, project name, student’s name, and date.
<
Table of Contents (TOC)
<
Use the autogenerated TOC
<
Provide the TOC on a separate page. Update it at each phase.
<
Section headings (Create each heading on a new page with TBD as content except for sections listed under “New content” below.)
<
Project Outline
<
Requirements Elicitation
<
Requirements Analysis
<
Requirements and Software Quality
<
Requirements Validation and Verification
<
Requirements Specification
<
New content (needs to be completed for Week 1)
<
Project Outline
<
Include a brief description of the project.
<
Include the project’s goals.
<
Material can be taken from the approved proposal submitted to the instructor.
<
Ensure that this project is approved by the instructor.
<
Requirements Specification
<
Begin working on this section of the document.
<
Identify 2–3 high-level requirements of the system, and provide a brief description of each one.
<
This section will be considered a draft and will be modified in each of phase of the course.
<
Format the document according to APA guidelines
