Web based application and related documents

Project requirements for the Web Application We need an web application that performs several different tasks. We also want it to have payment methods such as Paypal. Maps integration would be a nice addition to have using API. Project Report The final project report should include all the following documents covering the software development process. Include a cover page with the project title, complete names and e-mails of team members. Problem definition: outline the problem requirements and include the ap plication domain and motivations of your project (1 page). Application benefits (2 pages): what are the benefits of your application when compared to existing systems. Choose two systems only and include their references. Requirements elicitation and specification: (a) (6 pts) Functional Requirements List and Table: For each user role (two exactly), provide a list of proposed requirements and specify which ones have been implemented. Create a table that includes the following columns: ● Requirement ID (e.g., R-01) ● Requirement Name (e.g., User Registration) ● User Role (e.g., Customer) ● Implementation Status (Implemented, Partially Implemented, Not Implemented) ● Manager’s Note (leave this column empty) After presenting the table, list (only) implemented requirement with a clear name and provide a brief explanation. (b) (3+3 pts) For each user role, provide the use case diagram with all the use cases and actors. (c) (3+3 pts) Describe in detail two use cases using the activity diagram. Choose the most complex use cases. (d) (6 pts) Software qualities: Correctness, Time-efficiency and Robustness. Include at least two concrete examples for each quality for each user role. The sign-in and sign-up use cases are excluded from the examples. Top-level and Low-level Software Design, aligned with project requirements: (a) (5+3 Model-View-Controller (MVC) Architecture: Provide the MVC architecture for your application based on the selected web framework. Describe at least three benefits of using the MVC architecture specifically for your application (avoid generic MVC definitions). Design Patterns - Observer and Factory: ● Explain in detail how the Observer and Factory design patterns are used in your specific application. ● Include complete class diagrams for each pattern. ● Provide algorithms corresponding to the important methods within each pattern. ● For each class, specify the data types of the attributes and prototypes of the methods. (c) (6 pts) Comprehensive Class Diagram: Provide a class diagram of the entire system (that incorporates the Observer and Factory design patterns). Ensure the diagram is clear and easy to understand, using standard UML notations,highlighting the relationships between classes and design patterns. Software construction: (a) (2 pts) Submit the screenshot of the entire structure of the code within the web framework. (b) (3 pts) Deployment diagram regarding the hardware configuration of the code. Indicate the supported Web browsers, the application/Web servers and the database solution. (c) (2 pts) Screenshots of all table contents of the system data. Technical documentation: (a) (1 pt) List of programming languages. (b) (1 pt) List of reused algorithms and programs. Include their sources. (c) (2 pts) List of software tools and environments. Provide briefly their benefits specifically for your application. Important Notes 1. The two design patterns Facade and Singleton cannot be used as they are simple. 2. All the UML diagrams must be readable and produced with a UML tool, such as starUML, ArgoUML, Visual Paradigm or Microsoft Visio. 3. The design patterns must be designed according to the GoF book. 4. The code is constructed based on the specification and design documents. It should contain the MVC architecture and the two design patterns.