Chapter 4 Notes

Chapter 4 Notes - 1 Chapter 4 Information Gathering:...

Info iconThis preview shows pages 1–6. Sign up to view the full content.

View Full Document Right Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: 1 Chapter 4 Information Gathering: Interactive Methods Systems Analysis and Design Kendall & Kendall Seventh Edition 2 Test Slide- Check your clickers 1 2 3 4 0% 0% 0% 0% 1. 1 2. 2 3. 3 4. 4 2 3 Objectives Functional Decomposition Diagram Requirement Gathering Recognize the value of interactive methods for information gathering Construct interview questions to elicit human information requirements Structure interviews in a way that is meaningful to users Understand the concept of JAD and when to use it Write effective questions to survey users about their work Design and administer effective questionnaires 4 Project Initiation An opportunity to create business value from using information technology initiates a project. Projects are selected based on business needs and project risks. 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 The System Proposal is the key deliverable from the Analysis Phase 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 isnt needed. 3 5 A statement of what the system must do A statement of characteristics the system must have Focus is on business user needs during analysis phase Requirements will change over time as project moves from analysis to design to implementation What is a Requirement? 6 A process the system has to perform Examples: The system must allow registered customers to view their account history The system must check the incoming customer orders for inventory available Information the system must contain Examples: The system must retain customer order history for three years The system must include real time inventory levels at all warehouses Requirement Types- Functional 4 7 Nonfunctional Requirements: Behavioral properties the system must have Operational Example- The system can run on handheld devices Performance Example- An interaction between user and system should not exceed 2 seconds Security Example-The system include all available safeguards from virus, worms, etc Cultural and political Example- Company policy say we only buy computers from Dell Requirement Types- Nonfunctional 8 Basic Process of Analysis (Determining Requirements) Understand the As-Is system Identify improvement opportunities Develop the To-Be system concept 5 9 Identifying Improvements in As-Is Systems Problem Analysis Ask users to identify problems and solutions Improvements tend to be small and incremental Rarely finds improvements with significant business value Root Cause Analysis Challenge assumptions about why problem exists Trace symptoms to their causes to discover the real problem 10 Duration Analysis Calculate time needed for each process step Calculate time needed for overall process...
View Full Document

Page1 / 35

Chapter 4 Notes - 1 Chapter 4 Information Gathering:...

This preview shows document pages 1 - 6. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online