1

System Analysis and Design Overview

Contents
System ..................................................................................................................................................... 2
System Analysis ....................................................................................................................................... 2
System Design ......................................................................................................................................... 2
Role of System Analyst............................................................................................................................ 2
Problem ............................................................................................................................................... 2
Solution ............................................................................................................................................... 2
Implementation of UML.......................................................................................................................... 3
Uml as sketch ...................................................................................................................................... 3
UML as Blue Print................................................................................................................................ 3
UML as Programming Language ......................................................................................................... 3
Components of the UML ......................................................................................................................... 3
Class Diagram .......................................................................................................................................... 3
Example of Class Diagram ................................................................................................................... 3
Object Diagram ....................................................................................................................................... 4
Use Case Diagram ................................................................................................................................... 4
SYSTEM DEVELOPMENT LIFE CYCLE ........................................................................................................ 5
System Study ...................................................................................................................................... 5
Feasibility Study ................................................................................................................................. 5
System Design .................................................................................................................................... 6
Coding ................................................................................................................................................. 6
Testing ................................................................................................................................................. 6
Implementation .................................................................................................................................. 6
Maintenance ........................................................................................................................................ 7
SDLC Objectives....................................................................................................................................... 7
Prepared By............................................................................................................................................. 7

System

organized set of related components established to accomplish certain task

Natural

Planned and placed by people

System Analysis
It emphasises to the investigation of the problem and users/clients requirements rather
than the solutions
Phrase: do the right thing
Concentration: investigation part of the problem. i.e: specific specification that are going to
mentioned by the user.

System Design
It emphasises to the conceptual solution rather than the implementation
Phrase: do the thing right
Concentration: aspects of the design, aspect of the implementation, transformation of
users\Clients requirements into software processes, data structures.

Role of System Analyst

Gather requirements from the user AKA information gathering

Prepare Requirement analysis document
Pass the document to the developers to do the implementation

Problem
Misunderstanding between user/client and system analyst, due to lack of proper
interpretation and support while information gathering

Solution
UML as in diagrammed notation, blue print of the system. A simplified overview of desired
system and its functionalities.

Implementation of UML
Uml as sketch: informal way and incomplete diagram created to explore difficult parts
of the problem exploiting the power of visual language.

UML as Blue Print: relatively designed diagrams used both for reverse engineering to
visualize and better understanding by existing code UML diagrams and for forwarded
engineering.

UML as Programming Language: complete executable specification of a software

system in UML. Executable code will automatically generated but it is not normally seen
or modified by developers. In short prototype.

Components of the UML:

1. UML consists of various graphical elements that combine to form diagrams.
2. Since UML is a language, it has rules for combine these elements
3. The purpose of the diagram is to present multiple views of a system; this set of
multiple views is called a mode
4. A model is set of UML diagrams that we can examine, assess and modify in order
to understand and develop a system

Class Diagram
1.
2.
3.
4.
5.

Think about the things in the world around you.

They will have attributes/properties and they behave in certain ways/operations
Also, these things fall into categories
We refer the categories as Classes
A class is category or group of things that have the same attributes and the same
behaviours

Example of Class Diagram

1. A class of washing Machine
2. Attributes: Brand name, Model, Serial Number, Capacity etc.
3. Operations: Accept clothes, Accept detergent, Turn On, Start washing, Stop
washing Turn off etc.
4. The rectangle with 3 areas is the icon that represents the class.

Washing Machine
Brand Name
Model
SerialNumber
Capacity
acceptClothes()
acceptDetergent()
turnOn()
startWashing()
stopWashing()
turnoff()
Fig: Icon of Class Diagram

Object Diagram
1. An object is an instance of the class
2. A specific thing that has specific values of the classs attributes
3. Your washing machine might have the brand name LG, the model name SP12T and
capacity 5kg

myWashingMechine:WashingMechine
Fig: Icon for named Object
:WasingMechine
Fig: Icon for Anonymous Object

Use Case Diagram

A Use Case is description of a systems behaviour from a users standpoint

For systems developers, the use case is a valuable tool: a technique to gather
system requirements from a users point of view.

SYSTEM DEVELOPMENT LIFE CYCLE

System life cycle is an organizational process of developing and maintaining systems. It helps
in establishing a system project plan, because it gives overall list of processes and subprocesses required developing a system.
Following are the different phases of software development cycle:
1. System study
2. Feasibility study
3. System analysis
4. System design
5. Coding
6. Testing
7. Implementation
8. Maintenance

Fig. Different phases of System development Life Cycle

System Study
The system study is done in two phases. In the first phase:
1. Identifying the scope of the system
2.
Identification
of
limitations
and
problems

users
of
the

requirement
present
system

and
are

the
studied.

Feasibility Study
Workability, meeting users requirements, effective use of resources and the cost
effectiveness.
The
main goal of feasibility study is not to solve the problem but to achieve the scope. In the

process of feasibility study, the cost and benefits are estimated with greater accuracy.

System Analysis
Specification of what the new system is to accomplish based on the user
requirements.
Functional hierarchy showing the functions to be performed by the new system
and their relationship with each other.
Function network which are similar to function hierarchy but they highlight the
those functions which are common to more than one procedure.
List of attributes of the entities - these are the data items which need to be held
about each entity (record)

System Design
The design proceeds in two stages :
Preliminary or general design
Structure or detailed design
There are several tools and techniques used for designing. These tools and techniques are:
Flowchart
Data flow diagram (DFDs)
Data dictionary
Structured English
Decision table
Decision tree
Coding
This
is
also
called
the
programming phase in which the programmer converts the program specifications into
computer instructions, which we refer as programs. The programs coordinate the data
movements and control the entire process in a system.

Testing
Before actually implementing the new system into operations, a test run of the system is done
removing all the bugs, if any. It is an important phase of a successful system.

Implementation
After having the user acceptance of the new system developed, the implementation phase
begins. Implementation is the stage of a project during which theory is turned into
practice. During this phase, all the programs of the system are loaded onto the user's

computer. After loading the system, training of the users starts. Main topics of such type
of training are:

How to execute the package

How to enter the data
How to process the data (processing details)
How to take out the reports

Maintenance
Maintenance is necessary to eliminate errors in the system during its working life and to
tune the system to any variations in its working environment. It has been seen that there
are always some errors found in the system that must be noted and corrected. It also
means the review of the system from time to time.

SDLC Objectives
Ease of use
Good performance
Cost effective
Ease of maintenance
Expandable
Key - system that responds & fulfills needs

Prepared By
Sheikh Faiyaz Moorsalin
Awlad Hossain
Joy Acharia