Modern Systems Analysis and

Design
9th Edition

Chapter 1
The Systems Development
Environment

Note: Slides were edited using publisher’s

current and previous editions in addition
to illustrations from external sources
Learning Objectives
1. Define information systems analysis and design
2. Describe the information systems development life cycle
(SDLC)
3. Describe alternative systems development methodologies:
– Waterfall, RAD, agile methodologies, eXtreme
Programming, and Scrum, Rational Unified Process
(RUP)

Copyright © 2020, 2017, 2014 Pearson Education, Inc. All Rights Reserved
Introduction
• Information Systems Analysis and Design
– Defined as the complex, challenging, and simulating
organizational process that a team of business and
systems professionals uses to develop and maintain
information systems. A Team Manage this system analysis
and design.
• Application Software –‫لتطبيقات‬..‫مج ا‬.‫را‬..‫ب‬
– Software designed to support organizational function or
process. Help us To create a design

• Systems Analyst
– Organizational role most responsible for analysis and
design of information systems – other people with IT
development write code , I want people to create.
Copyright © 2020, 2017, 2014 Pearson Education, Inc. All Rights Reserved
Systems Analyst Role in Systems Development

• Study problems and needs of an organization

• Help system users and managers define their
requirements for new or enhanced information
systems

Copyright © 2020, 2017, 2014 Pearson Education, Inc. All Rights Reserved
Information Systems Components

• System: Turns data into information and

includes:
– Hardware and system software
– Documentation and training materials
– Job roles associated with the system
– Controls to prevent theft or fraud
– The people who use the software to perform their jobs

Copyright © 2020, 2017, 2014 Pearson Education, Inc. All Rights Reserved
Information Systems Components

Copyright © 2020, 2017, 2014 Pearson Education, Inc. All Rights Reserved
Key Types of Information Systems
Transaction Processing Systems (TPS)
– Automate handling of data about business activities
(transactions)
Management Information Systems (MIS)
Converts raw data from transaction processing system into
meaningful form.
Development Decision Support Systems (DSS)
Designed to help decision makers
Provides interactive environment for decision making

Copyright © 2020, 2017, 2014 Pearson Education, Inc. All Rights Reserved
 Figure 1-1: An Organizational Approach to Systems
Analysis and Design Is Driven by Methodologies,
Techniques, and Tools
• Methodologies:  sequence of step-by-step
approaches that help develop the information
system

• Tools: Computer programs that aid in

applying techniques

• Techniques: Processes that the analyst

follows to ensure thorough, complete and
comprehensive analysis and design 

(Sources: Top: Monkey Business Images/Shutterstock; Left: benchart/Shutterstock; Right: Lifestyle

Graphic/Shutterstock)

Copyright © 2020, 2017, 2014 Pearson Education, Inc. All Rights Reserved
Developing Information Systems and the
Systems Development Life Cycle

• Systems development methodology

– A standard process followed in an organization to conduct
all the steps necessary to analyze, design, implement, and
maintain information systems
• The systems development life cycle (SDLC)
– The traditional methodology used to develop, maintain,
and replace information systems
▪ Features several phases that mark the progress of the
systems analysis and design efforts

Copyright © 2020, 2017, 2014 Pearson Education, Inc. All Rights Reserved
Systems Development Life Cycle
• A circular process, with the end of the useful life
leading to the start of another
• At any given phase the project can return to a
previous phase when needed
• Can be an iterative process

Copyright © 2020, 2017, 2014 Pearson Education, Inc. All Rights Reserved
Figure 1-2: Systems Development
Life Cycle

Copyright © 2020, 2017, 2014 Pearson Education, Inc. All Rights Reserved
 Figure 1-3: Evolutionary Model

• A spiral process in which one is constantly cycling through phases at different

levels
• Sometimes the life cycle is iterative; that is, phases are repeated as required until
an acceptable system is found.

Copyright © 2020, 2017, 2014 Pearson Education, Inc. All Rights Reserved
Phases of the SDLC (1 of 3)
• Planning
– Need for a new or enhanced system is identified
– Needs are identified, analyzed, prioritized, and arranged
– Determine the scope of the proposed system
– Baseline project plan is developed

• Analysis
– System requirements are studied from user input and structured
– Requires careful study of current systems, manual and
computerized, that might be replaced or be enhanced
– Output is description of the alternate solution recommend by the
analysis team

Copyright © 2020, 2017, 2014 Pearson Education, Inc. All Rights Reserved
Phases of the SDLC (2 of 3)
• Design
– Analyst converts the alternate solution into logical and physical
specifications
– Logical Design
▪ The design process part that is independent of any specific
hardware or software platform
– Physical Design
▪ The logical specifications of the system from logical design are
transformed into technology-specific details from which all
programing/system construction can be accomplished
– Choices of language, database, and platform are many times
already decided by the organization or client

Copyright © 2020, 2017, 2014 Pearson Education, Inc. All Rights Reserved
Phases of the SDLC (3 of 3)
• Implementation
– Occurs when the information system is coded, tested, installed,
and supported in the organization
– New systems become part of the daily activities of the
organization

• Maintenance
– The phase in which an information system is systematically
repaired and improved
– Organization’s needs may change over time requiring changes
to the system based on user’s needs

Copyright © 2020, 2017, 2014 Pearson Education, Inc. All Rights Reserved
Table 1-1: Products of SDLC Phases
1.2 Describe the information systems development life cycle (SDLC)
Phase Products, Outputs, or Deliverables
Planning • Priorities for system and projects; an architecture for data, networks, and
selection hardware, and information systems management are the result of
associated systems
• Detailed steps, or work plan, for project
• Specification of system scope and planning and high-level system requirements
or features
• Assignment of team members and other resources
• System justification or business case
Analysis • Description of current system and where problems or opportunities exist, with a
general recommendation on how to fix, enhance, or replace current system
• Explanation of alternative systems and justification for chosen alternative
Design • Functional, detailed specifications of system elements (data, processes, inputs,
and outputs)
• Technical, detailed specifications of all system elements (programs, files,
network, system software, etc.)
• Acquisition plan for new technology
Implementation • Code, documentation, training procedures, and support capabilities
Maintenance • New versions or releases of software with associated updates to
documentation, training, and support

Table 1-1 Products of SDLC Phases

Copyright © 2020, 2017, 2014 Pearson Education, Inc. All Rights Reserved
 Slide
17

Categories of Methodologies
1. Structured Design
– Waterfall Development

2. Rapid Application Development (RAD)

– Prototyping

3. Agile Development
– eXtreme Programming
– Scrum

4. Object-Oriented Analysis and Design

– RUB
Systems Development Methodologies
• Waterfall (SDLC)
• Rapid Application Development (RAD)
–Prototyping
• Agile Methodologies
–eXtreme Programming
–Scrum
• Object-Oriented Analysis and Design
–RUB

Copyright © 2020, 2017, 2014 Pearson Education, Inc. All Rights Reserved
1.Traditional Waterfall SDLC

Figure 1-8:

Copyright © 2020, 2017, 2014 Pearson Education, Inc. All Rights Reserved
The SDLC Traditional Waterfall
Problems
• Once one phase ends another begins, going
downhill until complete
• Makes it difficult to go back
• Results in great expense to make changes
• Limited user involvement
• Focused on deadlines

Copyright © 2020, 2017, 2014 Pearson Education, Inc. All Rights Reserved
2. Rapid Application Development
(RAD)
• Process of creating workable systems in a very short period of
time.
• Analyst needs to use special techniques and tools to speed up
analysis, design, and implementation:
– CASE tools
– JAD sessions (joint application design)
– Fourth generation/visualization programming languages:
simplify and speedup programming
– Code generators: automatically produce program from
design

Copyright © 2020, 2017, 2014 Pearson Education, Inc. All Rights Reserved
CASE Tools

A class diagram from IBM’s Rational Rose

Copyright © 2020, 2017, 2014 Pearson Education, Inc. All Rights Reserved
2.1 Joint Application Design (JAD)

• Structured process involving users, analysts, and

managers
• Several-day intensive workgroup sessions
• Purpose: to specify or review system
requirements

Copyright © 2020, 2017, 2014 Pearson Education, Inc. All Rights Reserved
 • Brings end users and
information systems
specialists together in
interactive session to
discuss system’s
design

Copyright © 2020, 2017, 2014 Pearson Education, Inc. All Rights Reserved
2.2 Prototyping
• Iterative development process
• Requirements quickly converted to a working
system
• System is continually revised.
• Close collaboration between users and analysts.
• Perform analysis, design, implementation
concurrently, and the three phases are
performed repeatedly in a cycle till system is
completed.
Copyright © 2020, 2017, 2014 Pearson Education, Inc. All Rights Reserved
 System prototyping: perform
Prototyping analysis, design, implementation
rapidly and concurrently, and the
three phases are performed
repeatedly in a cycle till system is
completed.
The Prototyping Process (Another Look)

Copyright © 2020, 2017, 2014 Pearson Education, Inc. All Rights Reserved
Prototyping
•
Advantages of prototyping
– Useful if some uncertainty in requirements or design
solutions
– Often used for end-user interface design
– More likely to fulfill end-user requirements
•
Disadvantages
– May not undergo full testing or documentation
– May not accommodate large quantities of data or large
number of users

Copyright © 2020, 2017, 2014 Pearson Education, Inc. All Rights Reserved
3. Agile Methodology
• Agile model is a combination of a simple iterative and incremental
process models with focus on process adaptability and customer
satisfaction by rapid delivery of working software product.

• A group of programming-centric methodologies that focus on streamlining the

SDLC by eliminating much of modeling and documentation overhead and the
time spent on those tasks.

• All Agile methodologies are used in conjunction with Object-Oriented

technology

The Most popular Agile methodologies are:

– Extreme programming (XP) emphasizes customer satisfaction and
teamwork.
– Scrum
3. Agile Methodologies
• Focuses on rapid delivery of working software by
breaking large project into several small sub-projects
• Subprojects
• Treated as separate, complete projects
• Completed in short periods of time using iteration and
continuous feedback
• Emphasizes face-to-face communication over written
documents, allowing collaboration and faster decision
making

Copyright © 2020, 2017, 2014 Pearson Education, Inc. All Rights Reserved
Agile Key Principles
– Key Agile principles (www.AgileAlliance.org):
▪ The highest priority is to satisfy the customer through early and
continuous delivery of valuable software.
▪ Welcome changing requirements, even late in development. Agile
processes harness change for the customer’s competitive
advantage.
▪ Deliver working software frequently, from a couple of weeks to a
couple of months, with a preference to the shorter timescale.
▪ Businesspeople and developers work together daily throughout the
project.
▪ Build projects around motivated individuals. Give them the
environment and support they need and trust them to get the job
done.
▪ The most efficient and effective method of conveying information to
and within a development team is face-to-face conversation.
▪ Working software is the primary measure of progress.
Copyright © 2020, 2017, 2014 Pearson Education, Inc. All Rights Reserved
3.1 Extreme programming (XP)
• XP is based on four core values:
Communication, simplicity, feedback, and
courage
• Short, incremental development cycles
• Two-person programming teams
• Coding and testing operate together
• Advantages:
–Communication between developers
–High level of productivity
–High-quality code
Copyright © 2020, 2017, 2014 Pearson Education, Inc. All Rights Reserved
3.2 Scrum
• Uses small teams to produce small pieces of deliverable
software using sprints (2 weeks to a month), or 30-day
intervals, to achieve an appointed goal.
– Sprint means a set period of time during which specific tasks
must be completed.

• Under this methodology, each day ends or begins with a

stand-up meeting to monitor and control the development
effort

• Three primary artifacts in the Scrum process

1. Product Backlog: Listing of potential requirements
2. Sprint Backlog: Listing of only items to be addressed in a
particular sprint
3. Increment: Represents the sum of all the Product Backlog
items completed during a sprint.
Copyright © 2020, 2017, 2014 Pearson Education, Inc. All Rights Reserved
Scrum
Agile Methodologies—Not for Every
Project
• Agile methodologies are not for everyone
• Fowler recommends an agile process if your project
involves:
– unpredictable or dynamic requirements
– responsible and motivated developers
– customers who understand the process and will
get involved

Copyright © 2020, 2017, 2014 Pearson Education, Inc. All Rights Reserved
Selecting the Appropriate
Development Methodology
Selecting the Appropriate
Development Methodology
 Important factors to consider in
selecting the development methodology
- Clarity of User Requirements
- Familiarity with Technology
- System Complexity
- System Reliability
- Short Time Schedules
- Schedule Visibility
4. Object-Oriented Analysis and
Design (OOAD)
• Based on objects rather than data or processes
• Combines data and processes (called methods) into
single entities call objects
• Object: A structure that encapsulates attributes and
methods that operate on those attributes
• Inheritance: Hierarchical arrangement of classes
enabling subclasses to inherit properties of superclasses
• Object Class: Logical grouping of objects that have the
same attributes and behaviors

Copyright © 2020, 2017, 2014 Pearson Education, Inc. All Rights Reserved
4.1 Relational Unified Process (RUP)
• Relational Unified Process (RUP) is an object-
oriented systems development methodology
• Based on an iterative, incremental approach to
systems development
• RUPs four phases (each can be further divided)
– Inception
– Elaboration
– Construction
– Transition

Copyright © 2020, 2017, 2014 Pearson Education, Inc. All Rights Reserved
Unified Process Phases
Inception Elaboration Construction Transition

 Inception
◦ Establish the business case for the system, define risks, obtain 10% of
the requirements, estimate next phase effort.
 Elaboration
◦ Develop an understanding of the problem domain and the system
architecture, risk significant portions may be coded/tested, 80%
major requirements identified.
 Construction
◦ System design, programming and testing. Building the remaining
system in short iterations.
 Transition
◦ Deploy the system in its operating environment. Deliver releases for
feedback and deployment.
Phase Deliverables
Inception Phase Elaboration Construction Transition Phase
Phase Phase
• The initial version of • The completed • The initial user • All the artifacts
the domain model domain model manual and other (final versions)
• The initial version of • The completed manuals, as • The completed
the business model business model appropriate manuals
• The initial version of • The completed • All the artifacts
the requirements requirements (beta release
artifacts artifacts versions)
• A preliminary • The completed • The completed
version of the analysis artifacts architecture
analysis artifacts • An updated version • The updated risk
• A preliminary of the architecture list
version of the • An updated list of • The project
architecture risks management plan
• The initial list of • The project (for the remainder
risks management plan of the project)
• The initial ordering (for the rest of the • If necessary, the
of the use cases project) updated business
• The plan for the • The completed case
elaboration phase business case
• The initial version of
the business case
Summary

• In this chapter you learned how to:

–Define information systems analysis and
design
–Describe the information systems
development life cycle (SDLC)
–Describe Waterfall, RAD, Agile
Methodologies, eXtreme Programming, and
Scrum
–Explain object-oriented analysis and design
and the Relational Unified Process (RUP)

Copyright © 2020, 2017, 2014 Pearson Education, Inc. All Rights Reserved
A video to watch

 https://www.youtube.com/watch?
v=Xt5tBXRTtkM
Copyright

This work is protected by United States copyright laws and is

provided solely for the use of instructors in teaching their
courses and assessing student learning. Dissemination or sale of
any part of this work (including on the World Wide Web) will
destroy the integrity of the work and is not permitted. The work
and materials from it should never be made available to students
except by instructors using the accompanying text in their
classes. All recipients of this work are expected to abide by these
restrictions and to honor the intended pedagogical purposes and
the needs of other instructors who rely on these materials.

Copyright © 2020, 2017, 2014 Pearson Education, Inc. All Rights Reserved