0% found this document useful (0 votes)
21 views61 pages

SAD Chapter1 REVISED

The document discusses system analysis and design (SAD), including its importance, required textbook, definitions of analysis and design, learning objectives, and introductions to systems, stakeholders, and subsystems.

Uploaded by

Suzan Shrestha
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)
21 views61 pages

SAD Chapter1 REVISED

The document discusses system analysis and design (SAD), including its importance, required textbook, definitions of analysis and design, learning objectives, and introductions to systems, stakeholders, and subsystems.

Uploaded by

Suzan Shrestha
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/ 61

System Analysis and Design

(SAD)
Course Objective
• To provide you with new ways of looking at information in the
world in order to solve business problems
• To introduce you to concepts and methods of SAD
• To describe the systems development life cycle (SDLC)
• To teach you effective methods for gathering essential
information during system analysis
• To teach you effective methods for designing systems to solve
problems effectively using technology
Why is it important?
• Success of information systems depends on
good SAD
• Widely used in industry
• Part of career growth in IT - lots of interesting
and well-paying jobs!
• Increasing demand for systems analysis skills
Required Text Book

Modern System Analysis & Design, 4th


Jefferey A. Hoffer, Joey F. George and Joseph. S.
Valacich, Prentice-Hall, 2005
System Analysis and Design (SAD)
• Analysis: defining the problem
– From requirements to specification
• Design: solving the problem
– From specification to implementation
• Systems Analysis: understanding and specifying in detail
what an information system i.e software should do??
• System Design: specifying in detail how the parts of an
information system i.e software should be implemented??
• Definition of SAD:
– The complex organizational process whereby computer-based
information systems are developed and maintained.
Learning Objectives

 Define information systems analysis and design.


 Describe the information Systems Development Life Cycle
(SDLC).
 Explain Rapid Application Development (RAD), prototyping,
Computer Aided Software Engineering (CASE), and Service-
Oriented Architecture (SOA).
 Describe agile methodologies and eXtreme programming.

6
Introduction
• Information Systems Analysis and Design
– Complex organizational process
– Used to develop and maintain computer-based
information systems
– Used by a team of business and systems
professionals

7
Introduction (Cont.)

FIGURE 1-1 An organizational approach to systems analysis and


design is driven by methodologies, techniques, and tools

8
A Modern Approach to Systems Analysis
and Design
• 1950s: focus on efficient automation of
existing processes
• 1960s: advent of 3GL, faster and more reliable
computers
• 1970s: system development becomes more
like an engineering discipline

9
A Modern Approach to Systems Analysis
and Design (Cont.)
• 1980s: major breakthrough with 4GL, CASE
tools, object oriented methods
• 1990s: focus on system integration, GUI
applications, client/server platforms, Internet
• The new century: Web application
development, wireless PDAs, component-
based applications

10
Developing Information Systems
• System Development Methodology is a
standard process followed in an organization
to conduct all the steps necessary to analyze,
design, implement, and maintain information
systems.

11
Systems Analysis

• It is a process of collecting and interpreting facts,


identifying the problems, and decomposition of a system
into its components.
• System analysis is conducted for the purpose of studying
a system or its parts in order to identify its objectives. It is
a problem solving technique that improves the system
and ensures that all the components of the system work
efficiently to accomplish their purpose.
• Analysis specifies what the system should do??
 Investigation of the problem and requirement rather than
solution.
Systems Design

• It is a process of planning a new business


system or replacing an existing system by
defining its components or modules to satisfy
the specific requirements. Before planning,
you need to understand the old system
thoroughly and determine how computers can
best be used in order to operate efficiently.
• System Design focuses on how to accomplish
the objective of the system.
• System Analysis:
– Investigation of the problem and
requirement rather than solution.

• System Design:
– A conceptual solution that fulfills the
requirements, rather than implementation.
SAD
Introduction:

• Software analysis and design includes all activities, which help the
transformation of requirement specification into implementation.
Requirement specifications specify all functional and non-functional
expectations from the software. These requirement specifications come in
the shape of human readable and understandable documents, to which a
computer has nothing to do.

• Software analysis and design is the intermediate stage, which helps


human-readable requirements to be transformed into actual code.

• Systems development is systematic process which includes phases such as


planning, analysis, design, deployment, and maintenance.
What is a System?
• A collection of parts that work together to achieve a
goal/task
– Examples
• Solar system
• Digestive systems
• Public transport system
• Central heating system
• Computer system
• Information system

• A set of objects and relationships among the objects


viewed as a whole and designed to achieve a
purpose
System Components
Outputs and Inputs
The main aim of a system is to produce an output which is useful for its
user.Inputs are the information that enters into the system for
processing.Output is the outcome of processing.
Processor(s)The processor is the element of a system that involves the
actual transformation of input into output.
It is the operational component of a system. Processors may modify the
input either totally or partially, depending on the output specification.
As the output specifications change, so does the processing. In some
cases, input is also modified to enable the processor for handling the
transformation.
Control
The control element guides the system.
It is the decision–making subsystem that controls the pattern of activities governing
input, processing, and output.
The behavior of a computer System is controlled by the Operating System and
software. In order to keep system in balance, what and how much input is needed is
determined by Output Specifications.
Feedback
Feedback provides the control in a dynamic system.
Positive feedback is routine in nature that encourages the performance of the system.
Negative feedback is informational in nature that provides the controller with
information for action.
Environment
The environment is the “supersystem” within which an organization operates.It is the source of external elements that strike on the system.It determines how a
system must function. For example, vendors and competitors of organization’s environment, may provide constraints that affect the actual performance of the
business.
Boundaries and Interface
A system should be defined by its boundaries. Boundaries are the limits that identify its components, processes, and interrelationship when it interfaces with
another system.
Each system has boundaries that determine its sphere of influence and control.The knowledge of the boundaries of a given system is crucial in determining the
nature of its interface with other systems for successful design.
What is subsystem?
• A subsystem is simply a system within a
system.
– Automobile is a system composed of subsystems:
• Engine system
• Body system
• Frame system
– Each of these subsystem is composed of sub-sub
--systems.
• Engine system: carburetor system, generator system,
fuel system, and so son
Stakeholders: Players in the Systems Game
• A stakeholder is any person who has an interest in
an existing or proposed information system.
Stakeholders can be technical or nontechnical
workers. They may also include both internal and
external workers.
• Figure 1-1: next slide
– System owners
– System users
– System designers
– System builders
– Systems analysts (project managers)
System Owners
System owners – an information system’s sponsor and executive
advocate, usually responsible for funding the project of
developing, operating, and maintaining the information system.
– They usually come from the ranks of management.
- medium (large) IS: middle (executive) managers
- smaller IS: middle or supervisory
Primary Concerns
- how much will the systems cost?
- how much value or what benefits will the system return to the
business?
System Users
System users
– a “customer” who will use or is affected by an IS on a regular basis
• capturing, validating, entering, responding to, storing, and exchanging data
and information
– Make up the vast majority of the information workers in any IS
– Primary concern: get the job done using an IS!
– Internal users
• service workers, technical and professional staff, supervisors, middle
managers, and executive managers
– External users
• Internet EC consumers, suppliers, partners…
System Designers and System Builders
System designer – a technical specialist who translates system
users’ business requirements and constraints into technical
solution.
– DBA, Network architects, web designer, security experts…

System builders – a technical specialist who constructs


information systems and components based on the design
specifications generated by the system designers.
– Programmers (applications, systems, and DB), network administrators,
web masters..
A Simple System Development Process
System development process – a set of activities, methods, best
practices, deliverables, and automated tools that stakeholders
use to develop and maintain information systems and
software.
A general problem-solving approach
1. Identify the problem.
2. Analyze and understand the problem.
3. Identify solution requirements or expectations.
4. Identify alternative solutions and choose the “best” course of action.
5. Design the chosen solution.
6. Implement the chosen solution.
7. Evaluate the results. If the problem is not solved, return to step 1 or 2 as
appropriate.
Computer-based Information Systems (CBIS) vs Manual
Systems

• CBIS
– Information system that rely on computer
hardware and software for processing and
disseminating information
• Manual systems
– Use paper + pencil technology

IS vs. IT
An information system (IS) is an arrangement of
people, data, processes, and information technology
that interact to collect, process, store, and provide as
output the information needed to support an
organization.

Information technology is a contemporary term that


describes the combination of computer technology
(hardware and software) with telecommunications
technology (data, image, and voice networks).
What is an Information Systems?
• Interrelated components working together to
– Collect
– Process
– Store
– Disseminate information
To support decision making, coordination, control,
analysis and visualization in an organization
i) Transaction Processing System (TPS):
-It is a category of OSS that generally record and process data
resulting from business transaction.
-
It is generally process sales, purchase, inventory and other
organizational database. These database then provide the data
resources that can be processed and used by DSS and EIS.
Ex: Sales and Inventory Processing
ii) Process Control System (PCS):
It is a category of OSS in which decision about a physical
production process are automatically made by computer through
routine decisions that control operational process.
Ex: A petroleum refining center uses electronic sensors which are linked
to the computers to continuously monitor chemical processes and make
instant adjustments that control the refined process.
iii) Enterprise Collaboration System (ECS):

-It is the information system that uses a variety of information


technology to help the people to work together.
-ECS helps to collaborate and communicate ideas, share resources
and co-ordinate work effort of an organization.
-The aim of an ECS is to use the information technology to enhance
productivity and creativity of organization and work group in an
organization.
Ex: E-mail, chat, video conferencing etc.
2. Management Support System:
-This is generally deals with providing information and support for
effective decision making.
-It refers to computer technology and system theory to data
processing in an organization.
-It helps in designing system frameworks for organizing information
system application.
-It helps in management decision making and processing of data
generated by business operation.
i) Management Information System (MIS):
-MIS is a form of MSS that provides managerial enduser with
information product that support their day to day decisions.
-It provides a variety of information in the form of report and
display to management that contain information specified in
advance by manager.
-Information is generally provided on demand or periodically to the managers.
Ex: Sales manager may use their network computer, net web browser to
get instant display of the sales, result of their product and access their
daily sales report.
ii) Decision Support System (DSS):
-Decision support systems are computer based information systems
that provide interactive information support to managers and
business professionals during the decision making process.
-It provides managerial enduser with information in an interactive
manner i.e, analytical modeling, data retrieval information
presentation capability.
Ex: Product pricing, Risk Analysis
iii) Executive Information System (EIS):

-An Information System that provides Strategic information tailored


to the needs of executives and other decision makers (top
management).
-It provides top management with immediate and easy access to
select information about key factors that are critical to
organizational strategic objectives.
Ex: The top level executives may use the touch screen to instantly view
text and graphics that display the key areas of the organization.
The Systems Analyst as a Facilitator
 The Systems Analyst - A Key Resource
 The systems analyst performs systems 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 in a systems analysis. (Note:
Increasingly, the design takes the form of a
working prototype.).
The Systems Analyst As A Modern Business Problem Solver

 What is a Systems Analyst?


 A formal definition:
 A systems analyst facilitates the study of the problems and

needs of a business to determine how the business system and


information technology can best solve the problem and
accomplish improvements for the business. The product of this
activity may be improved business processes, improved
information systems, or new or improved computer
applications frequently all three.

Prepared by Kevin C. Dittman for


Systems Analysis & Design Methods 4ed
by J. L. Whitten & L. D. Bentley
Skills Required by Systems Analysts
– Working knowledge of information technology
– Computer programming experience and expertise
– General business knowledge
– Problem-solving skills
– Interpersonal communication skills
– Interpersonal relations skills
– Flexibility and adaptability
– Character and ethics
– Systems analysis and design skills
ROLE OF SYSTEMS ANALYST
 Defining Requirements
- Involves Interviewing Users
 Prioritizing Requirements
- Obtain Users Consensus
 Fact Gathering
- Data, Facts, Opinions of Managers
- Lower level Users should be consulted
ROLE OF SYSTEMS ANALYST

 Analysis and evaluation


- Arrive at appropriate system
 Solving problems
- Hazy requirements converted into specific
requirements
- Suggest many alternative solutions
- Quantify cost and benefits

2.3.2 System Analysis And Design © V. Rajaraman


ROLE OF SYSTEMS ANALYST

 Drawing up specifications
- FUNCTIONAL SPECIFICATIONS

- Understood by users and programmers


- Accepted by users
- Precise and detailed
- Account for possible changes

2.3.3 System Analysis And Design © V. Rajaraman


ROLE OF SYSTEMS ANALYST

SYSTEM DESIGN
 Logical design of system
- Objects identification
- Normalizing database
- Test plan
 Design must be modular to accommodate change

2.3.4 System Analysis And Design © V. Rajaraman 18 of 23


ROLE OF SYSTEMS ANALYST

 Evaluating Systems
- Evaluation after use for sometime
- Plan periodicity for evaluation
- Modify as needed
ATTRIBUTES OF A SYSTEMS ANALYST

 KNOWLEDGE OF ORGANISATION

- Knowing practices
- Know Management functions.
 KNOWLEDGE OF COMPUTERS AND
SOFTWARE

2.3.6 System Analysis And Design © V. Rajaraman


ATTRIBUTES OF A SYSTEMS ANALYST

 GOOD INTERPERSONNAL RELATIONS

- Need to work as team member


- Lead smaller teams
- Interface with programmers & Users
- Motivator.

 ABILITY TO COMMUNICATE
- Oral Presentation
- Report Writing
- Answer queries

2.3.7 System Analysis And Design © V. Rajaraman 21 of 23


ATTRIBUTES OF A SYSTEMS ANALYST

 ANALYTICAL MIND

- Problem solving attitude


- Ability to assess trade offs
- Sound commonsense
- Curiosity to learn about new organizations

 BREADTH OF KNOWLEDGE

- Broad Liberal Knowledge


- Variety of jobs to be tackled in diverse organizations

2.3.8 System Analysis And Design © V. Rajaraman 22 of 23


System Development
Life Cycle (SDLC)
SDLC
• Most organizations use a standard set of steps,
called a systems development methodology
to develop and support their information
systems. It is a standard process followed in an
organization to conduct all the steps necessary
to analyze, design, implement, and maintain
information systems
SDLC Phases
Preliminary
Investigation

System
System Operation Analysis
& Maintenance

System System
Implementation
n Design

System
Development
Phase 1:
Preliminary Investigation
• Determine if a new system is needed
• Three primary tasks:
– Define the problem
• By observation and interview, determine what
information is needed by whom, when, where and why
– Suggest alternative solutions
– Prepare a short report
Feasibility Analysis
Feasibility – the measure of how beneficial or practical
an information system will be to an organization.

Feasibility analysis – the process by which feasibility is


measured.

11-53
Six Tests For Feasibility
Operational feasibility – a measure of how well a solution
meets the system requirements.
Cultural (or political) feasibility - a measure of how well a
solution will be accepted in an organizational climate.
Technical feasibility – a measure of the practicality of a
technical solution and the availability of technical resources
and expertise.
Schedule feasibility – a measure of how reasonable the
project timetable is.
Economic feasibility - a measure of the cost-effectiveness of a
project or solution.
Legal feasibility - a measure of how well a solution can be
implemented within existing legal/contractual obligations.

11-54
Phase 2:
System Analysis

• In depth study of the existing system to determine


what the new system should do.
– Expand on data gathered in Phase 1
• In addition to observation and interviews,
examine:
– Formal lines of authority (org chart)
– Standard operating procedures
– How information flows
– Reasons for any inefficiencies
System analysis:
• Systems analysis is a process of collecting factual data,
understand the processes involved, identifying problems
and recommending feasible suggestions for improving
the system functioning.
• The major objectives of systems analysis are to find
answers for each business process:
 What is being done?
 How is it being done?
 Who is doing it?
 When is he doing it? Why is it being done?
 How can it be improved?
Phase 2: System Analysis
Tools Used
• Checklists - list of questions
• Top-down analysis - start with top level
components, break down into smaller parts
through each successive level
• Grid charts - to show relationship between inputs
and outputs
• System flowcharts - charts flow of input data,
processing, and output which show system
elements and interactions
Phase 2: System Analysis
Documentation Produced

• Complete description of current system and its


problems
• Requirements for for new system including:
– Subject
– Scope
– Objectives
– Benefits
• Possible development schedule
Phase 3: System Design
Documentation Produced

• System Design Report


– Describe Alternatives including:
• Inputs/Outputs
• Processing
• Storage and Backup
– Recommend Top Alternative based upon:
• System Fit into the Organization
• Flexibility for the future
• Costs vs. benefits
Phase 5: System Implementation
• The implementation phase of the SDLC involves the
actual construction and installation of the system.
• This phase also includes the maintenance of the system
and any future updates or expansion of the system.
• The major steps involved in this phase are:
 Installation of Hardware and Software
 Conversion
 User Training
 Documentation
Phase 6: Operations & Maintenance

• Types of changes:
– Physical repair of the system
– Correction of new bugs found (corrective)
– System adjustments to environmental changes
– Adjustments for users’ changing needs (adaptive)
– Changes to user better techniques when they
become available (perfective)
Phase 6: Operations & Maintenance

• Evaluation Methods
– Systems audit - performance compared to
original specifications
– Periodic evaluation - “checkups” from time to
time, modifications if necessary
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.
• The review of the system is done for:
 Knowing the full capabilities of the system.
 Knowing the required changes or the
additional requirements .
 Studying the performance.
The Heart of the Systems Development Process
FIGURE 1-7 FIGURE 1-8
The analysis–design–code–test loop The heart of systems development

Current practice combines analysis, design, and implementation


into a single iterative and parallel process of activities.

You might also like