L/615/1677 Unit 34 System Analysis and Design Report: Suzuki Analysis

This report provides a comprehensive analysis of system analysis and design principles, focusing on the evaluation of traditional and agile systems analysis methodologies. The report begins with an overview of the System Development Life Cycle (SDLC) models, including Waterfall, Prototyping, and Spiral models, detailing their strengths and weaknesses. It then delves into Agile methodologies, specifically Scrum, Extreme Programming, Lean, and Scaled Agile Frameworks (SAFe), highlighting their key features and applications. The report includes a case study of the Suzuki car spare parts manufacturing company, analyzing its current paper-based system and proposing a systems design to overcome existing limitations. A feasibility study is produced, along with an analysis of user and system requirements, and the design of a fully functional system to meet these requirements. The document is a valuable resource for students studying system analysis and design, offering insights into various methodologies and practical application through a real-world business scenario. The report also explores the advantages and disadvantages of each methodology, along with the user and system requirements.

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.

Product Refining:
In this phase, after the prototype has been reviewed by the customer and changes have been
made, it is once again given back to the customer so that they can check it once more and give
feedback. If it does not meet the requirements the customer wanted, another prototype is made
and the process repeats until it meets the requirements.
Engineer Product:
This phase is where the final product gets finalized and sent to the customer for full time use,
maintenance checkups are done to ensure the program does not fail.
Advantages of Prototyping:
 Due to the fact that the customer can see the product in an early stage gives the customer a
sense of satisfaction.
 The detection of errors at an earlier stage can save a lot of time
 Design has flexibility
Disadvantages of Prototyping:
 It is costly and time consuming
 Each time the prototype is evaluated by the customer, its challenging for the developers to
accommodate it each time
 Documentation is poor because customer’s requirements can change from time to time
 Hard to figure out how many times the program needs to be changed which is not good when
it comes to time management and cost
 Customer can lose interest if the product does not seem to match their standards, it can also
lead to them demanding for the product to be released quickly; they grow impatient.
Spiral Model, Advantages and Disadvantages:
Spiral Model:
Spiral model is said to be one of the most important models. The logic behind the name of this
model is that each loop in the spiral is considered a phase and it varies from project to project,
the radius of the spiral represents how costly the project is going to be, the angle of the spiral
shows how much progression has been made.
As with most models, there are any variations about each model but the main phases can be
explained into four phases which are:

 Requirement Gathering and Multiple Solutions
 Find and Solve Risks
 Next Iteration of the Product
 Planning for next Phase
Requirement Gathering:
The requirements are gathered from the customer which carries onto the objectives that get
elaborated and analyzed, this takes place in every phase.
Find and Solve Risks:
This is the second quadrant of the model and in this phase all the possible solutions are listed
which then later on gets evaluated. Since there are many solutions, many of them narrowed
down the right ones. Once the best possible solution is selected, it is then analyzed again in
terms or how much risk it carries.
Next Iteration of the Product:
After the product goes through the first and second phase, it is then created with all those things
included.
Planning of next Phase:
The customer evaluates the product again once it reaches the fourth quadrant and the next phase
begins.
Advantages for Spiral Model:
 It handles risk very well
 Very useful for large products
 Requirements can be flexible
 Customer is satisfied by this model
Disadvantages of Spiral Model:
 Complex
 Costly
 Requires experienced workers to use this model
 Not time manageable

Agile Methodologies:
Agile methodologies are multiple methods in a group which all in one way or another try to do
the same thing but each one of them contain unique traits, the list of these methodologies are as
follows:
 Scrum
 Extreme
 Lean
 Scaled Agile Frameworks (SAFe)
 Disciplined Agile Delivery (DAD)
 Kanban
 Disciplined Agile Delivery (DAD)
 Agile Modeling (AM) models
Scrum Methodology:
In the scrum methodology, the
main catch here is that the method
is used in ‘sprints’. The time for a
sprint lasts from 1 to 2 weeks.
Before each sprint a meeting is
planned out where the objectives
and what to complete is discussed
which leads to the creation of a
sprint backlog (a list of tasks to
perform during a sprint). The
hierarchy of Scrum methodology
is as follows:
 ScrumMaster
 Owner
 Scrum team

And other key terms to look out for are:
 Product backlog
 Sprint Backlog
Once a sprint has begun, each day a meeting is held where team members discuss what they
finish in that one day and eventually implement it into the main program or software, these
meetings are led by someone known as the ScrumMaster with the owner of the product lasting
no more than 15 minutes. After the sprint has been completed, the software is presented where
feedback is given ad later on those said feedbacks are added into the main software. Final phase
of Scrum ends with the members, ScrumMaster, and the owner hold a meeting discussing any
improvements in the software.
Product Backlog:
simply put a product backlog consists of all the main objectives that need to be accomplished
it can also be referred to as a to do list.
Sprint Backlog:
Sprint backlog basically includes the objectives that are in the product backlog in addition of
a plan on how to deliver the next increment of the sprint.
Advantages of Scrum Methodology:
 Incremental delivery helps in shortening overall program build time
 Testing after each sprint allows for thorough testing
 Requirements are not fixed which allows the owner themselves to join in and help
Disadvantages of Scrum Methodology:
 Does not always have clear requirements which leads to unstable management
 Constant change of pattern in the program makes it hard for the team to work properly
 Daily meetings can be taxing on the employee
Extreme Programming:
Extreme programming is a unique agile methodology as it forces the team to work extremely
hard on a project or following a high risk high reward method. Some of the main objectives that
it follows are:
 Small releases
 Simple design

 Development is test driven
 Pair programming
 Ownership of code
 40-hour work week
Programming starts out by coding it from the get go and releasing the program in small releases
and changing it when necessary. A simple design is kept to ensure that it will not hinder the main
program in terms of complexity. Usage of pair programming is utilized for a better work
environment that leads to better results. Ownership of the code is with everyone and no single
person so that it can be changed by everyone and to keep a better pace. Following of coding
standards is a must as the code is being handled by a team.
Although this model is meant to complete the program as fast as possible, it can prove to be a bit
difficult due to the fact that not everyone will work accordingly.
https://www.whizlabs.com/blog/what-is-extreme-programming-in-agile-software-development/
Advantages of Extreme Programming:
 Reduce time and cost when making a program
 Since simple code and design are made in extreme programing, it is easy to work with
 Progress is always being displayed
 Feedback is always given
Disadvantages of Extreme Programming:
 Due to the fact that most designs made are simple, the overall program will not have a
innovative design
 Focusing on how fast the code is created rather than the quality of it leads to poor quality
code
Lean Methodology:
Lean methodology at its core is simple which is to improve continuously all the while keeping
the respect of people, meaning the whole methodology revolves around keeping respect for the
customer and the employee and to continuously improve the program that they’re working on. It
is not as harsh as extreme programming and implies a softer and caring approach.
Lean consists of 5 main principles which are:
 Value
 Value Mapping
 Flow
 Pull
 Waste removal

Value:
Value can be determined into three categories which are non value add, value add, and business
value add activity and to know is the customer can pay for the project
Value Mapping:
to create a map for the steps, processes, and sequence in order to create the product
Flow:
To make sure info is going through smoothly with no drawbacks
Pull:
To only use material that is required and removing other items that will not be needed as a result
allowing us to communicate with the customer as soon as possible
Waste Removal:
What lean is mostly known for is the removal of waste, the acronym WORMPIT is used to
explain the 8 steps that are taken which will be discussed below
Value Determination:
There are three types of value:
 non-value add
 value add
 business value add activity
no value add stands for how value that will not help in the overall project, value add stands
for requirements that will help in the overall project and business value add activities are
requirements that are needed but not necessary
Waste Elimination:
As stated above the acronym WORMPIT is used to easily simplify the 8 main types of waste in
the lean methodology:
Type Definition
Waiting The waiting which comes in when the customer’s request is not fulfilled as
soon as possible, waiting for specific parts/information.
Overproduction The production of items or resources that the customer does not require
weather it is in a larger quantity or it is an item that the customer has not
requested for
Re-work Changing the product or repairing it is considered a type of waste because

Lean method is known for making something right on its first try
Motion Due to it taking a long time to complete, movement itself is also considered
a type of waste
Processing Giving the customer information which is not useful for them or that they do
not care for
Inventory Supplies that are not used due to it being above its minimum use is a type of
waste as it goes hand in hand with financial resources
Intellect Failure in using employees in terms of time and utilizing them effectively is
a type of waste
Transportation Transportation itself is considered a waste because it is not changing the
product with regards to its quality, rather it is only moving it from one place
to another so it is a waste.
Chain of Command in Lean Methodology:
much like in Scrum methodology, there exists a chain of command similar to Scrum in Lean
methodology which is:
 Lean Masters
 Lean Leaders
 Lean Practitioners
Lean Master:
they are at the top of the command and their job consists of guiding everyone including the
leaders and practitioners by making sure that everything goes accordingly to plan
Lean Leaders:
They are basically practitioners but with experience and their role is similar to a Lean Master,
they can handle 4 to 6 projects a year and are experts in using tools related to Lean
Lean Practitioners:
They usually lead small projects and help the leaders and masters
Advantages of Lean Methodology:
 Development process is simplified
 Due to its heavy focus on reducing waste, the percentage of losses are very miniscule
 Team involvement is increased
Disadvantages of Lean Methodology:
 Issues in const flow of supplies
 Costly

 Overtime work on employees
Safe Agile Frameworks (SAFe):
SAFe is a framework that allows for the use of Lean and Scrum methodologies on a enterprise
level
SAFe consists of 4 parts:
 Portfolio Level
 Programming Level and Team Level
 Large Solution
Portfolio Level:
On this level people like executives and leaders work and try to figure out the vison of the
business, its goals, and ways to make it more efficient. The visions and goals of the business
are then later sent down to the programming level.
Programming and Team Level:
At the programming level SAFe works similar to the Agile Release Train (ART) where
employee with within teams and divide time to work lasting 2 weeks on specific points of the
main project. While this is going on, other activities such as demos and meetings are also
being held.
Large Solution Level:
As the name states, large solution level consists of people that work on the business if it were
given a task which is too big to handle for one ART team as a result multiple ART teams are
dispatched which are controlled by the Large Solution team. Factors such as artifacts, roles,
events and coordination is a main job for this level.
Advantages and Disadvantages of SAFe:
 Provides a lightweight framework that still keeps is decision making skills of an enterprise
level intact
 Keeps teams and its goals in check
 Due to the nature of the framework, it distances certain members of the team such as
developers, testers and owner of the product making it hard for them to communicate to each
other
Disciplined Agile Delivery (DAD):

The objective regarding this methodology is that it focuses on a people-first learning-oriented
approach. It consists of many factors such as:
 lifecycle depending on risk and value
 is IT solution focused
 Goal driven
People-First Approach:
This means that people in work in teams from all sorts of specialists and there is no such
hierarchy within the team and people are encouraged to work cross functionally rather than
work on their specialty.
Learning-Oriented:
its proven before that a work environment which surrounds around learning is the best one so
in DAD there are three main aspects that are looked over which are domain learning which
asks the employee how they are helping the stakeholders and identify what they need to help
them with. Second point is to improve the overall process of you as an individual when it
comes to working in teams on a higher level. Third point consists of how an individual uses
the tools given to them and how to use them.
IT Solution Focused:
This factor presses on the matter that instead of employee to work on making software to
providing solutions. In other words it puts the word of stakeholders in a high regard and work
accordingly.
Goals Driven:
Due to the fact that each member is different and come from different places and have unique
thinking process, making sure to let the people working know that what they are supposed to
do, what skills to use and what where to use them is a big part that DAD focuses on.
Risk and Value Driven:
Risk and value over here points toward to how the employee have to look over smaller risks
and how much value they can offer, resulting to actions such as how each risk can affect the
main project and what value they can get from it if it were to be negated.
Advantages and Disadvantages of DAD:
 DAD is not prescriptive, does not force too much onto the employee.
 Focuses on solutions not software making it a better software as it is made by taking in
feedback constantly from stakeholders and consumers

 Is complicated because of its nature to follow an enterprise approach especially if someone
inexperienced works on it
 The fact that it relies on giving choices gives it more complexity
Kanban System:
Kanban system was originally made in Japan, the actual word itself means ‘billboard”. The
concept of Kanban is similar to of lean and Just in Time (JIT) methodology. Its not a control
system meant for inventory rather its main objective is to tell you what to, when and how
much to produce. There are three types of Kanban which are:
 Raw Material Kanban
 In-Process Kanban
 Finished Goods Kanban
Raw Material Kanban:
The amount of the product and when it should it be sent is the main objective of Raw Material
Kanban
In-Process Kanban:
In process Kanban or WIP Kanban (Work in Progress) shows the number of tasks that are taking
place at the moment and has the ability to set limits onto certain events to make sure it does not
overload the project and allows for a improved workflow.
Finished Goods Kanban:
As the name states, finished goods Kanban makes sure that an item is always in stock for it to be
used whenever it is needed and removal of said item notifies the user that more of that product is
needed/manufactured.
Advantages and Disadvantages of Kanban:
 Very simple to use and understand
 It is not costly at all

 If a lot of uncertainties were added in the Kanban system, the estimation will not be as
accurate
Main Differences between Traditional and Agile Models:
Traditional Agile
Making changes is not as easy due to it
following a top down approach by finishing
one phase at a time
Teams work on different things at a same
time and over time come to a best solution by
experimenting different methods
Work is based around leadership Anyone can present an idea to anyone and
communication flows freely
Phases require pre planning before they are
carried out
Workflow is more flexible and can be altered
if a request for modification were to be added
Involvement of customers is only needed in
the initial phases of the project
input from customers is essential for this
model and is required more frequently
1.2: Suggesting Suitable SDLC model, Identify Problems, Provide Reasoning for
Moving from Traditional to Agile:
The most suitable SDLC in this scenario that can be applied is Kanban as the problems that
Suzuki are facing is that their system is paper based which leads to delays and misplacements of
records that causes potential loss of customers. These main issues can be solved with ease if
Kanban system were to be used due to the fact that it fits really well with the type of work that
Suzuki is doing which is to manufacture parts of cars and sell it to them to customers, the
traditional method being used by Suzuki now cannot keep track which is why an Agile method
like Kanban is needed.
LO2: Produce a Feasibility Study for a System for a Business-
Related Problem:
P2 Produce a Feasibility Study for a System for a Business Related Problem:
Feasibility Report:

A study for all the things that a company or organization needs in terms of what they will need
ranging from technical to economic and that if it feasible to go for that idea, in out case its
Suzuki going from paper based to an online computer-based system, this will be categorized as
follows:
 Technical: about tech what sort of tech is going to be used
 Operational: who is going to use what
 Legal: getting licenses for the equipment, software, taxes, government registration
 Schedule: timing to fit all of the stuff (5 months etc)
 Economic: all the cost for the stuff mentioned in technical
Technical Feasibility:
This category of the report focuses on the technical side of thing such as computers, hardware,
the system used on the computers etc. in terms of Suzuki, they can easily do so as their line of
work heavily needs the use of computers which overall boast their capacity to work more
efficiently and effectively.
Operational Feasibility:
This category focuses on what will be the required factors needed to make the equipment work
ranging from employee to how well they can use their new systems in terms of what
opportunities they can achieve if they were to have it, for Suzuki this is excellent as some of their
problems are how records are getting misplaced, written down twice or lost and not found.
Having this will allow them to avail to many more opportunities. Proper employee will have to
be hired so that they can use their systems properly such as IT professionals.
Legal Feasibility:
What will the project have in terms or legal implications and what they need to do to get all of
their legal and ethical implications in order, in case of Suzuki they would need copyright over
the software that they are going to use, legal rights to use the server provided by SQL and to pay
all their taxes that come along with them moving to a digitalized system.
Schedule Feasibility:
Focuses on how much time the project will take, since Suzuki is following the Kanban
methodology, judging from the phases that are in Kanban the time frame is as follows:
 product backlog: 2 weeks
 Requirements: 1 month
 Design: 1 week
 Development:2 months
 Testing: 1 week
 Deployment: 3 to 4 days

Economic Feasibility:
Analysis regarding cost/analysis are focused in this category, what the amount will take to get
the certain equipment, how cost efficient its going to be and if it is worth it for the company. For
Suzuki it is very much needed that they use their assets to get an online system. Suzuki is a
multimillion dollar company and taking their system online will be very beneficial to them.
Servers and computers’ cost is 100,000PKR.
- Computers = 60,000
- Switches= 10,000
- Cabling= 10,000
- Internet connection=5000
- Trainer= 15000
Vision and Goal:
The main vision/ goal of this feasibility report is to shift Suzuki’s paper-based system to an
digitalized system. With the help of a system that can make it so that all of their main problems
regarding records are solved by using Kanban methodology
Security:
Installation of Bitefender GravityZone Elite offer very easy to use and comprehensive controls.
Login and pass
Cost-benefit analysis:
Moving to a digital way might cost more but it will be a one time buy as compared to the buying
of equipment for a paper-based system such as paper, ink paper clips. Not only this will be
costlier but it is hard to keep a track of as they are multiple items that are being bought in bulk
again and again which is not efficient as compared to buying a computer system. Cost for hiring
the right employee for the system to work is also a one time thing as once the employee get the
hang of it there is no need to spend more money, annual cost for paper based equipment is
45,000PKR monthly and cost for all the system based equipment including staff is around
10,0000 PKR.
LO3: Analyze Their System Using a Suitable Methodology:
P3 Analyses a System Using a Suitable Methodology for a Business-Related
Problem:
The methodology I will be using is called Kanban methodology, it consists of 6 phases which
are:
 Product Backlog
 Requirements

 Design
 Development
 Testing
 Deployment
Product Backlog:
A product backlog consists of all of the new features that are going to be changed once the
system is implemented such as infrastructure changes and changes to existing features, the
changes for our scenario are as follows:
 Going from paper based to digital
 Existing paper based will be removed
 Employee will need to learn the new system
 New employee will be hired such as teaching staff and new members for new departments
Requirements:
 An SQL server
 Internet
 Project manager
 Computers
 Routers
 Wires
 New roles for the employee
 New system to run on the computers
 Teaching staff for software
 Coder
Design:
This will include diagrams such as DFDs and ER diagrams which will be shown later down in
LO4
Development:
What it will take the develop the software, for our case Suzuki needs a software which can
handle all their records on a PC so that will be the main focus of the software which will be made
by the coder in junction with the designer
Testing:
Coder after coding the program he will test and debug the application to check effectiveness and
efficiency of the application if any error occur he will remove on timely basis.

Deployment:
This will be a joint effort for everyone working on the software as this is the final push, the
software will be checked one last time for nay bugs and will be deployed, buying the equipment,
creating a LAN, training staff with a guidebook
3.1: User and System Requirements, issues, security issues:
User and System Requirements:
The main user requirements are that they can operate the system, since we are making a new
software from scratch, it is essential to make it in a way that suits the needs for the company
which in our case is Suzuki and that it is not that hard to understand by the employee. Basic
requirements are needed though from the employee such as how to efficiently use a PC,
knowhow of shortcuts and a general understanding of the PC. Of course this software will be
taught by the teaching staff but a general understanding is definitely needed. As for the system
requirements, a PC with more than 4GB ram and a good intel core such as i8 and preferably
windows 10, server to save the records, routers and wires for internet.
Constraints, Security and How to Overcome them:
The main constraints here are that the employee might have a hard time learning the new system
as they are not used to this due to the fact that they were using paper-based system so this might
be a little bit overwhelming to them. Security issues can range from the PCs getting hacked
which can leak information of the employee such as addresses and personal info including
customer information.
Overcoming the learning process is solved by the teaching staff, as for security, a username and
password will be provided to every employee to ensure a safe and secure environment when it
comes to computer based work.
Identifying Team Members, Roles, Responsibilities,
Team Members:
 Project Manager:
Will overlook all other roles and all information will regulate from and to the project
manager. their responsibility is to make sure all the roles under their command are doing a
proper job and there are no issues
 Coder:

Main coder, will be help responsible for all the coding for the software, responsibilities range
from them having to make a proper software according to the instructions given by Suzuki
employees and work with designer.
 Designer:
Will be the main designer for the software, will be responsible for making sure the front end
of the software has all the needed animations, buttons, and according features properly fixed.
 Teaching Staff:
Consist of 2 people whose main job is to teach the new software to the already existing
employee, having daily classes and will regulate between positions from day to day,
responsible for teaching all the employee perfectly and that everyone understands how to use
the software.
 Tester:
Testing the final product, is going to work together with coder and designer so ensure that no
mistakes go thought to the final product such as bugs and errors
LO4: Design the System to Meet User and System Requirements:
P4 Design a Fully Functional System to Meet User and System Requirements for the
Business-Related Problem:
The main goal for this software is to make sure that the employee are able to use this instead of
the paper base system
 Adding Order
 search for records
 delete records
 logging in easily
 Adding User
 Adding Product
 Stock Report
 Track Order
What combination of buttons to press will be shown below for each of the commands.
These are the buttons for the software:
Ctrl+A Adding Order
Input Will ask to provide information about order
Process a record will be made in the database
Output A visible record will be displayed to user

Ctrl+S Search Record
Input Will ask for record’s name, date and date of
creation if any of them are provided
Process Search command will be sent to MySQL
database to search for said product
Output All results will be shown depending on what
type of information was added
Ctrl+D Deleting Record
Input A list will appear for which records that needs
to be deleted, user can sort them in multiple
ways
Process Database sends records to the PC for which
they searched for and deleted once the
command is given
Output Deleted successfully message appears on the
screen with an Undo option if needed
Ctrl+L Quick Login
Input Will ask for username and password
Process Both fields provided by user will be matched
with the ones in the database
Output Successfully logged in prompt appears
Ctrl+Alt+A Adding New User
Input Will ask for username and password and
email from user
Process A new record is made with the user’s
information in database
Output New user successfully added prompt is shown
otherwise error occurred prompt is shown
Ctrl+R Stock Report
Input Will ask user to type in the record’s date, data
of entry or keywords to search it
Process Database searches in the Records tab for all
possible searches
Output A list of all possible stock reports are shown,
if none are found error message shows

Ctrl+T Track Order
Input Will ask user to give either name of record,
date of creation or keywords
Process Database command is given to search for
record and show its tracking updates
Output All data regarding the order will be shown in
the form of a logbook, if not found then error
message is given
Tools Used:
Tools that will be used in this to make Kanban methodology are a data flow diagram and flow
chart, these two types of charts will be used to show how our solution for Suzuki will be
displayed in a form of a chart, both of these contain key elements that are:
Data Flow Diagram:
 Processes:
Takes in data and gives out a different result can be in a different from aswell, oval shaped
 Data Store:
This symbol represents when data needs to be stored for some amount of time due to other
processes taking place, rectangle shaped with a line in between
 External Entity:
An external entity that can either be a person or an organization that are outside of the main
components, rectangle shaped
 Data Flow Chart:
To represent when data is flowing from one part to another, can either be one date element or
multiple elements, an arrow

Data flow diagram of the whole process
Flow Chart:
Main elements in a flow chart are:
 Start:
the start or end of a process, oval shaped
 Process:
Takes in data and gives out a different result can be in a different from as well, rectangle
shaped
 Decision:
Diamond shaped, used when a decision is being made
 Arrow:
Gives a directional pathway for the user to follow when reading the chart
Flow chart used in our solution:

Tools and Techniques:
Tools are ways to define how a objective can be achieved whereas the technique is a way to
achieve that said objective in an efficient manner
Database application:
The database application used for Suzuki will be MySQL
Tools:
Some of the tools that are available to use in MySQL are:
 it offers scalability
 it is a Relational database management system
 compatible on many OS
some tools used in phpMyAdmin which is another great tool for creating a database which are:
 it can create, alter browse and drop databases
 can support foreign keys and InnoDB tables
Techniques:
Normalization:
it is the process of organizing your data in a database and its two main goals are to keep data
redundant and that all data are stored together. It is very important because it makes sure that the
database is not taking too much space
Specify Primary keys and Table Relationships:
Using primary key makes it so that it can uniquely identify each row and is very helpful if
duplicate rows or tables were to be made and making relationships allows for clarity when
defining certain items to another as relating them will make it easier to identify later on
Web Application:
Tools:
The tool used for developing the website is going to be Dreamweaver and some of its features
are:
 capability to design website in code view or create a website using front end commands
which does the coding on its own

 pre-emptive code suggestions
Techniques:
 be organized is a sense that the buttons, links that are used are in a certain formation so that
the user does not get distracted and remembers which buttons are where and familiarizes
themselves with the layout
 web animations are essential as they will help with creating a fluid website and make it look
cleaner and make it easier to understand
Software Applications:
Tools and techniques used in producing an software application:
Tools:
 DFD or dataflow diagrams is a way to represent a flow of data or a process visually
 HIPO Diagram or hierarchical input process output diagram is used to represent the hierarchy
of modules in a software system allowing for functions and sub functions to be kept in a
hierarchical manner
Techniques:
 Prototyping
 Waterfall
 Agile Methodologies
Identifying Design Documentation:
Documentation for Database System:
Documentation regarding a database includes viewpoints, certain aspects and main functions that
used for Suzuki
 Detailed informatics:
Each and every row means something and holds importance, so explaining each and every point
and what it means in the database is explained here

 What it Means for Employee:
with a database with many roles and a lot of information so this section will explain what each
employee will accomplish and what roles they shall be given
 Advantages:
This section states all the plus sides the company can achieve if it were to use this as Suzuki as of
now is still using paper based systems and have to go on a digitalized system, some
advantages can be efficiency with ease of access
Documentation for Web Application:
Ease of access:
Organizing all of the parts related information in a single tab with proper headings to ensure that
if the customer is looking for something specific they can do so with ease. Placing an order is
going to be just besides the part information
Customer Support:
Customer support option will always be available in any tab so if any customer wants help they
can easily look for it there
Healthy website design:
Overall website is based around it being user friendly and helpful to customers in every stop of
way with colorful headings and easy to find options and buttons with information regarding the
website, what its about, using logos and interactive tips to help the customer out
Documentation for Software Application:
This section explains what the software contains, description and constraints:
Description:
An overview of the software, what it includes, what it is used for, its main features and how it is
beneficial for Suzuki
Constraints:
With any product comes its down sides so in this section all the downsides of the software will
be explained if an emergency were to occur or if a component of the app were to fail, what steps
should be taken and what the employee should worry about and how it can be solved

References:
 Tutorialspoint.com. (2019). SDLC - Waterfall Model - Tutorialspoint. [online] Available at:
https://www.tutorialspoint.com/sdlc/sdlc_waterfall_model.htm [Accessed 26 Dec. 2019].
 GeeksforGeeks. (2019). Software Engineering | Prototyping Model - GeeksforGeeks.
[online] Available at: https://www.geeksforgeeks.org/software-engineering-prototyping-
model/ [Accessed 26 Dec. 2019].
 GeeksforGeeks. (2019). Software Engineering | Spiral Model - GeeksforGeeks. [online]
Available at: https://www.geeksforgeeks.org/software-engineering-spiral-model/
[Accessed 26 Dec. 2019].
 Cohn, M. (2019). Scrum Methodology and Project Management. [online] Mountain Goat
Software. Available at: https://www.mountaingoatsoftware.com/agile/scrum [Accessed 26
Dec. 2019].
 LeanKit. (2019). Lean Methodology | LeanKit. [online] Available at:
https://leankit.com/learn/lean/lean-methodology/ [Accessed 26 Dec. 2019].
 Scaledagileframework.com. (2019). Scaled Agile Framework – SAFe for Lean Enterprises.
[online] Available at: https://www.scaledagileframework.com/ [Accessed 26 Dec. 2019].
 Digite. (2019). What Is Kanban? An Overview Of The Kanban Method. [online] Available
at: https://www.digite.com/kanban/what-is-kanban/ [Accessed 26 Dec. 2019].