R. Clayton (rclayton@clayton.cs.monmouth.edu)
(no date)
You are now in system design, the second phase of the 325 software development
process. In system design you use the requirements spec as a basis for
designing a system to solve the problem described in the requirements spec.
Note well that you are designing the system, not implementing it.
To make things interesting, and to help you appreciate the importance and
difficulty of creating good requirements specs, each group will not be
designing from their own requirements spec, but from the requirements spec from
another group. In particular,
the group gould, khera, cheng, king, and aw will design from the
requirements specification provided by martemucci.
the group merrill, lee, anastasia, and brizuela will design from the
requirements specification provided by gould.
the group tang, salmeri, meyer, kozemchak will design from the
requirements specification provided by merrill.
the group martemucci, shi, capuano, and rau will design from the
requirements specification provided by tang.
That is, the requirements-specification manager is visiting another group.
These assignments assume the personnel for the requirements-specification
manager haven't changed from the original group assignments. If the personnel
has changed, then whoever is the current requirements-specification manager
will do the visiting.
Nobody is changing groups; the groups are the same as they were for
requirements specification. Now, and for the rest of the semester, one member
of each group will be selected to visit another group and act as the
stakeholder for each phase.
You should not wait to get your graded requirements specs back from me; use the
version of the requirements spec you handed in. Each group can modify their
requirements spec and resubmit it along with their design document to have
their requirements spec regraded.
Resubmitting your requirements spec is optional - if you're happy with your
grade on the requirements spec, you needn't do a thing (you still, however,
have to be responsive to the comments of the group designing from your
requirements spec).
Keep in mind that 30% of your grade on each document (or whatever) is
continuity with the document (or whatever) that proceeded it. That means, in
this case, that most features in your design document should be traceable back
to some feature in the requirements spec from which the design document came.
Also, every feature of the requirements spec should appear somewhere in the
design document.
This archive was generated by hypermail 2.0b3 on Tue Apr 24 2001 - 13:15:04 EDT