UNIT: 34 SYSTEM

ANALYSISAND DESIGN
Made by: Amjad Ali

System Analysis:
 System analysis is a process of collecting factual data understands the
processes involved identifying problems and create systems and
procedures that will efficiently achieve them.

(SDLC):
 SDLC or the software Development life Cycle It was process that the
produce software the highest quality and low cost in the shortest time
possible. Software Development life cycle provides a well-structured flow a
phases it was help organization too quickly and produce very high quality
software it was tested and ready to production use it.
P1:

Traditional SDLC:

Water Fall Model:

 The waterfall model is a classical model it used in a SDLC create system with
a linear and sequential approach it was termed waterfall because the
model development systematically from one phase to another downward
fashion.

 Water Model illustrates the software Development process in a linear

sequential flow and it means that they any phase in the development
process begins only.
The picture below illustrates the working design of Water Fall Model:

Strengths Weaknesses

That it was allows for departmentalization This methodology does not allow for
and control discovery iteration and refinement
whilst developing the product instead
Then schedule can be set schedule with new requirements must be written
deadlines for each stage of development

IT was product can proceed through the As it is static this methodology is not
development process model phases one suitable for projects where client or
by one business requirements many change
during development

Stage of Waterfall Model:

  Requirements Gathering and analysis
 System Design
 Implementation
 Integration and Testing
 Deployment of system
 Maintenance

 Requirements Gathering and analysis:

All Possible requirements of system to be developed they are captured this

phase and documented in a requirement specification doc.
 System design:
These requirements are specification to the first phase there are studied in that
phase or system design was prepared that was help in to specifying hardware or
system requirements it can also help to define overall system and architecture
this software code was written in to next stage was created now.

 Implementation:
When the code was written by (SDLC phase’s n.d) that was phase belong to
programmers to the waterfall method that was take a project and
requirements or specifications and this applications project was rolled out
the customer and maintenance phase begin.

 Integration and Testing:

When the project was done developer was tested to the product and installs
the system and it was test the project and that was fixed all bugs and problems
then was run system.

 Deployment of system:
 In that phase involve to making the software live and in this production real
environment after that was tested for that was tested thoroughly to the
previous phase.

 Maintenance:

When the deployment phase the next step was provide support or
maintenance to software making sure that was run smoothly that was
client and user come across to errors /bugs during to use and fixed them to
the main purpose of that stage.

Prototyping Model:
 It is a system development method in which a prototype is built tested and
then reworked as necessary until an acceptable outcome is achieved from
which the complete system or product can be development.
 Strengths Weaknesses

It model was flexible for design There model was very costly

This was very easy to detect errors This was poor documentation because
of continuously changing customer
requirements
We are find very easily mission functionality IT may be too much variation in
requirements
We can be reused by the developer for Sometimes customer demand the
more complicated project in the future actual product delivered soon after
seeing an early prototype

Stages of prototype model:

 Requirement:
 Developing:
 Review :
 Revise and Enhance:
  Requirement:
It was represent to the shell of actual production and that was use the
prototype to gather additional requirements and it will receive the
requirements and it should be document of some way you would
document and additional requirements that will gathering to through other
means.

 Developing:

It can range to a detailed draw with pen and paper it was fully working version
of product therefore prototype development was simply a series of processes
to the manufacture user and produce to the prototype model it was many
refer to prototype development as prototype manufacturing.

Spiral Model:
 This model is similar to the incremental development for a system with
more emphasis placed on risk analysis The spiral model has four phases
 planning design construct and evaluation the software project repeated the
passes through these phases in iterations called spirals this modal.


Strengths Weaknesses

Risk of high amount analysis hence
avoidance of Risk is enhanced
It was perfect for large and mission
critical project
Its strong approval and
documentation control and additional
functionality can be added at later
date
This is not suitable for small projects it
was expansive
It was more complex than other SDLC
model
Its dependable on risk analysis and
highly specific expertise and Difficulty
in time management end spiral may go
on indefinitely

Stages of Spiral model:

 Identification:
 Design:
 Construct and Build:
  Evaluation and Risk Analysis:

 Identification:

That phase was gathering to the business requirement or baselines spiral this
phase was includes understanding the system and requirements by continuous
communication between to customer or system analyst.

Design:

In that stages start the concept design was standard the spiral or that was include
the architectural design modules rational design physical produce and our last
design was successive to spiral model.

 Construct and Build:

That was refer to this production of actual software product to every spiral
in that base line are spiral then the product was just thought to design is
being developed proof of concept or it was developed to the phase and get
the customer feedback.

 Evaluation and Risk Analysis:

It was risked in to analysis include the identifying estimating or observing

technical feasibility that was schedule slippage and that cost overrun after to the
testing and build the end of first iteration was user is evaluates to the software
and that was provide the feedback.

Agile Methodologies:

Scrum:
 It is a framework that helps teams work together often thought of as an
agile project management farm work scrum describes a set of meetings
 tools and roles that work under the concert help teams structure or
manage their work.

 It is a lightweight framework that helps people team and organizations

generate values through adaptive solutions for complex problems.

 This is a lightweight agile process framework it used primary managing

software development scrum is often contrasted with the so called
waterfall approach which emphasize up front planning and it scheduling is
activities followed by execution.

Strengths Weaknesses

It was help to team complete project
and deliverables quickly and efficiently
This was ensure effective use of time
and money
There large project are divided into
easily manageable sprints
It often leads to scope creep due to the
lack of a definite end date
The chances of project failure are high if
individuals aren’t very committed or
cooperative
This framework can be successful only
with experienced team members
Phases of Scrum:
1. Product Backlog Creation
2. Sprint planning and creating backlog
3. Working on sprint
4. Testing and product Demonstration
5. Retrospective and the next sprint planning

1. Product Backlog Creation:

It was simply list of all things it will need to done with in project that will
replace the traditional requirements specification artefacts this items can
have a technical nature and it can be user centric.

2. Sprint planning and creating backlog:

It will be start with planning it will be usually done during the sprint
meeting the planning phase scrum team product backlog items in that
sprint once these item was selected to the team go to plan how they will go
and about the work.

3. Working on sprint :
It will set period of time and during which specific or work was to be
complete and it made ready for review each sprint begins with a planning
meeting or traditionally a sprint last thirty days after a sprint beings product
owner must step back and let team do their work.

4. Testing and product Demonstration:

When the product was done the team was tested a product and seen that
how it was turn out form the customer point of view.

5. Retrospective and the next sprint planning:

 Sprint review are about the product while the sprint retrospective was
about the team and while the sprint review was help to you regularly and
meet customer expectations and retrospectives allow scrum team and
become a faster , smarter or even happier.

Extreme Programming:
 Extreme programming it is a software development methodology that’s part
of what’s collectively known as agile methodologies It is a built upon values
principles and practices and its goal that was allow small to mid-sized teams
to produce good and high quality software or adapt to evolving and
changing requirements.

Advantages
No Unnecessary programming work
Stables software through continuous
testing
These more difficult to measure
progress than in the waterfall because
Disadvantages
Customer must participate in the
process
Relatively large time investment and
relatively high costs
It is not best option of programmers
are separated to geographically
the progress happens across several
cycles

Phases of XP:
 Coding
 Testing
 Listening
 Designing

Coding:

It will give a uniform to codes and written to different engineers and that improve
readability or maintainability of code and that will reduce the complexity also
help to again use code and detect error very easily and it was promote sound
programming practices or increases efficiency of programmer.

Testing:

It was an integrated activity of XP team and developer tea, was need to continual
feedback with the customer expressing they need to terms and programmers and
expressing the design or coding in that terms of test and the XP team was tested
and play both the customer and programmer roles.

Listening:

In this pair programming we are listening to known what to code and how to test
if we do not listen we don’t know what to code and how to test it.

Designing:
It is a methodology that the rule is to keep thing and the name suggest simple an
acronym was brought an early to the birth of XP that underline the methodology
and simple design.

Lean:
 We are explain the example of Agile method that of lean software
development. It mean by removing all thing unnecessary of the little
suggest to that aims removing all things unnecessary all the fat from
software engineering overall there are seven principle of to the lean
software development each aiming to quicken delivery and bring higher
values to and user eliminating waste.

Eliminate Waste:
 Waste is anything that interferes with giving customer what they really
value at the time and place where it will provide the most value.

 Many times caused by large inventories of partially done work.

Build Quality:
 You don’t focus on putting defects into a tracking system you avoid creating
defects in the first place.
 Expect to change exiting code and refactor often.
 Write code keep the code base simple.
Create Knowledge:
 Software is a knowledge creating process.
 Validation of architecture comes as the code is being written.
 An early design cannot fully anticipate the complexity encountered during
implementation.

Defer Commitment:
 Schedule irreversible decisions for the last responsible moment.
 We should try to most decision reversible.

Deliver Fast:
 We need to figure out how to deliver software so fast that our customers
don’t have time to change their minds.
 Eliminated a huge amount of waste and low defect rates.

Respect People:
 Expert technical work force.
 Appropriate technical expertise is nurtured.

Optimize the Whole:

 A lean organization optimizes the whole value stream.
 A customer wants some new features yesterday.
The picture below shows the working of the Lean Model:

Strengths Weaknesses
Less infrastructure and limited waste Equipment or labour failure
Worker satisfaction just in time Missed deliveries
Competitive advantages and strong Low margin for error
customer relationships

Disciplined Agile Delivery:

It is a people first learning oriented hybrid agile approach it solution delivery it
has a risk value delivery lifecycle is goal driven is enterprise aware and is scalable.
It was seven summary primary principles behind DAD are listed below.

1. Delight Customer: They delight our customer when our product and
services not only fulfil their needs and expectation but surpass them.

2. Be Awesome: its team are built around motivated individuals who are
given the environment and support required to fulfil their objectives its
very good working.

3. Pragmatism: In fact we have met many who say that to do agile right
you need to have 5-9 people in room, with the business Product Owner
present at all times.

4. Context Counts: Every person is unique with their own set of skills
preferences for work style career goals and learning styles every team is
unique not only because it was composed to unique people but also
because that faces a unique situation.

5. Choice is Good: it was given a choice to choose own process and its
experiment is discover what’s work them.

6. Optimize Flow: We want to optimize flow across the value stream that
we are part of and better yet across our organization.
 7. Enterprise Awareness: The observation is that DA teams work within
your organizations.

Advantage
Empowering and engaging team
members,
DAD promotes a goal based strategy
over the prescriptive procedure,
Its meaning team are empowered to
choose their own way of working its
applying method and frameworks
which work for them,
Disadvantage
DAD has no rigid guidelines new
organizations may find it difficult to
cope up ,
It may not successful for organizations
preparing for a transition,
It’s from the traditional methodology to
agile methodology,

Phases of Disciplined Agile Delivery:

 Inception:
 Construction:
 Transition:

Inception:
Team will be initiation activities and occur during that phase.

Construction:

During in that phase is delivery team was produce the potentially consumable of
solution an incremental basis.

Transition:

In this process the tool kit of include an explicit transition phase and sometime a
deployment phase release the phase and hardening sprint and it will conducted
after the construction by agile lean project team.

Kanban:
 This is Japanese for sign it is an inventory control system used in just in time
JIT manufacturing to track production and order new shipment of parts and
materials that system will be help us to manage flow by highlighting the
various stage of the workflow or the status of work in each stage kanban
help us team analyse to the system and make adjustment to improve flow
so as to reduce the time it takes to complete each pieces of work it was
fowling two concept.

Visualize the Work:

 Make the workflow stages to columns on a board

 Identify the values stream
 Define types of work and what done means for them
 Decide on a card template for each types of work.

Limit the Work-in-Progress:

In this process of reducing the number of work items that they are in progress at
any one time. For an organization this may mean limiting the number of projects
in development.
 Advantage
It is method applied across all field of
work to help team
Drive down cost and become more
efficient by visualizing and improving
work flows
it give you flexibility to build
sustainable competitive advantage
and empower team to accomplish
more faster
Disadvantage
Kanban is a method applied across all
fields of work to help teams drive
down costs
It became more efficient by
visualizing and improving workflows
It gives you the flexibility to build
sustainable competitive advantage
and empower your team to
accomplish faster.
Phases of Kanban:

 Backlog:
 Impact and Analysis:
 Build:
 Testing and done:

Backlog:

That project and product backlog is visual representation of these items and we
are May or may not deliver on kanban board its lives on the left most part before
to do stage of column.

Impact and Analysis:

it will help us to manage the flow by highlighting various stage of workflow or

status of work in each stage it was help to team analyse the system or make be
adjustment and improve flow it reduce the time and this take to complete each
piece of work.

Build:

We are shared benefit of kanban or scrum methodologies and create bare bones
and basic kanban and scrum board and we are decided if we are doing kanban or
scrum we are add the user stories column to our board.

Testing and done:

Its simple level of kanban in software testing it’s all about of visualizing project
status it was clearly understand what sitting in backlog waiting to pick up and
what work of currently in that progress or what work is complete.

Feature-Driven Development:
In this methodology for develop a software feature driven development FDD was
customer centric iterative or incremental to the goal delivering tangible software
result and efficiently FDD in agile encourages status reporting at all levels which
helps to track progress and results FDD has five processes that are considered
while using it.

1. Develop an Overall Model:

Domain member present or initial high level highlights only walkthrough to the
scope of system or its context the domain and development to member produce
skeletal model and the very beginning of that will follow the present more detail
walkthrough.

2. Build a feature:

It list. Knowledge gathered during the initial modelling is used to identify a list of

features by functionally decomposing the domain into subject areas.

3. Plan by Feature:

It is an approach used in release planning. Features and scope take priority over
date. Using this approach release plans are created by estimating the amount of
time that will be required to complete a certain defined amount of scope.

4. Design by Feature:

This is known as design by features or feature based modelling one can start
either with a more or less complete geometric model and define form features on
it, or one starts from scratch by combining form features from a standard library.

5. Build by Feature:

Finely we are design inspection is complete and developer activity and develop
the code and within respective classes.
 Advantages
Gives the team a very good
understanding of the project's scope
and context
 Fdd uses documentation to
communicate
Uses a user centric approach With
scrum the product manager is usually
considered the end user with fdd the
client is the end user
Disadvantage
Provides no written documentation to
the client, although
There is a lot of documented
communication among team
members during the project
development cycles. 
 Therefore, the client is not able to get
a proof for their own software.
P2: Produce a feasibility study for a system for a
business related problem:

Feasibility Report:
 IT was study in the system analysis it’s consider to all of project relevant
factor or including economic technical legal and scheduling considerations
and ascertain in the completing to the project for successfully.

 Why we need to conduct a feasibility study?

 That is important feasibility study it was based on resources and business
or budget and time, it was provide a new ideas

Types of Feasibility Study:

These are different types of feasibility studies I will define under the some types:

1. Technical Feasibility
2. Economic Feasibility
3. Legal Feasibility
4. Schedule Feasibility
5. Operational Feasibility

Technical Feasibility:
That was say to company does have a technological resources are available in
company complete his project.

Economic feasibility:
That was say to us financial resource of company and it study was most common
and that cost/benefits analysis.

Legal feasibility:
This study that will make sure to project get start to meet of all legal or ethical
and what are legal implication of project did the company have its own legal
license for work?

Schedule feasibility:
Did the company that was complete the project of in fixed time and it was
currently time to get start his project.

Operational feasibility:
Operational feasibility that how to better solve problems to your company to the
project,

Technical Feasibility:

Technologies available to support the proposed system:

 They need some computers of the Suzuki Company for counter.
 They needed to printer to the print the docks.
 They were need for connections for some switches wires and internet
connection.
 Suzuki company need to barcode reader it was read to parts information.
Economic Feasibility:
The price of management system install is give:

 New hardware cost:

 New computer cost – 70,000 PKR
 New install network cost – 30,000 PKR
 New barcode cost – 15,000 PKR
 New printer cost --50,000 PKR
 Total cost of management system and installing is –165,000 PKR

Benefits:
They will save a time and it was do the work many time that system data was safe
and secure because it is manual system and they are manage to very easy. And it
was store own data and they will find very easy in to the computer system.

Legal Feasibility:

We are defining these are some rules and regulation should they
follow and use a system:
 They get software license for Suzuki Company.
 They complete his legal requirement of Software Company to Suzuki
Company.
 They get SQL server license for Suzuki Company.
 And paid taxes (EPF, ETF)
  Registration to the government

BENEFITS:

 This information is safe and secure.

 This information could be right.
 That information was used for limited purpose.
 This information could be right and up the data.
 This software license is only for Suzuki Company cannot be copy anything
for the market.

Schedule Feasibility:
These are propose of system will take 7 months at last to finished and
ready to installed.

Information gathering Apr/5/2021

Designing Apr/20/2021

Designing SDLC model Apr/28/2021

Develop user interface May/18/2021

Coding May/24/21
Release version Jun/14/2021

Testing alpha Jun/28/2021

Fix problems in alpha stage July/11/2021

Release beta version July/22/2021

Testing beta version Aug/8/2021

Fix and problems in the alpha stage Aug/30/2021

Final system test Sep/20/2021

Software release to Suzuki Company Oct/21/2021

Operational Feasibility:
Operational feasibility that was solved problem and they are present in manual
system. These are so many problems in present manual system of Suzuki
Company When the complete process of analyse these are so many issues found
in present to the system.

 Stored the many recode two times.

 That was consuming when its recode was done.
 These are so many products they are not measured properly.

P3:

This 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:

It 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 they 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 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 held 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 e

P4:

Introduction:
Its describe the document that is a software It will do and that will be expected to
the perform that will be describe the functionality that product needs to fulfil all
stake holder and Business user.

Purpose:

It is provide us detailed and overview our software product and it was minimizes
to the development cost that good it’s define to how an application interact in
system hardware this other programs and human user in wide variety of real
world situation.

Document Conventions:

Follow convention is used in written the SRS:

 Space of line is 1.4.

 Font heading size is 14pts, not bold.
 These other all font description is in 14pts, normal fonts.
 The font size is 16pts and bold I will use to main heading.
 That reference was written by according the Harvard referencing
format.
Intended Audience and reading suggestions:

These documents are helpful of users, testers, project managers, director of

system, these document was submit in the requirements of client and it
procedure was used in realize a goal set in developer.

 Users were administrator of system, and owner or workers of Suzuki

Company, this document are very help full idea of them about knows the
software.
 Testers that should have these document for them system test and again
these documentation the check of his performance and function excited in
this line that required level was uttered or agreed him.

Developers:

They will document find need in order then they follow the guidelines and it will
easy access the program of system in the development and these are also use this
same documentation in future when if the need of observe what the requirement
of these and he had agreed to develop the software

Product scope:

That rule is objective in this software it was provide a Suzuki management system
Automated for Suzuki parts and we are implement web based application they
are used manual system and all records are in book instead Suzuki part
management system after the evaluation of the company resources the project
objective was decided and setup of objective was denoted to achieved from
estimation and time of company parts are available.
Overall description:

Product Perspective:

These purposed of Suzuki company management system it was develop of

desktop application and web based application these purpose of in the system
control all of the day by day activities and well organized in that moment these all
process work manually this system was help the improving work flow and
between virus processes of management of perfect collation it details of very best
system that able intro of Suzuki company was perfect organize management that
will easy to track and take all information collect and recover easy any time these
are ability, we easy to generate report and take decision and it will purpose new
system disappear to current paper work based manual method that is so much
harmful us .

Data Flow Diagram:

Its show the way information flow through a process or system it include data
input and output data stores and the various sub processes the data and move
through we can use these diagram to map out an existing system and make it
better to plan out a new system for implementation.

We are representation of our solution data flow diagram will look following:

Updated
Customer More Parts Costumer
inventory
 Oder placing Inventory Checking Delivery

User use a computer or mobile system it will place an order to Suzuki spare parts
and manufacturer and our system will check these parts are available in the
inventory if part are available in inventory so these parts check quality officer
check-up mark After We start the delivery process and the product reach the
customer.

Flow Chart:
This was used to represent our workflow that was show diagrammatic
representation of an algorithm in that step by step then approach elements
involved in a producing in flow chart and we are define the below.

 Diamond: IT making use for the decisions.

 Arrow: IT was represent the flow the chart process.
 Rectangle: IT was symbol that was show in the process done.
 Oval: This shape is used for show start and end process.
Flow chart used for our solution is shown below:

We are show the process start first user place and order and this order was
submit in to the database we are check customer requirement of parts are
available or not. If part are available we are start the delivery process and we are
delivered the part of costumer and process stop, if other parts or not available
then we designed new part and our database update following these the new
items and delivered to costumer and the flow stop.
Entity Relation Diagram:
The database for newly designed will work on following entity relationship
diagram:

We can be seen the ERD many products if we one invoice and multiple invoice
given each customer When a single product or multiple number and copies the
stock they are one too many relationships One and other hand many customer
then place and order for same product then before the many to one relationship
exists.
Function:
Following is the way how the user will be able to use the newly built agile
system remotely:

User login:

Ctrl + R (user) User authentication

Description IT place were asked user information

login
Date input The user put in the information login
such as user , name and password etc.
Description This system was match user given
information and database system
check an authentic user in trying to
login

Display Know user was login successfully into

the system

Search inventory:

Ctrl + d (find) That’s search bar open short key

Description In this search bar user was available
Search bar It was enter key (s) in the search bar to locate the
item
 Description It was match the user and located his item on the
search bar
Display Finely it was show the result query located the item
in search bar is available

Add product:

Ctrl + (product) Product section It will appear the

system
Description It will show information about product
in system by the user
Process This system save the user information if
are valid
Display Last update added the product
information and it will show massage to
the user

Add item:

Ctrl + I (item) Section of item information

Description That product was selected it can be
added of rest information
Input We will enter the product price and
serial number
Display It will cross the referencing that the
system massage show successful

Purchase item:

Ctrl + Y (BUY) Buy the items

Description Price of item, R, p type and it will
added to the purchase line
 Data input Add the product name
Process It system was save product purchased
after veiled database

Sale:
Ctrl + A (Sale) That was open sale section
Description It was put the information about sales
Invoice Database was generate invoice that the
purchased item
Action When invoice to save in database and
show successful massage

Billing:

Ctrl + T (report) It will be generate key of report section

Description It will chose best database format for
bill generation
Data input It will be added data invoice by the
database administer
Description When invoice was printed show
successful massage and appear update
of current inventory

Use case name New account create

Pre-conditions The system was running and up
The user was login successful in the system
Primary actor Owner , administer
Main success scenario 1.This case begin the user is entered relevant of
data
2. User input the field details
3.User proceed click button
4.The data system is valid
5. create a new profile
 Extensions Create a new account that has been error massage

Other Non-functional requirements:

 Performance requirement:

 That Suzuki management system was using multiple user access to system
at same time.

 That fix response time was 10 ss.

 That application was handle very large amount of work load.

Safety Requirements:

Software system use is solution of Suzuki parts and management data product
safety and user moral matter could be give deliberation when using system, it
should not be damage or injured a data to virus technical failure its backup and
restoration of data that was required to the client and loss of data unforeseen
form database its away from build the data and that should influence
performance of the system this situation we are current suddenly go for work
save in duplicate file into safe way after that software in good position.

Software Requirement:

User login system then he should give username and password veiled
 Then specific user various provide advantages to Suzuki company
employment hierarchy user could access permission provide fast then
must avoid mistake for example violation access right. There was any
modification system could regulated the system administrator.

Software quality attributes:

 Availability
 Security
 Usability
 Maintainability
 Reliability
 Integrity

Business rules:
Each user of the system must have an authenticated username and
password.

 Administrator full capacity control to the login system. Than he was

access capability change any required control or system of the user
and then activities the system.
 Allocated operations only allow for cashier, He did not control
systems capacity and these activities.
 Worker did not functioning capacity and basic functionalities
perform the system.

Other Requirements:

Following are the additional requirements and constraints of the system to be

implemented.

- System that could be only follows Suzuki company parts.

- The Desktop application was development with C++ programing language
in visual studio 2012,
- MYSQL server was the database management software and it was be must
enough storage hold like a data.