Chapter 4: Beginning the Analysis: Investigating System Requirements

Slides:



Advertisements
Similar presentations
Systems Investigation and Analysis
Advertisements

Object-Oriented Analysis and Design LECTURE 3: REQUIREMENTS DISCIPLINE.
The System Development Life Cycle
Systems Analysis and Design 9th Edition
Chapter 2.
Today’s Outline Review exam one performance and overall grade
Chapter 8 Information Systems Development & Acquisition
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
2Object-Oriented Analysis and Design with the Unified Process Overview  Requirements discipline prominent in elaboration phase  Requirements discipline.
Fundamentals of Information Systems, Second Edition
Systems Analysis and Design in a Changing World, Tuesday, Jan 30.
Systems Analysis Requirements determination Requirements structuring
Systems Analysis and Design in a Changing World, Fourth Edition
Systems Analysis and Design in a Changing World, Fifth Edition
Jump to first page Chapter 2 System Analysis - Determining System Requirements.
Fact-Finding Fact-Finding Overview
Chapter 4: Beginning the Analysis: Investigating System Requirements
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Introduction to Systems Analysis and Design
Systems Analysis and Design: The Big Picture
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 7 Determining.
Determining System Requirements Classes 9,10. SDLC Project Identification & Selection Project Initiation & Planning Analysis ** Logical Design Physical.
INFORMATION SYSTEM APPLICATIONS System Development Life Cycle.
Chapter 4 Investigating System Requirements
Module 4: Systems Development Chapter 13: Investigation and Analysis.
CIS 321—IS Analysis & Design Chapter 4: Analysis— Investigating System Requirements.
Investigating System Requirements
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
2Object-Oriented Analysis and Design with the Unified Process The Requirements Discipline in More Detail  Focus shifts from defining to realizing objectives.
Team-Based Development ISYS321 Determining Object- Oriented Systems Requirements.
1 4 Systems Analysis and Design in a Changing World, 2 nd Edition, Satzinger, Jackson, & Burd Chapter 4 Beginning the Analysis: Investigating System Requirements.
 Describe the activities of the requirements discipline  Describe the difference between functional and nonfunctional system requirements  Describe.
Lecture 7: Requirements Engineering
IS2210: Systems Analysis and Systems Design and Change Twitter:
Systems Analysis and Design 8 th Edition Chapter 2 Analyzing the Business Case.
Objectives Describe the activities of the requirements discipline Describe the difference between functional and nonfunctional system requirements Describe.
4 Systems Analysis and Design in a Changing World, Fourth Edition.
Systems Analysis and Design in a Changing World, Thursday, Feb 1.
1 ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 Information Gathering Prototypes Structured Walkthrough.
IFS310: Module 3 1/25/2007 Fact Finding Techniques.
Systems Analysis and Design in a Changing World, Fourth Edition
Fundamentals of Information Systems, Second Edition 1 Systems Development.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 7 Determining.
IAD 2263: System Analysis and Design Chapter 3: Investigating System Requirements.
Chapter 6 Determining System Requirements. Objectives:  Describe interviewing options and develop interview plan.  Explain advantages and pitfalls of.
© 2005 by Prentice Hall Chapter 6 Determining System Requirements Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George Joseph.
APPROACH TO SYSTEM DEVELOPMENT. SYSTEMS DEVELOPMENT LIFE CYCLE A project is a planned undertaking that has a beginning and an end and that produces a.
Module 4: Systems Development Chapter 13: Investigation and Analysis.
2Object-Oriented Analysis and Design with the Unified Process Objectives  Describe the activities of the requirements discipline  Describe the difference.
1 Week 8 - Life cycle vs Methodology IT2005 System Analysis & Design.
ANALYSIS PHASE OF BUSINESS SYSTEM DEVELOPMENT METHODOLOGY.
Investigating System Requirements
Fundamentals of Information Systems, Third Edition2 An Overview of Systems Development: Participants in Systems Development Development team –Responsible.
1 Systems Analysis & Design 7 th Edition Chapter 2.
5. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Describe the activities of the requirements discipline  Describe the difference.
1 Requirements Determination (Analysis) Lecture 3 Courtesy to Dr.Subhasish Dasgupta.
CHAPTER 2 SYSTEM PLANNING DFC4013 System Analysis & Design.
4 Chapter 4: Beginning the Analysis: Investigating System Requirements Systems Analysis and Design in a Changing World, 3 rd Edition.
The System Development Life Cycle
Objectives Describe the activities of the requirements discipline
Fundamentals of Information Systems, Sixth Edition
Systems Analysis and Design in a Changing World, 6th Edition
The System Development Life Cycle
Investigating System Requirements
Chapter 7 Determining System Requirements
Systems Analysis – ITEC 3155 Requirements
UNIT No- III- Leverging Information System ( Investing strategy )
Presentation transcript:

Chapter 4: Beginning the Analysis: Investigating System Requirements Systems Analysis and Design in a Changing World

Overview Analysis phase of SDLC skills needed: Fact-finding for investigation of system requirements Analyst should learn details of business processes and daily operations 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 requirements Systems Analysis and Design in a Changing World, 3rd Edition

The Activities of the Analysis Phase Systems Analysis and Design in a Changing World, 3rd Edition

Activities of the Analysis Phase and Their Key Questions Systems Analysis and Design in a Changing World, 3rd Edition

Business Process Reengineering and Analysis Fundamental strategic approach to organizing company Streamlines internal processes to be as efficient and effective as possible Questions basic assumptions for doing business and seeks to find a better way Uses IT as BPR enabler Systems analyst may discover opportunities for process improvement Any project may include components of BPR Systems Analysis and Design in a Changing World, 3rd Edition

System Requirements New system capabilities and constraints Functional requirements are: Activities system must perform Based on procedures and business functions Documented in analysis models Nonfunctional requirements include: Operating environment or performance objectives Usability, reliability, and security requirements Systems Analysis and Design in a Changing World, 3rd Edition

Stakeholders – The Source of System Requirements People with interest in successful system implementation Three primary groups of stakeholders: Users (use system) Clients (pay for and own system) Technical staff (ensure system operation) Every type of stakeholder is identified by analyst Systems Analysis and Design in a Changing World, 3rd Edition

Stakeholders Interested in New System Development Systems Analysis and Design in a Changing World, 3rd Edition

Users as Stakeholders Horizontal user roles - information flow across departments Vertical user roles - information needs of clerical staff, middle management, and senior executives 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

Techniques for Information Gathering Analysis phase done to understand business functions and develop system requirements Original structured approach Create model of existing system Derive requirements from existing system model Current 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

Information Gathering and Model Building Systems Analysis and Design in a Changing World, 3rd Edition

Themes for Information-Gathering Questions Systems Analysis and Design in a Changing World, 3rd Edition

Fact Finding Methods Review existing reports, forms, and procedure descriptions Interview and discussion processes with users Observe and document business processes Build prototypes Distribute and collect questionnaires Conduct joint application design (JAD) sessions Research vendor solutions Systems Analysis and Design in a Changing World, 3rd Edition

Review Existing Reports, Forms, and Procedure Descriptions Source: External industry wide professional organizations and trade publications Source: Existing business documents and procedure descriptions within organization 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

Sample Order Form for RMO Systems Analysis and Design in a Changing World, 3rd Edition

Conduct Interviews and Discussions with Users Effective way to understand business functions and rules Time-consuming and resource-expensive May require multiple sessions to: Meet all users Understand all processing requirements Can meet with individuals or groups of users List of detailed questions prepared Systems Analysis and Design in a Changing World, 3rd Edition

Sample Checklist to Prepare for User Interviews Systems Analysis and Design in a Changing World, 3rd Edition

A Sample Open-items List Systems Analysis and Design in a Changing World, 3rd Edition

Observe and Document Business Processes Varies from office walkthrough to performing actual tasks Not necessary to observe all processes at same level of detail May make users nervous, so use common sense May be documented with workflow (activity) diagrams Systems Analysis and Design in a Changing World, 3rd Edition

Activity Diagram Symbols Systems Analysis and Design in a Changing World, 3rd Edition

Simple Activity Diagram to Demonstrate a Workflow Systems Analysis and Design in a Changing World, 3rd Edition

Activity Diagram Showing Concurrent Paths Systems Analysis and Design in a Changing World, 3rd Edition

Build Prototypes Preliminary working model of a larger, more complex system Discovery, design, evolving prototypes Operative Working model to provide “look and feel” Focused to accomplish single objective Quick Built and modified rapidly with CASE tools Systems Analysis and Design in a Changing World, 3rd Edition

Distribute and Collect Questionnaires Limited and specific information from a large number of stakeholders Preliminary insight into business Not well suited for gathering detailed information Closed-ended questions direct person answering question Open-ended questions encourage discussion and elaboration Systems Analysis and Design in a Changing World, 3rd Edition

Conduct Joint Application Design Sessions Expedite investigation of systems requirements Seeks to compress fact-finding, modeling, policy formation, and verification activities into shorter time frame Critical factor is to have all important stakeholders present Systems Analysis and Design in a Changing World, 3rd Edition

Joint Application Design Participants Session leader trained in group dynamics and JAD group facilitation Knowledgeable business and system users Policy making managers Technical staff representatives to handle: Computer and network configurations Operating environments Security issues Project team members Systems Analysis and Design in a Changing World, 3rd Edition

Joint Application Design Facilities Conducted in special room Limit interruptions May be off-site Resources Overhead projector, white board, flip charts, work material Electronic support (Laptops) CASE Tools Group support systems (GSS) Systems Analysis and Design in a Changing World, 3rd Edition

A JAD Facility Systems Analysis and Design in a Changing World, 3rd Edition

Research Vendor Solutions Many problems have been solved by other companies Positive contributions of vendor solutions Frequently provide new ideas May be state of the art Cheaper and less risky Danger May purchase solution before understanding problem Systems Analysis and Design in a Changing World, 3rd Edition

Useful Techniques in Vendor Research Technical specifications from vendor Demo or trial system References of existing clients On-site visits Printout of screens and reports Systems Analysis and Design in a Changing World, 3rd Edition

Validating the Requirements Make sure gathered information is correct Structured walkthrough Effective means of implementing quality control early in project Verify and validate system requirements Review of findings from investigation and of models based on findings Project manager responsible for system quality System analyst, project manager are partners Systems Analysis and Design in a Changing World, 3rd Edition

Summary Analysis Phase Activities Gather information Define system requirements Prioritize requirements Prototype for feasibility and discovery Generate and evaluate alternatives Review recommendations with management BPR is becoming widespread and can affect analysis phase Systems Analysis and Design in a Changing World, 3rd Edition

Summary (continued) Gathering system requirements Functional and Nonfunctional Work with various stakeholders (users, clients, technical staff) “What kind of information do I need?” What are the business processes and operations? How are the business processes performed? What are the information requirements? Systems Analysis and Design in a Changing World, 3rd Edition

Summary (continued) Primary information gathering techniques 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