Systems Analysis and Design in a Changing World, Fifth Edition

Slides:



Advertisements
Similar presentations
Systems Investigation and Analysis
Advertisements

© 2005 Prentice Hall13-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
Object-Oriented Analysis and Design LECTURE 3: REQUIREMENTS DISCIPLINE.
The System Development Life Cycle
Systems Analysis and Design 9th Edition
Today’s Outline Review exam one performance and overall grade
CAP 252 Lecture Topic: Requirement Analysis Class Exercise: Use Cases.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
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 and Design in a Changing World, Fourth Edition
Systems Development Life Cycle
Jump to first page Chapter 2 System Analysis - Determining System Requirements.
Chapter 4: Beginning the Analysis: Investigating System Requirements
Systems Analysis and Design in a Changing World, 6th Edition
Introduction to Systems Analysis and Design
Requirements Modeling
Introduction to Computer Technology
Chapter 4: Beginning the Analysis: Investigating System Requirements
Systems Analysis and Design: The Big Picture
INFORMATION SYSTEM APPLICATIONS System Development Life Cycle.
Chapter 4 Investigating System Requirements
Systems Analysis and Design in a Changing World, 6th Edition
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design.
Module 4: Systems Development Chapter 13: Investigation and Analysis.
CIS 321—IS Analysis & Design Chapter 4: Analysis— Investigating System Requirements.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Investigating System Requirements
Chapter 14 Information System Development
2Object-Oriented Analysis and Design with the Unified Process The Requirements Discipline in More Detail  Focus shifts from defining to realizing objectives.
5 Systems Analysis and Design in a Changing World, Fourth Edition.
1 4 Systems Analysis and Design in a Changing World, 2 nd Edition, Satzinger, Jackson, & Burd Chapter 4 Beginning the Analysis: Investigating System Requirements.
Copyright 2002 Prentice-Hall, Inc. 1.1 Modern Systems Analysis and Design Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 1 The Systems Development.
 Describe the activities of the requirements discipline  Describe the difference between functional and nonfunctional system requirements  Describe.
Lecture 7: Requirements Engineering
1 ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 The Analysis Phase System Requirements Models and Modelling of requirements Stakeholders as a source of requirements.
IS2210: Systems Analysis and Systems Design and Change Twitter:
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.
Systems Analysis and Design in a Changing World, Fourth Edition
IAD 2263: System Analysis and Design Chapter 3: Investigating System Requirements.
© 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.
2Object-Oriented Analysis and Design with the Unified Process Objectives  Describe the activities of the requirements discipline  Describe the difference.
ANALYSIS PHASE OF BUSINESS SYSTEM DEVELOPMENT METHODOLOGY.
Main tasks of system analysis ? 1-study exit=sting information system 2-identify problem 3-spelify system requirement 4-asalysis decision ========= How.
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.
Systems Analysis and Design in a Changing World, 6th Edition 1 Chapter 2 CHAPTER 2 SATZINGER | JACKSON | BURD INTRODUCTION TO SYSTEMS ANALYSIS AND DESIGN:
Systems Analysis Lecture 5 Requirements Investigation and Analysis 1 BTEC HNC Systems Support Castle College 2007/8.
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
Systems Development Life Cycle
Investigating System Requirements
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
Systems Analysis – ITEC 3155 Requirements
Systems Development Life Cycle
UNIT No- III- Leverging Information System ( Investing strategy )
Presentation transcript:

Systems Analysis and Design in a Changing World, Fifth Edition

Learning Objectives Describe the activities of systems analysis Explain the difference between functional and nonfunctional system requirements Describe three types of models and reasons for creating models Identify and understand the different types of users who will be involved in investigating system requirements Systems Analysis and Design in a Changing World, 5th Edition

Learning Objectives (continued)‏ Describe the kind of information that is required to develop system requirements Determine system requirements through review of documentation, interviews, observation, prototypes, questionnaires, joint application design sessions, and vendor research Discuss the need for validation of system requirements to ensure accuracy and completeness and the use of a structured walkthrough Systems Analysis and Design in a Changing World, 5th Edition

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, 5th Edition

The Analysis Phase in More Detail Gather information Define system requirements Functional and nonfunctional Prioritize requirements Prototype for feasibility and discovery Generate and evaluate alternatives Review recommendations with management Systems Analysis and Design in a Changing World, 5th Edition

The Activities of the Analysis Phase ‏ Figure 4-3 Systems Analysis and Design in a Changing World, 5th Edition

Activities of the Analysis Phase and Their Key Questions‏ Figure 4-2 Systems Analysis and Design in a Changing World, 5th Edition

System Requirements System requirements – specifications that define the new system Functional requirements Activities system must perform (use cases)‏ Based on procedures and business functions Documented in analysis models Systems Analysis and Design in a Changing World, 5th Edition

System Requirements (cont)‏ Nonfunctional requirements Technical requirement – hardware and software Performance requirement – workload measures Usability requirement – user interface, workflow Reliability requirement – outages, error detection Security requirement – access & protection Systems Analysis and Design in a Changing World, 5th Edition

Models and Modeling Analyst describes information system requirements using a collection of models Complex systems require more than one type of model Models represent some aspect of the system being built Process of creating models helps analyst clarify and refine design Models assist communication with system users Systems Analysis and Design in a Changing World, 5th Edition

Reasons for Modeling Figure 4-3 Systems Analysis and Design in a Changing World, 5th Edition

Types of Models Different types of models are used in information systems development Mathematical – formulas that describe technical aspects of the system Descriptive – narrative memos, reports, or lists that describe aspects of the system Graphical – diagrams and schematic representations of some aspect of the system Systems Analysis and Design in a Changing World, 5th Edition

Some Descriptive Models Figure 4-4 Systems Analysis and Design in a Changing World, 5th Edition

Overview of Models Used in Analysis and Design Analysis activities named “define system requirements” Logical models Provide detail without regard to specific technology Design models Physical models Provide technical details Extend logical models Systems Analysis and Design in a Changing World, 5th Edition

Models Created During Analysis Figure 4-5 Systems Analysis and Design in a Changing World, 5th 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, 5th Edition

Stakeholders Interested in New System Development Figure 4-6 Systems Analysis and Design in a Changing World, 5th Edition

More On 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, 5th Edition

RMO Stakeholders Figure 4-7 Systems Analysis and Design in a Changing World, 5th 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, 5th Edition

Relationship Between Information Gathering and Model Building‏ Figure 4-8 Systems Analysis and Design in a Changing World, 5th Edition

Themes for Information-Gathering Questions Figure 4-9 Systems Analysis and Design in a Changing World, 5th Edition

Fact-Finding Methods Review existing reports, forms, and procedure descriptions Interview and discuss 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, 5th 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, 5th Edition

Sample Order Form for RMO‏ Figure 4-10 Systems Analysis and Design in a Changing World, 5th 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, 5th Edition

Sample Checklist to Prepare for User Interviews Figure 4-11 Systems Analysis and Design in a Changing World, 5th Edition

Sample Agenda for Interview Figure 4-12 Systems Analysis and Design in a Changing World, 5th Edition

A Sample Open-Items List Figure 4-13 Systems Analysis and Design in a Changing World, 5th Edition

Observe and Document Business Processes Varies from office walkthroughs to performing actual tasks Not necessary to observe all processes at same level of detail May make users nervous, so use common sense Can document workflows with UML activity diagrams Systems Analysis and Design in a Changing World, 5th Edition

Activity Diagrams Workflow – sequence of steps to process a business transaction Activity Diagram – workflow diagram to describe sequence of steps Synchronization bar – symbol to control splitting or merging of a path on an activity diagram Swimlane – bounded area that contains activities of a single agent Systems Analysis and Design in a Changing World, 5th Edition

Activity Diagram Symbols Figure 4-14 Systems Analysis and Design in a Changing World, 5th Edition

Activity Diagram that Models a Workflow Figure 4-15 Systems Analysis and Design in a Changing World, 5th Edition

Activity Diagram with Concurrent Paths Figure 4-16 Systems Analysis and Design in a Changing World, 5th Edition

Build Prototypes Prototype - Preliminary working model of a larger, more complex system component Discovery, design, evolving prototypes Prototype should be 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, 5th 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, 5th Edition

Sample RMO Questionnaire Figure 4-17 Systems Analysis and Design in a Changing World, 5th Edition

Conduct Joint Application Design Sessions Expedites investigation of system 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, 5th Edition

Joint Application Design Participants Session leader trained in group dynamics and JAD group facilitation Knowledgeable business and system users and policy makers Technical staff representatives to handle Computer and network configurations Operating environments Security issues Project team members Systems Analysis and Design in a Changing World, 5th 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, 5th Edition

A JAD Facility Figure 4-18 Systems Analysis and Design in a Changing World, 5th 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, 5th 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, 5th 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 Systems analyst, project manager are partners Systems Analysis and Design in a Changing World, 5th Edition

Structured Walkthrough Form Figure 4-19 Systems Analysis and Design in a Changing World, 5th 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 and Zachman Framework can help with the analysis phase activities Systems Analysis and Design in a Changing World, 5th 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, 5th 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, 5th Edition