R. Clayton (rclayton@clayton.cs.monmouth.edu)
(no date)
You are now in implementation, the third phase of the 325 software development
process. In implementation you use the system design document as a basis for
implementing the system that solves the problem described in the requirements
spec.
Once again, each group will not be using their own document from the previous
phase:
the group gould, khera, cheng, and king will implement from the system design
provided by salmeri.
the group merrill, lee, anastasia, and brizuela will implement from the
system design provided by shi.
the group tang, salmeri, meyer, kozemchak will implement from the system
design provided by khera.
the group martemucci, shi, capuano, and rau will implement from the system
design provided by lee.
The same rules as for design are in effect: the current design manager goes
visiting; nobody is changing groups; design specs may be revised and regraded.
You do need to submit some working code, and it should bare some resemblance to
the system design. You should probably follow the same approach you took for
system design: implement the first few high-level modules (or classes) and
then pick one or two lower-level modules to expand in detail.
This archive was generated by hypermail 2.0b3 on Tue Apr 24 2001 - 13:15:04 EDT