What's needed:
A tally of what will be required to implement the app features mentioned.
Authentication:
- Hardware: User device, web host, Internet
- Interfaces: device, web
-
Views: (design/styling hours)
- Registration (≈ 1 hrs.)
- Login (≈ .5 hrs.)
- Change Password (≈ .5 hrs.)
- Group Selection (≈ .5 hrs.)
- User Verification (≈ 1.5 hrs.)
-
Forms: (functionality/testing hours)
- Registration: Username, password, email?, first name?, last name? (≈ 1.5 hrs.)
- Login: Username & password (≈ 1 hrs.)
- Change Password (≈ .75 hrs.)
- Group Selection: group(s) (≈ 1 hrs.)
- Faculty / Staff Verification: New requests, Is/Is not in “Group” (≈ 1.5 hrs.)
-
Alerts: (Errors & Warnings)
- Invalid / Unavailable Username (≈ .5 hrs.)
- Invalid password (≈ .25 hrs.)
- Invalid login information (≈ .5 hrs.)
- Faculty / Staff verification note (≈ .5 hrs.)
- Save / Don't Save login information? (≈ .5 hrs.)
- (≈ hrs.)
-
Business Logic:
- Invalid / Unavailable Username (≈ .5 hrs.)
- Invalid password (≈ .25 hrs.)
- Invalid login information (≈ .5 hrs.)
- Faculty / Staff Group Verification Note (≈ 1 hrs.)
- Save / Don't Save login information? (≈ 1 hrs.)
- Device registration (≈ 1.5 hrs.)
- User registration (≈ 1.5 hrs.)
- Encrypt & store user information on device (≈ .5 hrs.)
- Maintenance: None
- Expense(s): None
- Database: Users, Groups, UserGroups (≈ 3 hrs.)
- Notes: None
Public Information E.g. Finals Schedule, AU Contact Information (Per Static Item):
These estimates are very rough due to the different natures of the data.
- Hardware: User device, web host, Internet
- Interfaces: device, web
-
Views: (design/styling hours)
- Input (≈ 1 hrs.)
- View (≈ 1 hrs.)
-
Forms: (functionality/testing hours)
- Input, Editing & Saving (≈ 1.5 hrs.)
- Validation (≈ 1 hrs.)
-
Alerts (Errors & Warnings): Varies By Type
-
Business Logic: Varies By Type
- Maintenance: Varies By Type
- Expense(s): None
- Database: Varies By Type (≈ 1.5-2 hrs.)
- Notes: Some data could possibly be combined into the same database table(s) and input/edit forms.
“Push” Notifications:
- Hardware: User device, web host, Internet
- Interfaces: device, web, Web API, Push Notification API(s)
-
Views: (design/styling hours)
- Write New Post (≈ 1 hrs. / each interface)
- View New Notifications (≈ 1 hrs. - Device only)
- View All Notifications (≈ 1 hrs. each web & device)
-
Forms: (functionality/testing hours)
- Write New Post (≈ 1 hrs. / each interface)
- View New Notifications (≈ 1 hrs. - Device only)
- View All Notifications (≈ 1 hrs. each web & device)
-
Alerts: (Errors & Warnings)
- Missing data (≈ .75 hrs.)
-
Business Logic:
- New post validation (≈ .75 hrs.)
- New post insertion (≈ .75 hrs.)
- Post editing (≈ 1 hrs.)
- Push Notification integration (≈ 1.5 hrs.)
- Maintenance: None
- Expense(s): None
- Database: Users, Groups, UserGroups, Posts, Pushes (≈ 1 hrs.)
- Notes: None
Grouping:
- Hardware: User device, web host, Internet
- Interfaces: device, web
-
Views: (design/styling hours)
- Select / Edit User's Group(s) (≈ 1 hrs.)
- Verify privileged users (≈ .75 hrs. / device and/or web)
- View users by group (≈ 1 hrs)
-
Forms: (functionality/testing hours)
- Select / Edit User's Group(s) (≈ 1 hrs.)
- Verify privileged users (≈ 1 hrs. / device and/or web)
- View users by group (≈ 1 hrs)
-
Alerts: (Errors & Warnings)
- Faculty / Staff Group Verification Note (≈ .25 hrs.)
- Verify Added Faculty / Staff designation (≈ .5 hrs.)
-
Business Logic: Negligible (≈ 1 hrs.)
- Maintenance: None
- Expense(s): None
- Database: Users, Groups, UserGroups (≈ 1 hrs.)
- Notes: None
Web Interface:
- Hardware: Laptop / Desktop, web host, Internet
- Interfaces: computer, web
-
Views: (design/styling hours)To be determined
-
Forms: (functionality/testing hours)To be determined
-
Alerts: (Errors & Warnings)To be determined
-
Business Logic: To be determined
- Maintenance: To be determined
- Expense(s): None
- Database: All
- Notes: These are dependant on what is made available through the web interface.
Feedback:
- Hardware: User device, web host, Internet
- Interfaces: device, web
-
Views: (design/styling hours)
- Input (≈ .5 hrs.)
- View (≈ .5 hrs.)
- Respond (≈ .75 hrs.)
-
Forms: (functionality/testing hours)
- Input (≈ 1 hrs.)
- Respond (≈ 1 hrs.)
-
Alerts: (Errors & Warnings) None
-
Business Logic:
- Save feedback (≈ .75 hrs.)
- Save & Send Response (≈ 1 hrs.)
- Maintenance: None
- Expense(s): None
- Database: Feedback, Responses (≈ 2 hrs.)
- Notes: None
Usage Statistics:
- Hardware: User device, web host, Internet
- Interfaces: device, web
-
Views: (design/styling hours)
- Allow usage statistics collection? (in Settings) (≈ .5 hrs.)
- Installs / Uninstalls (≈ 1 hrs.)
- Average usage (≈ 1 hrs.)
-
Forms: (functionality/testing hours)
- Choose time frame to view (≈ 1 hrs.)
-
Alerts: (Errors & Warnings)
- Start date is after end date (≈ .5 hrs.)
-
Business Logic:
- Record app open (≈ .5 hrs.)
- Record app close (≈ .5 hrs.)
- Record data access (≈ 4 hrs. - would require additional work for every data type)
- Maintenance: None
- Expense(s): None
- Database: Usage, UserGroups (≈ 3 hrs.)
- Notes: None
Possible Extensions / Additions
User Profiles:
- Hardware: User device, web host, Internet
- Interfaces: device, web
-
Views: (design/styling hours)
- Groups (≈ 5 hrs.)
- Users (by group or all) (≈ 1 hrs.)
- User Profile (≈ 1.5 hrs.)
- Add / Edit profile (≈ 1 hrs.)
- Delete Image (≈ .5 hrs.)
-
Forms: (functionality/testing hours)
- Edit profile (≈ 1 hrs.)
- (≈ hrs.)
- (≈ hrs.)
- (≈ hrs.)
-
Alerts: (Errors & Warnings)
- Confirm Image Delete (≈ .5 hrs.)
-
Business Logic:
- Select Groups (≈ .5 hrs.)
- Select Users (by Group) (≈ .5 hrs.)
- Select User Data (≈ .5 hrs.)
- Upload User Image (≈ .5 hrs.)
- Delete User Image (≈ .5 hrs.)
- Save user profile data (≈ 1 hrs.)
- Flag user profile / image (≈ .75 hrs.)
- Maintenance: None
- Expense(s): None
- Database: Users, Groups, Profiles, Images (≈ 2 hrs.)
- Notes: None
Opportunities:
- Hardware: User device, web host, Internet
- Interfaces: device, web
-
Views: (design/styling hours)
- Post new opportunity (≈ 1 hrs.)
- Edit / Delete opportunity (≈ .5 hrs.)
- View opportunities (≈ 1 hrs.)
- Search By Keyword (≈ 1 hrs.)
-
Forms: (functionality/testing hours)
- Post new opportunity (≈ 1.5 hrs.)
- Edit / Delete opportunity (≈ 1 hrs.)
- View opportunities (≈ 1 hrs.)
- Search By Keyword (≈ 1 hrs.)
-
Alerts: (Errors & Warnings)
- Missing data (≈ .25 hrs.)
- Verify flag post (≈ .25 hrs.)
-
Business Logic:
- Verify completeness (≈ .5 hrs.)
- Post, edit, & delete (≈ 1 hrs.)
- Select opportunities (≈ .5 hrs.)
- Select opportunities by keyword (≈ .5 hrs.)
- Flag post & notify admin (≈ .75 hrs.)
- Maintenance: None to minimal. If postings were to require approval before being listed,
then it would depend on usage.
- Expense(s): Depends on the method of moderation.
- Database: Users, Groups, UserGroups (≈ 3 hrs.)
- Notes: None
Keywords:
- Hardware: User device, web host, Internet
- Interfaces: device, web
-
Views: (design/styling hours)Applied to all “posting” views.
-
Forms: (functionality/testing hours)Applied to all “posting” views.
-
Alerts: (Errors & Warnings)None
-
Business Logic:
- Verify & save new keywords (≈ .5 hrs.)
- Search / filter by Keyword (≈ 2 hrs. applies to all views)
- Maintenance: None
- Expense(s): None
- Database: Keywords (≈ 3 hrs.)
- Notes: None
User to User Messaging
- Hardware: User device, web host, Internet
- Interfaces: device, web
-
Views: (design/styling hours)
- Select User(s) (≈ 1 hrs.)
- Compose Message (≈ 1 hrs.)
- View Message (≈ 1 hrs.)
- Allow Users to Message Me? (In Setting) (≈ .75 hrs.)
-
Forms: (functionality/testing hours)
- Select User(s) (≈ 1 hrs.)
- Compose Message (≈ 1 hrs.)
-
Alerts: (Errors & Warnings)
- Verify flag message (≈ .5 hrs.)
-
Business Logic:
- Select Users (≈ .5 hrs.)
- Save Message (≈ .5 hrs.)
- Push Notifications (≈ 1 hrs.)
- Flag Message (≈ .75 hrs.)
- Ban User (≈ .75 hrs.)
- Maintenance: None
- Expense(s): None
- Database: Users, Messages (≈ 3 hrs.)
- Notes: None