The
project documentation
should include the following sections:
• Title of the project (with the list of project team members);
• Executive Summary;
• Table of Contents;
• Introduction;
• Project Plan;
• Functional Specifications (including descriptions of Actors/Roles; Business Rules; Use-Case
Diagrams with Use-Case descriptions; Examples of Class Diagrams (related to particular Use
Cases); Examples of Object Diagrams [related to the selected Class Diagrams]; Examples of
Sequence Diagrams; Examples of Collaboration or Communication Diagrams; Examples of StateChart Diagrams);
• Functional Tests Plan;
• System Design Specifications (including System Architectural [Layered, “Physical”] Design Scheme selected; Package Diagram [populated with interrelated classes]; Database Tables; Entity-
Relational diagrams; Window Navigation Diagrams; Drafts of User Interfaces; and Examples of System-Response Report Forms);
• Integration Tests Plan;
• Issues to Future Studies;
• Conclusion;
• References;
.
The project documentation should include the following secti.docx
1. The
project documentation
should include the following sections:
• Title of the project (with the list of project team members);
• Executive Summary;
• Table of Contents;
• Introduction;
• Project Plan;
• Functional Specifications (including descriptions of
Actors/Roles; Business Rules; Use-Case
Diagrams with Use-Case descriptions; Examples of Class
Diagrams (related to particular Use
Cases); Examples of Object Diagrams [related to the selected
Class Diagrams]; Examples of
Sequence Diagrams; Examples of Collaboration or
Communication Diagrams; Examples of StateChart Diagrams);
• Functional Tests Plan;
• System Design Specifications (including System Architectural
[Layered, “Physical”] Design Scheme selected; Package
Diagram [populated with interrelated classes]; Database Tables;
Entity-
2. Relational diagrams; Window Navigation Diagrams; Drafts of
User Interfaces; and Examples of System-Response Report
Forms);
• Integration Tests Plan;
• Issues to Future Studies;
• Conclusion;
• References;
![The
project documentation
should include the following sections:
• Title of the project (with the list of project team members);
• Executive Summary;
• Table of Contents;
• Introduction;
• Project Plan;
• Functional Specifications (including descriptions of
Actors/Roles; Business Rules; Use-Case
Diagrams with Use-Case descriptions; Examples of Class
Diagrams (related to particular Use
Cases); Examples of Object Diagrams [related to the selected
Class Diagrams]; Examples of
Sequence Diagrams; Examples of Collaboration or
Communication Diagrams; Examples of StateChart Diagrams);
• Functional Tests Plan;
• System Design Specifications (including System Architectural
[Layered, “Physical”] Design Scheme selected; Package
Diagram [populated with interrelated classes]; Database Tables;
Entity-](https://image.slidesharecdn.com/theprojectdocumentationshouldincludethefollowingsecti-230118033309-4d6d9067/85/The-project-documentation-should-include-the-following-secti-docx-1-320.jpg)
