| | 1 | = About: The Chore Store = |
| | 2 | |
| | 3 | == Team members == |
| | 4 | * Elena Spasovska 231141 |
| | 5 | * Marija Sergievska 231048 |
| | 6 | * Kristijan Trimceski 231132 |
| | 7 | |
| | 8 | == Short description == |
| | 9 | |
| | 10 | The Chore Store is a web-based application that connects clients who need help with everyday tasks with workers willing to complete those tasks for compensation. The system manages structured data related to users, task requests, task offers, tasks, categories, locations, payments, reviews, complaints, notifications, and communication between users. |
| | 11 | |
| | 12 | The database includes entities such as User, Client, Worker, !TaskRequest, !TaskOffer, Task, Payment, Review, Message, Category, Badge, and Location. Clients create task requests by defining a category and location, after which the system suggests suitable workers based on their location and category preferences. |
| | 13 | |
| | 14 | Workers can either apply to available task requests or receive direct offers from clients. For one task request a client can send different offers to many workers with different prices. The system enforces minimum pricing based on worker badges, which depend on their performance and ratings within specific category. Once a worker accepts an offer, it becomes an active task, while all other offers for that request are discarded. |
| | 15 | |
| | 16 | Within a task, users can communicate, complete payments, rate each other, and file complaints if necessary. |
| | 17 | |
| | 18 | |
| | 19 | == Detailed description of the project == |
| | 20 | |
| | 21 | The Chore Store is designed as a centralized platform that manages the full lifecycle of everyday task execution, from task creation to completion and evaluation. The system introduces structured workflows and data relationships that ensure efficient coordination between clients and workers. |
| | 22 | '''System workflow and logic:''' |
| | 23 | * A client creates a !TaskRequest by specifying category and location |
| | 24 | * The system suggests a set of matched workers |
| | 25 | * The client can send !TaskOffers to multiple workers with specific prices |
| | 26 | * Workers can also independently apply for open tasks |
| | 27 | * The minimum price for a worker is determined by their Badge, which depends on their average ratings within a category |
| | 28 | * Once a worker accepts a !TaskOffer, it is converted into a Task and all other offers are discarded |
| | 29 | * A communication channel (chat) is opened for the task |
| | 30 | * After completion, the client performs payment |
| | 31 | * Both client and worker rate each other |
| | 32 | * A complaint can be submitted if issues arise |
| | 33 | |
| | 34 | '''Ownership and target organization:''' |
| | 35 | The system is intended to be owned and maintained by a company or platform provider that offers task management services. The organization requires a reliable infrastructure to manage user interactions, task assignments, pricing logic, and trust mechanisms such as ratings and complaints. |
| | 36 | |
| | 37 | '''Problems addressed:''' |
| | 38 | * lack of trust and transparency in informal task coordination |
| | 39 | * absence of structured task assignment and tracking |
| | 40 | * inefficient matching between clients and workers |
| | 41 | * lack of standardized pricing mechanisms |
| | 42 | * no reliable system for feedback, complaints, and dispute resolution |
| | 43 | |
| | 44 | The system solves these issues by introducing structured workflows, automated matching, controlled task assignment, and integrated evaluation mechanisms. |
| | 45 | |
| | 46 | '''Types of users:''' |
| | 47 | * Clients – create task requests, define category and location, send offers to selected workers, choose a worker, pay for completed tasks, recieve and leave reviews |
| | 48 | * Workers – apply for tasks or receive direct offers, accept or reject offers, complete tasks, and receive and leave review |
| | 49 | * Platform administrators – monitor the system, manage complaints, and ensure proper system operation |
| | 50 | |
| | 51 | '''Comparison with existing solutions:''' |
| | 52 | Unlike informal solutions such as social media platforms, this system introduces: |
| | 53 | * a centralized platform for connecting clients and workers |
| | 54 | * faster task fulfillment by directly connecting clients with available workers, without relying on delayed responses typical for social platforms |
| | 55 | * pricing based on worker reputation (badges) |
| | 56 | * full task lifecycle tracking |
| | 57 | * integrated messaging, payment, rating, and complaint systems |
| | 58 | |
| | 59 | This leads to improved trust, transparency, and efficiency. |
| | 60 | |
| | 61 | '''Application type:''' |
| | 62 | The application is designed as a web-based system, with potential future expansion to mobile platforms. |
