COIT20248: Information Systems Analysis and Design Assessment 1

Verified

Added on  2025/07/24

|15
|2674
|280
AI Summary
Desklib provides solved assignments and past papers to help students succeed.
Document Page
COIT20248: Information Systems Analysis and
Design
Assessment 1 - Systems Development
Lecturer: Lecturer Name
Tutor: Tutor Name
Prepared by:
Student Name
Student Number
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
Contents
Introduction......................................................................................................................................3
Approaches to Systems Development.............................................................................................4
Systems Requirements.....................................................................................................................5
Project Cost/Benefit Analysis..........................................................................................................7
Project Management and Scheduling..............................................................................................8
Reflections.....................................................................................................................................14
Conclusions....................................................................................................................................14
List of figures
Figure 1: Cost-benefit analysis........................................................................................................7
Figure 2: Gantt chart........................................................................................................................9
Figure 3: WBS...............................................................................................................................10
Document Page
Introduction
The present report is all about a store which is situated in the city of Melbourne, Australia. The
store is named as RME (Repair made easy), this provides the users with the spare parts when any
of the system gets damaged or any other issue occur. The scenario of the report shows that the
owner of the store was maintaining their operations manually in a spreadsheet but now from
some time the issue arises and they are facing the issues regarding their work. Thus, the owner
has decided to appoint a developer who can design and develop a new system for their store in
which all the operations of the store should be performed directly and the transactions done in
the spreadsheet should be automatically added to the system without any issue. Also, if any of
the modification is done in the spreadsheet then the new system must have the capability to alter
the same changes automatically in the system. The time which has been allotted for the
development of the new system is the one year, the developer have to finish this project within
one year. In addition with this, the budget which is estimated for this project is $0.8 million. This
report is going to explain about the functional and non-functional requirement of the system.
Also, the cost analysis and Gantt chart will be design to show the exact time and budget along
with the NPV.
Document Page
Approaches to Systems Development
The methodology which is used to design this system is the system development life cycle. This
is the effective tool to design any project in systematic manner. This was introduced in 1960s
just to manage and perform the operations of the big projects (Wang, 2017). This methodology is
going to help us in managing the risk and in this it is very easy to control the high or big risk as
these tasks are completed first. This is known that the process of this methodology is difficult but
the problems and risks can be managed easily by using this tool. There are many stages which ae
used to design this new system and these are defined below in the report -
Initial Analysis - This is the first stage which included the test of feasibility and also
depicts the future scope of the new system.
System Analysis - This is the second stage in which the requirements of the system is
going to be gathered and assembled by the developer in order to develop and design the
new system.
System Design - This is the third stage in which the developer is going to assign the
designing task to the project designer and they are going to design a blueprint of the new
system and then take the approval from the user to start implementing the project.
Programming - This is the stage in which the coding is to be done to develop the
effective new information system. The different and several programmers are going to
design the code part for the system.
Testing - This is the stage in which the testing is to be done after the programming part
of the system (Wang, 2017). The system tester are going to test the entire process of the
new system so that if any of the error occur then that can be resolve at the same stage
only. This stage is used to fix the bugs and errors which are found by the testers.
Implementation - After fixing all the bugs and errors of the new system, the project
developer is going to implement the system. This stage also includes the training sessions
for the employees of the store so that they can able to learn the use of the new system and
can obtain or acquire the best outputs.
Maintenance - This is the last stage as everything after implementation needs
maintenance. This stage is for the services provided to the client after the implementation
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
for the project. If any of the issue faced by the client then this stage is going to fix and
resolve all those issues.
Systems Requirements
Functional requirements
Business requirement The system is going to work through the
internet services and for using this system, it is
very essential that the user must have the
internet services. The products of the store are
also available on the internet so that the online
business can also be done with the customers
of the RME.
Interface requirements The interface for the system is that, this can be
run at any platform and this is going to print
the data on-screen. This will takes the input
and gives the output in the form of numerical.
Security requirement The security is that much provided in this
system that the employees of the store can add
the request of the customers into the system but
not having the access to approve or delete that
(Rodriguez-Martinez, et al., 2015). In the
similar manner, the managerial department of
the store are having the permission to approve
and add the request of the customers but not
allowed to delete it.
Regulatory requirement This is very essential for any system to have
the security and provide much safety to their
users. The system is going to be used by only
the authorized users and is locked for the
illegal persons.
Document Page
Non-functional requirements
Security As this is very necessary to provide the security of
the system to the user, so to keep the system secure
from the malware attacks and viruses, security
requirement is must.
Usability This requirement shows that how much the
system is usable for the user and in how many
days they are going to learn the use of new
system (Mishra & Sharma, 2010).
Performance The performance capability of the system must be
high, the splash screen of the system does not take
the time more than5 seconds as the high
performance results in the positive outcomes.
Reliability This requirement shows that how much the system
is reliable for the user and what happen when any
of the bug or virus is going to occur. For example-
Is the system having that much of capability to bear
the risk of viruses?.
Document Page
Project Cost/Benefit Analysis
The cost analysis of any system is designed and develops to show the entire budget required for
the development of the new system. This shows that what will the cost of the sales, and how
much profit the owner is going to attain after the implementation of the new system in their store.
This defines the cost summary of the newly designed system.
Figure 1: Cost-benefit analysis
Description - The above cost analysis chart shows the cost summary for the newly designed
summary and this has also evaluated the NPV and net benefit for the upcoming five years.
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
Project Management and Scheduling
Gantt chart - This is the type of bar chart which shows that how all the operation of the project
are going to be performed by the project developer and how much time is required for the
completion of this project. This is the chart which is design in the MS project file and defines the
entire tasks which are performed by the developer for the successful completion of the project.
Document Page
ID Task
Mode
Task Name Duration Start Finish PredecessorsResource Names
0 New RME System 288 days Wed 8/7/19 Fri 9/11/20
1 Initial analysis 24 days Wed 8/7/19 Mon 9/9/19
2 Scheduling 12 days Wed 8/7/19 Thu 8/22/19 Software Consultant,Sponsor
3 Estimation for the cost 3 days Mon 9/2/19 Wed 9/4/19 2 Software
Consultant,Sponsor
4 Feasability Analysis 3 days Thu 9/5/19 Mon 9/9/19 3 Software Consultant,Sponsor
5 Milestone : Initial
analysis
0 days Mon 9/9/19 Mon 9/9/19 4
6 RME new System
Analysis
35 days Tue 9/10/19 Mon
10/28/19
7 Staff management 14 days Tue 9/10/19 Fri 9/27/19 5 Software Consultant
8 Collection of
Resources
11 days Mon 9/30/19 Mon 10/14/19 7 Software
Consultant
9 Requirement for the
cost
10 days Tue 10/15/19 Mon 10/28/19 8 Software
Consultant
10 Milestone : RME new
System Analysis
0 days Mon 10/28/19 Mon 10/28/19 9
11 System Designing 37 days Tue 10/29/19 Wed 12/18/19
12 Sketch designing 15 days Tue 10/29/19 Mon 11/18/19 10 System designer
13 Outline for the system 16 days Tue 11/19/19 Tue 12/10/19 12 System designer
14 Aprooval from Client 11 days Wed 12/4/19 Wed 12/18/19 13 Software Consultant
15 Milestone : System
Designing
0 days Wed 12/18/19 Wed 12/18/19 14
16 Programming of the
new system
56 days Tue 12/24/19 Tue 3/10/20
17 Coding 32 days Tue 12/24/19 Wed 2/5/20 15 Software Developer
18 Procedures 24 days Thu 2/6/20 Tue 3/10/20 17 Software Developer
19 Milestone:
programming of the
new system
0 days Tue 3/10/20 Tue 3/10/20 18
20 Testing of the
designed system
65 days Wed 3/11/20 Tue 6/9/20
21 Hardware Testing 17 days Wed 3/11/20 Thu 4/2/20 19 System Tester
22 Detecting malware
attacks and viruses
17 days Thu 4/16/20 Fri 5/8/20 21 System Tester
23 Fixing the errors and
bugs
22 days Mon 5/11/20 Tue 6/9/20 22 System Tester
24 Milestone : Testing of
the designed system
0 days Tue 6/9/20 Tue 6/9/20 23
25 Execution 26 days Wed 6/10/20 Wed 7/15/20
26 System Execution 11 days Wed 6/10/20 Wed 6/24/20 24 Software
Developer
27 Hardware Installation 15 days Thu 6/25/20 Wed 7/15/20 26 Software
Developer
28 Milestone :
Implementation
0 days Wed 7/15/20 Wed 7/15/20 27
29 Project Closing 42 days Thu 7/16/20 Fri 9/11/20
30 Deployment 9 days Thu 7/16/20 Tue 7/28/20 28 Software
Consultant
31 Repairs 10 days Wed 7/29/20 Tue 8/11/20 30 Software
Consultant
32 Placement 12 days Wed 8/12/20 Thu 8/27/20 31 Software
Consultant
33 Submission 11 days Fri 8/28/20 Fri 9/11/20 32 Software
Consultant
34 Milestone : Project
Closing
0 days Fri 9/11/20 Fri 9/11/20 33
Software Consultant,Sponsor
Software Consultant,Sponsor
Software Consultant,Sponsor
9/9
Software Consultant
Software Consultant
Software Consultant
10/28
System designer
System designer
Software Consultant
12/18
Software Developer
Software Developer
3/10
System Tester
System Tester
System Tester
6/9
Software Developer
Software Developer
7/15
Software Consultant
Software Consultant
Software Consultant
Software Consultant
9/11
J S N J M M J S N
Half 2, 2019 Half 1, 2020 Half 2, 2020
Figure 2: Gantt chart
Document Page
Work Breakdown Structure
This is the structure which divides all the project tasks into small sections or modules, this shows
that how the project can be completed successfully in effective tome frame. By the distribution
of task the system will be design and test at each level or stage and this will result in the better
outputs.
Figure 3: WBS
Goals, Scope and the requirement
The main aim of designing and developing this RME new system is that they must be able to
perform their operations automatically through the use of system instead of doing it manually.
Apart from this the scope of this newly designed system is huge as this will help the firm to
enhance their business in the international market also through the online business or by
spreading it (Haki, et al.). In addition with this, the owner is having certain requirement related to
the new system and that are, the system must not exceed the cost of 0.8 dollar million and the
time which is estimated and given for the successful completion of the system is the one year so
this requirement of the owner should also get fulfilled. Apart from all this, the system must
generate the exact profit in the third year and the NPV cost of the system should not be less than
New RME
System
Initial analysis
Scheduling
Estimation for
the cost
Feasability
Analysis
Milestone : Initial
analysis
RME new System
Analysis
Staff
management
Collection of
Resources
Requirement for
the cost
Milestone : RME
new System
Analysis
System
Designing
Sketch designing
Outline for the
system
Aprooval from
Client
Milestone :
System Designing
Programming of
the new system
Coding
Procedures
Milestone:
programming of
the new system
Testing of the
designed system
Hardware Testing
Detecting
malware attacks
and viruses
Fixing the errors
and bugs
Milestone :
Testing of the
designed system
Execution
System Execution
Hardware
Installation
Milestone :
Implementation
Project Closing
Deployment
Repairs
Placement
Submission
Milestone :
Project Closing
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
the 0.25 million dollar. The last requirement of the system is that the payback period must be less
than the three years.
Document Page
System Information Requirement Investigation Techniques
There are various stakeholders who are intricate for the development of the new RME system are
stated as below -
Stakeholders
Users Organisation Team Software
Consultant
Software
developer
These are the one
who are going to
use the entire
design system in
order to perform
their operations.
This is the RME
store, which
raised the
requirement of
the new system
for their store.
This is the most
important
stakeholders as
without them the
development of
the new system
would not be
possible.
This was the
person who was
included just to
guide the entire
team about the
development of
the system and
also consult to
the client time to
time.
This was the
person who was
included just to
develop and
design the coding
part of the
system
effectively.
Investigation techniques
The investigation techniques were used so that the project developer gets the feedback and the
reviews of the peoples who are using it. The three investigation techniques are defined below -
Questionnaire - In this technique of investigation, the project developer makes the sets of
questions related to designed new system and then asks randomly from any of the person
about the use of the new system and how that system is effective and reliable to them.
Interviews - This technique is used in which the software consultant is going to ask to the
specific person such as the owner of RME store about the use of new system that how
this system is giving advantage to them and is there any increment in the profitability or
productivity of the business (Agus & Rian, 2017).
Survey - In this, the software consultant and the entire team are involved in the survey
just to get the feedback and to know the viewpoint of the certain peoples about the new
RME designed system. If any of the negative feedback is attained by the team and they
will going to work on that issue just to make the requirement of people fulfil.
All the above three investigation techniques are used to get the reviews of the users that they
are satisfied with the designed system or not and to know perception about the system that
chevron_up_icon
1 out of 15
circle_padding
hide_on_mobile
zoom_out_icon
[object Object]