0% found this document useful (0 votes)
8 views53 pages

1 Chapter 1 Introduction To SAD

The document provides an overview of system analysis and design, detailing the importance of information systems in business decision-making and the various types of information systems. It outlines key concepts such as system characteristics, components, and development phases, including systems investigation, analysis, design, implementation, and maintenance. Additionally, it highlights the roles of system analysts and the necessary skills for effective system development.

Uploaded by

Ketema Deba
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
8 views53 pages

1 Chapter 1 Introduction To SAD

The document provides an overview of system analysis and design, detailing the importance of information systems in business decision-making and the various types of information systems. It outlines key concepts such as system characteristics, components, and development phases, including systems investigation, analysis, design, implementation, and maintenance. Additionally, it highlights the roles of system analysts and the necessary skills for effective system development.

Uploaded by

Ketema Deba
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 53

Chapter 1Chapter 1
Introduction system
Introduction system analysis and
design
analysis and design
page 1
Chapter 1- The system development environment
..
Chapter 2 Object Orientation the new software paradigm
Chapter 3 Understanding the Basics: Object oriented concepts
Chapter 4 Gathering user requirements
Chapter 5 Ensuring Your Requirements Are correct
Chapter 6 Determining What to Build: OO Analysis
Chapter 7 Determining What to Build: OO Design
Chapter 8 Software process , Object Oriented Testing and
Maintenance

page 2
Chapter 1
Introduction system analysis and design

• Meaning and role of an Information


• Systems definition and concepts
• Introduction to Information System
• Types of Information Systems
• Systems analysis and design – core concepts
• Approaches to Systems Analysis and Design
• Role of the System Analyst
• Systems development Life Cycle (SDLC)
• Approaches for Development
page 3
Meaning and role of an Information
• Information is very important part of any business, which
helps the managers to make decisions.
• The data flows throughout the organization and makes it
active.
• There is lot of data available in the business, at every time
a transaction takes place (Ex. a sale), some data is recorded.
It could be recorded on paper or in a computer system.
• The difference between data and information
• Data;- are raw (unprocessed) facts about people, objects,
events in an organization
• Facts about real entities.
• (Ex. all the sales orders for the year)
page 4
Ctd…

 Information;- is data that have been processed and


presented in a form suitable for human interpretation.
• Information is facts that are arranged in meaningful
manner.
• States about specific subject of the business process
• (how many of each product were ordered in each
month, may be shown on a graph)

page 5
Systems definition and concepts

System:
 A System is a set of interrelated components with
identifiable boundry working together for some purpose.
• Example: an inventory system in the materials
department keeps track of the raw materials supply.
 The system takes input from outside, processes it, and
sends the resulting output back to its environment.
• A system can also defined as collections of people using
information technology and processes that define how
people carry out their work.
 The system also includes informal interactions that take
place in an organization. Ex.pageemails, phone calls. 6
Characteristics of a System
A System has nine characteristics
 Components: A component is either an irreducible part or
an aggregate of parts , also called as a subsystem
 Interrelated Components: The function of one component is tied to
the functions of the others.
 Output from one is input for another, the dependence of a part on
one or more other parts.
 Boundary: A system has boundary, within which all of its components
are contained and which establishes the limits of a system, separating
it from other systems.
 Components within the boundary can be changed whereas systems
outside the boundary cannot be changed.
 Purpose: All components work together to achieve the overall
purpose/objective of the system.
page 7
Ctd…

• Environment: An area within which the system exist ,


everything outside the system’s boundary that
influences and / or interacts the system.
• Interfaces: The points at which the system meets its
environment and there are also interfaces between
subsystems.
• Input: System takes input from its environment.
• Output: System returns output to its environment as a
result of its functioning to achieve the purpose. Output
from individual subsystems may be inputs to other
subsystems.

page 8
Ctd…
• Constraints: There are limits to what the system can
do (capacity, speed, and capability), some of these
constraints are imposed inside the system and others
are imposed by the environment.

page 9
Some important Systems concepts

• Decomposition – is the process of breaking down a system into its


smaller components, decomposing a system also allows us to focus
on one particular part of a system, making it easier to think of how
to modify that one part independently of the entire system.
• Modularity A complex system may be divided into separate and
distinct pieces or decomposition which divides a system into
modules of a relatively uniform size. This makes it easier to
understand the system.
• Coupling means that subsystems are dependent on each other,
messages are passed between subsystems
• simpler and easier to change just one part of the system without
affecting the other parts.
• Cohesion is the extent to which a subsystem performs single
functions. Generally coupling must be reduced and cohesion
increased, so that it performs only one function.
page 10

• System thinking - Is a mindset or way of viewing


a world as a system. It is one type of the skills
that system analyst requires.
• It helps to see the big picture and pays attention
to break problems down to their components to
avoid complexity during system development.
• Minimize the effect a change in one module will
have on another.
• Abstraction is a process in which we identify
the important aspects of a problem and ignore
its unimportant details.
page 11
Introduction to Information System

 (IS) is a set of interrelated elements /components that


collect (input), manipulate (process), store, and
disseminate (output) data and information and provide a
corrective reaction (feedback mechanism) to meet an
objective.

page 12
Ctd…
• An Information System is an arrangement of people,
data, processes, interfaces, networks and technology
that interact for the purpose of supporting and
improving both day-to-day operations in a business
(data processing) as well as supporting the problem
solving and decision making needs of management
(information services).

page 13
Ctd …
• The Information System key components includes the
following:
• Hardware – Computers, servers and printers
• Software- System software and application software
• Documentation and training materials – The materials
created by Systems Analyst to help users to use the software
• Specific job roles – The roles associated with the overall
system, such as the people who run the computers and the
software operating.
• Controls- which are the parts of the software written to
prevent fraud and theft
• People- Who uses the software in order to do their job.
page 14
Types of Information Systems

The main types of IS are:


• Transaction Processing Systems
• Management Information Systems
• Decision Support Systems
• Expert Systems
• Office automation system
• Executive support systems

page 15
Transaction Processing Systems (TPS)

 automates the handling and capture of data about transactions or


business activities
 Accepted transactions are stored in the system database
• Reporting provides summaries of transactions (ex. daily, weekly)
 The analysis and design of a TPS requires focusing on the firm’s
current procedures for processing transactions. How the
organizations track, capture, process and output data?
 The goal of TPS development is to
 improve transaction processing by speeding it up, using
fewer people,
 improving efficiency and accuracy, integrating it with other
organizational information systems, or providing
information not previouslypage
available. 16
Management Information System (MIS)
 takes the raw data available through a TPS and
converts them into a meaningful aggregated form.
• It provides reports of this information to managers
• Developing MIS calls for good understanding of
what kind of information managers require and
how managers use information in their jobs.
• Thus, the System Analyst must develop a good
understanding of the business and the transaction
processing systems that provide data for an MIS

page 17
Decision support System (DSS)
 Helps the manager to take decisions by analyzing the data
 It provides an interactive environment in which decision maker
can quickly manipulate data and models of business operations
• DSS has three parts,
 The first part is composed of a database, extracted from a TPS
or MIS
 The second part consists of mathematical or graphical models
of business processes.
 The third part is made up of a user interface, which provides a
way for the decision maker to communicate with the DSS.
• System Analyst is to concentrate on the three main
components database, model base and user dialogue.
page 18
Expert Systems (ES)

 system that gives a computer the ability to make suggestions


and function like an expert in a particular-field.
it replicates the decision making process by applying rules to
information in the way that an expert would
• An ES is developed for a particular area of knowledge or
domain, Ex Medical diagnosis, Weather forecasting, etc.
• The ES asks questions, and the end user supplies the answers,
rules applied on the answers and the ES provides a
recommendation.
• The focus on developing and ES is acquiring the knowledge of
the expert in the particular problem domain. Knowledge
engineers perform knowledge acquisition.
page 19
Office Automation Systems
• Office Automation Systems are information systems
that try to improve the productivity of employees
who need to process data and information.
• Keeps records of office information. Computer
systems such as :
• Word Processing,
• Electronic mail system, and
• Scheduling system
• Are designed to increase the productivity of data
workers in the office

page 20
Executive Support Systems (ESS)
• Is an information system at the strategic level of
an organization that addresses unstructured
decision making through advanced graphics and
communications.
• Help senior managers address strategic issues and
long term trends, both in the firm and in the
external environment
• Designed to help senior management make
strategic decisions.
• Gathers analyses and summarizes the key internal
and external information used in the business.
page 21
.

page 22
The systems development phases
systems investigation:
- The systems development phase during which problems and opportunities
are identified and considered in light of the goals of the business.
Systems analysis
• The systems development phase that attempts to answer the question
“What must the information system do to solve the problem?”
systems design
• The systems development phase that defines how the information system
will do what it must do to obtain the problem solution
systems implementation
• The systems development phase involving the creation or acquisition of
various system components detailed in the systems design, assembling
them, and placing the new or modified system into operation.

page 23

• systems maintenance and review


• The systems development phase that ensures the system
operates as intended and modifies the system so that it
continues to meet changing business needs.
• prototyping
• An iterative approach to the systems development process in
which, at each iteration, requirements and alternative solutions
to a problem are identified and analyzed, new solutions are
designed, and a portion of the system is implemented
rapid application development (RAD)
• A systems development approach that employs tools,
techniques, and methodologies designed to speed application
development.

page 24
IS Components:
Data - Input that the system takes to produce information
Hardware - Computer itself and its peripheral equipment:
input, output, storage devices; includes data communication
equipment
Software - Sets of instructions that tell the computer how
to input, process, output and store data
Communication networks - Hardware and software
specializing in transmission and reception of electronic data
People - IS professionals and users who design, construct,
operate and maintain IS
Procedures - Rules to process data, e.g. priorities in running
different applications, security measures, routines for
malfunctioning IS,
page
et
25
Participants in Information System Development

• System owners- An individual, organization, or enterprise


that is legally, administratively responsible,and accountable
for the system development, operation, products, outcomes
and disposal. They own the system, set priorities for the
system, and determine policies for its use.
• System users- are the people who use the system to perform
or support the work to be completed. System users physically
operate a system or provide inputs data, preprocessed
materials to the system.
• System analysts- facilitate the development of information
systems and computer applications by bridging the
communications gap that exists between non-technical
system owners, users, technical system designers and
builders.
page 26

• System designers- are the technical specialists


who design the system to meet users’
requirements. In many cases, system designers
may also be system builders.
• System builders are the technical specialists who
code, test, install and deliver the system into
operation. Usually system builders are
programmers.
• IT vendors and consultants who sell hardware,
software and services to businesses for
incorporation into their information systems.
page 27

• Information system architecture-


It provides a framework to understand information
systems and combines the above stakeholders
and building blocks to arrive at a unified view of
the information system development process.

page 28
System analyst skills
• Analytical skills
- enables to understand the organization and its
functions, to identify opportunities and problems and
to analyze and solve problems
• Systems thinking-
• Organizational knowledge- how organizations work.
• Problem Identification-a problem is the difference between an
existing situation and a desired situation.
• Problem analyzing and solving- is finding out more about the
problem, formulating alterative solutions, choosing the best
alternative, devising a plan for its implementation
page 29
Technical skills- …

helps to understand the potential and the limitations of information


technology. Programming languages skills, operating systems,
database systems, data communication systems, system
development tools, web development languages, CASE tools skills.
Management skills-
• Resource management- delegating work, use resources effectively
and efficiently.
• Project management- prevent projects from coming in late or going
over budget.
• Risk Management- identifying risk in an IS development process
and minimizing it.
• Change management- helps people make a smooth transition from
one information system to another.

page 30
Interpersonal skills

- enables to work with end users as well as other analysts


and programmers.
Communication skills- interviewing, listening and
questionnaires, written and oral presentations;
communicate with users, management or information
systems professionals.
• Ability of Working alone and with a team,
• Ability of facilitating groups-guiding groups to work
together- including meetings, interviewing, and
listening to end users required.
• a system analyst plays a major role as liaison among
users, programmers and other analyst
page 31
Basic Concepts of System Analysis and Design
Systems Analysis
 is the study of a business problem domain for the purpose of
recommending improvements and
specifying the business requirements for the solution.
Systems Design
 is the specification or construction of a technical, computer based
solution for the business requirements identified during systems
analysis.
Systems Analysis and Design (SAD)
 Information systems analysis and design is a method used by
companies to create and maintain information systems that
perform basic business functions.

page 32
Ctd…
Main goal
 is to improve organizational systems through developing or
acquiring application software that can
 help employees accomplish key business tasks more easily and
efficiently.
 An application software is designed to support a specific
organizational function or process, such as inventory
management, payroll.
• The goal of application software is to turn data into information.
 An Information System is developed by following Software
Engineering Process, which consists of proven methodologies,
techniques and tool. These three process work together to form
an organization approach to SAD

page 33
ctd …

fig. software engineering process

Methodol
ogy

Technique
s Tools

page 34
Ctd…
 Methodologies: are sequence of step by step
approaches that helps to develop the final product.
 incorporate techniques like, direct observations
and interviews with users.
 Techniques : provide support for a wide range of
tasks
 including conducting interviews with users,
planning and managing the activities of a project
and designing the reports.
• Tools : are computer programs, such as computer
aided software engineering (CASE) tools, that
 make it easy to use specific
page techniques. 35
Approaches to Systems Analysis and Design

 Every Information System consists of three key components


that anyone who analyzes and designs must understand,
 they are data, data flows and processing logic.

• Data: are raw facts that describe people, objects and


events in an organization.
 Ex. customers account no, account type, balance amount

• Dataflow: are groups of data that move and flow through a


system
 Ex. customers account number is captured when he uses a credit
card for purchase
• Processing logic: describes the steps that transform the
data and the events that trigger these steps
page 36
 Ex. processing logic in a credit card bill preparation
Process Oriented approach
 Traditionally, Systems Analysts designed an Information System
based on what the system was meant to do, such as billing or
inventory control.
The focus was on outputs and processing logic
The data used as inputs were seen as important also, but
secondary to the application
Each system would contain its own files and data storage areas
The data in each system would match the specifications for
that system only
Each systems was considered ( looked at) separately
 The problems with this approach are,
I. existence of several files of data each locked with different
applications and programs.
II. many of the files in different applications contains same data, updating
the data becomes tedious process, it also difficult to combine data files
page 37
created for specific applications.
Data Oriented approach
 Tends to focus on how the data should be
represented independently of where and how
data are used in the system
• A data model is produced, which describes the data
and relationships between the data. Business rules
define how the organization deals with the data
 Databases are designed around the subjects such
as customers, suppliers, parts. This lets use the
same databases for many different applications
 means that the application is independent of data
and data definitions it is called as application
independence page 38
Systems Integration approach
 Today, systems development focuses on systems
integration.
Systems integration allows hardware and
software from different vendors to work together
in an application.
Mostly used today’s approach

page 39
Ctd…

page 40
Role of the System Analyst
• A system analyst bridges the communication gap
between those who need the information system and
those who understand the technology
• A system analyst facilitates the study of the problems
and needs of a business to determine how the business
systems and information technology can best solve the
problem and accomplish improvements for the
business.
• Involving End users – it is important to include the
people (users or end users) who are involved in the
system. Since,
• They use the system, or will use the new system
• They know about the data page
and / or processes in the system 41
Involving managers
 managers in the business also need to be
considered, since
 They define the business goals for projects
 They need to know what resources are required for a
project
 They need to know how long the project will take
 They make the decisions

page 42
Systems Development Life Cycle – SDLC
 The series of steps used to mark the phases of development for an
information system. It is a common methodology for systems
development

page 43
Ctd…
 The common four SDLC steps are 1) Planning and
selection 2)Analysis 3) Design and 4) Implementation
and operation.
• The specific steps and their sequence are meant to be
adapted as required for a project, if necessary the project
can return to an earlier phase.
• Some activities in one phase in parallel with some
activities of another phase. Sometimes the life cycle is
iterative.
• Each phase has specific outcomes and deliverables that
feed important information to other phase.
• These deliverables are reviewed by parties outside the
project team, including managers
page and executives. 44
System planning and selection
 The first phase in the SDLC has two primary activities
• Identifying the need for a new or enhanced system
• Information needs of the organization are examined
and projects to meet these needs are identified from
– Requests to deal with problems in current procedures
– The desire to perform additional tasks
– The realization that information technology could be
used to improve the organization
• The Systems analyst prioritizes and translates the
needs into a written plan including a schedule for
developing new systems.
page 45
Ctd…
• The organization may decide whether or not the
resources devoted for the project and a careful
feasibility study is conducted to determine the
economic and organizational impact of the system
• The second task is investigating the system and
determining the proposed system’s scope. Then a
specific plan for the proposed project for the team
to follow is produced.
• This is Baseline Project Plan customizes the
standardized SDLC and specifies the time and
resources needed for its execution
page 46
Systems analysis
• It has three sub phases,
I. involves the systems analyst to determine the
requirements of the system, ie, what the users
want from a proposed system
II. the requirements gathered are structured
according to their interrelationships, eliminating
the redundancies
III. system analyst has to generate alternative initial
designs to match the requirements, best suited
design is selected for the development after the
comparison of all alternative designs
page 47
Systems Design
• The system analyst converts the description of
recommended solution into logical and physical designs
• Logical design involves in designing the user interface,
databases and compute processes, irrespective of the
programming languages ( Algorithms, input and output
forms, reports, table normalization)
• During the Physical design, the analyst team decides the
programming language, database systems to be used,
hardware platform, operating systems and network
environment.
• The final outcome of the design phase is the physical system
specifications, presented in the form such as a diagram or
written report ready to be turned over to programmers and
other system builders for construction.
page 48
Systems Implementation and operation
 In this phase the information system is coded,
tested and installed in the organization, and
 in which the information system is systematically
repaired and improved
Planning for both testing and installation is to be done
as early as the project planning and selection phase,
because they both require extensive analysis in order
to develop exactly the right approach.
• This phase also includes the initial training to the
users and documentation of the system
documented throughout the life cycle.
page 49
Ctd…
 During operation part, the problems faced by the users
should be solved, and changes and enhancements (new
versions) is to be made as per the users’ desire to
reflect changing business conditions.
• There inevitably comes a time, when an information
system is no longer performing as desired, when the
costs of keeping a system running become prohibitive,
or when an organization’s needs have changed
substantially.
• Such problems indicate that it is time to begin designing
the system’s replacement, thereby completing the loop
and starting the life cycle over
page
again. 50
Approaches for Development
 There are four approaches that streamline and improve the systems analysis
and design process
 Prototyping,
 rapid application development(RAD),
 Joint application design(JAD) and
 Participatory design (PD).
Prototyping

• Is developing small scaled information system to the user and taking feed
back for acceptance.
• Designing and building a scaled-down version of the desired information
system with the help of CASE tools
• Prototyping is a key tool that supports rapid application development.
RAD
 involves gaining user acceptance of the interface and developing key system
capabilities as quickly as possible.
 Systems development methodology created to radically decrease the
time needed to design and implement
page information systems 51
Joint Application Design

• A structured process in which users, managers


and analysts work together for several days in a
series of intensive meetings to specify or review
system requirements.
• Eg. JAD room JAD room.png
• Participatory design

 involves users in the development process,


they have an equal voice in determining system
requirements and in approving system design.
page 52
End of chapter-1
Questions ?

page 53

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy