Chap3 Determining System Requirements
Transcript of Chap3 Determining System Requirements
![Page 1: Chap3 Determining System Requirements](https://reader033.fdocuments.us/reader033/viewer/2022052310/5532a5df4a79599f5e8b46ae/html5/thumbnails/1.jpg)
Module 3 Determining System Requirements
4.14.1
![Page 2: Chap3 Determining System Requirements](https://reader033.fdocuments.us/reader033/viewer/2022052310/5532a5df4a79599f5e8b46ae/html5/thumbnails/2.jpg)
Learning Objectives
Describe options for designing and conducting interviews
Discuss planning an interviewDiscuss using questionnaires to determine
system requirementsExplain advantages and disadvantages of
observing workers and analyzing business documents to determine requirements
4.24.2
![Page 3: Chap3 Determining System Requirements](https://reader033.fdocuments.us/reader033/viewer/2022052310/5532a5df4a79599f5e8b46ae/html5/thumbnails/3.jpg)
Learning Objectives
Learn about Joint Application Design (JAD) and Prototyping
Discuss appropriate methods to elicit system requests
Explain Business Process Re-engineering (BPR)
Examine requirements determination for Internet applications
4.34.3
![Page 4: Chap3 Determining System Requirements](https://reader033.fdocuments.us/reader033/viewer/2022052310/5532a5df4a79599f5e8b46ae/html5/thumbnails/4.jpg)
Performing Requirements Determination
Gather information on what system should do from many sources Users Reports Forms Procedures
4.44.4
![Page 5: Chap3 Determining System Requirements](https://reader033.fdocuments.us/reader033/viewer/2022052310/5532a5df4a79599f5e8b46ae/html5/thumbnails/5.jpg)
Performing Requirements Determination
Characteristics for gathering requirements Impertinence
Question everything Impartiality
Find the best organizational solution Relaxation of constraints Attention to detail Reframing
View the organization in new ways
4.54.5
![Page 6: Chap3 Determining System Requirements](https://reader033.fdocuments.us/reader033/viewer/2022052310/5532a5df4a79599f5e8b46ae/html5/thumbnails/6.jpg)
Deliverables and Outcomes
Types of deliverables: Information collected from users Existing documents and files Computer-based information Understanding of organizational components
Business objective Information needs Rules of data processing Key events
4.64.6
![Page 7: Chap3 Determining System Requirements](https://reader033.fdocuments.us/reader033/viewer/2022052310/5532a5df4a79599f5e8b46ae/html5/thumbnails/7.jpg)
Traditional Methods for Determining Requirements
Interviewing and Listening Gather facts, opinions and speculations Observe body language and emotions Guidelines
Plan Checklist Appointment
Be neutral Listen Seek a diverse view
4.74.7
![Page 8: Chap3 Determining System Requirements](https://reader033.fdocuments.us/reader033/viewer/2022052310/5532a5df4a79599f5e8b46ae/html5/thumbnails/8.jpg)
Traditional Methods for Determining Requirements
Interviewing (Continued) Interview Questions
Open-Ended No pre-specified answers
Close-Ended Respondent is asked to choose from a set of
specified responses
4.84.8
![Page 9: Chap3 Determining System Requirements](https://reader033.fdocuments.us/reader033/viewer/2022052310/5532a5df4a79599f5e8b46ae/html5/thumbnails/9.jpg)
Traditional Methods for Determining Requirements
Administering Questionnaires More cost-effective than interviews Choosing respondents
Should be representative of all users Types of samples
Convenient Random sample Purposeful sample Stratified sample
4.94.9
![Page 10: Chap3 Determining System Requirements](https://reader033.fdocuments.us/reader033/viewer/2022052310/5532a5df4a79599f5e8b46ae/html5/thumbnails/10.jpg)
Traditional Methods for Determining Requirements
Questionnaires Design
Mostly closed-ended questions Can be administered over the phone or in
person Vs. Interviews
Interviews cost more but yield more information Questionnaires are more cost-effective See table 4-4 for a complete comparison
4.104.10
![Page 11: Chap3 Determining System Requirements](https://reader033.fdocuments.us/reader033/viewer/2022052310/5532a5df4a79599f5e8b46ae/html5/thumbnails/11.jpg)
Traditional Methods for Determining Requirements
Directly Observing Users Serves as a good method to supplement
interviews Often difficult to obtain unbiased data
People often work differently when being observed
4.114.11
![Page 12: Chap3 Determining System Requirements](https://reader033.fdocuments.us/reader033/viewer/2022052310/5532a5df4a79599f5e8b46ae/html5/thumbnails/12.jpg)
Analyzing Procedures and Other Documents
Types of information to be discovered: Problems with existing system Opportunity to meet new need Organizational direction Names of key individuals Values of organization Special information processing circumstances Rules for processing data
4.124.12
![Page 13: Chap3 Determining System Requirements](https://reader033.fdocuments.us/reader033/viewer/2022052310/5532a5df4a79599f5e8b46ae/html5/thumbnails/13.jpg)
Modern Methods for Determining Requirements
Joint Application Design (JAD) Brings together key users, managers and systems
analysts Purpose: collect system requirements simultaneously
from key people Conducted off-site
Prototyping Repetitive process Rudimentary version of system is built Replaces or augments SDLC Goal: to develop concrete specifications for ultimate
system4.134.13
![Page 14: Chap3 Determining System Requirements](https://reader033.fdocuments.us/reader033/viewer/2022052310/5532a5df4a79599f5e8b46ae/html5/thumbnails/14.jpg)
Joint Application Design (JAD)
Participants Session Leader Users Managers Sponsor Systems Analysts Scribe IS Staff
4.144.14
![Page 15: Chap3 Determining System Requirements](https://reader033.fdocuments.us/reader033/viewer/2022052310/5532a5df4a79599f5e8b46ae/html5/thumbnails/15.jpg)
Joint Application Design (JAD)
End Result Documentation detailing existing system Features of proposed system
4.154.15
![Page 16: Chap3 Determining System Requirements](https://reader033.fdocuments.us/reader033/viewer/2022052310/5532a5df4a79599f5e8b46ae/html5/thumbnails/16.jpg)
PrototypingQuickly converts requirements to working version of systemOnce the user sees requirements converted to system, will ask for modifications or will generate additional requestsMost useful when: User requests are not clear Few users are involved in the system Designs are complex and require concrete form History of communication problems between
analysts and users Tools are readily available to build prototype
4.164.16
![Page 17: Chap3 Determining System Requirements](https://reader033.fdocuments.us/reader033/viewer/2022052310/5532a5df4a79599f5e8b46ae/html5/thumbnails/17.jpg)
Prototyping
Drawbacks Tendency to avoid formal documentation Difficult to adapt to more general user
audience Sharing data with other systems is often
not considered Systems Development Life Cycle (SDLC)
checks are often bypassed
4.174.17
![Page 18: Chap3 Determining System Requirements](https://reader033.fdocuments.us/reader033/viewer/2022052310/5532a5df4a79599f5e8b46ae/html5/thumbnails/18.jpg)
Business Process Reengineering (BPR)
Search for and implementation of radical change in business processes to achieve breakthrough improvements in products and services
Goals Reorganize complete flow of data in major
sections of an organization Eliminate unnecessary steps
4.184.18
![Page 19: Chap3 Determining System Requirements](https://reader033.fdocuments.us/reader033/viewer/2022052310/5532a5df4a79599f5e8b46ae/html5/thumbnails/19.jpg)
Business Process Reengineering (BPR)
Goals (Continued) Combine steps Become more responsive to future change
Identification of processes to reengineer Key business processes
Set of activities designed to produce specific output for a particular customer or market
Focused on customers and outcome Same techniques are used as were used for
requirements determination
4.194.19
![Page 20: Chap3 Determining System Requirements](https://reader033.fdocuments.us/reader033/viewer/2022052310/5532a5df4a79599f5e8b46ae/html5/thumbnails/20.jpg)
Business Process Reengineering (BPR)
Identify specific activities that can be improved through BPR
Disruptive technologies Technologies that enable the breaking of
long-held business rules that inhibit organizations from making radical business changes
See table 4-6
4.204.20
![Page 21: Chap3 Determining System Requirements](https://reader033.fdocuments.us/reader033/viewer/2022052310/5532a5df4a79599f5e8b46ae/html5/thumbnails/21.jpg)
Summary
Interviews Open-ended and close-ended questions Preparation is key
Questionnaires Must be carefully designed Can contain close-ended as well as open-
ended questions
4.214.21
![Page 22: Chap3 Determining System Requirements](https://reader033.fdocuments.us/reader033/viewer/2022052310/5532a5df4a79599f5e8b46ae/html5/thumbnails/22.jpg)
Summary
Other means of gather requirements Observing workers Analyzing business documents
Joint Application Design (JAD)
Prototyping
Business Process Reengineering (BPR) Disruptive technologies
4.224.22