FALL 2000
MODEL DRAFT DUE: (in class, three copies): Nov. 9 & 10
FINAL REPORT DUE: (in class, one copy): Dec. 4 & 5
PRESENTATIONS: (in class) Nov. 30, Dec. 1,4,5,7,8
Your team is to take the project for which you are writing a requirements summary through the next phase: architecting the software and developing an implementation strategy. You will write a report and present of your work orally.
There are three parts to this effort:
The system decomposition & object model is to first identify the major subsystems of the new system. This hierarchy may be one to several layers deep. Subsystems will be composed of functionally related sub-subsystems or objects. You are to specify interfaces, which these components offer. Sequence diagrams and/or state transition or activity diagrams should capture the behavior of active subsystems and objects. A narrative must accompany each model diagram including a description of each of the diagram's components in dictionary form and indicating relationships to other components of other models. The correspondences between events, actions, activities and processes and subsystem/object operations must be made explicit in the narrative. (Use cases may be used to explain the system decomposition & object model.)
The user interface prototype should consist of screen/window images created with software. There must be a narrative describing the role of each principal interface component and pointing out its role in a use cases or scenarios. It must be complete, not omitting user interface features required by any system feature.
The implementation strategy should give an overall strategy for implementation and go on to cover the likely mode of implementation of each system feature and operation. This should include algorithm and data structure candidates for attributes and operations. Further, a task breakdown and proposed schedule should be included. Donıt overlook quality assurance documentation, delivery, and customer install and training.
The requirements summary should be made an appendix to your report.
As always, the report must have title page, table of contents, and introduction (describing the nature & purpose of the report, its audiences & their uses of it, as well as a summary overview of the reportıs contents).
Remember: Write the report and presentation for the members of your firm's management and also of your firmıs software development division. Make the nature, purpose and uses of your work clear up front.
Edwin H. Rogers (rogere@rpi.edu) ================>
BACK to D&D Home