System Analysis Of UNICEF Child Care Project †MyAssignmenthelp.com

Question: Discuss about the System Analysis Responsibilities of Global Business System The Project UNICEF Child Care. Answer: Introduction: The main aim of this report is to provide the system analysis responsibilities of Global Business System. This project deals with system analysis known as UNICEF Child Care. The UNICEF Chile Care is an organization that provides caring as well as supervision for children from age six week to an age of thirteen. UNICEF provides children with food, babysitters, teachers and many other services. The Chairman of UNICEF wants to make the manual system as an automated one so that the payments can be made online. He also wants to make the inventory system better so that there will be less wastage of materials in the organization. This report includes the approaches that are involved while developing the system for UNICEF Chile Care. All the functional as well as non-functional requirements that are needed to develop the online software is described in this report. The cost analysis for making the system is described in this report along with a work breakdown structure. There are many stakeholders involved in this project that helps to make the system. The list of stakeholders are also described in detailed in this project. Approaches to Systems Development In order to select an approach for developing information system, the characteristics of the proposed system are required to be described. The system will be a cloud based application. The system will collect input from the end users. The system will forecast various things like required needed supply and child registration. The system will also accept payment from parents. After evaluating the features of the system, it is clear that the system development project will be a simple approach. The system is proposed on straight forward and simple ideas. The main purpose of the system will be processing collected data and generating reports. The project will be a short term one. The waterfall model is the perfect approach for system development. The waterfall model has five phases (Alshamrani and Bahattab 2015). These phases are system requirement gathering as well as analysis, designing, development, testing and deployment. The system functions are identified in system requirement gathering and the analysis phase. In the phase, analysts will gather business requirements and convert those into system requirements. The system requirements are input of the design phase. The output of the design phase are well designed system diagrams like class, use case, database and many more. The designs are used for creating the units of the system. Based on the use case diagram, the interaction of the user and system is determined (Saxena and Upadhyay 2016). The designers use the use case diagram to employ interaction in the interface. The system units are tested until most of the errors are eliminated. At last, the system will be deployed in UNICEF environment. Functional and Non-Functional Requirements Functional requirements: Functional requirements mainly define system operations. The functional requirements of UNICEF Child Care System are as following. Online Payment: The system will include a payment gateway into its core. The parents will be depositing fees online through this payment gateway. The end users will enter their card type, number and other required details. For verification, a message will be sent to the card holders registered mobile number. The message will have the OTP. The user will enter OTP and confirm payment. Interface: The system will have two interfaces. One is for the parents and external end users. The other is for the staff and management of UNICEF. The interface will act as the intermediate communication medium between user and system. The interface will be developed after identifying and evaluating the interaction and interface diagrams. Database: The database will record the organizational data. The system will use the stored data to generate information through data processing operation. The data are not only useful in daily operations but also offer the opportunity of creating accurate reports. Reporting: The system will generate reports based on the stored data and processed information. These reports will be generated monthly and yearly basis. The report will provide an idea to the management about how much supply is required for a specific month. Automation: The automation of the system is a crucial factor. The system will be placing orders automatically. The system will automate the back processes. This will provide enough time to the staff to concentrate on core activities. Non-Functional Requirements: Non-functional requirements of a system define how good the system will function. Scalability: The scalability is one of the most required non-functional requirement of the system. The system resources will be increased or decreased based on the business need (Dabbagh and Lee 2014). The management of UNICEF will be responsible for determining the resource usage. Security: An important non-functional requirement of the system is the security. The system will hold and process various user data and sensitive business data. Securing these data and information from the intruders. The system will be audited every three months to identify any flaw in the security (Khanet al. 2016). The servers will be configured to prevent DoS attacks. Real time data flow: System mainly shows real time data to the users. As soon as some data is inserted into a system, users will be able to see the data, if authorized to see it. Cost Benefit Analysis The entire cost and the benefit of the proposed system is defined by the project cost benefit analysis. The cost benefit analysis is done through tangible and intangible factors. The cost of labor, equipment, total cost of project, maintenance cost, support services and many other factors are considered in this analysis. The cost of the project is $225,000. Total benefit from the system is $507,043.00. Break Even Analysis ROI 1.87 Breakeven analysis Yearly NPV Cashflow ($33,608.00) $33,254.72 $68,022.43 $105,086.75 $150,612.33 $183,674.77 Overall NPV Cashflow ($33,608.00) ($353.28) $67,669.14 $172,755.89 $323,368.23 $507,043.00 Project Breakeven occurs between year 1 and 2 1.01 Actual Breakeven Cost/Benefit Analysis for the Recovery project Category Year 0 Year 1 Year 2 Year 3 Year 4 Year 5 Value of benefits $20,000 $25,500 $15,570 $27,500 $35,260 Development costs ($225,000) Annual expenses ($12,500) ($13,150) ($11,250) ($13,570) ($10,230) Net benefit/costs ($70,000) $7,500 $12,350 $4,320 $13,930 $25,030 Discount factor $1 0.9091 0.8264 0.7513 0.6830 0.6209 Net present value ($55,000) $6,818 $10,207 $3,246 $9,514 $15,542 Cumulative NPV ($25,000) ($18,182) ($7,975) ($4,730) $4,785 $20,3 Task Name Duration Start Finish Predecessors UNICEF Child Care System 72 days Thu 4/5/18 Fri 7/13/18 Pre-Project Planning 7 days Thu 4/5/18 Fri 4/13/18 Define the business opportunity 2 days Thu 4/5/18 Fri 4/6/18 Identify a viable for the project 2 days Mon 4/9/18 Tue 4/10/18 2 Assess the feasibility 3 days Wed 4/11/18 Fri 4/13/18 3 Project Initiation 14 days Mon 4/16/18 Thu 5/3/18 Garnering initial support and funding for the project 2 days Mon 4/16/18 Tue 4/17/18 4 Actively working with stakeholders to initially model the scope of the system 3 days Wed 4/18/18 Fri 4/20/18 6 Starting to build the team 1 day Mon 4/23/18 Mon 4/23/18 7 Modeling an initial architecture for the system 3 days Tue 4/24/18 Thu 4/26/18 8 Setting up the environment 3 days Fri 4/27/18 Tue 5/1/18 9 Estimating the project 2 days Wed 5/2/18 Thu 5/3/18 10 Construction Iterations 24 days Fri 5/4/18 Wed 6/6/18 Collaborating closely with both our stakeholders and with other developers 2 days Fri 5/4/18 Mon 5/7/18 11 Implementing functionality in priority order 3 days Tue 5/8/18 Thu 5/10/18 13 Analyzing and designing 4 days Fri 5/11/18 Wed 5/16/18 14 Ensuring quality 7 days Thu 5/17/18 Fri 5/25/18 15 Regularly delivering working solutions 3 days Mon 5/28/18 Wed 5/30/18 16 Testing 5 days Thu 5/31/18 Wed 6/6/18 17 Transition 17 days Thu 6/7/18 Fri 6/29/18 Final testing of the system 2 days Thu 6/7/18 Fri 6/8/18 18 Rework 4 days Mon 6/11/18 Thu 6/14/18 20 Finalization of any system and user documentation 2 days Fri 6/15/18 Mon 6/18/18 21 Training 8 days Tue 6/19/18 Thu 6/28/18 22 Deploy the system 1 day Fri 6/29/18 Fri 6/29/18 23 Production 5 days Mon 7/2/18 Fri 7/6/18 Help desk to assist users 2 days Mon 7/2/18 Tue 7/3/18 24 Run and monitor systems 3 days Wed 7/4/18 Fri 7/6/18 26 Retirement 5 days Mon 7/9/18 Fri 7/13/18 The system is being complete replaced 5 days Mon 7/9/18 Fri 7/13/18 27 Figure 1: Gantt Chart of the Project (Source: Created by Author) Figure 2: Work Breakdown Structure of the Project (Source: Created by Author) The project will start at 5th April, 2018. The project is created as per the activities defined in the waterfall model. The work breakdown structures are represented through three levels. The activities in the WBS are the activities mentioned in the Gantt chart. System Information Requirement Investigation Techniques Stakeholders: Stakeholders of the project are UNICEF staff, management executives, parents, children, suppliers and government. The staff and management executives are internal stakeholders of the project. The parents, children, supplier and governments are external stakeholders of the project. All the stakeholders will participate in the project. The stakeholders will inform the project manager or analysts about their requirements from the system. They will also take part in interaction and usability testing. Investigation Techniques: The project manager and analysts will consider following three investigation techniques in this project. Interviews: The analysts will arrange interview with the individual stakeholders. In the interview they will gather user requirement information. Each of the stakeholders will communicate freely with the interviewer. The interviewer will ask them various questions and the stakeholders will provide answer. The interviewer will record all the questions and answers in a document. Questionnaire: The analyst will create a set of questions. These questions will be asked to the stakeholders. All the questions will be pre-determined. An electronic form will be provided to the participants. They will fill the form and send it to the analyst. Survey: The survey will be done through analyzing the documents and business processes of UNICEF. The analyst will gather various hidden information and communicate with the management. In the meeting with the management, the analyst will ask various questions regarding the identified data. Justification: The investigation techniques used in the project are supportive to one another. The interview will reveal what individual end users want. The survey will provide idea and information of core processes. Reflection and Conclusion From this report, I learnt the details about making the system automated. There are many approaches that can help to make a system automated. I have learnt functional as well as non-functional requirements that are used to make the system. This report detailed the structure of the software to make the system of the UNICEF Child Care. This report details all the requirements that are needed to make the system online so that the money can be submitted online. As the system was not automated, the organization was facing loss regarding the stocks of the organization. All the details are system development are described clearly in this report. Bibliography: Alshamrani, A. and Bahattab, A., 2015. A comparison between three SDLC models waterfall model, spiral model, and Incremental/Iterative model. International Journal of Computer Science Issues (IJCSI), 12(1), p.106. Boardman, A.E., Greenberg, D.H., Vining, A.R. and Weimer, D.L., 2017. Cost-benefit analysis: concepts and practice. Cambridge University Press. Brace, I., 2018. Questionnaire design: How to plan, structure and write survey material for effective market research. Kogan Page Publishers. Dabbagh, M. and Lee, S.P., 2014. An approach for integrating the prioritization of functional and nonfunctional requirements. The Scientific World Journal, 2014. Eskerod, P., Huemann, M. and Savage, G., 2015. Project stakeholder managementpast and present.Project Management Journal, 46(6), pp.6-14. Khan, S., Babar, M., Khan, F., Arif, F. and Tahir, M., 2016. Collaboration Methodology for Integrating Non-Functional Requirements in Architecture. the Journal of Applied Environmental and Biological Sciences (JAEBS), 6, pp.63-67. Lock, D., 2017. The essentials of project management. Routledge. Saxena, A. and Upadhyay, P., 2016. Waterfall vs. prototype: Comparative study of sdlc. Imperial Journal of Interdisciplinary Research, 2(6). Schwalbe, K., 2015. Information technology project management. Cengage Learning. Torriti, J. and Ikpe, E., 2014. CostBenefit Analysis. In Encyclopedia of Law and Economics (pp. 1-8). Springer New York. Tozluoglu, M., Mao, Y., Bates, P.A. and Sahai, E., 2015. Costbenefit analysis of the mechanisms that enable migrating cells to sustain motility upon changes in matrix environments. Journal of the Royal Society Interface, 12(106), p.20141355. Zablotsky, B., Black, L.I., Maenner, M.J., Schieve, L.A. and Blumberg, S.J., 2015. Estimated prevalence of autism and other developmental disabilities following questionnaire changes in the 2014 National Health Interview Survey.