COIT 20248: Information Systems Analysis and Design - Assessment 1: Systems Development for UNICEF Childcare

COIT 20248: Information Systems Analysis and Design
Term 1, 2018
Assessment 1 - Systems Development
Lecturer: Lecturer Name
Tutor: Tutor Name
Prepared by:
Student Name
Student Number

Table of Contents
Introduction................................................................................................................................2
Task 1. Approach to Systems Development..............................................................................3
Task 2. Systems Requirements..................................................................................................4
2.1 Functional Requirements..................................................................................................4
2.2 Non-Functional Requirements..........................................................................................4
Task 3. Project Cost-Benefit Analysis.......................................................................................6
Task 4. Project Schedule............................................................................................................7
4.1 Work breakdown structure and Gantt Chart.....................................................................8
4.2 System Goals, Requirement, Project scope and project schedule....................................9
Task 5. System Information Requirement Investigation Techniques......................................10
5.1 List of Stakeholders........................................................................................................10
5.2 Three most useful investigation techniques...................................................................10
5.3 Usefulness of three techniques.......................................................................................10
Reflections and Conclusions....................................................................................................12
References................................................................................................................................13
List of Figures
Figure 1 Cost-benefit analysis table of project..........................................................................6
Figure 2 Project Schedule..........................................................................................................8
Figure 3 Work breakdown structure..........................................................................................8
Figure 4 Gantt Chart...................................................................................................................9
Page 1

Introduction
“UNICEF Childcare” is a corporate organisation for children’s supervision and care who are
between the age of six weeks to thirteen. It provides food, teachers, babysitter, nannies and
many other services for the children’s for which parents pay. The current manual process
carries various problems as parents have to make payment through bank transfer or
depositing money directly to the UNICEF account. After funds are fetched at the week-end
the accountant prepares receipts/ tax invoices for each parent to post or email them.
John Smith, chairperson of UNICEF aims for this project are:
• Online system to deposit fees
• Automatic generation of thanking email for users when payment is received.
• Provision to download consolidated statement.
• Automated products ordering
.
Page 2

Task 1. Approach to Systems Development
Developing Information system for UCC
For developing an Information system for UCC firstly, there is need of considering the needs
of the organization. After this strategize the data storing and accessing capacity of the
organization so that right system can be chosen. The system needs to have data encryption so
that data can be accessed fastly and no one would be able to see data unless he has the
encryption key. Finally look for aspects of cost and efficiency to reach out to best alternative
(Sami, 2012).
To develop the better system we need to include all the stakeholders of UCC for their advice
and for this Joint application design could be the best approach.
Validation of preferred system development approach
The problems faced by UCC during manual pen and paper system can be replaced effectively
by JAD (Joint Application Design) approach because it will contain all the opinion,
requirements and stakeholders. JAD is a technique for developing requirements of the
business system by bringing users and system developers in a creative and productive
environment via structured approach to acquiring specifications and requirements. The
specifications which will prove JAD approach to be the best for the UCC are mentioned
below.
• JAD helps to encourage team members in pushing each other for working quickly to
get the delivery on time.
• It allows solving of difficulties more simply while producing error-free and better
software.
• It reduces time and cost required for the development of the project.
• The mutual collaboration among the clients and the company lower down all risks.
• Properly defined requirements enhance system quality (Mrsic, 2017).
Page 3

Task 2. Systems Requirements
The UCC case study gets with the system requirements which are mentioned below:
2.1 Functional Requirements
It is termed as any requirement which specifies or lays on what the system must perform.
Functional requirements are as follows.
• Login/ signup
Parents or clients must first register to use the benefits of UCC services.
• Authentication or Validation
Proper passwords with username will help users, staff or admins with proper assessing of
system.
• Online Payment
Customer will be benefitted with online system as they will be able to give payments anytime
and from anywhere.
• Notifications
New emails, payment transfers or any deadline details can be managed with the help of
system notification.
• Order Online
The system will help in proper product supplies for the children by determining the current
stock levels.
• Reporting
Evaluation and analysis of the business reports can be easily done.
• Permission levels
There are many users and each one of them needs to be confined at some level like admins
can have access to all records in order to edit them, staff members cannot edit data and
customers can only read the data.
2.2 Non-Functional Requirements
It is termed as any requirement which lay down how a particular function is performed by the
system. Non-functional requirements are as follows.
• Interface
The interface needs to be user-friendly because it is an important factor in considering how
system interfaces with other company.
Page 4

• Reliability
• Authentication
• Security
• Report generation
Customer needs to have the reports timely and accurately.
• Quality
This factor helps in enabling users to enable the easy maintenance of data and extend the
project.
Page 5

Task 3. Project Cost-Benefit Analysis
According to Boardman, Greenberg, Vining and Weimer; Cost-benefit analysis is a
procedure for assessing all possible profits and costs involved from a proposal or business
opportunity. It takes both qualitative and quantitative factors for money analysis. This process
is done by making comparison among the benefit and cost involved for an information
system to validate whether investment in the project is worth or not (Boardman, et-al, 2017).
In UCC, the CBA is done to verify with economic feasibility. Here, NPV which is Net
present value is calculated for the cost. Payback period and ROI which is Return on
investment are calculated after which profit of project gains are calculated.
Project CBA is done by recurring and one-time cost. One-time expenses are not recurring or
regular in nature and thus cannot be forecasted easily. Whereas recurring cost occurs
regularly in some interval of time (Maverick, 2015).
Figure 1 Cost-benefit analysis table of project
Here the NPV is positive, ROI is 1.89 and project break even occurs between year 1 and 2
which comes out to be 1.51
.
Page 6

Task 4. Project Schedule
It is the probable time needed for the completion of various tasks of the entire project. Here it
is represented in tabular and graphical with the help of Work breakdown structure and Gantt
chart. Here every task has its subtasks like initial scheduling, Requirements Analysis, Design,
Coding, Testing and documentation, Maintenance.
Page 7

Figure 2 Project Schedule
4.1 Work breakdown structure and Gantt Chart
The project schedule is made in accordance to work breakdown structure and for this
activities needs to be defined, estimation is to be made, dependencies is to be determined and
resources are assigned (Ray, 2017). Work breakdown structure gets with all the needful
activities and project task which needs to be carried in the phase of project life cycle.
Figure 3 Work breakdown structure
Page 8

ID Task
Mode
Task Name Duration Start Finish
0 UNICEF Child Care43 days Tue 4/3/18Thu 5/31/18
1 1 Initial Scheduling6 days Tue 4/3/18 Tue 4/10/18
2 1.1 Work Plan 2 days Tue 4/3/18 Wed 4/4/18
3 1.2 Feasibility Study3 days Thu 4/5/18 Mon 4/9/18
4 1.3 Risk Analysis1 day Tue 4/10/18Tue 4/10/18
5 2 Requirements
Analysis
6 days Wed
4/11/18
Wed
4/18/18
6 2.1 Data collection3 days Wed 4/11/18Fri 4/13/18
7 2.2 Design Prototype2 days Mon 4/16/18Tue 4/17/18
8 2.3 Build 1 day Wed 4/18/18Wed 4/18/18
9 3 Design 9 days Thu 4/19/18Tue 5/1/18
10 3.1 Database design3 days Thu 4/19/18Mon 4/23/18
11 3.2 Project design5 days Tue 4/24/18Mon 4/30/18
12 3.3 System
specification
1 day Tue 5/1/18 Tue 5/1/18
13 4 Coding 8 days Wed 5/2/18Fri 5/11/18
14 4.1 Programming5 days Wed 5/2/18 Tue 5/8/18
15 4.2 System
implementation
1 day Wed 5/9/18 Wed 5/9/18
16 4.3 Debugging 2 days Thu 5/10/18Fri 5/11/18
17 5 Testing and
Documentation
8 days Mon
5/14/18
Wed
5/23/18
18 5.1
Performance
testing
3 days Mon
5/14/18
Wed
5/16/18
19 5.2 Software testing2 days Thu 5/17/18Fri 5/18/18
20 5.3 System
documentation
1 day Mon
5/21/18
Mon
5/21/18
21 5.4 User
documentation
2 days Tue
5/22/18
Wed
5/23/18
22 6 Maintenance 6 days Thu 5/24/18Thu 5/31/18
23 6.1 Regular
system
update
3 days Thu
5/24/18
Mon
5/28/18
24 6.2 Training 2 days Tue 5/29/18Wed 5/30/18
25 6.3 System install1 day Thu 5/31/18Thu 5/31/18
T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F
Apr 1, '18 Apr 8, '18 Apr 15, '18 Apr 22, '18 Apr 29, '18 May 6, '18 May 13, '18 May 20, '18 May 27, '18
Figure 4 Gantt Chart
43 days is been acquired in project completion through the project could be completed
earlier if some tasks can be done in parallel and some carry predecessor with them.
4.2 System Goals, Requirement, Project scope and project schedule
System Goals: The UCC main goal is in minimizing the paper and pen work and getting all
the things online. It will help in maintain data accuracy and integrity.
Requirement: For the system to get online most important essentials needed is a good system
approach, customer and organization requirements and proper planning, development and
testing.
Project scope: The new design will help in data scheduling and management so that project
can be completed in desired cost and time. Work breakdown structure will help in proper
management of resources.
The project schedule will be reasonable when in any problem the system gives up an
inappropriate result like time delays, information collection and fanatical resources.
Page 9

Task 5. System Information Requirement Investigation Techniques
5.1 List of Stakeholders
Stakeholders are the person who maintains professional relations with all the members and
gets a hold of all the activities in business. Types of stakeholders are Internal, External,
Executive and Operational.
1. Internal Stakeholders- These involve the business internally like the people in the
management team, staff and all.
2. External Stakeholders- These involve in the business externally like the customers,
contractors, suppliers and people like them.
3. Executive Stakeholders- They are the people with high control on activities like the
system analysts and system managers possess.
4. Operational Stakeholders- These people are involved in the operations of business like
sales representatives, universities etc. are.
5.2 Three most useful investigation techniques
Techniques are:
1. One-on-One and Group interviews- In this discussion, interviews must be open-ended so
that interviewee gets on talking and probing questions come to uncover requirements.
2. Questionnaires and Prototyping- Questionnaires are an informal way to collect input from
thousands or dozens of people. In Prototyping approach, preliminary requirements are
gathered
3. User cases and (RFP) Request for Proposals- Use cases are the stories which demonstrate
that how discrete processes operate. Use cases will be distilled later to more precise
detailed requirements. RFP provides vendors with all the requirements so that proper
comparison can be made for the capabilities in defining how near a match are you to the
needs of the client.
5.3 Usefulness of three techniques
Usefulness is:
1. A richer set of necessities can be uncovered in a smaller span if people can be kept
focused.
Page 10

2. Questionnaires will help in gathering data from remote location and Prototyping due to its
repetitive process can meet business needs of critical masses.
3. Use case tends to be easier to articulate for the users and RFP will help in setting a close
match to the customer’s need (Mochal, 2008).
Page 11

Reflections and Conclusions
The problems in UCC have been properly identified and to resolve it proper system
development methodology has been selected. Here system requirements, project cost-benefit
analysis, project schedule and investigating techniques are made with proper justification.
Work breakdown structure and Gantt chart is formed which shows the feasibility of the
project.
The project aims to have fully automated UCC system as it will help in improvising the
business profits. The project here is fully feasible for executing the tasks within time and in
accordance with the cost-benefit analysis.
Page 12

References
 Boardman, A. E., Greenberg, D. H., Vining, A. R., & Weimer, D. L. (2017). Cost-benefit
analysis: concepts and practice. Cambridge University Press.
 Maverick, J. B., (2015). What is the difference between recurring and non-recurring
general and administrative expenses?, viewed 3 April 2018,
https://www.investopedia.com/ask/answers/072815/what-difference-between-recurring-
and-nonrecurring-general-and-administrative-expenses.asp
 Mochal, T 2008, 10 techniques for gathering requirements, viewed 3 April 2018,
https://www.techrepublic.com/blog/10-things/10-techniques-for-gathering-requirements/
 Mrsic, M 2017, Joint Application Development (JAD), viewed 3 April 2018,
https://activecollab.com/blog/project-management/joint-application-development
 Ray, S 2017, What Is Project Scheduling?, viewed 3 April 2018,
https://www.projectmanager.com/blog/what-is-project-scheduling
 Sami, M 2012, Choosing the right Software development life cycle model, viewed 3 April
2018, https://melsatar.blog/2012/03/21/choosing-the-right-software-development-life-
cycle-model/
Page 13