support@essaywritingexpert.orgThe project documentation should include the following sections:
- Title of the project (with the list of project team memabers and the CS552BH2 course affiliation).
- Executive Summary.
- Table of Contents.
- Project Plan (with clear indication of the System Development phases and time periods for every stage performed by your team).
- Functional Specifications (including descriptions of Actors/Roles; Business Rules; system-integrated Use Case Diagram with Use-Case descriptions; Examples of Class Diagrams [related to particular Use Cases]; Examples of Object Diagrams [related to the selected Class Diagrams included in your project report]; Examples of Sequence Diagrams; Examples of Communication Diagrams; and Examples of State-Chart Diagrams).
- Functional Tests Plan.
- System Design Specifications (including System Architectural [Layered, “Physical”] Design Scheme (known as a Deployment diagram) selected; Package Diagram [where all packages are populated with the interrelated classes and represented relationships between packages as links between the corresponding classes from different packages]; Database Tables; Entity-Relational diagrams [where tables are connected via corresponding prime and/or foreign keys]; Window Navigation Diagrams; Drafts of User Interfaces; and Examples of System-Response Report Forms).
- System Integration Tests Plan.
- Issues to Future Studies.
- Appendices (if any). All the diagrams could be built by using Visual Paradigm, ArgoUML, MS Visio, or MS Word Drawing tools. (You can use any other tools available to you, which should be specified [cited] in your project reports). Visual Paradigm Community Edition (https://www.visual-paradigm.com/editions/community/) and ArgoUML (https://argoumltigris-org.github.io/tigris/argouml/) tools are available in MEM-202 and MEM-204 (or free on the Internet). All CS tools (traditionally used in particular CS courses) are