Project Description
Wireframes
Database Schema
Priority Matrix
User Stories
MVP
Post MVP
Time Estimates
More than ever it's critical to be organized in this fast paced society. With this app users will be able to keep track of any tasks and events they might have. With a monthly and daily view, users can easily check to see what their day will look like. You can also view upcoming appointments and a log of your daily schedule. Taking notes for your daily plans is also a feature. Users will also have the option to choose between different themes and alarm sounds for the dashboard.
- Site Example 1: https://asana.com/
- Site Example 2: https://tasks.office.com/
Column Name | Data Type |
---|---|
id | primary key |
username | text not null |
text not null | |
password_digest | text not null |
Column Name | Data Type |
---|---|
id | primary key |
user_id | references users(id) |
text | text not null |
isComplete | boolean not null |
set_date | date not null |
Column Name | Data Type |
---|---|
id | primary key |
user_id | references users(id) |
text | text not null |
set_time | string not null |
set_date | date not null |
Column Name | Data Type |
---|---|
id | primary key |
user_id | references users(id) |
text | text not null |
set_date | date not null |
Column Name | Data Type |
---|---|
id | primary key |
user_id | references users(id) |
text | text not null |
set_time | string not null |
set_date | date not null |
Include a full list of features that have been prioritized based on the Time and Importance
Matrix.
Component | Priority | Estimated Time |
---|---|---|
Database Setup | 1 | 2hrs |
Page Layout | 2 | 6hrs |
App Logic | 3 | 10hrs |
Page Design | 4 | 9hrs |
Auth | 5 | 1hrs |
Total | 28hrs |
When the app is started users will see the home page that tells them what they can do with the app, and a link to the dashboard. If users aren't logged, instead of seeing a link to the dashboard the login and register buttons will be seen.
Once a user has entered the dashboard they will see a view of the current month with options to add events, tasks and notes to a particular day when it is clicked on. They can also plan out their whole day by the hour using the schedule tab.
Users will be able to view their tasks and events with a by daily view. The monthly view will be color coded to inform users which day they added any tasks, events, etc. They can add tasks, events and notes by going to a specific date on the calendar. Notes can include important details that go along with a specific task. The app will be simple enough that a person of any age can feel comfortable using it as their own personal organizer.
Users will be able to
- Add any tasks they must complete for a particular day
- Add important events
- Take notes that they feel is important
- View and edit a daily schedule by the hour
- View tasks and events by the month or day
Have users
- Customize the look of their dashboard
- View holidays that will be coming up
Based on the initial logic defined in the previous app phases section try and breakdown the logic further into functional components, and by that we mean functions. Does your logic indicate that code could be encapsulated for the purpose of reusablility. Once a function has been defined it can then be incorporated into a class as a method.
Time frames are also key in the development cycle. You have limited time to code all phases of the game. Your estimates can then be used to evalute game possibilities based on time needed and the actual time you have before game must be submitted.
Component | Priority | Estimated Time | Time Invested | Actual Time |
---|---|---|---|---|
Database Setup | 1 | 2hrs | 1hrs | 1hrs |
App Logic | 2 | 6hrs | 12hrs | 12hrs |
Page Layout | 3 | 10hrs | 6hrs | 6hrs |
Routes | 4 | 3hrs | 2hrs | 2hrs |
Page Design | 5 | 9hrs | 12hrs | 12hrs |
Auth | 5 | 8hrs | 1hrs | 6hrs |
Post-MVP | 7 | 9hrs | 1hrs | 1hrs |
Total | 39hrs | 34hrs | 34hrs |
- React
- Rails
- Postgresql
- React-Calendar