UNICEF Child Care: System Development, Requirements And Cost Analysis
Approach to Systems Development
The UNICEF Child care go is a special project designed for the underprivileged children. In this project the parents of some children buy products for their children from UNICEF and from the purchase of the product some revenue is generated which goes to the development of the underprivileged children. However for the process the organization wants to implement and automated system that would help the organization in automating their procedures of payment from the parents.
For the development of the system the prototype model approach should be adopted. This model is very useful in situation where the client are sent a prototype before delivery of the actual project to the clients. In the UNICEF project the payment system would be sent to the client for testing. They would be required to provide some feedback for the system so that there can be improvements in the actual system. Hence, the choice of the prototype model is a justified one. The main phases of the prototype model are: Planning, prototype design, and customer feedback and project delivery.
The system requirement can be classified into Functional requirements and Non-Functional Requirement:
- The system needs to provide the users with an efficient payment option where the user can enter their details and make the payments online.
- The system should also be able to provide the users with an automated accounting system.
Non-Functional Requirements:
- Data Integrity: The system should be able to provide an efficient data security as a large scale of user data and system data would be at risk if the functionality is not maintained by the system.
- Reliability: The system should be reliable as the system would be dealing with the financial aspect of the organization.
The total cost of the system is provided below:
|
Cost Benefit Analysis for UNICEF Case Study |
|
|
Hardware |
$ 75,000.00 |
|
Software |
$ 75,000.00 |
|
Development team salaries |
$ 70,000.00 |
|
Training |
$ 5,000.00 |
|
Total Development Cost |
$ 225,000.00 |
|
Maintenance |
$ 6,000.00 |
|
Changes |
$ 3,000.00 |
|
Operational Labor |
$ 50,000.00 |
|
Total Operational Cost |
$ 59,000.00 |
|
Approximate salary savings |
$ 54,000.00 |
|
Reduced Food Wastage |
$ 60,000.00 |
|
Total Benefit |
$ 114,000.00 |
|
Discount Rate Used |
6.00% |
Table 1: Cost Inputs
Source: (Created by Author)
The cost benefit analysis of the project is described in the table below:
|
Project Cost-Benefit Analysis |
||||||||
|
Analysis Variables: |
||||||||
|
Discount Rate Used |
6.00% |
|||||||
|
Annual Benefits |
$ 114,000.00 |
|||||||
|
Annual Operational Costs |
$ 59,000.00 |
|||||||
|
One-Time Development Cost |
$ 225,000.00 |
|||||||
|
Year of Project |
||||||||
|
Start |
First Year |
Second Year |
Third Year |
Fourth Year |
Fifth Year |
TOTALS |
||
|
Economic Benefit |
$0.00 |
$ 114,000.00 |
$ 114,000.00 |
$ 114,000.00 |
$ 114,000.00 |
$ 114,000.00 |
||
|
Discount Rate |
1.0000 |
0.9434 |
0.8900 |
0.8396 |
0.7921 |
0.7473 |
||
|
PV of Benefits |
$0.00 |
$107,547.17 |
$101,459.59 |
$95,716.60 |
$90,298.68 |
$85,187.43 |
||
|
NPV of all BENEFITS |
$0.00 |
$ 107,547.17 |
$ 209,006.76 |
$ 304,723.36 |
$ 395,022.04 |
$ 480,209.47 |
$ 480,209.47 |
|
|
One-Time COSTS |
$(225,000.00) |
|||||||
|
Recurring Costs |
$0.00 |
$ (59,000.00) |
$ (59,000.00) |
$ (59,000.00) |
$ (59,000.00) |
$ (59,000.00) |
||
|
Discount Rate |
1.0000 |
0.9434 |
0.8900 |
0.8396 |
0.7921 |
0.7473 |
||
|
PV of Recurring Costs |
$0.00 |
$ (55,660.38) |
$ (52,509.79) |
$ (49,537.54) |
$ (46,733.53) |
$ (44,088.23) |
||
|
NPV of all COSTS |
$(225,000.00) |
$ (280,660.38) |
$ (333,170.17) |
$ (382,707.71) |
$ (429,441.23) |
$ (473,529.46) |
$ (473,529.46) |
|
|
Overall NPV |
$ 6,680.01 |
|||||||
|
Overall ROI |
0.0141 |
Table 2: Cost Benefit Analysis
Source: (Created by Author)
Project Schedule
|
Task Name |
Duration |
Start |
Finish |
Predecessors |
Resource Names |
|
UNICEF Online Payment System |
126 days |
Wed 2/6/19 |
Wed 7/31/19 |
||
|
project Initiation |
6 days |
Wed 2/6/19 |
Wed 2/13/19 |
||
|
Client Meeting |
1 day |
Wed 2/6/19 |
Wed 2/6/19 |
||
|
Problems discussion session |
1 day |
Thu 2/7/19 |
Thu 2/7/19 |
3 |
Project Manager, Technical head |
|
Brainstorming sessions |
1 day |
Fri 2/8/19 |
Fri 2/8/19 |
4 |
Back End Developer, Front End Developer, Project Manager, Software Analyst |
|
Proposing solutions to the clients |
3 days |
Mon 2/11/19 |
Wed 2/13/19 |
5 |
Project Manager, Technical head |
|
Project Approval |
0 days |
Wed 2/13/19 |
Wed 2/13/19 |
6 |
Technical head |
|
Project Planning |
19 days |
Thu 2/14/19 |
Tue 3/12/19 |
||
|
Identifying system requirements |
1 day |
Thu 2/14/19 |
Thu 2/14/19 |
7 |
Project Manager, Technical head |
|
Project Schedule Estimation |
2 days |
Fri 2/15/19 |
Mon 2/18/19 |
9 |
Project Manager, Technical head |
|
Deciding the budget of the project |
1 day |
Tue 2/19/19 |
Tue 2/19/19 |
10 |
Project Manager, Finance Manager |
|
Cost benefit analysis of the project |
2 days |
Wed 2/20/19 |
Thu 2/21/19 |
11 |
Project Manager, Finance Manager |
|
Identification of hardware requirements |
1 day |
Fri 2/22/19 |
Fri 2/22/19 |
12 |
Back End Developer, Front End Developer, Project Manager |
|
Hardware procurement |
5 days |
Mon 2/25/19 |
Fri 3/1/19 |
13 |
Technicians, Project Manager, Hardware[1] |
|
Software set up on the system of the organization |
3 days |
Mon 3/4/19 |
Wed 3/6/19 |
14 |
Back End Developer, Front End Developer, Software |
|
Assembling the project team |
4 days |
Thu 3/7/19 |
Tue 3/12/19 |
15 |
Project Manager |
|
Project plan completion |
0 days |
Tue 3/12/19 |
Tue 3/12/19 |
16 |
Project Manager |
|
Prototype development |
13 days |
Wed 3/13/19 |
Fri 3/29/19 |
||
|
GUI development of the project |
7 days |
Wed 3/13/19 |
Thu 3/21/19 |
17 |
Front End Developer, Technicians, Software |
|
Delivery of the prototype to the clients |
2 days |
Fri 3/22/19 |
Mon 3/25/19 |
19 |
Project Manager |
|
Feedback of the clients |
4 days |
Tue 3/26/19 |
Fri 3/29/19 |
20 |
Project Manager |
|
Completion of the prototype phase |
0 days |
Fri 3/29/19 |
Fri 3/29/19 |
21 |
|
|
Project Execution |
53 days |
Mon 4/1/19 |
Wed 6/12/19 |
||
|
development of the backend |
14 days |
Mon 4/1/19 |
Thu 4/18/19 |
22 |
Front End Developer, Technicians, Software |
|
development of the front end |
14 days |
Fri 4/19/19 |
Wed 5/8/19 |
24 |
Back End Developer, Software |
|
Database Designing |
15 days |
Thu 5/9/19 |
Wed 5/29/19 |
25 |
Back End Developer, Front End Developer, Technicians, Software |
|
System integration |
10 days |
Thu 5/30/19 |
Wed 6/12/19 |
26 |
Back End Developer, Front End Developer |
|
Completion of execution phase |
0 days |
Wed 6/12/19 |
Wed 6/12/19 |
27 |
Back End Developer, Front End Developer, Project Manager |
|
Project Testing |
19 days |
Thu 6/13/19 |
Tue 7/9/19 |
||
|
project testing |
4 days |
Thu 6/13/19 |
Tue 6/18/19 |
28 |
Software Analyst, Software |
|
Risk Identification |
5 days |
Wed 6/19/19 |
Tue 6/25/19 |
30 |
Project Manager, Software Analyst |
|
Risk mitigation |
10 days |
Wed 6/26/19 |
Tue 7/9/19 |
31 |
Back End Developer, Front End Developer, Software, Software Analyst |
|
Testing phase completion |
0 days |
Tue 7/9/19 |
Tue 7/9/19 |
32 |
Project Manager, Software Analyst |
|
Project Closure |
16 days |
Wed 7/10/19 |
Wed 7/31/19 |
||
|
Selection of domain |
10 days |
Wed 7/10/19 |
Tue 7/23/19 |
33 |
Technicians, Back End Developer, Front End Developer, Project Manager |
|
uploading the system on the selected domain |
1 day |
Wed 7/24/19 |
Wed 7/24/19 |
35 |
Project Manager |
|
Documentation |
3 days |
Thu 7/25/19 |
Mon 7/29/19 |
36 |
Technicians, Project Manager |
|
Team dispersion |
2 days |
Tue 7/30/19 |
Wed 7/31/19 |
37 |
Project Manager |
|
Project Sign Off |
0 days |
Wed 7/31/19 |
Wed 7/31/19 |
38 |
Technicians, Back End Developer, Finance Manager, Front End Developer, Project Manager, Software Analyst, Technical head |
Table 3: Project Schedule
Source: (Created by Author)
The table below provides the details of the stakeholders that are involved with the project:
|
Stakeholder Name |
Stakeholder Designation |
Role |
|
Bruno Gomez |
Project Manager |
The project manager is one of the main stakeholders of the system. They play a key role is all the sectors of the project. |
|
Jerome Boeteng |
Finance Manager |
The finance manager looks after the financial aspects of the project such as the budget and the cost benefit analysis for the project. |
|
Mats Hummels |
Technical Head |
The technical head is responsible taking all the key decisions of the project. |
|
Darcy Scott |
Front End Developer |
The front development and the prototype development of the project is handled by the front end developer. |
|
Arturo Vidal |
System Analyst |
The system analysts is responsible for checking the risks involved with the system and provide insights for the possible risk mitigation techniques for the systems |
|
James rodriguez |
Back end developer |
The back developer is entrusted with the development of the backend coding and integration of the system with the database of the organization. |
|
John |
Chairman |
The chairman is the one who finally signs the contract and acknowledgement of the chairman is very important for any of the process of the project. |
Table 3: Stakeholder list
Source: (Created by Author)
The description of the investigation techniques to be used for the assessment of the system are provided below:
Checking all the access points to the system that is to be developed: The system analyst would be testing all the entrance point to the system and try to seal them off so that no external intrusions take place in the systems.
Interface Usability testing: Interface testing is a very efficient form for testing the system. The navigation of the system and the responsive testing would help the team to identify the possible drawbacks of the system and improve them significantly.
Reflections and Conclusions
After the construction of the report we are able to understand the concepts of project management and this would help us in implementation of a real project in future. This subject also provides us with the concepts of information system.
For conclusion it can be said that the report is very useful in providing us with the information about the project and details of project construction. The schedule and budget criteria is also provided in the report.
References
Herrnstein, H.A., 2015. The integration of project management and organizational change management is now a necessity. International Journal of Project Management, 33(2), pp.291-298.
Joslin, R. and Müller, R., 2015. Relationships between a project management methodology and project success in different project governance contexts. International Journal of Project Management, 33(6),pp.1377-1392.
Kerzner, H. and Kerzner, H.R., 2017. Project management: a systems approach to planning, scheduling, and controlling. John Wiley & Sons.
Laudon, K.C. and Laudon, J.P., 2016. Management information system. Pearson Education India.
Muller, R., 2017. Project governance. Routledge.
Nicholas, J.M. and Steyn, H., 2017. Project management for engineering, business and technology. Taylor & Francis.
Schwalbe, K., 2015. Information technology project management. Cengage Learning.
Serrador, P. and Pinto, J.K., 2015. Does Agile work?—A quantitative analysis of agile project success. International Journal of Project Management, 33(5), pp.1040-1051.
Turner, R., 2016. Gower handbook of project management. Routledge.