Project Report
Software Design Document
for
<Project>
Version < >
Prepared by <author>
<organization>
<date created>
VERSION HISTORY
|
Version # |
Implemented By |
Revision Date |
Approved By |
Approval Date |
Reason |
|
1.0 |
<Author name> |
<mm/dd/yy> |
<name> |
<mm/dd/yy> |
Design Plan draft |
|
|
|
|
|
|
|
VERSION HISTORY
|
Version # |
Implemented By |
Revision Date |
Approved By |
Approval Date |
Reason |
|
1.0 |
Joakim |
20/02/16 |
Viral |
22/02/16 |
Created document |
|
1.1 |
Joakim |
14/04/16 |
Viral |
15/04/16 |
Updated format of document |
|
|
|
|
|
|
|
Table of Contents
Table of Contents ii
Revision History ii
1. Introduction 1
1.1 Purpose 1
1.2 Document Conventions 1
1.3 Intended Audience and Reading Suggestions 1
1.4 Product Scope 1
1.5 References 1
2. Overall Description 2
2.1 Product Perspective 2
2.2 Product Functions 2
2.3 User Classes and Characteristics 2
2.4 Operating Environment 2
2.5 Design and Implementation Constraints 2
2.6 User Documentation 2
2.7 Assumptions and Dependencies 3
3. Design Diagrams 3
3.1 Use cases 3
3.2 Class diagrams 3
3.3 Sequence Diagrams 3
3.4 Activity diagrams 3
3.6 Sysem Architecture 4
3.5 Entity Relationships diagrams 4
Appendix A: Glossary 5
Appendix B: Analysis Models 5
Appendix C: To Be Determined List 6
Purpose
The purpose of the Software Design document is to establish and justify the design choices that have been made for the …..
Scope
The main artifact of this document will be ..
Page 3 of 4