Chapter 2
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2 1
©2016. Cengage Learning. All rights r
eserved.
Chapter 2 Outline
The RMO Consolidated Sales and Marketing
System Project
Systems Analysis Activities
What Are Requirements?
Stakeholders
Information-Gathering Techniques
Models and Modeling
Documenting Workflows with Activity Diagrams
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
©2016. Cengage Learning. All rights 2
reserved.
Learning Objectives
Describe the activities of systems analysis
Explain the difference between functional and
nonfunctional requirements
Identify / understand stakeholders and their
contributions to requirements
Information-gathering techniques & determine when
each is best applied
Describe the role of models in systems analysis
Develop UML activity diagrams to model workflows
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
©2016. Cengage Learning. All rights 3
reserved.
Overview
Chapter 1 introduced the SDLC & demonstrated its use for
resolving a business need
This chapter expands the SDLC processes to cover a wider
range of concepts, tools and techniques
Core process 3: Discover and understand the details of the
problem or need—is the main focus of systems analysis
Systems analysis activities are detailed in this chapter
A larger Ridgeline Mountain Outfitters (RMO) project:
Introduced & used throughout the text to illustrate analysis and design
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
©2016. Cengage Learning. All rights 4
reserved.
Ridgeline Mountain Outfitters (RMO)
RMO has an elaborate set of information systems that
support operations and management
Drivers to upgrade support for sales and marketing:
Customer expectations,
modern technological capabilities, and
competitive pressures
A new Consolidated Sales and Marketing System was
proposed
This is a major project that grew out of the RMO
strategic planning process
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
©2016. Cengage Learning. All rights 5
reserved.
RMO Information Systems Strategic Plan
Technology architecture— the set of computing
hardware, network hardware and topology, and system
software employed by the organization
Application architecture—the information systems
that supports the organization (information systems,
subsystems, and supporting technology)
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
©2016. Cengage Learning. All rights 6
reserved.
RMO Existing Application Architecture
1. Supply Chain Management (SCM)
5 years old; Java/Oracle
Tradeshow system will interface with SCM
2. Phone/Mail Order System
12 years old; Visual Studio/MS SQL
Reached capacity; minimal integration
3. Retail Store System
Older package solution; minimal integration
4. Customer Support System (CSS)
Web based system; evolved over the years, minimal
integration
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
©2016. Cengage Learning. All rights 7
reserved.
Proposed Application Architecture: Integrate SCM
and New CSMS
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
©2016. Cengage Learning. All rights 8
reserved.
New Consolidated Sales and Marketing System
(CSMS)
Sales Subsystem
Integrates online, phone, and retail stores
Order Fulfillment Subsystem
Track shipments, rate products and services
Customer Account Subsystem
Shopping history, linkups, “mountain bucks” rewards
Marketing Subsystem
Promotional packages, partner relationships, more
complete merchandise information and reporting
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
©2016. Cengage Learning. All rights 9
reserved.
Systems Analysis Activities for CSMS
It will require discovering and understanding
extensive and complex business processes and
business rules
The SDLC indicates the project starts with:
(1) identifying the problem,
(2) obtaining approval, and
(3) planning the project (as seen in Chapter 1)
To get to the heart of systems analysis, this text skips right to analysis
activities generally and the specifically for the RMO CSMS project (Core
Process #3)
Project planning and project management are covered in detail later in the
text
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
©2016. Cengage Learning. All rights 10
reserved.
Systems Analysis Activities
Involve discovery and understanding
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
©2016. Cengage Learning. All rights 11
reserved.
Systems Analysis Activities
Gather Detailed Information
Interviews, questionnaires, documents, observing business processes,
researching vendors, comments and suggestions
Define Requirements
Modeling functional requirements and non-functional requirements
Prioritize Requirements
Essential, important, vs. nice to have
Develop User-Interface Dialogs
Flow of interaction between user and system
Evaluate Requirements with Users
User involvement, feedback, adapt to changes
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
©2016. Cengage Learning. All rights 12
reserved.
What Are Requirements?
System’s Requirements =
1. Functional requirements
2. Non-functional requirements
Functional Requirements– the activities the system
must perform
Business uses, functions the users carry out
Shown as use cases in Chapter 1
Non-Functional Requirements– other system
characteristics
Constraints, accessibility, technical requirements,
performance goals, etc
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
©2016. Cengage Learning. All rights 13
reserved.
FURPS+ Requirements Acronym
Functional requirements
Usability requirements(user interface)
Reliability requirements(downtime)
Performance requirements(response time)
Security requirements(encryption)
+ even more categories…
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
©2016. Cengage Learning. All rights 14
reserved.
FURPS+ Requirements Acronym
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
©2016. Cengage Learning. All rights 15
reserved.
Additional Requirements Categories
Design constraints –
Specific restrictions for hardware and software(memory
usage)
Implementation requirements
Specific languages, tools, protocols, etc.
Interface requirements
Interface links to other systems(RSS feeds, facebook)
Physical requirements
Physical facilities and equipment constraints
Supportability requirements
Automatic updates and enhancement methods
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
©2016. Cengage Learning. All rights reserved
Stakeholders
Who do you involve and talk to?
Stakeholders– persons who have an interest in the
successful implementation of the system
Classes of stakeholders:
Internal Stakeholders– persons within the organization
External stakeholders – persons outside the organization
Operational stakeholders – persons who regularly interact with
the system
Executive stakeholders– persons who don’t directly interact, but
use the information or have financial interest
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
©2016. Cengage Learning. All rights 17
reserved.
Stakeholders of a comprehensive accounting system for public company
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
©2016. Cengage Learning. All rights 18
reserved.
Stakeholders For RMO CSMS Project
Phone/mail sales order clerks
Warehouse and shipping personnel
Marketing personnel who maintain online catalog
information
Marketing, sales, accounting, and financial managers
Senior executives
Customers
External shippers (e.g., UPS and FedEx)
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
©2016. Cengage Learning. All rights 19
reserved.
RMO Internal
Stakeholders
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
©2016. Cengage Learning. All rights 20
reserved.
Information Gathering Techniques
1. Interviewing users and other stakeholders
2. Distributing and collecting questionnaires
3. Reviewing inputs, outputs, and documentation
4. Observing and documenting business procedures
5. Researching vendor solutions
6. Collecting active user comments and suggestions
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
©2016. Cengage Learning. All rights 21
reserved.
Interviewing Users and Other Stakeholders
Prepare detailed questions
Meet with individuals or groups of users
Obtain and discuss answers to the questions
Document the answers
Follow up as needed in future meetings or interviews
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
©2016. Cengage Learning. All rights 22
reserved.
Themes for Information Gathering Questions
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
©2016. Cengage Learning. All rights 23
reserved.
Preparing for the Interview
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
©2016. Cengage Learning. All rights 24
reserved.
Interview
Session
Agenda
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
©2016. Cengage Learning. All rights 25
reserved.
Keeping an Open Items List
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
©2016. Cengage Learning. All rights 26
reserved.
Distribute and Collect
Questionnaires
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
©2016. Cengage Learning. All rights 27
reserved.
Review Inputs, Outputs, and Procedures
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
©2016. Cengage Learning. All rights 28
reserved.
Additional Techniques
Observe and Document Business Processes
Watch and learn
Document with Activity diagram (next section)
Research Vendor Solutions
See what others have done for similar situations
White papers, vendor literature, competitors
For build or buy analysis
Collect Active User Comments and Suggestions
Feedback on models and tests
Users know it when the see it
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
©2016. Cengage Learning. All rights 29
reserved.
Models and Modeling
How do we define requirements? After collecting
information, create models
Model– a representation of some aspect of the
system being built
Types of Models
Textual model– something written down, described
Graphical models– diagram, schematic
Mathematical models– formulas, statistics, algorithms
Unified Modeling Language (UML)
Standard graphical modeling symbols/terminology used for
information systems
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
©2016. Cengage Learning. All rights 30
reserved.
Reasons for Modeling
Learning from the modeling process
Reducing complexity by abstraction
Remembering all the details
Communicating with other development team
members
Communicating with a variety of users and
stakeholders
Documenting what was done for future
maintenance/enhancement
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
©2016. Cengage Learning. All rights 31
reserved.
Some Analysis and Design Models
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
©2016. Cengage Learning. All rights 32
reserved.
Documenting Workflows with Activity Diagrams
Workflow– sequence of processing steps that
completely handles one business transaction or
customer request
Activity Diagram– describes user (or system)
activities, the person who does each activity, and the
sequential flow of these activities
Useful for showing a graphical model of a workflow
A UML diagram
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
©2016. Cengage Learning. All rights 33
reserved.
Activity Diagrams Symbols
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
©2016. Cengage Learning. All rights 34
reserved.
Activity
Diagram for
RMO Order
Fulfillment
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
©2016. Cengage Learning. All rights 35
reserved.
Activity Diagram with Concurrent Paths
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
©2016. Cengage Learning. All rights 36
reserved.
Summary
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
©2016. Cengage Learning. All rights 37
reserved.
Summary
Systems analysis activates correspond to the core
SDLC process Discover and understand details
System projects originate from the information
system strategic plan, which contains an technology
architecture plan and an application architecture plan
The RMO CSMS Project will be used throughout the
text as an example of analysis and design
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
©2016. Cengage Learning. All rights 38
reserved.
Summary
Systems analysis involves defining system
requirements– functional and non-functional
Analysis activities include
Gather detailed information
Define requirements
Prioritize requirements
Develop user-interface dialogs
Evaluate requirements with users
FURPS+ is the acronym for functional, usability,
reliability, performance, and security requirements
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
©2016. Cengage Learning. All rights 39
reserved.
Summary
Stakeholders are the people who have an interest in
the success of the project
There are internal vs. external stakeholders and
operational vs. executive stakeholders
Information gathering techniques are used to collect
information about the project
Interviews, questionnaires, reviewing documents, observing business
processes, researching vendors, comments and suggestions
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
©2016. Cengage Learning. All rights 40
reserved.
Summary
The UML Activity Diagram is used to document
(model) workflows after collecting information
Models and modeling are used to explore and
document requirements
Unified Modeling Language (UML) is the standard set
of notations and terminology for information systems
models
Systems Analysis and Design in a Changing World, 7th Edition - Chapter 2
©2016. Cengage Learning. All rights 41
reserved.