Professional Documents
Culture Documents
Cycles
Name Ananda Aditya Surya
Note: Read Project Definition Section in previous Module Project Brief. The project assumed for
these questions are based on that scenario.
Project Scenario:
Employee mobility is at its peak now and will continue to grow in the future as more and more
jobs becoming mobile-enabled. Employers and HR departments have to understand how it
affects their organization to successfully overcame its challenges.
By analysing employee turnover, organizations can understand its pace, effects and root causes
so they can take actions.
Proposed Solution: To create a dashboard so that we can track the employee headcounts, the
attrition rate and the reasons on why they leave
Note: Read Project Definition Section in previous Module Project Brief. The project assumed for
these questions are based on that scenario.
Technical Environment -
Guidelines -
Duration 30 mins
1. Introduction
1.1 Overview of the Project
Nowadays, employee mobility will grow and grow in the future into mobile-enabled
technology. Organization needs to create system that analyzing employee turnover use a
dashboard that can represent and track the employee headcount, the attrition rate, and the
reason why they leave their jobs. Based on that data, the organization can take action to
overcome the employee mobility problem
1.2 Objectives of the Project
• A system that can help for analyzing the employee turnover
• The system that mobile-enabled technology
• The system representing and record the data about employee headcount, the attrition rate,
and the reason why they leave their jobs in the form of a dashboard
1.3 The Need for the Project
on organization view, this system is very helpful because the process of data collection is done
by machine and the visualization of the data is easy to understand and manage. The system
makes a flow that automate the process of data collection and the data is visualized into a
dashboard to make it easier to understand the calculation of the data
1.4 Overview of Existing Systems and Technologies
Organization current system haven’t used an automation process in data collection. The
procedure of the current system is giving the form into the employees and tell them to fill the
form. After the form has been filled, the data will be inputted into the database manually. The
calculation of the data also done manually that makes the data tracking have some calculation
mistakes
1.5 Scope of the Project
The system will be used by the organization employee who works in collecting data and it also
used by the other employees who will fill the survey questions. Meanwhile, monitoring and
maintenance of the system are IT employee responsibility
1.6 Deliverables.
The system used the automation process, that is mean when the employees have submitted
their answer, it is automatically stored into the database sequentially. And the data is auto-
transferred into dashboard accurately. The system is published as a web application, so that
the user does not need to install an application in their devices.
2. Feasibility study
2.1 Financial Feasibility
Form
Database
Dashboard
2.3 Operational Feasibility
Describing the processes to each department what can they do in the system and how can
they do that. Each department have their own steps and processes.
2.4 Resource and Time Feasibility
the system will work effectively and efficiently to reduce the consumption of resources and
time
2.5 Risk Feasibility
Any risk has been considered and this system is bringing more advantages and less risk. So, it’s
system is low-risk high return. Upcoming problem may come in the developing process. It has
been considered to make the system don’t get a high impact of it.
2.6 Social/Legal Feasibility
All documents refer to this system has been created to make the system is legal to use.
2.7 Alternate Systems
Alternative system is already considered but it does not have a big change of this system. A
little change will be executed if the system is not work properly and not like the expected
result. Outsourcing maybe executed, if the system never works as the organization
requirements.
3. Consideration
The app is expected to hit:
• Technical consideration: The web is expected to work properly as same as the
plan. There are no bugs and error after the system completely deployed.
• Economic consideration: the cost of making the system must be less than the
revenue. So, the web will be profitable to the organization.
• Social consideration: the app is user friendly and easy to use, even for
beginners. The web also strives to have a good design so the user is comfortable
to use the web