INDIVIDUAL ASSIGNMENT COVERSHEET AUSTRALIAN INSTITUTE OF BUSINESS AND MANAGEMENT PTY LTD CRICOS: 03171A ABN:72 132 629 979
KING’S OWN INSTITUTE* Success in Higher Education
INDIVIDUAL ASSIGNMENT COVERSHEET Family Name:
Given Name:
Student Number:
Lecturer’s Name: Shaleeza Sohail
Subject Name: Systems Analysis and Design
Assignment Title: System Analysis Report
Declaration (This declaration must be completed by the student or the assignment will not be marked.)
I certify the following:
• I have read and understood the Student Academic Misconduct Policy.
• This assignment is my own work, based on my personal study and/or research.
• I have acknowledged all material and sources used in the preparation of this assignment, including any material generated in the course of my employment.
• The assignment has not previously been submitted for assessment.
• I have not copied (in part or in whole) or otherwise plagiarised the work of other students.
• I have read and I understood the criteria used for this assignment.
• The assignment is within the word and page limits specified in the subject outline.
• The use of any material in this assignment does not infringe upon the intellectual property /copyright of a third party.
• I understand that this assignment may undergo electronic detection for plagiarism and an anonymous copy of the assignment may be retained on the database and used to make comparisons with other assignments in the future.
• By completing this coversheet in full and submitting this assignment electronically, I am bound by the conditions of the KOI’s Student Academic Misconduct Policy and the declaration on this coversheet.
e-Signature:
Date:
INDIVIDUAL ASSIGNMENT COVERSHEET AUSTRALIAN INSTITUTE OF BUSINESS AND MANAGEMENT PTY LTD CRICOS: 03171A ABN:72 132 629 979
Table of Contents
Contents Introduction ........................................................................................................................ 3
Methodology ....................................................................................................................... 4
Types of Approach in SDLC ............................................................................................. 4
SDLC Methodologies ....................................................................................................... 5
Waterfall and Agile Model .............................................................................................. 6
Chosen Methodology .......................................................................................................... 6
Agile Model ..................................................................................................................... 7
Requirement Gathering ...................................................................................................... 8
Requirements ...................................................................................................................... 9
Functional Requirements ................................................................................................ 9
Non-functional Requirements ........................................................................................ 9
Requirement Modelling .................................................................................................... 10
Reference .......................................................................................................................... 11
INDIVIDUAL ASSIGNMENT COVERSHEET AUSTRALIAN INSTITUTE OF BUSINESS AND MANAGEMENT PTY LTD CRICOS: 03171A ABN:72 132 629 979
Introduction
[1] A case study can be defined as the process of researching about the development
of a certain groups or individuals by checking the present records or by collecting
information about the needed subject.
The IT company, IT Solutions provides support to wide range of networking,
computer hardware, and software problems to businesses in the CBD area. It is
getting a large number of new clients. Any kind of networking, hardware or
software problem are managed and the required tasks are performed whenever
clients call and e-mail arrived. The range of staffs present in the IT Solution consists
of technicians, designers, systems analyst, programmers along with two
administration staffs.
As the number of clients increases, it become difficult to keep the record of network,
hardware and software problems. Different types of problems are managed by the
consultants. Sometimes, multiple trips are required to solve the complex problems
along with the tracking of things a consultant has done in-order to solve the
problems. A specialist has to be dispatched to the work site in-case the problem is
serious.
If the problems are not complex, the consultant are going to advice the client
through the e-mail or phone, whereas, if the problems are complex, the consultants
are going to visit the client and can have multiple trips as well.
This case study is done in order to make such a system which will help both the
clients and consultants. Along with the development of this system, the existing
problems of the company are going to be solved. One of the reasons behind
developing this system is to make sure that the client is able to access the service
request of the company. By doing so, the company will be able to pay or charge
money to the consultant and the client as per the time spent to solve the problem.
INDIVIDUAL ASSIGNMENT COVERSHEET AUSTRALIAN INSTITUTE OF BUSINESS AND MANAGEMENT PTY LTD CRICOS: 03171A ABN:72 132 629 979
Methodology
SDLC, software development life cycle is a framework or a tool that is used during
the development of the software at each step. Software’s quality is improved along
with development process with the help of SDLC. [2]
SDLC consists of following activities:
• Planning: …………………………………..
• Design: ……………………………………….
• Implementation: …………………………………..
• Testing: ………………………………………………..
• Documentation: ………………………………………….
• Deployment: ………………………………………………..
• Maintaining: ………………………………………………….
INDIVIDUAL ASSIGNMENT COVERSHEET AUSTRALIAN INSTITUTE OF BUSINESS AND MANAGEMENT PTY LTD CRICOS: 03171A ABN:72 132 629 979
Types of Approach in SDLC
There are two types of approach in SDLC, and they are:
Predictive approach: Definition
Some of the benefits of predictive approach are:
1. ……………..
2. ……………..
Some of the disadvantages of predictive approach are:
1. ……………..
2. ………………
Adaptive approach: Definition
Some of the benefits of adaptive approach are:
1. ………………….
2. …………………
Some of the disadvantages of adaptive approach are:
1. …………………..
2. ………………….
SDLC Methodologies
There are numbers of SDLC methodologies that can be used during the
development of software. Some of the basic methodologies are given below:
• Waterfall Model
• V-shaped Model
• Spiral Model
• Iterative Model
INDIVIDUAL ASSIGNMENT COVERSHEET AUSTRALIAN INSTITUTE OF BUSINESS AND MANAGEMENT PTY LTD CRICOS: 03171A ABN:72 132 629 979
• Big Bang Model
• Agile Model
Waterfall and Agile Model
Waterfall and agile model are described below:
➢ Waterfall Model (Define)
It is one of the oldest and linear models. Its every phase relies on the
information of the previous phase. It is simple to understand and manage
but difficult to find the error once moved to the next phase. It is best to used
when the developer is fully knows about the requirements. If the developer
is not knowledge about the requirements than it will be difficult to develop
the system.
➢ Agile Model (Define)
This model is a combination of both incremental and iterative model where
a working version of a model is delivered after each cycle. Since, it is the
done with the collaboration of the developer, customer and the tester, the
product is delivered quickly and is realistic. As using this model, the
developer can interact with the customer more frequently, if the customer
provides the wrong information then the whole project can head to the
wrong direction.
Chosen Methodology
The model that I find suitable for the system given in the case study is Agile Model.
Note:
Discuss about the chosen methodology. Why do you think that this
methodology is best for your case? Highlights the advantages of chosen
methodology over another model. Justify your selection.
INDIVIDUAL ASSIGNMENT COVERSHEET AUSTRALIAN INSTITUTE OF BUSINESS AND MANAGEMENT PTY LTD CRICOS: 03171A ABN:72 132 629 979
Agile Model
Agile is a software development methodology which works in an iterative process.
Changes can be made to the previous part as long as the results are not satisfactory.
This method is generally used while developing software, as there are always
changes that needs to be done in the previous part if the result is not what that has
been expected. Here, iterations are done depending upon the case. The works are
done in such a way that feedback arrive in a short time and the products are ready
when the iteration is finished.
As a result of these planning and feedbacks, the developers are able to finish their
work on time and satisfy their clients.
Some principles of Agile model are mention below:
• Face to face communication
• Customer interaction
• Frequent delivery of software
• Simplicity
• Sustainable development
• Customer satisfaction
• Easily adapt with changing environment
• Adapt changes in the requirements
The reason for choosing agile model can be easily understood when we take a
look towards its advantages.
• Easy to manage
• Adapt with regular changes which make easy during requirement changes
• Deliver working software on certain amount of time which help to
evaluate the software and point out the improvement needed
• Requirements can be even changed even at the very end
• It is flexible in use
INDIVIDUAL ASSIGNMENT COVERSHEET AUSTRALIAN INSTITUTE OF BUSINESS AND MANAGEMENT PTY LTD CRICOS: 03171A ABN:72 132 629 979
• No planning is required
• Provide customer satisfaction since user can see various version of
software developed and can choose the one, they liked
• Promote face-to-face communication which help in better understanding
of the requirements
Requirement Gathering
The needed and the necessary information are to be gathered from the concerned
individuals and the group. For this, an interview is to be organized with the company
representative. Some sets of questions are prepared to be answered by the
representative.
Prepare some sample for the technique you are going to choose
The questions are mentioned below:
• What is the problems present in the current system?
• What are the changes they want in the new system?
• How many times does the client sends requests in a daily basis?
• How many times are the request cancelled in a daily basis?
• How many trips does a consultant has to take for a complex problem?
• How long does it take to respond to a client’s requests?
• How quick was the response to the client about their problem?
• How quick was the problem solved?
• Are the clients satisfied with the provided service?
There are many more additional methods to find out the information’s like as:
• Research and Vendor Solutions: here, the way in which others individuals
or group have solved the situations can be used as a reference. Papers, old
reports and research done by others can be taken as reference.
• Take suggestions and feedback from users: The problems are best known
by the users as they are the one who use the system. The problems they face
INDIVIDUAL ASSIGNMENT COVERSHEET AUSTRALIAN INSTITUTE OF BUSINESS AND MANAGEMENT PTY LTD CRICOS: 03171A ABN:72 132 629 979
can be taken as feedbacks and upgrade or install the system as per their
suggestion.
Requirements
The requirements of the system are:
Functional Requirements- Define/Discuss
It describes “what a software system should do” and also the behaviour of the
system. It can be documented in various ways. One of the common methods of
documentation is Use Cases. Use case describe every user action.
Some typical functional requirements are:
• Authentication
• Historical Data
• Use Case
• Calculations
• Legal requirements
• Business rules
• Technical details
• Data manipulation
• Login page
• Security
In other words, functional requirements describe a particular behaviour of the
system when certain conditions are met. It is from client to the developer.
Non-functional Requirements– Define/Discuss
It describes “how the system performs a certain function”. It generally specifies the
system quality characteristics. Non-functional requirements can sometimes be
defined in terms of metrics. This requirement can place restriction on the product
being develop.
INDIVIDUAL ASSIGNMENT COVERSHEET AUSTRALIAN INSTITUTE OF BUSINESS AND MANAGEMENT PTY LTD CRICOS: 03171A ABN:72 132 629 979
Some typical non-functional requirements are:
• Reliability
• Fault tolerance
• Efficiency
• Effectiveness
• Maintainability
• Quality
• Robustness
• Security
• Stability
Non-functional requirements must be stated correctly since it may affect the user
experience when interacting with the system. It is from developer to the client.
Requirement Modelling
A diagram as per the outcome of the requirement analysis has been made. An
activity diagram to provide a graphical illustration of the new system is shown
below:
INDIVIDUAL ASSIGNMENT COVERSHEET AUSTRALIAN INSTITUTE OF BUSINESS AND MANAGEMENT PTY LTD CRICOS: 03171A ABN:72 132 629 979
In above diagram, a server is kept because the consultants need to enter the client
server from their main office virtually to solve the problem if possible.
Reference
1. https://www.google.com.au/search?q=case+study%3F&ie=&oe=
2. Emstell Technology Consulting, 15th Jan 2018. Software development life
cycle (SDLC)- A quick overview. [online] Available at:
<https://yourstory.com/mystory/78797bfe72-software-development-l >
(Figure of SDLC)
INDIVIDUAL ASSIGNMENT COVERSHEET AUSTRALIAN INSTITUTE OF BUSINESS AND MANAGEMENT PTY LTD CRICOS: 03171A ABN:72 132 629 979
3. MY ASSIGNMENT HELP, Pros and cons of Adaptive and Predictive
SDLC. [online] Available at: https://myassignmenthelp.com/free-
samples/pros-and-cons-of-adaptive-and-predictive-sdlc