Professional Documents
Culture Documents
Term1, 2016
Assessment 1 - Systems Development
Prepared by:
Your Name
Your Student Number
Contents
1. Introduction........................................................................................................ 1
2. Approach to Systems Development............................................................................1
3. Systems Requirements........................................................................................... 3
4. Project Cost Benefit Analysis................................................................................... 4
5. Project Schedule................................................................................................... 5
6. System Information Requirement Investigation Techniques...........................7
7. Reflections and Conclusions...........................................................................8
References.......................................................................................................... 9
1. Introduction
We are given the case study for Natural Health Food store, which is a chain of health food
stores. At present the food chain has a traditional way of serving their customers from NSW,
Queensland and Victoria. David Brown, its owner had at first started this chain in the year
1965 and currently has 15 stores. Mr. David has now wished to implement Automatic
Delivery System (ADS) for his existing line of products and services. So far the customers
are served manually and are facing various problems like lot of overheads in terms of cost in
manual serving of the order, which at times taken an hour or so. To reduce these overheads
and be more prompt in delivering the orders, Mr David wants that the system should be able
to process customers subscription automatically without the interference of the staff. Once
the subscription is in place, then the customer is a member in the system. Then the system
should allow the customer to place orders.
owner or the user like Mr David in our case, has to see and verify the model and
suggest the changes. With this the scrum developer quickly makes another model
with the help of the team. The model is re-presented to the owner for further
verification and feedback process. These steps continues iteratively till the model is
accepted. There are more chances that the project will succeed as the users or owners
have more confidence in the system. However, this is very resource intensive and
even the owner has to devote lot of time, which may not be possible every time as
Mr David or his team may be busy handling existing business.
b. Other way is called extreme programming which is also a faster way to develop the
system. This takes into account the customers changing requirements and is a very
flexible method of development. The method stresses on quality and strictly adheres
to the customer specification and quality standards. Hence the name extreme
programming as it takes into account even the smallest details to maintain the
quality.
c. Waterfall Method: it is a conventional method of system design where the system has
is designed beforehand. We have all the system diagrams, analysis designs and
planning complete before we start the development work. However, this method is
not flexible as once the system design is complete then we cannot accept more
changes.
Page 2
3. Systems Requirements
For each of above approaches, most important stage is to understand the system or user
requirements. A software development project constitutes two tyes of system requirements:
A. User requirements or the functional requirements
B. System Requirements or the non- functional requirements.
The Functional requirements are basically the user requirements specified the users or the
owner of the system. They provide the details as to how the system will work. For instance,
the system operates manually and what all processes are being followed like customer
details acquisition and maintenance, order taking, delivery and so on. These requirements
have to be coded into the system and these are called functional requirements.
In this context, we can enlist the functional requirements as given below:
1. There has to be an automated system or order taking and delivery.
2. The system will take the customers orders and before that it will record the customers
details
3. The system will allow the first time customers to register into the system so it is easy
for them to just order without worrying about the details like phone numbers, addresses
and the timings or delivery frequency.
4. The system will allow the customers to become members and the system can acquire
their details and shall be able to retrieve these details next time when the member
orders.
5. The system will be able to maintain a high performing database to store and retrieve
the information and to process their orders with the help of the stored information in
quick turnaround time.
6. The system shall be able to generate the reports based on the customers, members,
frequency of the products or services ordered and other management information
reports.
Apart from the above non-exhaustive functional requirements, there are a set of Non
functional requirements which define the quality standards. Extreme programming
methodology as we discussed above is concerned more on non-functional requirements as
Page 3
its main focus is on quality. Other 2 methods or software development approaches also
focus on quality. So we can enlist the following non-functional requirements:
a. The system should be responsive and is able to reduce the turnaround time of
processing the orders
b. The system should have fast response time and should be able to process the orders
in the matter of minutes.
c. The system should not be breakable and work efficiently in storing and retrieving
the information
Page 4
Annual Benefits
Annual Operational Costs
One-Time Development Cost
Economic Benefit
Discount Rate
PV of Benefits
NPV of all BENEFITS
$
140,000.00
$
25,209.00
$
30,610.00
0
$0.00
$
140,000.00
0.9709
$135,922.33
1.0000
$0.00
$0.00
Year of Project
2
$
140,000.00
0.9426
$131,963.43
$
140,000.00
0.9151
$128,119.83
$
140,000.00
0.8885
$124,388.19
$
140,000.00
0.8626
$120,765.23
$
135,922.33
$
267,885.76
$
396,005.59
$
520,393.78
$
641,159.01
$
(25,209.00)
0.9709
$
(24,474.76)
$
(25,209.00)
0.9426
$
(23,761.90)
$
(25,209.00)
0.9151
$
(23,069.81)
$
(25,209.00)
0.8885
$
(22,397.87)
$
(25,209.00)
0.8626
$
(21,745.50)
$
(55,084.76)
$
(78,846.66)
$
(101,916.46)
$
(124,314.33)
$
(146,059.84)
TOTALS
$
641,159.01
One-Time COSTS
$(30,610.00)
Recurring Costs
Discount Rate
PV of Recurring Costs
$0.00
1.0000
$0.00
$
(146,059.84)
$
495,099.17
Overall ROI
3.3897
Break-even Analysis
Yearly NPV Cash FLOW
Page 1
$(30,610.00)
Overall NPV Cash FLOW
$(30,610.00)
111,447.57
$
80,837.57
108,201.53
$
189,039.10
Page 2
105,050.03
$
294,089.13
101,990.32
$
396,079.44
99,019.72
$
495,099.17
5. Project Schedule
Having seen that there will be economic benefits in taking up this project, now we develop a
project plan, schedule and draw a Gantt chart for this schedule:
The below diagram shows the project schedule and Gantt Chart:
Stakeholders
There are various stakeholders for the system and they are the people who are impacted by
the outcome of the project
Techniques
We discussed some techniques while detailing about the project methodologies. For instance
if we select the agile development then there will be certain techniques which will be
applicable. For scrum or waterfall development there are other techniques. For agile methods
we need to have the project sponsor or important stakeholders associated with us
continuously till the project is finally completed and deployed. A set of meetings are required
Page 1
and the communication is sent to the stakeholders giving the details of the meetings. This is
an important way to investigate and ascertain on the actual requirements.
7.
References
Burke, R. (2003), Project Management, Planning and Control Techniques, John Wiley and
Sons
Field, M., Keller, L. (1998) Project Management. Open University
Yardley, D. (2003) Success IT Project Delivery: Learning the Lessons of Project Failure.
PRINCE2 (2005). Retrieved from http://www.PRINCE2.com/p2download20102005.asp
The Executive Guide to Directing Projects: within a PRINCE2 and MSP Environment (TSO,
2009)
Page 2