Lecture "Chapter 4: Beginning the analysis - Investigating system requirements" provides students with the knowledge: The analysis phase in more detail, system requirements, techniques for Information gathering, conduct interviews and discussions with users, activity diagram showing concurrent paths,... Invite you to consult.
4
4
cycle phase
Describe the activities of the systems analysis life
reengineering on activities of the analysis phase
Explain the effect of business process
nonfunctional system requirements
Systems Analysis and Design in a Changing World, 3rd Edition
Describe the difference between functional and
users who will be involved in investigating system requirements
Systems Analysis and Design in a Changing World, 3rd Edition
2
4
4
Identify and understand the different types of
to develop system requirements
Fact-finding for investigation of system
requirements
Analysis phase of SDLC skills needed: Describe the kind of information that is required
Analyst should learn details of business processes
and daily operations
of documentation, interviews, observation, prototypes, questionnaires, vendor research, and joint application design sessions
Analyst should become as knowledgeable as
business domain users to build credibility
Analyst brings fresh perspective to problem
Modeling of business processes based on system
Determine system requirements through review
requirements
Systems Analysis and Design in a Changing World, 3rd Edition
Systems Analysis and Design in a Changing World, 3rd Edition
3
4
4
4
Discuss the need for validation of system requirements to ensure accuracy and completeness and the use of a structured walkthrough
Gather information
Logical model and physical model
Define system requirements
Prioritize requirements
Prototype for feasibility and discovery
Generate and evaluate alternatives
Systems Analysis and Design in a Changing World, 3rd Edition
Systems Analysis and Design in a Changing World, 3rd Edition
5
6
Review recommendations with management
4
4
company
and effective as possible
Questions basic assumptions for doing business
and seeks to find a better way
Streamlines internal processes to be as efficient
process improvement
Uses IT as BPR enabler Systems analyst may discover opportunities for
Systems Analysis and Design in a Changing World, 3rd Edition
Systems Analysis and Design in a Changing World, 3rd Edition
7
8
4
4
Any project may include components of BPR
implementation
Activities system must perform
New system capabilities and constraints People with interest in successful system Functional requirements are:
Based on procedures and business functions
Users (use system)
Documented in analysis models
Clients (pay for and own system)
Three primary groups of stakeholders:
Technical staff (ensure system operation)
Operating environment or performance objectives
Usability, reliability, and security requirements
Nonfunctional requirements include:
Systems Analysis and Design in a Changing World, 3rd Edition
Systems Analysis and Design in a Changing World, 3rd Edition
9
10
4
4
Every type of stakeholder is identified by analyst
departments
Horizontal user roles - information flow across
Business users perform day-to-day operations
Information users need current information
Management users need summary information
Executive users need strategic information
External users may have access to system
Systems Analysis and Design in a Changing World, 3rd Edition
Systems Analysis and Design in a Changing World, 3rd Edition
11
12
Vertical user roles - information needs of clerical staff, middle management, and senior executives
4
4
Analysis phase done to understand business functions and develop system requirements
Create model of existing system
Derive requirements from existing system model
Original structured approach
Identify logical requirements for new system
Balance the review of current business functions
with new system requirements
Systems Analysis and Design in a Changing World, 3rd Edition
Systems Analysis and Design in a Changing World, 3rd Edition
14
13
4
4
Current approach
descriptions
Review existing reports, forms, and procedure
Interview and discussion processes with users
Observe and document business processes
Build prototypes
Distribute and collect questionnaires
Conduct joint application design (JAD) sessions
Systems Analysis and Design in a Changing World, 3rd Edition
Systems Analysis and Design in a Changing World, 3rd Edition
16
15
4
4
Research vendor solutions
organizations and trade publications
Source: External industry wide professional
Identify business rules, discrepancies, and
redundancies
Be cautious of outdated material
Obtain preliminary understanding of processes
Use as guidelines / visual cues to guide interviews
Systems Analysis and Design in a Changing World, 3rd Edition
Systems Analysis and Design in a Changing World, 3rd Edition
17
18
Source: Existing business documents and procedure descriptions within organization
4 Conduct Interviews and Discussions with Users
4 Sample Checklist to Prepare for User Interviews
and rules
Effective way to understand business functions
Time-consuming and resource-expensive
Meet all users
Understand all processing requirements
May require multiple sessions to:
Can meet with individuals or groups of users
Systems Analysis and Design in a Changing World, 3rd Edition
Systems Analysis and Design in a Changing World, 3rd Edition
19
20
4
4
List of detailed questions prepared
actual tasks
Varies from office walkthrough to performing
level of detail
Not necessary to observe all processes at same
May make users nervous, so use common sense
diagrams
Systems Analysis and Design in a Changing World, 3rd Edition
Systems Analysis and Design in a Changing World, 3rd Edition
21
22
4
4
May be documented with workflow (activity)
Systems Analysis and Design in a Changing World, 3rd Edition
Systems Analysis and Design in a Changing World, 3rd Edition
23
24
4
4
complex system
Discovery, design, evolving prototypes
Preliminary working model of a larger, more
Working model to provide “look and feel”
Operative
Focused to accomplish single objective
Built and modified rapidly with CASE tools
Systems Analysis and Design in a Changing World, 3rd Edition
Systems Analysis and Design in a Changing World, 3rd Edition
25
26
4
4
Quick
number of stakeholders
Limited and specific information from a large Expedite investigation of systems requirements
Preliminary insight into business
question
Not well suited for gathering detailed information Seeks to compress fact-finding, modeling, policy formation, and verification activities into shorter time frame Closed-ended questions direct person answering
stakeholders present
elaboration
Systems Analysis and Design in a Changing World, 3rd Edition
Systems Analysis and Design in a Changing World, 3rd Edition
27
28
4
4
Critical factor is to have all important Open-ended questions encourage discussion and
JAD group facilitation
Limit interruptions
Session leader trained in group dynamics and Conducted in special room
May be off-site
Technical staff representatives to handle:
Overhead projector, white board, flip charts, work
Computer and network configurations
material
Operating environments
Electronic support (Laptops)
Security issues
CASE Tools
Knowledgeable business and system users Policy making managers Resources
Group support systems (GSS)
Systems Analysis and Design in a Changing World, 3rd Edition
Systems Analysis and Design in a Changing World, 3rd Edition
29
30
Project team members
4
4
companies
Many problems have been solved by other
Frequently provide new ideas
May be state of the art
Cheaper and less risky
Positive contributions of vendor solutions
May purchase solution before understanding
problem
Systems Analysis and Design in a Changing World, 3rd Edition
Systems Analysis and Design in a Changing World, 3rd Edition
31
32
4
4
Danger
Technical specifications from vendor Make sure gathered information is correct
Effective means of implementing quality control
early in project
Structured walkthrough Demo or trial system
Verify and validate system requirements
Review of findings from investigation and of
References of existing clients
models based on findings
On-site visits
System analyst, project manager are partners
Systems Analysis and Design in a Changing World, 3rd Edition
Systems Analysis and Design in a Changing World, 3rd Edition
33
34
4
4
Project manager responsible for system quality Printout of screens and reports
Gather information
Functional and Nonfunctional
Define system requirements
Work with various stakeholders (users, clients,
technical staff)
Prioritize requirements
“What kind of information do I need?”
Prototype for feasibility and discovery
Generate and evaluate alternatives
What are the business processes and operations?
How are the business processes performed?
Review recommendations with management
What are the information requirements?
Analysis Phase Activities Gathering system requirements
analysis phase
Systems Analysis and Design in a Changing World, 3rd Edition
Systems Analysis and Design in a Changing World, 3rd Edition
35
36
BPR is becoming widespread and can affect
4
Review existing reports, forms, and procedure
descriptions
Conduct interviews and discussions with users
Observe and document business processes
Build prototype working models
Distribute and collect questionnaires
Conduct JAD sessions
Research vendor solutions
Systems Analysis and Design in a Changing World, 3rd Edition
37
Primary information gathering techniques
