| 7 | | All aspects of Trac have been designed with the single goal to |
| 8 | | '''help developers write great software''' while '''staying out of the way''' |
| 9 | | and imposing as little as possible on a team's established process and |
| 10 | | culture. |
| | 5 | This database system will manage all operations for an e-commerce platform specializing in handmade crafts. The database will store comprehensive information about products including automatically generated codes, prices, inventory levels, dimensions, available colors, production time, and customer reviews. It will also maintain employee records with detailed permission systems, customer profiles with order history and preferences, and comprehensive sales analytics. If we proceed with this project, we would develop a full-stack web application that allows customers to browse and purchase handmade items, employees to manage inventory and customer interactions, and managers to monitor business performance through detailed analytics dashboards. |
| 23 | | You can use [wiki:TracAdmin trac-admin] to configure |
| 24 | | [http://trac.edgewall.org/ Trac] to better fit your project, especially in |
| 25 | | regard to ''components'', ''versions'' and ''milestones''. |
| | 13 | **Content**: |
| | 14 | |
| | 15 | {{{#!html |
| | 16 | <table border="1" cellpadding="6" cellspacing="0" style="border-collapse: collapse; width: 100%;"> |
| | 17 | <tr style="color: darkred; font-weight: bold; text-align: center;"> |
| | 18 | <th>Phase</th> |
| | 19 | <th>Link to Wiki page</th> |
| | 20 | <th>Status</th> |
| | 21 | </tr> |
| | 22 | |
| | 23 | <tr> |
| | 24 | <td style="color: darkred; font-weight:bold;">P0 Phase0</td> |
| | 25 | <td><a href="P0">Project Definition</a></td> |
| | 26 | <td>Completed</td> |
| | 27 | </tr> |
| | 28 | |
| | 29 | <tr> |
| | 30 | <td style="color: darkred; font-weight:bold;">P1 Phase1</td> |
| | 31 | <td><a href="P1">Conceptual Model (ERD)</a></td> |
| | 32 | <td>In Progress</td> |
| | 33 | </tr> |
| | 34 | |
| | 35 | <tr> |
| | 36 | <td style="color: darkred; font-weight:bold;">P2 Phase2</td> |
| | 37 | <td><a href="P2">Logical and Physical Design, DB Creation (DDL)</a></td> |
| | 38 | <td>Not started</td> |
| | 39 | </tr> |
| | 40 | |
| | 41 | <tr> |
| | 42 | <td style="color: darkred; font-weight:bold;">P3 Phase3</td> |
| | 43 | <td><a href="P3">Application Scenarios for DB Access (SQL)</a></td> |
| | 44 | <td>Not started</td> |
| | 45 | </tr> |
| | 46 | |
| | 47 | <tr> |
| | 48 | <td style="color: darkred; font-weight:bold;">P4 Phase4</td> |
| | 49 | <td><a href="P4">First Application Prototype</a></td> |
| | 50 | <td>Not started</td> |
| | 51 | </tr> |
| | 52 | |
| | 53 | <tr> |
| | 54 | <td style="color: darkred; font-weight:bold;">M1 Milestone1</td> |
| | 55 | <td><a href="M1">First Prototype Public Presentation</a></td> |
| | 56 | <td>Not started</td> |
| | 57 | </tr> |
| | 58 | |
| | 59 | <tr> |
| | 60 | <td style="color: darkred; font-weight:bold;">P5 Phase5</td> |
| | 61 | <td><a href="P5">Normalization</a></td> |
| | 62 | <td>Not started</td> |
| | 63 | </tr> |
| | 64 | |
| | 65 | <tr> |
| | 66 | <td style="color: darkred; font-weight:bold;">P6 Phase6</td> |
| | 67 | <td><a href="P6">Complex DB Reports</a></td> |
| | 68 | <td>Not started</td> |
| | 69 | </tr> |
| | 70 | |
| | 71 | <tr> |
| | 72 | <td style="color: darkred; font-weight:bold;">P7 Phase7</td> |
| | 73 | <td><a href="P7">Advanced Database Development</a></td> |
| | 74 | <td>Not started</td> |
| | 75 | </tr> |
| | 76 | |
| | 77 | <tr> |
| | 78 | <td style="color: darkred; font-weight:bold;">P8 Phase8</td> |
| | 79 | <td><a href="P8">Advanced Application Development</a></td> |
| | 80 | <td>Not started</td> |
| | 81 | </tr> |
| | 82 | |
| | 83 | <tr> |
| | 84 | <td style="color: darkred; font-weight:bold;">P9 Phase9</td> |
| | 85 | <td><a href="P9">Other Topics</a></td> |
| | 86 | <td>Not started</td> |
| | 87 | </tr> |
| | 88 | |
| | 89 | <tr> |
| | 90 | <td style="color: darkred; font-weight:bold;">M2 Milestone2</td> |
| | 91 | <td><a href="M2">Final Presentation</a></td> |
| | 92 | <td>Not started</td> |
| | 93 | </tr> |
| | 94 | </table> |
| | 95 | }}} |
| 40 | | For a complete list of local wiki pages, see TitleIndex. |
| | 105 | * Klimentina Efremova 235018 |
| | 106 | |
| | 107 | **Short description:** |
| | 108 | |
| | 109 | This database will contain comprehensive information about handmade craft products, employees with hierarchical permission systems, customer profiles with order history, and business analytics. If we continue developing this project, we would create a full e-commerce platform that enables seamless online shopping for handmade items, efficient inventory management for store employees, and detailed business intelligence for managers. The system will manage product catalogs, customer relationships, employee permissions, and sales analytics to provide a complete solution for a handmade crafts retailer. |
| | 110 | |
| | 111 | **Detailed description of the project:** |
| | 112 | |
| | 113 | Our project aims to create a comprehensive database system for a handmade crafts e-commerce business. The system will handle product management with automatic coding, inventory tracking, customer reviews, and production timelines. It will implement a sophisticated employee management system with different permission levels (store managers, regular employees) and track all employee activities. Customer management will include order tracking, wishlists, and secure payment information storage. The analytics module will provide business intelligence on sales performance, employee productivity, and store profitability. |
| | 114 | |
| | 115 | * The database and application are intended for a handmade crafts retailer who needs to manage their online store operations. The system owner will be responsible for maintaining the database and providing it as a service to customers browsing and purchasing products, employees managing inventory and customer service, and managers monitoring business performance across multiple store locations. |
| | 116 | |
| | 117 | * Our project will address several key problems: inefficient manual inventory tracking, disorganized customer order management, lack of centralized employee permission systems, and insufficient business analytics. Specifically, it will solve inventory management challenges by providing real-time stock tracking, streamline customer service through organized communication logs, enforce security through hierarchical employee permissions, and enable data-driven decision making through comprehensive sales and performance analytics. |
| | 118 | |
| | 119 | * The system will have multiple user types: Customers (who can browse products, place orders, and leave reviews), Regular Employees (with permissions for product management, customer communication, and order processing), Store Managers (with additional permissions for employee oversight and store-specific analytics), and the Business Owner (with full system access and cross-store analytics). Each user type will have different access levels and permissions appropriate to their role. |
| | 120 | |
| | 121 | * While there are existing e-commerce solutions such as Shopify or WooCommerce, our proposal differs in its specialized focus on handmade crafts with features like production time tracking, maker-specific inventory management, and hierarchical employee permission systems tailored for craft businesses. Our approach offers integrated business analytics specifically designed for multi-location craft retailers, which provides advantages in operational efficiency and business intelligence for this specific market segment. |
| | 122 | |
| | 123 | * This will be a web application with responsive design for both desktop and mobile access. The frontend will be built using modern JavaScript frameworks (React/Vue.js) while the backend will utilize PostgreSQL for data storage and Node.js/Python for server-side processing. The application will include separate interfaces for customers (shopping experience), employees (management dashboard), and administrators (analytics and system configuration). |
| | 124 | |
| | 125 | |
| | 126 | ---- |
