SE 2730 Intro. to Software Engineering Project
Phase 3: Review Requirement Specification
Due: Friday, Feb. 26
Review the requirements another team wrote for Phase 2. Refer to Note 3 for SMART requirements.
 Organize your review team. Contact the author team and make sure one representative is in your review
meeting.
 Use the following checklist to check for potential issues. Once you identify issues, discuss how they can
be improved together with the author team representative.
 Not every issue needs to be identified, but it would be surprising if more than half of the table was
blank. For one issue, that might be several violations.
 Note you can certainly add further checklist items as you identify them.
The outcome of this phase should be a requirements review document organized as following:
Section 1: Team Reviewed
Section 2: Review team organization
Review Team Number
Review Leader
Author
Recorder
Reviewers
Section 3: Review Checklist
Violations
Requirements with
Issue
Improvement Suggestion
Comments
Correct
Complete
Concise
Precise
Unambiguous
Consistent
Measurable
Attainable
Realistic
Traceable
Timely
Details
1. I will put another group’s initial requirement under your reqs folder in the repository.
2. Submit the file in the repository as
reqs\GroupXRequirementReview.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.
3. Submit the phase report in the repository as
reports\GroupXPhase3Report.docx
4. Copy and paste the grading rubric below at the very beginning of the phase report.
5. List requirements using the appropriate labels as mentioned above. DO NOT use auto-numbering feature
in Words.
6. As always, be sure to use grammar and spell checks.
SE 2730 Intro. to Software Engineering Project
Grading Rubric for Phase 3:
Item
Issues identified
Improvement suggestion
Group work: time logging,
meetings
Total
Possible
Points
4
4
2
10
Comments
Score