ICF Information System Implementation In Cloud

Discuss about the Understanding Success of an Information System Project.

The ICF or International Charity Foundation is willing to implement an Information System in their environment.  The system will be implemented in the cloud. The system development project is developed with the objective of changing the paper-based works into automated processes.

The report consists of selection of system development method, description of system requirements and many more. The report also consist of cost benefit analysis along with project schedule.

The information system of ICF will be consisting of two parts internal system and website.

The IS development approach: As the requirements of the system is not completely clear, the system will be developed using adaptive prototyping model.

1. Planning: The planning phase consist of team member employing, scheduling, cost estimation and other tasks
2. Requirement gathering: The user and business requirements of the system will be collected in this phase. The requirements are prioritized and selected.

• Prototyping:The prototyping process will be consisting of the phases named quick design, build prototype, customer evaluation and refining developed prototype.

1. Iterations: The iterations part of this adaptive SDLC method consist of the phases named design, coding, testing and maintenance.

Justification for Selecting Adaptive Prototyping Model Approach: 

1. The adaptive approach will allow incorporating new requirements
2. The users of the system can have idea about the proposed system

Functional Requirements: 

1. Donation:The donors can donate capital using the website only.
2. Receipts:The system will generate receipt immediately after a donation is successfully done. The receipt will be sent to donor’s email.

• Data Storage:The system will store the data like donor, donations, participants, operational information many more in a structured way.

Non-Functional Requirement: 

1. Security:The system should be properly secured so that donors bank account details are not revealed to cyber criminals.
2. Usability: The donors and staff must be able to use the system easily.

• Availability:The system should be accessed 24*7.

The organization will be benefitted due to using cost benefit analysis for non-critical financial decision. The cost of development, projected income every year, cost of operation all the financial factors will be highlighted in the CBA. This will allow the project manager to strengthen the positiveness of the project.

Cost benefit analysis for Global Business System
	Year 0	Year 1	Year 2	Year 3	Year 4	Year 5
Overall savings	$0	$40,000	$35,000	$30,000	$35,000	$25,000
Development cost	($67,812)	$0	$0	$0	$0	$0
Maintenance Cost	($10,000)	($3,500)	($3,500)	($3,500)	($3,500)	($3,500)
Net benefit/costs	$19,000	$19,000	$19,000	$19,000	$19,000	$19,000
Net cash flow	($58,812)	$36,500	$31,500	$26,500	$31,500	$21,500
Discount factors
Discount rate	10%
Year Index	0	1	2	3	4	5
Discount factor	1	0.91	0.83	0.75	0.68	0.62
Discounted flows
Cost	($67,812)	($3,182)	($2,893)	($2,630)	($2,391)	($2,173)
Benefit	$27,000	$32,000	$35,000	$40,000	$45,000	$50,000
Net	($40,812)	$28,818	$32,107	$37,370	$42,609	$47,827
Cumulative	($40,812)	($11,994)	$20,114	$57,484	$100,093	$147,920
Net present value	$147,920
ROI	30%
Payback Analysis
	Years	Months
	1	4
Payback Period in Years	1.37

WBS	Task Name	Duration	Start	Finish	Predecessors
0	ICF System Development	72 days	Thu 8/23/18	Fri 11/30/18
1	Planning	13 days	Thu 8/23/18	Mon 9/10/18
1.1	Hiring Project Team Members	2 days	Thu 8/23/18	Fri 8/24/18
1.2	Creating Project Scope	2 days	Mon 8/27/18	Tue 8/28/18	2
1.3	Creating Project Deliverable	2 days	Wed 8/29/18	Thu 8/30/18	3
1.4	Estimate Project Cost	1 day	Fri 8/31/18	Fri 8/31/18	4
1.5	Create a Schedule	1 day	Mon 9/3/18	Mon 9/3/18	5
1.6	Divide Responsibilities Among Team Members	1 day	Tue 9/4/18	Tue 9/4/18	6
1.7	Meeting with Stakeholders	3 days	Wed 9/5/18	Fri 9/7/18	7
1.8	Acceptance of Project Scope and Deliverables	1 day	Mon 9/10/18	Mon 9/10/18	7,8
1.9	Planning Phase Complete	0 days	Mon 9/10/18	Mon 9/10/18	9
2	Requirement Gathering	7 days	Tue 9/11/18	Wed 9/19/18
2.1	Interview with Stakeholders	2 days	Tue 9/11/18	Wed 9/12/18	10
2.2	Create Questionnaire	1 day	Thu 9/13/18	Thu 9/13/18	10,12
2.3	Store the Questionnaire Results	1 day	Fri 9/14/18	Fri 9/14/18	13
2.4	Observation Method	4 days	Fri 9/14/18	Wed 9/19/18	10,12,13
2.5	Document all the Requirements	1 day	Mon 9/17/18	Mon 9/17/18	12,13,14
2.6	Prioritize Requirements	1 day	Tue 9/18/18	Tue 9/18/18	16
2.7	Requirement Gathering Phase Complete	0 days	Tue 9/18/18	Tue 9/18/18	17
3	Quick Design	2 days	Wed 9/19/18	Thu 9/20/18
3.1	Use Case Design	1 day	Wed 9/19/18	Wed 9/19/18	18
3.2	UX Design	1 day	Thu 9/20/18	Thu 9/20/18	20
3.3	Quick Design Complete	0 days	Thu 9/20/18	Thu 9/20/18	21
4	Build Prototype	2 days	Fri 9/21/18	Mon 9/24/18
4.1	Create User Interface	1 day	Fri 9/21/18	Fri 9/21/18	22
4.2	Make the Interface Clickable	1 day	Mon 9/24/18	Mon 9/24/18	24
4.3	Build Prototype Complete	0 days	Mon 9/24/18	Mon 9/24/18	25
5	Customer Evaluation of Prototype	3 days	Tue 9/25/18	Thu 9/27/18
5.1	Customer Use the Prototype	1 day	Tue 9/25/18	Tue 9/25/18	26
5.2	Customer Provide Reviews of Prototypes	1 day	Wed 9/26/18	Wed 9/26/18	28,26
5.3	The Customer Reviews are Categorized	1 day	Thu 9/27/18	Thu 9/27/18	29,26,28
5.4	Customer Evaluation of Prototype Complete	0 days	Thu 9/27/18	Thu 9/27/18	30
6	Refine Requirements Incorporating Customer Suggestions	4 days	Fri 9/28/18	Wed 10/3/18
6.1	Analyze the Customer Review	1 day	Fri 9/28/18	Fri 9/28/18	31
6.2	Prioritize Reviews	1 day	Mon 10/1/18	Mon 10/1/18	33
6.3	Select Changes to be Done	1 day	Tue 10/2/18	Tue 10/2/18	34
6.4	Create Documentation	1 day	Wed 10/3/18	Wed 10/3/18	35
6.5	Refine Requirements Incorporating Customer Suggestions Completion	0 days	Wed 10/3/18	Wed 10/3/18	36
7	Design	5 days	Thu 10/4/18	Wed 10/10/18
7.1	Create System Architecture	1 day	Thu 10/4/18	Thu 10/4/18	37
7.2	UML Design	2 days	Fri 10/5/18	Mon 10/8/18	39
7.3	Database Design	2 days	Fri 10/5/18	Mon 10/8/18	39
7.4	Convert Functional Requirements into System Design	2 days	Tue 10/9/18	Wed 10/10/18	39,41
7.5	Design Phase Complete	0 days	Wed 10/10/18	Wed 10/10/18	42
8	Coding	22 days	Thu 10/11/18	Fri 11/9/18
8.1	Develop the System Interface	8 days	Thu 10/11/18	Mon 10/22/18	43
8.2	Create the Backend Coding	10 days	Tue 10/23/18	Mon 11/5/18	45
8.3	Create the Database	4 days	Tue 11/6/18	Fri 11/9/18	43,46
8.4	Coding Phase Complete	0 days	Fri 11/9/18	Fri 11/9/18	47
9	Testing	10 days	Mon 11/12/18	Fri 11/23/18
9.1	Debugging the Backend Code	2 days	Mon 11/12/18	Tue 11/13/18	48
9.2	White Box Testing	3 days	Wed 11/14/18	Fri 11/16/18	50
9.3	Unit Testing	3 days	Mon 11/19/18	Wed 11/21/18	51
9.4	System Functionality Testing	2 days	Thu 11/22/18	Fri 11/23/18	52
9.5	Testing Phase Complete	0 days	Fri 11/23/18	Fri 11/23/18	53
10	Maintenance	5 days	Mon 11/26/18	Fri 11/30/18
10.1	Deploy the System in to Cloud	1 day	Mon 11/26/18	Mon 11/26/18	54
10.2	Maintain the System	2 days	Tue 11/27/18	Wed 11/28/18	56
10.3	Post Implementation Review	2 days	Thu 11/29/18	Fri 11/30/18	57
10.4	Maintenance Phase Complete	0 days	Fri 11/30/18	Fri 11/30/18	58

The stakeholders of ICF System are ICF Staff, Donors, Management Executives, Youth who participate.

The interview, questionnaire and observation, the information gathering methods, are best suited for ICF system development project. The interview is done in the presence of two persons. In the interview methodology, the interviewee freely communicates with the interviewer. The questionnaire is quite different from the interview process in terms of collecting information. The system analyst creates a set of questions for individual types of stakeholders. The participants submit the survey form from their individual devices. The observation method does not include any participant. The system analyst physical appears on-site to evaluate organizational data and identify business requirements.

The interview is suitable for collecting in depth and accurate data regarding user requirements. As the interviewer and interviewee carries out this method face-to-face, the chance of collecting authentic data is high. The questionnaire takes less time to collect responses from much more numbers of participants than interview. The questionnaire has the drawback of producing wrong information. The observation fills the gaps remained after collecting data from interview and questionnaire. The observation reveals more about business requirements where other two were focused on user requirements.

The study concludes that proposed information system should be deployed in the cloud server. The study successfully described the development process of ICF system. The clouds servers are becoming more and more secure every day. The security is a big concern for the organization due to risk of losing sensitive business data. That is why, the cloud server host must consider the security as a big part of the project. The system will process all the back-office operations automatically thus staff will have more time to focus on core works rather than paper management.

Alshamrani, A., & 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), 106.

Boardman, A. E., Greenberg, D. H., Vining, A. R., & Weimer, D. L. (2017). Cost-benefit analysis: concepts and practice. Cambridge University Press.

Carvalho, J., Francisco, R., & Relvas, A. P. (2015). Family functioning and information and communication technologies: How do they relate? A literature review. Computers in Human Behavior, 45, 99-108.

Celli, G., Pilo, F., Pisano, G., & Soma, G. G. (2018, May). Including voltage dips mitigation in cost-benefit analysis of storages. In Harmonics and Quality of Power (ICHQP), 2018 18th International Conference on (pp. 1-6). IEEE.

Chakraborty, D. (2016). Indian Tea Garden Information System-A WebGIS Enabled Solution. Asian Journal of Geoinformatics, 16(1).

Laudon, K. C., & Laudon, J. P. (2015). Management information systems (Vol. 8). Prentice Hall.

Laudon, K. C., & Laudon, J. P. (2016). Management information system. Pearson Education India.

MINE, P. O., & AREA, C. (2015). Cost Benefit Analysis.

Putra, S. J., Ahlan, A. R., & Kartiwi, M. (2016). A Coherent Framework for Understanding the Success of an Information System Project. TELKOMNIKA (Telecommunication Computing Electronics and Control), 14(1), 302-308.

Sahar, S., Ayaz, S., Akram, M. U., & Basit, I. (2015). A Case Study Approach: Iterative Prototyping Model Based Detection of Macular Edema in Retinal OCT Images. In SEKE (pp. 266-271).

Schmitter-Edgecombe, M., & Parsey, C. M. (2014). Cognitive correlates of functional abilities in individuals with mild cognitive impairment: Comparison of questionnaire, direct observation, and performance-based measures. The Clinical Neuropsychologist, 28(5), 726-746.

Schwalbe, K. (2015). Information technology project management. Cengage Learning.

Bibliography: