SYSTEM ANALYSIS AND DESIGN

LECTURE-1

System ?
Is a Collection of Components that will work

together to achieve some Goal. Three Basic components are 1. INPUT 2. PROCESSING 3. OUPUT

 Systems are created to solve problem.

The System approach is an organized way of

dealing problem. Example: Library System.

Introduction-System
The word System is derived from the Greek

Word SYSTEMA. Which means organized relationship among Components

Characteristics of a System
The following are the Characteristics of a System
1. 2. 3. 4. 5.

Systems are organized. System components interact with each other. System components are interdependent. System components are integrated. System has a central objective

1. Systems are organized

It have particular order and have a structure to

achieve specific objective. E.g.: Hierarchical relationship from Chief Librarian to Clerk.
It specifies the formal flow of communication

2. System Components Interact with each other.

Interaction between Components.

Eg: Library System Circulation Component - Interact with User. Acquisition Component - Interact with cataloguing and classification of books.

3. System Components are Interdependent

No Subsystem can function isolate.
They are linked with other components according

to the plan. One component depends on another one. E.g.: User Taking Book in the library.

4. System Components are integrated.

It concerned with how systems are tied together.
It is more than SHARING a physical part or

location with other components.

5. System has a Central Objective

System works to achieve a central objective.

Eg: To meet the information needs of the users Library is formed .

Elements of a System
1.
2. 3. 4. 5. 6.

Input / Output. Processor. Control. Feedback. Environment. Boundaries and interface.

1. Input / Output
Input : Elements that are enter into

System for processing.

Output: Outcome of Processing.

2. Processor
Involved in actual transformation of input into

output.
It may modify the input totally or partially

depending on the specification.

3. Control
To keep system in BALANCE.
It control the activities like input, processing and

the output.

4. Feedback
It helps the user to inform how the system works.
It

can be collected implemented.

after

the

system

is

5. Environment
Is the Source of External Elements that acts on

the system and determine how the system should function. Eg: For Library Booksellers, Publishers.

6. Boundaries and interface

The role of components must be restricted.

Eg: Circulation System in the library is restricted to issue and return of books .

Types of System
1.
2. 3. 4. 5.

Physical Abstract Open System Closed System Man made information System.

1. Physical
They can be seen over the naked eyes and able

to counted.
These are tangible or the materials.

Eg: In Library Books, Shelves, Desks .

2. Abstract
These are Conceptual or Non Physical Entities.

They may be formula of relationship among

variables. E.g. : Model is the representation of planned thing .

3. Open System
Has several interfaces with its environment.
It receives input and delivers the output to the

outside. Eg: Library

4. Closed System
It is isolated from the environmental influences.
It is more relevant to scientific system.

5. Man made information System

Is the basics for interaction between the users

and the analyst.

It provides instruction ,commands and feedback.

LECTURE-2

Succeeding as a Systems Analysts

System Analyst
A systems analyst researches problems. He Plans solutions Recommends software and systems Coordinates development to meet business or other

requirements.
The systems analysts are the liaisons between

vendors and IT professionals.

System Analyst May

Interact with the customers to learn and document

requirements. Interact with designers to understand software limitations. Help programmers during system development. Perform system testing. Deploy the completed system. Document requirements or contribute to user manuals.

System Analysis
It includes system's study in order to get facts

about business activity.

It is about getting information and determining

requirements.
Here the responsibility includes only requirement

determination, not the design of the system.

Contents
Discuss the analytical skills

Describe the technical skills

Discuss the management skills Identify the interpersonal skills

Relationship between system analysts skills and SDLC phases

Interpersonal skills
Project identification and selections phase Project initiation and planning phase

Analytical skills
Analysis phase

Management skills
Design phase

Technical skills
Implementation phase Maintenance phase

Analytical skills for System analysts

We will focus on four sets of analytical skills. They

are:
System thinking Organizational knowledge

Problem identification
Problem analyzing and solving

Analytical skills for System analysts:

1. System thinking
Systems and its characteristics System is an interrelated set of components, with identifiable boundary, working together for some purpose A system has nine characteristics: Components----------------------Subsystems Interrelated components A boundary A purpose An environment Interfaces Input Output Constraints

Interface

Environment
Components Input

Output

Boundary
Interrelationship

System characteristics
A component an irreducible part or aggregation of parts that make up a system, also called a subsystem Interrelated components Dependence of one subsystem on one or more subsystems Boundary The line that marks the inside and outside of a system and that sets off the system form its environment

 Purpose The overall goal or function of a system Environment Everything external to a system that interacts with the system Interface Point of contact where a system meets its environment or where subsystems meet each other.

 Constraint A limit to what a system can accomplish Input Whatever a system takes from its environment in order to fulfill its purpose Output Whatever a system returns from its environment in order to fulfill its purpose

Technical Skills (1)

Many aspects of your job as a system analyst

are technically oriented. The following activities will help you stay up-todate:
Read trade publications Join professional societies Attend classes or teach at a local college Attend many courses or training sessions offered by your organizations Attend professional conferences, seminars, or trade shows Participate in electronic bulletin, new groups

Management Skills
System analysts are almost always members of

project teams and are frequently asked to lead team. Management skills are very useful for anyone in a leadership role. There are three class of management skills:
1- Resources 2- Project 3- Risk

Interpersonal skills
Communication skills

Interviewing, Listening, and questionnaires

Written and oral presentations Meeting agenda Meeting minutes Interview summaries Requests for proposal from contractors and vendors Working alone and with a team

End User
End-user is the person who uses a product. The end-user or consumer may differ from the

person who purchases the product.

For instance, if a zookeeper purchases Horse food. Here The purchaser of the product is different than

the end-user (the horse) of that product.

LECTURE-3

SDLC
Preliminary study

Feasibility study
Detailed system study System analysis System design Coding Testing Implementation Maintenance

(a) Preliminary System Study

Preliminary system study is the first stage of system development life cycle. This is a brief investigation of the system under consideration and gives a clear picture of what actually the physical systems? In practice, the initial system study involves the preparation of a 'System Proposal which lists the Problem Definition, Objectives of the Study, Terms of reference for Study, Expected benefits of the new system
problem identification and project initiation

(b) Feasibility Study

The feasibility study is basically the test of the proposed system in the light of its workability Meeting users requirements The cost effectiveness. These are categorized as technical, operational, economic and schedule feasibility. The main goal of feasibility study is not to solve the problem but to achieve the scope.

(c) Detailed System Study

Keeping in view the problems and new

requirements Work out the pros and cons including new areas of the system 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. List of attributes of the entities these are the data

System Analysis
Systems analysis is a process of collecting factual

data, understand The processes involved, identifying problems and recommending possibility to rectifying Suggestions for improving the system functioning Studying the business processes, gathering operational data Understand the information flow

System Design
Based on the user requirements and the detailed analysis of the existing system, the new system must be designed Preliminary or General Design: In the preliminary or general design, the features of the new system are specified. The costs of implementing these features and the benefits to be derived are estimated. Structured or Detailed Design: At this stage, the design of the system becomes more structured.

These tools and techniques are: Flowchart Data flow diagram (DFD) Data dictionary Structured English Decision table Decision tree

 The system design involves: i. Defining precisely the required system output

ii. Determining the data requirement for producing

the output iii. Determining the medium and format of files and databases iv. Devising processing methods and use of software to produce output v. Determine the methods of data capture and data input vi. Designing Input forms vii. Designing Codification Schemes viii. Detailed manual procedures

Coding
The system design needs to be implemented to

make it a workable system. This demands the coding of design into computer understandable language, i.e., programming language. This is also called the programming phase.

Testing
Before actually implementing the new system into

operation, a test run of the system is done for removing the bugs Program test: When the programs have been coded, compiled and brought to working conditions, they must be individually tested. System Test: After carrying out the program test for each of the programs of the system and errors removed, then system test is done.

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. The major steps involved in this phase are: Acquisition and Installation of Hardware and Software Conversion User Training Documentation

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 environments knowing the full capabilities of the system knowing the required changes or the additional requirements studying the performance.

LECTURE-3

Software Process Models

Software process models are general approaches

for organizing a project into activities.

Help the project manager and his or her team to

decide:
What work should be done;
In what sequence to perform the work.

The waterfall model

The classic way of looking at S.E. that accounts for

the importance of requirements, design and quality assurance.

The model suggests that software engineers should

work in a series of stages. The waterfall model also recognizes, to a limited extent, that you sometimes have to step back to earlier stages.

The waterfall model

Requirement definition

System and s/w design Implementatio n & Unit testing Integration & System testing

Operation & Maintenance

Limitations of the waterfall model

The model implies that you should attempt to

complete a given stage before moving on to the next stage

It also means that customers can not use anything until the

entire system is complete.

It implies that you can get the requirements right by

simply writing them down and reviewing them. The model implies that once the product is finished, everything else is maintenance.

SPIRAL MODEL

Analysis of Spiral Model

Strengths

Easy to judge how much to test

No distinction between development, maintenance For large-scale software only

Software Prototyping
Rapid software development to validate requirements. Prototyping is the rapid development of a system Now, the boundary between prototyping and normal system development is blurred. The principal use is to help customers and developers understand the requirements for the system

Prototyping benefits
Misunderstandings

between software users and developers are exposed. Missing services may be detected and confusing services may be identified. A working system is available early in the process.

Prototyping process
Establish prototype objectives Define prototype functionality Develop prototype Evaluate prototype

Prototyping plan

Outline definition

Executable prototype

Evaluation report

Prototyping with reuse

Application level development

Entire application systems are integrated with the prototype so that their functionality can be shared For example, if text preparation is required, a standard word processor can be used
Component level development

Individual components are integrated within a standard framework to implement the system

Agile Methods
Agile software development refers to a group of software development methodologies based on iterative development, where requirements and solutions evolve through collaboration between self-organizing crossfunctional teams. Each iteration involves a team working through a full software development cycle including planning, requirements analysis, design, coding, unit testing, and acceptance testing. Agile methods emphasize face-to-face communication over written documents when the team is all in the same location. When a team works in different locations, they maintain daily contact through videoconferencing, voice, e-mail, etc.

LECTURE - 5

What is Object-Oriented Methodology ?

Software development method based on Object-

Oriented Paradigm
Our world is a collection of collaborating entities called

objects Software has to be organized according to the structure of our world

It increases understandability. It makes evolution of software easier.

Computationally, Objects are

ObjectAttributes
(performance)
(qualities)

OperationsBehavior

AttributesLocal data of object OperationsFor changing/referencing the attributes Behavior perform operations, changes its states

Object is encapsulated. No internal state and attribute values can be seen from outside the object.

Objects and Classes

object:

Thai
Myanmar abstraction Indonesia instantiation Tan class: Country
lives-in

Laos

Shinoda

class: People

Relationships Among Classes

Class Hierarchy, Inheritance, is a Generalization/Specialization Mammal < Monkey < Human Composition, Aggregation, has a AutomobileBodyWheelsSteeringEngine Association, a general relation between

classes
Peoplelives-inCountry

Two Major Issues in Object-Oriented Methodology

Object-Oriented Analysis/Design
Constraints, Analysis Patterns,

Object-Oriented Programming
OO languages: Smalltalk, C++, Java

Typical Object-Oriented Development Process

Architecture design Choice of impl. strategy Object design

Analyzing requirement
Requirements

Object model Dynamic model

Analysis

Design

Coding
Coding in OO language

models Analysis

LECTURE - 6

Class Diagrams
Classes in the system + Relations

Relations among classes

Inheritance Aggregation Association Dependency

Class and Object

Employee name: String pos: String promote

Employee name:Smith pos:eng promote

Employee name:Sharp pos:chief eng promote

Class Employee

Objects instantiated from the class Employee

Link and Association

Link : Relation among objects instantiated from

classes
Channel for event transmission Access path for data access/navigation

Person Joe Smith

Work at

Company Simplex Co.

classes Abstraction of links between objects

Person Work at Company

Joe SmithPerson

Simplex Co.Company

Association and Multiplicity

Line name Line L1 2..* 0..*

Intersect

Point name Point P1 Point P2

Line L2
Line L3

L2 L3

P1

P2

Line L4
Line L5

L5

L1

L4

Inheritance
Attributes and operations are inherited from super classes
Equipment name manufacturer weight cost

Pump suction pressure discharge pressure flow rate

Heat exchanger surface area tube diameter .

Tank volume pressure

Diaphragm pump diaphragm material

Plunger pump

Floating roof tank diameter height

Inheritance
A method for classifying classes according to their

generality Inheritance is not an association

super class

B inherits attributes and operations from A Attr*(B)=Attr(A) Attr(B) Op*(B)=Op*(A) Op(B)

subclass

Event Trace
Sequence of events Scenario Sequence of events observe when the system performs some function

An Event Sequence in a Telephone System

Caller

event
caller-lifts-receiver
dial-tone-begins dial(5) dial(1)

Phone line

object

Callee

callee-hangs-up connection-broken caller-hangs-up connectin-broken

Sequence Diagram
Print(file)

:Computer

:PrinterServer

:Printer

:Queue

Print(file)

[printer free] Print(file)

[printer busy] Store(file)

Shows possible sequence(s) of messages among objects Inter-object behavior

Collaboration Diagram

Computer
1:Print(file)

Queue

[printer busy] 1.2: Store(file)

PrinterServer
[printer Free] 1.1: Print(file)

Printer