Unit: 34 system analysis and design

UNIT: 34 SYSTEM ANALYSIS
AND DESIGN
Made By: Nadir Sultan
[e-mail]
[Email address]
Assignment info:
Unit Code: L/615/1677
Unit Level: 5
Credit Value: 15

Contents
SCENARIO:....................................................................................................................................2
LO1: Evaluate the Strengths and Weaknesses of the Traditional and Agile Systems Analysis
Methodologies:................................................................................................................................2
P1 Discuss the Strengths and Weaknesses of the Traditional and Agile Systems Analysis
Methodologies:............................................................................................................................2
Waterfall, Advantages and Disadvantages:.................................................................................3
Prototyping, Advantages and Disadvantages:.........................................................................5
Spiral Model, Advantages and Disadvantages: ..................................................................7
Agile Methodologies:..................................................................................................................8
Scrum Methodology:...................................................................................................................9
Extreme Programming:..........................................................................................................10
Lean Methodology:................................................................................................................11
Safe Agile Frameworks (SAFe):...........................................................................................13
1.2: Suggesting Suitable SDLC model, Identify Problems, Provide Reasoning for Moving
from Traditional to Agile:..........................................................................................................17
LO2: Produce a Feasibility Study for a System for a Business-Related Problem:........................17
P2 Produce a Feasibility Study for a System for a Business Related Problem:........................17
Feasibility Report:.....................................................................................................................17
LO3: Analyze Their System Using a Suitable Methodology:.......................................................19
P3 Analyses a System Using a Suitable Methodology for a Business-Related Problem:.........19
3.1: User and System Requirements, issues, security issues:....................................................20
LO4: Design the System to Meet User and System Requirements:..............................................21
P4 Design a Fully Functional System to Meet User and System Requirements for the
Business-Related Problem:........................................................................................................22
References:....................................................................................................................................30

SCENARIO:
Suzuki is car spare parts manufacturing company. Suzuki is a global supplier of car spare parts to
different car manufacturers all over the world. Customers of Suzuki place orders for the spare
parts which they require, and estimated delivery time is one month. When a customer place an
order, the model name of spare parts required, quantity and the destination to which spare parts
has to be delivered is recorded by the CSR (customer sale representative). The customer orders
are being forwarded to the manufacturing department. At the end of the day, a forecast is made
based on the customer orders which we received and the spare part quantity already present in
stock to determine the number of spare parts need to be manufactured. When the required
quantity of spare parts is manufactured based on forecast, then the quantity available in stock is
updated and the spare parts are verified by the chief mechanic and after successful verification,
they are being sent to the procurement(checking) department. The procurement officer is
responsible for checking whether the model & quantity of the spare parts manufactured and
fulfilling the customer’s order and afterwards make proper arrangements for delivery of spare
parts to the customers. The status of delivery is also recorded from a reliable source. The
operations of Suzuki are mainly paper based records which results in delays and misplacement of
customer orders which leads to loss of potential customers. Assume that you have been hired by
Suzuki as a systems analyst to propose a systems design that will help overcome limitations with
the existing system.
LO1: Evaluate the Strengths and Weaknesses of the Traditional and
Agile Systems Analysis Methodologies:
P1 Discuss the Strengths and Weaknesses of the Traditional and Agile Systems
Analysis Methodologies:
As a systems analyst hired by Suzuki, explaining all the SDLC models and its main principles
which are as follows:
 Waterfall
 Prototyping
 Spiral
 Agile methodologies: Scrum, Extreme, Lean, Scaled Agile Frameworks (SAFe),
Disciplined Agile Delivery (DAD), Kanban. Disciplined Agile Delivery (DAD), Agile
Modeling (AM) models
 Describe Strengths and Weaknesses of Traditional Models and Agile Methodologies.

Waterfall, Advantages and Disadvantages:
Waterfall model was the first
of the models to be created,
another name for this model
linear-sequential life cycle.
This model is easy to use and
simple as this model requires
the user to complete each of
its phase and only then you
can proceed to the next
phase. For each mode la
certain set of requirements
are needed that allows for the
model to be used easily in the
first place which are:
 Requirements for the program itself are given beforehand
 Stable definition of program
 No out of the ordinary requirements
 Resources to help out the team are given
 Short project
It is the first iteration of a SDLC so it was not the best of its kind. Waterfall model consists of 6
phases which are:
 Requirement Analysis
 System Design
 Implementation
 Testing
 Deployment
 Maintenance
Requirement Analysis:
This phase requires the user to document all of the data required in order to develop said project
and save it into a specific document.
System Design:
The data collected and documented form the first phase and gets designed in this phase. This
helps in creating the project and it specifies the hardware and makes a road map of sorts in the
overall architecture.

Implementation:
just like how data from the first phase was used in phase two, the same concept applies here and
the development of the project starts here by making small programs called units and later on
used in the next phase.
Testing:
The said units that were talked about in the previous phase are tested out in this phase by
merging all of them into a singular program after each and every one of them are tested
individually.
Development:
In this phase the program is shipped out to the public after all the phases above have been fully
accomplished.
Maintenance:
The final step of the model is maintenance in which the program gets updates or patches after its
been out to the public or a new version gets created
Advantages of Waterfall:
 Using, understanding are simple and easy of the model
 Having specific points and review process in each step allows it to be a fairy easy model in
terms or managing
 Completion of each phase are done one at a time
 Smaller projects are benefited more as their requirements are easily understood
 Since each phase is defined easily, it is easy to arrange and process
 Results are documented well
Disadvantages of Waterfall:
 Until late during the life cycle, no working software is produced
 Uncertainty and risk is high
 Model is not recommended if the project is complex or has OOP involved
 Model not suited for long projects
 If the requirements of the model keep changing, the model is not good
 Development of program is done later during the life cycle which does little space for
identifying any issues until after it is made

Prototyping, Advantages and
Disadvantages:
Essentially what prototype model does is
that it helps in getting feedback for a
program by making a replica of it and
giving it out to the customer so they can
test it and give feedback accordingly.
This model is used if the customer does
not know what the exact requirements of
their program is going to be about. There
are many ways in this model can be
broken down to but the main phases of it
stays the same which are:
 Gathering of Requirements and Analysis
 Quick Design
 Building a Prototype
 User Evaluation
 Product Refining
 Engineer Product
Gathering of Requirements and Analysis:
Much like the waterfall model, this model’s first step is also to gather the requirements and to
analyze them. An interview is taken from the customer in order to know what the requirements
will be.
Quick Design:
Main reason as to why its called quick design is because the requirements given by the customer
aren’t in detail so as a result the designing phase gets completed rather quickly, it also helps in
developing the system quickly
Building a Prototype:
A prototype is made with the information given by the customer in this phase.
User Evaluation:
Now that the prototype is made, it is then sent out to the customer so they can review it and give
their opinion about it weather if they liked it or if they would like for something to get changed.