system analysis
DESCRIPTION
SYSTEM ANALYSIS. Chapter 5. Key Definitions. The As-Is system is the current system and may or may not be computerized The To-Be system is the new system that is based on updated requirements. Key Ideas. - PowerPoint PPT PresentationTRANSCRIPT
![Page 1: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/1.jpg)
1
SYSTEM ANALYSIS
Chapter 5
![Page 2: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/2.jpg)
2
Key Definitions
The As-Is system is the current system and may or may not be computerized
The To-Be system is the new system that is based on updated requirements
![Page 3: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/3.jpg)
3
Key Ideas
The goal of the analysis phase is to truly understand the requirements of the new system and develop a system that addresses them -- or decide a new system isn’t needed.
The line between systems analysis and systems design is very blurry.
![Page 4: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/4.jpg)
4
THE ANALYSIS PROCESS
![Page 5: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/5.jpg)
5
Analysis Across Areas
Combines business and information technology
Balance expertise of users and analysts
![Page 6: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/6.jpg)
6
The SDLC Process
![Page 7: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/7.jpg)
7
Three Steps of the Analysis Phase
Understanding the “As-Is” system
Identifying improvement opportunities
Developing the “To-Be” system concept
![Page 8: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/8.jpg)
8
Three Fundamental Analysis Strategies
Business process automation (BPA)
Business Process Improvement (BPI)
Business Process Reengineering (BPR)
![Page 9: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/9.jpg)
9
BUSINESS PROCESS AUTOMATION
![Page 10: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/10.jpg)
10
Business Process Automation
Goal:
Efficiency for users
![Page 11: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/11.jpg)
11
Identifying Improvements in As-Is Systems
Problem AnalysisAsking users to identify problems
Rarely finds significant monetary benefits
Root Cause AnalysisPrioritizing problems
Tracing symptoms to their causes
![Page 12: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/12.jpg)
12
Root Cause Analysis
Identify symptoms
Trace each back to its causes
Symptoms
ROOT CAUSES
Symptoms
![Page 13: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/13.jpg)
13
Root Cause Analysis Example
![Page 14: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/14.jpg)
14
BUSINESS PROCESS IMPROVEMENT
![Page 15: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/15.jpg)
15
Business Process Improvement
Introducing evolutionary changes
![Page 16: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/16.jpg)
16
Duration Analysis
Calculate time needed for each process step
Calculate time needed for overall process
Compare the twoDevelop process integration or parallelization
![Page 17: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/17.jpg)
17
Activity-Based Costing
Calculate cost of each process step
Consider both direct and indirect costs
Identify most costly steps and focus improvement efforts on them
![Page 18: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/18.jpg)
18
Benchmarking
Studying how other organizations perform the same business process
Informal benchmarkingCheck with customers
Formal benchmarkingEstablish formal relationship with other organization
![Page 19: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/19.jpg)
19
BUSINESS PROCESS REENGINEERING
![Page 20: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/20.jpg)
20
Business Process Reengineering
Radical redesign of business processes
![Page 21: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/21.jpg)
21
Outcome Analysis
Consider desirable outcomes from customers’ perspective
Consider what the organization could enable the customer to do
![Page 22: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/22.jpg)
22
Breaking Assumptions
Identify fundamental business rules
Systematically break each rule
Identify effects on the business if rule is broken
![Page 23: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/23.jpg)
23
Technology Analysis
Analysts list important and interesting technologies
Managers list important and interesting technologies
The group identifies how each might be applied to the business
![Page 24: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/24.jpg)
24
Activity Elimination
Identify what would happen if each organizational activity were eliminated
Use “force-fit” to test all possibilities
![Page 25: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/25.jpg)
25
Proxy Benchmarking
List similar industries
Look for techniques from other industries that could be applied by the organization
![Page 26: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/26.jpg)
26
Process Simplification
Eliminate complexity from routine transactions
Concentrate separate processes on exception handling
![Page 27: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/27.jpg)
27
DEVELOPING AN ANALYSIS PLAN
![Page 28: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/28.jpg)
28
Developing an Analysis Strategy
Potential business value
Project cost
Breadth of analysis
Risk
![Page 29: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/29.jpg)
29
Characteristics of Analysis Strategies
Business Business BusinessProcess Process ProcessAutomation Improvement Reeingineering
Potential Business Low-Moderate Moderate HighValue
Project Cost Low Low-Moderate High
Breadth of Analysis Narrow Narrow-Moderate Very Broad
Risk Low-Moderate Low-Moderate Very High
![Page 30: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/30.jpg)
30
Requirements Gathering
The goal of the analysis phase is to truly understand the requirements of the new system and develop a system that addresses them.
The first challenge is finding the right people to participate.
The second challenge is collecting and integrating the information.
![Page 31: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/31.jpg)
31
INTERVIEWS
![Page 32: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/32.jpg)
32
Interviews -- Five Basic Steps
Selecting interviewees
Designing interview questions
Preparing for the interview
Conducting the interview
Post-interview follow-up
![Page 33: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/33.jpg)
33
Selecting Interviewees
Based on information needed
Often good to get different perspectivesManagers
Users
Ideally, all key stakeholders
![Page 34: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/34.jpg)
34
Designing Interview Questions
Unstructured interviewBroad, roughly defined information
Structured interviewMore specific information
![Page 35: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/35.jpg)
35
Types of Questions
Types of Questions Examples
Closed-Ended Questions How many telephone orders are received per day?
How do customers place orders?
What additional information would you like the new system to provide?
Open-Ended Questions What do you think about the current system?
What are some of the problems you face on a daily basis?
How do you decide what types of marketing campaign to run?
Probing Questions Why?
Can you give me an example?
Can you explain that in a bit more detail?
![Page 36: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/36.jpg)
36
Questioning Strategies
High LevelVery General
Medium-LevelModeratelySpecific
Low-LevelVery Specific
TOP DOWN
BOTTOM UP
EXAMPLES?
![Page 37: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/37.jpg)
37
Interview Preparation Steps
Prepare general interview planList of question
Anticipated answers and follow-ups
Confirm areas of knowledge
Set priorities in case of time shortage
Prepare the intervieweeSchedule
Inform of reason for interview
Inform of areas of discussion
![Page 38: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/38.jpg)
38
Conducting the Interview
Appear professional and unbiasedRecord all informationCheck on organizational policy regarding tape recordingBe sure you understand all issues and termsSeparate facts from opinionsGive interviewee time to ask questionsBe sure to thank the intervieweeEnd on time
![Page 39: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/39.jpg)
39
Conducting the Interview Practical Tips
Don’t worry, be happy
Pay attention
Summarize key points
Be succinct
Be honest
Watch body language
![Page 40: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/40.jpg)
40
Post-Interview Follow-Up
Prepare interview notes
Prepare interview report
Look for gaps and new questions
![Page 41: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/41.jpg)
41
Interview Report
INTERVIEW REPORT
Interview notes approved by: ____________
Person interviewed ______________Interviewer _______________Date _______________Primary Purpose:
Summary of Interview:
Open Items:
Detailed Notes:
![Page 42: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/42.jpg)
42
Practice
You are interviewing the director of the PC lab at your school regarding a new program to support keeping track of students’ borrowing software
With a partner, write 5 questions you would ask the PC lab director
Take turns having one pair of students posing the questions to another pair of students
Be sure to take notes and write up the results when you have finished.
![Page 43: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/43.jpg)
43
JOINT APPLICATION DESIGN (JAD)
![Page 44: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/44.jpg)
44
JAD Key Ideas
Allows project managers, users, and developers to work together
May reduce scope creep by 50%
Avoids requirements being too specific or too vague
![Page 45: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/45.jpg)
45
JAD Important Roles
Facilitator
Scribe
![Page 46: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/46.jpg)
46
JAD Setting
U-Shaped seating
Away from distractions
Whiteboard/flip chart
Prototyping tools
e-JAD
![Page 47: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/47.jpg)
47
JAD Meeting Room
![Page 48: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/48.jpg)
48
The JAD Session
Tend to last 5 to 10 days over a three week period
Prepare questions as with interviews
Formal agenda and groundrules
Facilitator activitiesKeep session on track
Help with technical terms and jargon
Record group input
Help resolve issues
Post-session follow-up
![Page 49: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/49.jpg)
49
Managing Problems in JAD Sessions
Reducing domination
Encouraging non-contributors
Side discussions
Agenda merry-go-round
Violent agreement
Unresolved conflict
True conflict
Use humor
![Page 50: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/50.jpg)
50
QUESTIONNAIRES
![Page 51: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/51.jpg)
51
Questionnaire Steps
Selecting participantsUsing samples of the population
Designing the questionnaireCareful question selection
Administering the questionnaireWorking to get good response rate
Questionnaire follow-upSend results to participants
![Page 52: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/52.jpg)
52
Good Questionnaire Design
Begin with non-threatening and interesting questions
Group items into logically coherent sections
Do not put important items at the very end of the questionnaire
Do not crowd a page with too many items
Avoid abbreviations
Avoid biased or suggestive items or terms
Number questions to avoid confusion
Pretest the questionnaire to identify confusing questions
Provide anonymity to respondents
![Page 53: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/53.jpg)
53
Document Analysis
Provides clues about existing “as-is” system
Typical documentsForms
Reports
Policy manuals
Look for user additions to forms
Look for unused form elements
![Page 54: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/54.jpg)
54
Observation
Users/managers often don’t remember everything they do
Checks validity of information gathered other ways
Behaviors change when people are watched
Careful not to ignore periodic activitiesWeekly … Monthly … Annual
![Page 55: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/55.jpg)
55
Selecting the Appropriate Techniques
Interviews JAD Questionnaires Document Analysis
Observation
Type of information
As-is, improvements, to-be
As-is, improvements, to-be
As-is, improvements
As-is As-is
Depth of information
High High Medium Low Low
Breadth of information
Low Medium High High Low
Integration of information
Low High Low Low Low
User involvement
Medium High Low Low Low
Cost Medium Low-Medium Low Low Low-Medium
![Page 56: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/56.jpg)
56
Avoid Classic Analysis Mistakes
Reduced analysis time
Requirement gold-platingUser over-specification of features
Developer gold-platingToo many “cool” features
Lack of user involvement
![Page 57: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/57.jpg)
57
Proposal Outline
Table of contents
Executive summary
System request
Work plan
Analysis strategy
Recommended system
Feasibility analysis
Process model
Data Model
Appendices
![Page 58: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/58.jpg)
58
Summary
The analysis process aims to create value for the organization
Three main analysis strategies are BPA, BPI, and BPR
These strategies vary in potential business value, but also in potential cost and risk
![Page 59: SYSTEM ANALYSIS](https://reader034.vdocuments.mx/reader034/viewer/2022042718/5681316d550346895d97e5b1/html5/thumbnails/59.jpg)
59
Your Turn
How do you know whether to use business process automation, business process improvement, or business process reengineering?
Provide two examples.