Project 6: FNPF Staff Wellness Application

t/a BULA FIT

Mid-Term Report

Prepared by: Prepared for:

IEP Cohort: Industry Client:
Development Team 6, IT and HR Dept.,
CS400, 2022, USP FNPF

Team Members

Harshad Chand S11158346 Team lead

Shaliah Bano S11157320
Farish Khan S11171856
Suvneet Kumar S11173017
1 Table of Contents

2 Introduction .................................................................................................................................... 3
3 System Architecture ........................................................................................................................ 4
3.1 Proposed System Architecture ............................................................................................... 4
3.2 Use Case Diagram ................................................................................................................... 5
4 Updates on Project Plan.................................................................................................................. 6
4.1 Project Progress ...................................................................................................................... 6
4.1.1 Elicitation of App Requirements ..................................................................................... 6
4.1.2 Development Environment ............................................................................................. 6
4.1.3 Workload Distribution..................................................................................................... 6
4.1.4 Software Requirments Specification (SRS) Development ............................................... 6
4.1.5 App Development ........................................................................................................... 6
4.1.6 Change and Risk Documentation .................................................................................... 7
4.2 Mid-term Summary: Activities & Deliverables Achieved ........................................................ 7
4.3 Obstacles Encountered ........................................................................................................... 8
5 Deviations in Project Plan ............................................................................................................... 9
5.1 Progression and Changes ........................................................................................................ 9
6 Risk and Risk Mitigation ................................................................................................................ 10
6.1 Risks Identified and Mitigation ............................................................................................. 10
7 Team Interactions ......................................................................................................................... 12
7.1 Team Member Interactions .................................................................................................. 12
7.2 Client Interactions ................................................................................................................. 12
8 Timeline – Deliverables ................................................................................................................. 13
8.1 Project Timeline .................................................................................................................... 13
8.2 Updated Gantt Chart............................................................................................................. 14
8.3 Remaining Deliverables Timeline .......................................................................................... 15
9 Mark Allocation Sheet................................................................................................................... 16
10 Appendix ................................................................................................................................... 16
10.1 Risk Identification Breakdown .............................................................................................. 16

2
2 Introduction

After the global pandemic, many companies are considering implementing a comprehensive
employee wellness program. These programs, if well-designed, can manage employee wellness whilst
also helping improve workers' health and productivity and reducing associated costs of health care.
Likewise, the Fiji National Provident Fund the country's largest financial institution also acknowledges
their hardworking staff and willingness to provide health and wellness initiatives for its employees.
The HR team of the FNPF is the primary client for the project being served. They are responsible for
various aspects of employee relations and also the well-being of all employees. This project aims to
provide simple yet effective software that enables HR to monitor the health of its employees.

The software product will be a smartphone application and an admin portal, which will benefit all staff
and especially the Fiji National Provident Fund (FNPF) HR department. The ultimate goal of this app is
to provide an easy-to-use app that enables HR to track the health of all its employees. This project
would be fully completed in four stages but as per the timeframe and complexities that can arise from
developing software from scratch, Stage 1 was only assigned to our IEP Development Team 6 as the
scope to design and develop the founding of this app by only focusing on Physical Wellness aspects.
Whilst doing this, the team will ensure that the system (app and admin portal) is ready to easily
integrate into other remaining stages in the future.

This document aims to provide an overview of the current status of the development of the app and
its features, as well as the timeline that will allow the app to be delivered on time. The project plan
also includes a comprehensive view of the various activities that will be carried out in the coming
months. The development time of the app and its various services was estimated at 74 days, to deliver
fully functional features of the physical wellness aspects (stage 1). This review will help determine if
the project is on track and if it should be followed through with the schedule.

As the development of the app's requirements and implementation started, various issues
encountered during the development of the project led to changes in the timeline and a slight change
to app specification. This document provides a comprehensive view of the corrective measures that
were involved in resolving identified issues. The updated report will contain the changes made to the
project plan and the app requirements. It will also provide an overview of the progress made since the
project’s start. These changes have added to the project's risk profile and need to be managed to
maintain the project's schedule.

This document will provide an overview of the progress of the project, including the requirements for
refactoring and the defined milestones. It also includes a schedule for the second half of the
development of the Bula Fit app. The updated schedule will consider the risks and changes that are
expected to be encountered.

3
3 System Architecture
After deriving the system/user requirements project proposal and system requirements document,
the following diagrams show the proposed app and web portal architecture and the use cases

3.1 Proposed System Architecture

Figure 1: Proposed System Architecture of FNPF Bula Fit app

The goal of the admin portal is to provide a central hub for managing the various activities of the app
and its staff. It will also retrieve data from the app service. The results of the process will be returned
to the device after the server has analyzed the parameters. When a user's device is online, the app

4
will sync the data with the server. The system architecture will allow it to handle more complex
requests and processes. It will also help confirm the objective of complex computing.
3.2 Use Case Diagram

Figure 2: Use Case Diagram of FNPF Bula Fit app

The FNPF Bula Fit app has two active actors (users and admin). The user will have access to all use
cases as illustrated in the diagram above. Likewise, the Admin user will handle the app management
side from the admin portal.

5
4 Updates on Project Plan
4.1 Project Progress
The development team of the FNPF's Bula Fit app has been working on various tasks to create a
functional prototype of the Bula Fit app. These tasks were carried out in response to the changes in
the project's requirements. The project will be entering the development and testing phase of its life
cycle. Throughout the project activities, the team has been regularly meeting with the client and has
been actively involved with the various stakeholder including the FNPF HR team. To monitor the
progress of the project, the team and the client have agreed to meet once a week to review the
progress.

Due to the complexity of the project, the team is putting its best effort to absorb all the changes and
enhancements that have been made. This has resulted in some of the tasks being completed late while
others before time. The team's ultimate goal is to create a foundation for the future development of
the app's features.

4.1.1 Elicitation of App Requirements

The team members met with the client, project managers, and stakeholders to gather a
comprehensive list of requirements for the app and admin portal. This step helped them identify the
necessary features and functionality to implement the app. This was also beneficial as it allowed us to
gather the necessary details to create a functional and devise comprehensive solution.

4.1.2 Development Environment

The client wanted to develop an app using the C# .NET framework and a Flutter app development
toolkit. The team had to learn the framework and its various technologies to meet the client's
requirements. Our team also had to set up the environment in our machines to accommodate the
development requirements. Furthermore, to cater for some of the client’s existing and new
requirements, the development team had to make use of other implementation resources such as
(Firebase, Flutter flow and Postman) to implement and test certain functionalities

4.1.3 Workload Distribution

The team leader assigned each member tasks according to their skill level and priority. The tasks varied
throughout the week as the project progressed. The team leader was also responsible for ensuring
that the development and other academic deliverables were on schedule.

4.1.4 Software Requirements Specification (SRS) Development

After getting the clients' requirements, the SRS document was prepared. This process involved
gathering and revising the requirements multiple times during the meetings. The final specification
will serve as the guideline for the development of the platform's functionalities and modules.

The document also includes the non-functional and functional requirements of the app. These
requirements are the ones that are used to define the project’s overall scope.

4.1.5 App Development

The development of the app began after the team members got a brief idea of the client’s
requirements and the architecture. The implementation of the app started early as the team defined
the various modules and functionality. It was a challenging task due to the complexity of the
requirements. The team also took into account the feedback from the client during the initial
development of the app prototype. This resulted in the changes being incorporated into the prototype
after every review meeting.

6
 4.1.6 Change and Risk Documentation
Every client change was documented with the associated risks, and this was done to prevent any
potential issues later in the development process. This also provided the development team with the
necessary tools and resources to manage the project's scope. To ensure that the app adheres to the
specifications, every change was thoroughly analyzed to determine its feasibility and impact.

4.2 Mid-term Summary: Activities & Deliverables Achieved

The development of the app will be measured against the following milestones that were identified in
the project plan. This will help reveal the extent to which the project has been completed and show
the overall progress of the project. Each deliverable will also be used to determine the project's overall
progress.

Functionalities as Tasks Estimated Delivery Status

Login and Sign-Up UI for App Week 5 (Fri 16/ 09) Achieved

User Profiling Week 6 Achieved

BMI Calculation and necessary action. Week 7 Achieved

App development Activity

Blood Donation Feature Week 8 Achieved

Step counter feature Week 8 - 11 Progressing

Push Notification System based on various
Week 12 -13 Progressing
criteria
News, Events feed and generic information Week 13 Ongoing
Week 7 to 14 (Ongoing
Web Portal Ongoing
Development)
The ongoing development
API Ongoing
as and when required*

Documentation Estimated Delivery Status

Submit Project Proposal
The client's requirements and system goals
were understood. The project plan was then Week 6 (Sun 26/ 09) Achieved
prepared and submitted to the client for
approval.
Submit SRS (draft-1 to Client)
Deliverable

An unambiguous list of requirements was

developed and given for approval by the client Week 7 (Thurs 22/09) Achieved
for the app. Initial Draft.

Submit SRS (Updated draft 2 to Client)

A clear, more detailed and unambiguous list of
requirements was revised and passed to the Week 8 (Thurs 29/09) Achieved
client for approval. Updated Draft.

Submit SRS (Final .doc to Client & Academic Progressing

Week 10 to 11
Supervisor) (Submitted)
7
 The SRS clearly states all the non-functional and
functional features that will be included in the
app. Any requirements that are not stated in
the list are considered outside the scope of the
project.

Submit Mid-term Report & App Prototype .ppt

This review is designed to provide a
comprehensive overview of the project's
progress in the first half. It also includes a
written report that summarizes the various Progressing
steps that have been taken so far, as well as the Week 11
(Submitted)
obstacles that have been encountered.
Also provides a detailed analysis of the various
changes that have been made to the project's
plan.

4.3 Obstacles Encountered

During the first half of the project's development lifecycle, there were various obstacles were
encountered. These obstacles increased the likelihood that the project would encounter new risks.
The development team was able to identify these obstacles and develop effective mitigation
strategies.

Obstacles Effect on Project Mitigation

As the requirements for the app

were devised, the client
presented various new ideas
and information that the The first step in addressing
Changes/Addition of development team had to this issue was to create a
Requirements consider. To accommodate comprehensive software
these new changes to features, requirement document.
the team had to re-evaluate and
update it in the app and also in
the project documentation.

Our team understands the

Member working A member was forced to work
importance of one’s family
from home (Personal from home due to a family
and hence allowed for
Reasons) member falling ill.
remote work for a week.

One of the most common risks Since one’s health is

that were identified was the unpredictable, the team
Team Health Issues
possibility of a medical issue lead encouraged the team
affecting the work schedule. to take care of their health.

8
5 Deviations in Project Plan
The project plan deviated from its intended path. This was due to various factors that affected the
work progress and the project's overall development. Some of these included the lack of clarity on the
requirements, the increasing workload, and the unfavourable environment. The development team
used various strategies to address these issues.

5.1 Progression and Changes

Deliverable Dates Changes/ Additions Reason for Change Version
Initial Draft PP:
The first Draft of the Project Plan
− Risk Management
had simple client requirements
− Team Contract
and the system goal was
14-09 − Mark Allocation PP 1.0
understood. Submitted to the
− Functional and client for a high-level review of
Non-Functional the projects plan
Requirements
Second Draft PP:
− Feasibility Study In the second draft, a feasibility
− Draft WBS study was done and documented
− WBS Activity to give a fair idea about technical,
Table and resource and time and risk
Graphical feasibility. WBS was added with
16-09 Representation its graphical representation to
to − Project Budget outline the work activities of the
project. Likewise cost estimates PP 2.0
20-09 Estimates
Project Plan in the form of the project budget
− Gantt Chart
− Revised System in tabular format.
Architecture, Gantt Chart was developed and
Grammar and added to the document for a
Proofreading clear and concise depiction work
− Changes to WBS completion timeline.
And Gantt Chart
The client requested to remove
Final Check and budget estimates, hence we
Submission removed it but was submitted to
21-09
− Project Budget IEP supervisors for academic
to review. PP 3.0
Estimates
27-10
− Editing Client Minor changes were done to
Requested Changes improve the overall document
to the document standard.

The first Draft of the SRS had

Initial Draft high-level client requirements
10-09 − High-level with a description of system SRS 1.0
Requirements goals and features. Submitted to
the client for review of the SRS
SRS
Updated SRS In the updated SRS, system
20-09 − Detailed app features were fully described
to feature with their priority and sequence SRS 1.4
7-10 requirements from the feature from the user's
perspective.
− Proof Read,
9
 reviewed and Additional changes were minor
Finalization of but important including the
SRS. addition of mandatory fields in
user profiling including User
− Additional
Photo, Medical Conditions etc.
changes

Mid-term
from 7-10-22 to till date, this document
Review

Features Implemented
• User Registration
• Login/ Logout
As of
Prototype • User Profiling
28th of Release
BulaFit app Octob − Blood Donation as an inclusive minor feature 1
er
• BMI Calculation
• Updating of user profile which includes and captures the
change history of the weights, sugar, cholesterol and
blood pressure.

6 Risk and Risk Mitigation

6.1 Risks Identified and Mitigation
Every project has risks that need to be addressed during the development phase. These are identified
in the project plan and are then managed through the project's risk management plan. The team then
tackles these issues using the necessary tools and procedures. During the first half of the project,
various risks were also examined and mitigated.

Risk Identified Effect on Project Mitigation

Scope Creep
Changes to the scope
affecting the timeline of a
Requirements Deliverable
The first step in addressing
this issue was to create a
comprehensive software
As the requirements for
requirement document.
the app was devised, the
This document will be used
client presented various
to gather all the necessary
new ideas and information
details about the app’s
that the development
requirements, and any
team had to consider. To
changes will need approval
accommodate these new
from the relevant
changes to features, the
stakeholder.
team had to re-evaluate
The scope of the change
and update it in the app
will be analysed for validity
and also in the app and the
and feasibility to prevent it
requirements documents
from happening during the
development process.

10
 Since our app deliverable is
to provide a cross-platform
solution both for Android
and iOS devices, but due to
Technology Hindrance APPLE device security
iOS testing practices that allow only
in-app installs. Our team
was not able to test the
prototype release on any
physical iOS devices.
We accepted this risk since
it was out of the team's
control.
To compensate for this, we
are testing release 1 on iOS
emulators on our
machines to mimic the
actual testing.

Our team understands the

Remote Work A member was forced to
importance of one’s family
Member working from work from home due to a
and hence allowed for
home (Personal Reasons) family member falling ill.
remote work for a week.
Social activities are also
important in the work
environment hence our
team also participated in To meet schedules, these
External Factors
such activities as (USP tasks were catered for by
Social activities and IEP
open day, Fiji day either doing overtime or
Bonding Exercises
celebration, AWS taking it home.
emersion day seminar
etc.). This put the team
slightly behind schedule.
One of the most common
Since one’s health is
risks that were identified
unpredictable, the team
was the possibility of a
lead encouraged the team
medical issue affecting the
Team Member's Health to take care of their health.
work schedule. For
Issues And to meet schedules,
instance, a colleague got
tasks should be catered for
sick and was not ready to
by either doing overtime or
start working for a couple
taking it home.
of days.

11
7 Team Interactions
7.1 Team Member Interactions
• Viber platform used for fast & efficient communication.
• Periodically updates of upcoming activities and project workload was addressed by the team
leader
• For more sensitive issues, Stand-up meetings would be held, and minutes would be taken.
• All issues that were out of the member’s or team leaders' control were notified to the IEP
coordinator and the project managers, respectively.

7.2 Client Interactions

• Communication- Initial meet and greet session done, fortnightly meetings and need-be
communication via email.
• Viber for fast & efficient communication.
• Most of the communication regarding implementation was discussed in fortnightly meetings
• All important information such as improvements and requirements change and
documentation improvements were noted and implemented effectively.

12
8 Timeline – Deliverables
8.1 Project Timeline

Figure 3: Full-scale Project Timeline

Timeline jpeg link (for clearer quality): https://drive.google.com/file/d/17m-dhlUEQd1kFF52NR0TGKFMqgZn6T2A/view?usp=sharing

13
8.2 Updated Gantt Chart

Figure 4: Updated Gantt Chart

14
8.3 Remaining Deliverables Timeline

Figure 5: Second half of Project, Remaining Deliverables timeline

15
9 Mark Allocation Sheet

10 Appendix
10.1 Risk Identification Breakdown

The risks are divided into four categories as listed below:

i. Technical risks: risks involved in the requirements and the technologyused.

ii. Management risks: these are risks regarding the project, team, and processes. It looks at
communication, scheduling, and other processeswith the project. (MacKay, 2020)

iii. Organizational risks: risks that look at the resources and culture of theorganization. It looks
at the finance, staff, resources, and more of theorganization.

External Risks: these are risks that are not in the other three categories

16