Design Document
Authors
Title of Project
Due Date of Deliverable
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Guidelines and tips
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
System Design Document: Project Title, Study Guides, Projects, Research of Software Engineering
The design of a system, including its architecture, data stores, software control, and graphical user interface. The system architecture is described in detail, including the topology and architectural framework. Data stores are identified, and software control implementation is discussed. The graphical user interface design is presented, along with class descriptions for class name 1, class name 2, and class name 3, including their attributes, associations, dynamic behavior, and operations.
Typology: Study Guides, Projects, Research
Pre 2010
1 / 5
This page cannot be seen from the preview
Don't miss anything!
Related documents
Partial preview of the text
Download System Design Document: Project Title and more Study Guides, Projects, Research Software Engineering in PDF only on Docsity!
Design Document
Authors
Title of Project
Due Date of Deliverable
Contents
Contents
1. Introduction
2. System Architecture
o 2.1 Topology
o 2.2 Data Stores
o 2.3 Software Control
3. GUI Description
4. Class Name 1
o 4.1 Attributes
o 4.2 Associations
o 4.3 Dynamic Behavior
o 4.4 Operations
5. Class Name 2
o 5.1 Attributes
o 5.2 Associations
o 5.3 Dynamic Behavior
o 5.4 Operations
6. Class Name 3
o 6.1 Attributes
o 6.2 Associations
o 6.3 Dynamic Behavior
o 6.4 Operations
7. References
o 7.1 Existing Software Documentation
o 7.2 System Documentation
o 7.3 Vendor Documents
o 7.4 Technical References
Completely describe the dynamic behavior of the class, including diagram, and descriptions of each state. Describe how the control will be implemented for the class. Completely describe the functional behavior of the class, including diagram, processing narrative, inputs, outputs, and algorithm to be used (in pseudo-code) for each operation of the class. You may use a data flow diagram to clarify the processing of data handled by your class. Include any other information that is specific to the class and to implementation, such as data store formats (BNF grammars), global resources, optimization techniques, justification of why particular algorithms were chosen, etc. (See System Design for clarification on when BNF grammars should be used.) Once this description is completed for each class, the implementation WILL BE A SIMPLE TRANSFORMATION of the pseudo-code and attribute definitions into C++, Java, C#, etc. syntax.
**4. Class Name 1 4.1 Attributes 4.2 Associations 4.3 Dynamic Behavior 4.4 Operations
- Class Name 2 5.1 Attributes 5.2 Associations 5.3 Dynamic Behavior 5.4 Operations
- Class Name 3**
6.1 Attributes 6.2 Associations 6.3 Dynamic Behavior 6.4 Operations This section should contain the sources of any and all references to other group documents, articles, books, etc. that you used in creating this document. Those interested can replace this with a true bibliography.
7. References 7.1 Existing Software Documentation 7.2 System Documentation 7.3 Vendor Documents 7.4 Technical References