WORK BREAKDOWN STRUCTURE $($WBS$)$

$1\mathrm{.}0$ Development of Application for fitness and Nutritional goal

$1\mathrm{.}1$ Market survey

$1\mathrm{.}1\mathrm{.}1$ Collecting data

$1\mathrm{.}1\mathrm{.}2$ Pricing trend

$1\mathrm{.}1\mathrm{.}3$ Customer expectations

$1\mathrm{.}2$ Sub$-$Contractor Agreement and scope

$1\mathrm{.}2\mathrm{.}1$ Procure subcontract agreement for Architectural design $($Aaptiv Inc$)$

$1\mathrm{.}2\mathrm{.}2$ Scope of work.

$1\mathrm{.}2\mathrm{.}3$ Duration of work.

$1\mathrm{.}2\mathrm{.}4$ Price and payment.

$1\mathrm{.}2\mathrm{.}5$ Resources allocation

$1\mathrm{.}3$ Develop wireframes.

$1\mathrm{.}3\mathrm{.}1$ Prepare research for reference.

$1\mathrm{.}3\mathrm{.}2$ Map out user flow.

$1\mathrm{.}3\mathrm{.}3$ Sketch

$1\mathrm{.}3\mathrm{.}4$ Get testing.

$1\mathrm{.}4$ Develop the backend infrastructure.

$1\mathrm{.}4\mathrm{.}1$ Creating database architecture.

$1\mathrm{.}4\mathrm{.}2$ Implement user authentication and authorization features.

$1\mathrm{.}4\mathrm{.}3$ Develop the front$-$end user interface.

$1\mathrm{.}4\mathrm{.}4$ Integrate third$-$party APIs for fitness tracking and nutrition data.

$1\mathrm{.}4\mathrm{.}5$ Test and debug the application for functionality and usability.

$,$

$1\mathrm{.}5$ Testing

$1\mathrm{.}5\mathrm{.}1$ Conduct unit testing

$1\mathrm{.}5\mathrm{.}2$ Perform integration testing.

$1\mathrm{.}5\mathrm{.}3$ Conduct system testing

$1\mathrm{.}5\mathrm{.}4$ Beta testing

$1\mathrm{.}6$ Deployment of the Application

$1\mathrm{.}6\mathrm{.}1$ Prepare the application.

$1\mathrm{.}6\mathrm{.}2$ Release on application stores

$1\mathrm{.}6\mathrm{.}3$ Create app store listings.

$1\mathrm{.}6\mathrm{.}4$ Monitor the release process.

$1\mathrm{.}6\mathrm{.}5$ Address any issues that arise.

$1\mathrm{.}6\mathrm{.}6$ Promotional materials

$1\mathrm{.}6\mathrm{.}7$ Ensure High$-$quality and policy compliance.

$1\mathrm{.}6\mathrm{.}8$ Submit the application for review.

$1\mathrm{.}6\mathrm{.}9$ Get approval by the app store$($s$)$

$1\mathrm{.}6\mathrm{.}10$ Publish the application.

$1\mathrm{.}7$ Maintenance of the Application

$1\mathrm{.}7\mathrm{.}1$ Monitor the application's performance.

$1\mathrm{.}7\mathrm{.}2$ Get user feedback.

$1\mathrm{.}7\mathrm{.}3$ Provide regular updates.

$1\mathrm{.}7\mathrm{.}4$ bug fixes.

$1\mathrm{.}7\mathrm{.}5$ Feature Enhancements

$1\mathrm{.}7\mathrm{.}6$ Address user support requests.

$1\mathrm{.}7\mathrm{.}7$ Troubleshoot issues.

$1\mathrm{.}7\mathrm{.}8$ Continuously improve the application

I would like you to develop a schedule for your project. At the start of class, I made sure that everyone

knew that they would need to get access to Microsoft Project via NJIT. The latest version from NJIT is

Project $16$ Office $365.$ If you already have an older version, you can use that.

In "Course Material", I provided a sample Mic. Schedule, and slides that show how I used Mic. Project to

develop the schedule.

For your schedule, I want:

$1.$ All tasks from your WBS lowest level. Include next level up tasks in your schedule, as "roll$-$up$"$ tasks

$($the sample shows this$).$ You may include tasks on your schedule that are at a lower level then your

WBS lowest level, if that makes sense.

$2.$ All lowest level tasks should have predecessors. A predecessor can be either a task or a milestone

event.

$3.$ The resource sheet filled out $($no labor rates are required$).$ Resources are assigned at the lowest task

level, and should include sub$-$contractors.

$4.$ Task start and stop dates, and task durations. It is not acceptable to leave a $?$ in the duration field.

$5.$ Precedence of tasks should be set up $($indents$).$ I also recommend precedence at the highest level of

the project on the schedule. This is shown on the sample as $"1.$ Class Project". By doing this, you can

see the duration of major phases of the project, or the whole project. Also $-$ make sure I can see the

precedence lines on the GANT chart part of the schedule.

$6.$ Precedence allows tasks to be collapsed up to the highest task on the Gannt chart $($indicated by $"+"$

signs to the left of the task name$).$ Please do NOT collapse your tasks when you save your schedule

for submittal. With $30$ students work to grade, I do not want to have to add time by expanding tasks.

$7.$ Resources should be assigned to each task. In the $$Resource Sheet$,$ include individual named

people to be assigned as resources. If you have a subcontractor doing some of the work, you can

identify these resources as $$Subcontractor Name $$ Resource Type X$($for ex$.,$Joes Plumbing $$ Pipe

Fitter #$1).$ Do not "over$-$book" resources $-$ this is indicated if the resource name in the Resource

Sheet is colored red. What this means is that you have assigned the same resource to simultaneous

tasks. This is not a good practice from a PC perspective.

$8.$ Include $"\%$ Complete" column, if plan to show future in$-$flight progress. Please leave the value at

$0\%,$ since this is the initial schedule.

$9.$ Please set the Gantt time scale so that I can see all of the Gantt chart without scrolling left and right.

See the $$Sample Schedule$$ how to slides for this. $($Note $$ many students have lost points because

they ignored this$)$

$10.$ Remember that a milestone task is a zero day event $($not a one day task$).$ Use milestones to indicate

major and interim events in the project. I would like to see some interim milestones in the project.

Reminder from the lecture slides$-$ do NOT include a project start or stop milestone.

$11.$ I want the following columns included on the schedule $($to the left of the Gantt chart$),$ and in the order

listed: $\%$ Complete, Task Name, Duration, Start Date, Finish Date, Precedence, Resource Name. If

you "right click" on the columns headers, you will see how to insert columns.