Project: Revised Project Proposal

DUE WEDNESDAY MAR 5 AT 11:59PM.

Table of contents

The revised project proposal serves as a comprehensive design document that fully specifies your project’s scope, implementation strategy, and current status. This document should provide sufficient detail for another group to understand and potentially implement your vision. You may reuse elements from your proposal draft, but make sure to include additional details on the implementation plans and address the feedback received.

This revised proposal will serve as the primary reference document for your final project evaluation. No additional written report will be required beyond the presentation slides for your final project demo.

Proposal Format

Your proposal should be 5-7 pages in length, excluding the cover page. Additional pages are acceptable if necessary to fully document your project. The proposal should include the following sections:

  1. Cover page: Mention GROUP number, latest project title, list of project members and repeat the 3-4 line background of each member.
  2. Learning Goals and Problem Statement: Articulate your project’s learning objectives, focusing on the database technologies you aim to explore and master. Provide a detailed problem statement that outlines the application’s purpose and its target users. While your project may incorporate various technologies, the database component must be substantial in your implementation.
  3. System Functionality and User Interface: Provide a detailed description of your project’s core functionality and features. Each planned feature should be described with sufficient detail to understand its implementation requirements and technical challenges. Describe your application’s interface and user interaction patterns, including key workflows and user journeys. While sophisticated UI design isn’t a primary requirement, include mockups or wireframes to illustrate how users will interact with your system. This section should also clearly define what falls within and outside your project’s scope.
  4. Database Design: Present your database design through appropriate diagrams and schema specifications. For relational databases, include an EER diagram and detailed schema. For NoSQL systems like MongoDB or Neo4j, provide a conceptual design and explain how it maps to your chosen database system. When using public datasets, document both the original schema and your modifications.
  5. Data Pipeline: Whether using synthetic data, public datasets, or scraped information, provide specific details about data collection methods, cleaning and preparation steps, and storage strategies. For public datasets, include source URLs and scope of data used in the project. Describe any data generation or scraping procedures you plan to implement. Specify any real-time data processing or streaming requirements.
  6. Architectural Overview: Present a high-level system architecture diagram showing the main components of your application. Detail how these components interact, including data flow patterns and key interfaces. Describe each component’s responsibilities and how they work together to achieve your system’s objectives.
  7. Technology Stack: List and justify your choice of technologies, frameworks, and libraries. Describe your development environment or deployment platform requirements. Explain how these technologies support your database-focused objectives.
  8. Implementation Strategy: Describe your technical approach to implementing the core features, including specific implementation challenges and proposed solutions. For features based on published work or established algorithms, provide detailed explanations of the underlying methodology. Include any optimization strategies, data structures, or specific techniques you plan to employ. Document how you’ll address potential technical challenges and performance considerations.
  9. Demo Plan: Describe your planned demonstration approach, focusing on how you’ll showcase your database implementation and system functionality. Include specific features you’ll demonstrate and explain how you’ll illustrate the technical challenges you’ve overcome. Your demo should highlight both user-facing features and underlying database implementation details. If you plan to show any visualizations during the demo, provide sample images with clearly labeled axes and data representations.
  10. References: Include citations for any academic papers, technical documentation, or other resources that inform your project. Use a consistent citation format (e.g., the APA format)

NOTES:

  • Adapt the guidelines to fit your specific project needs
  • Use the suggested section headings to organize your report

Submission and Grading

Submit a PDF with your revised project proposal on canvas. Only one submission is required per group. We will evaluate on the basis of clarity of this report, completeness of the design and overall description of the approach taken.