Computer Science
587 - Fall 2009
Software
Inspections Assignment
Individual Reviews
Due: Wednesday, September 30, 2009
Group Report Due:
Wednesday October 7, 2009
As a group conduct
a software inspection for the requirements document found at the following Web
location: http://mcis.jsu.edu/studio/SRSSample.doc
This
is the SRS document for a “Web Accessible Alumni Database” program.
The actual inspection will commence
during class on 9/30. Prior to that you
should accomplish the following:
1. Select
someone from your team to serve as moderator, someone to serve as the recorder,
someone to be the reader, and someone to assume the role of the producer. Since we don’t have access to the real
producer(s), the team member serving as the producer will be the one answering
questions about what the product is intended to do. The producer can formulate any reasonable product
concept in order to provide answers to questions that might have been asked of
the real producer. All team members will
additionally have roles of inspectors, i.e., to identify errors and defects in
the product being inspected
2. All
members of the team should carefully review the Software Requirements
Specification prior to the inspection meeting on 9/30 and make written note of
any defects discovered and/or questions they would like to ask the
producer. It’s OK, and even encouraged
to make your notes on a copy of the specification itself. A copy of each team member’s review must be
turned in on 9/30. Additionally, each
team member must keep track the time he or she spends preparing for the
meeting.
On 9/30, during the second half of the
regular class period, the inspection will begin. If your team does not complete the inspection
during the class time allocated, you will need to suspend the meeting and
continue it at another time and place.
However, you should not spend more than a total of two hours on the
inspection meeting. If you haven’t
reached the end of the document after two hours, just end the inspection and
write up your findings for the portion of the requirements specification
covered. Complete the applicable
portions of an “Inspection Problem Report”
form for each problem found, as well as an “Inspection Process Summary Report”
for the meeting. These forms must be
turned in on or before 10/7.