SE 2730 Intro. to Software Engineering Project
Phase 2: Initial Requirement Specification
Due: Friday, Feb. 19
Write an initial version of the requirements for your system. The focus for this version is on completeness and
presentation; you will not lose points for issues such as precision or testability.
 Divide your requirements into at least three categories:
o rules for game play,
o input/output requirements,
o general requirements (including anything not in the other categories).
 Be sure to write a lot of requirements. You can’t just go by numbers because it depends on how much
information there is in each requirement, but you should think in terms of at least 30 to 40 requirements.
 Make sure your label your requirements consistently. You should use multi-level labeling such as R-FR1, IO-FR-1, G-FR-1…, R-NR-1, IO-NR-1, G-NR-1… where R means “rule”, IO means “input/output”,
G means “general”, FR means “functional” and NR means “non-functional”.
Details
1. Submit the file in the repository as
reqs\GroupXInitialRequirements.docx
Where X is your group number. Note there are no spaces in this name, and again pay attention to capital
vs. lower case letters.
2. Submit the phase report in the repository as
reports\GroupXPhase2Report.docx
3. Put the document name and the names of the group members at the top of the file.
4. Give a name for the system and put that below the member names.
5. Copy and paste the grading rubric below at the very beginning of the document.
6. List requirements using the appropriate labels as mentioned above. DO NOT use auto-numbering feature
in Words.
7. As always, be sure to use grammar and spell checks.
Grading Rubric for Phase 2:
Item
Requirements for game rules
Input/output requirements
Other requirements
Requirements naming, using
‘shall’, professional tone
Style, grammar, spelling
Group work: time logging,
meetings
Total
Possible
Points
3
3
3
2
2
2
15
Comments
Score