UC IRVINE - ICS 125 PROJECT IN SYSTEM DESIGNAssignment 4: Design |
The design document should also be an evolving document, or a living document. You should begin by documenting the conceptual model of your system. As you continue working, this model will be refined to include more detail, and some things will change. By the time you turn in your design document, it should contain a reasonably accurate description of your final system. You will also be asked to turn in a final version of the document at the end of the quarter that will include changes made to the requirements and design during the later stages of implementation.
The design document will consist of the following sections. Sections 1-4 and 8-13 are updates of what you turned in for the Requirements Document. The remaining sections, 5-7 and 14, are new to the Design Document.
Shaw and Garlan (in Software architecture: perspectives on an emerging discipline) have identified the following list of architectural styles:
1.Data Flow Style
Batch Sequential
Pipes and Filters
2.Call and Return Style
Main Program and Subroutines
Hierarchical layers
Object-oriented (client/server)
3.Independent Components
Communicating processes
Event systems
4.Virtual Machines
Rule-based systems
Interpreters
5.Data-Centered Systems
Transactional Database Systems
Blackboard Systems
Others find that UML provides a sufficient architecture
specification, but requires more than class diagrams.
This is the place for your "one great diagram" that shows how your
system is built. You might want to use more than one diagram, to show,
e.g., some different abstractions of the design (such as a data flow view,
a layers of abstraction view, an object view, or an OS process view)