I need actual design documents for the project, not a description of what the parts are. Thank you!

Design documents required:

1. Functional design - what it will do / not how it does it

2. UML Diagram showing all classes

3. ER (Entity Relationship) diagram showing how the objects/components interact with each other

4. UI design (Keep it simple but your project needs to have a Graphical User Interface)

What Goes into Your Software Design Document? A typical software requirements document should include the following details: Title: Add the title of the software design document. Typically, Program or Project name. System Overview: Provide a general description and functionality of the software system. What is the problem and how does your software solve it? Design Considerations: Describe any criteria that impact your design. - Assumptions and Dependencies: Describe any assumptions that are being made. - General Constraints: Describe any constraints that could have an impact on the design of the software. - Goals and Guidelines: Describe your goals and guidelines for the design of the software. System Architecture: This section should provide a high-level overview of how the functionality and responsibilities of the system were partitioned and then assigned to subsystems or components. This is where your UML diagrams and entity relationship diagrams go. Policies and Tactics: This is where you would discuss your design by contract rules. Detailed System Design: Most components described in the system architecture section will require a more detailed discussion. Here you will talk about the algorithms used or the methods developed to solve problems or perform specific tasks