1 ISA&D7‏/8‏/2013. 2 ISA&D7‏/8‏/2013 Information Gathering Prototypes Structured Walkthrough.

Slides:



Advertisements
Similar presentations
Object-Oriented Analysis and Design LECTURE 3: REQUIREMENTS DISCIPLINE.
Advertisements

The System Development Life Cycle
Systems Analysis and Design 9th Edition
Chapter 2.
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.
Lecture 13 Revision IMS Systems Analysis and Design.
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
Systems Development Life Cycle
Jump to first page Chapter 2 System Analysis - Determining System Requirements.
Analyzing the Business Case
Part 2: Requirements Days 7, 9, 11, 13 Chapter 2: How to Gather Requirements: Some Techniques to Use Chapter 3: Finding Out about the Users and the Domain.
Chapter 4: Beginning the Analysis: Investigating System Requirements
Systems Analysis and Design in a Changing World, 6th Edition
MIS 5241 Systems Analysis. MIS 5242 Agenda Why Systems Analysis? Precursors of Analysis The Process of Systems Analysis The Products of Systems Analysis.
1 Lecture 6 The Systems Analyst (Role and activities) Systems Analysis & Design Academic Year 2008/9.
Chapter 4: Beginning the Analysis: Investigating System Requirements
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 7 Determining.
System design technique  System Development Life Cycle  Prototyping  Rapid Application Development.
INFORMATION SYSTEM APPLICATIONS System Development Life Cycle.
RUP Fundamentals - Instructor Notes
Chapter 4 Investigating System Requirements
Systems Development Lifecycle Project Identification & Selection Project Initiation & Planning Analysis Logical Design Physical Design Implementation Maintenance.
Advanced Topics in Requirement Engineering. Requirements Elicitation Elicit means to gather, acquire, extract, and obtain, etc. Requirements elicitation.
CIS 321—IS Analysis & Design Chapter 4: Analysis— Investigating System Requirements.
Investigating System Requirements
Business Case Justification System Planning
1 ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 Systems Development Life Cycle Phases and Activities in the SDLC Variations of the SDLC models.
Conceptual Design versus Logical Design. Conceptual Data Design Prepared at beginning of project High level view of how the client sees the data Top down.
2Object-Oriented Analysis and Design with the Unified Process The Requirements Discipline in More Detail  Focus shifts from defining to realizing objectives.
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.
System Analysis-Gathering Requirements.  System analysis is the process of gathering info about existing system, which may be computerized or not, while.
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.
System Planning (Preliminary Investigation Overview)
Systems Analysis and Design 8 th Edition Chapter 2 Analyzing the Business Case.
Object Oriented Analysis and Design using the UML CIS 520 Advanced Object-Oriented Design.
Requirement Elicitation Process Lesson 3. Requirements Elicitation  Is the process to find out the requirements for an intended software system by communicating.
Objectives Describe the activities of the requirements discipline Describe the difference between functional and nonfunctional system requirements Describe.
Systems Analysis and Design in a Changing World, Thursday, Feb 1.
 2004 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, by Bodnar/Hopwood 10 – 1 Systems Planning and Analysis Chapter 10.
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.
Identifying needs and establishing requirements Data gathering for requirements.
Chapter 6 Determining System Requirements. Objectives:  Describe interviewing options and develop interview plan.  Explain advantages and pitfalls of.
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.
IAEA International Atomic Energy Agency. IAEA Outline LEARNING OBJECTIVES REVIEW TEAM AMD COUNTERPARTS Team Composition Qualification PREPARATORY PHASE.
2Object-Oriented Analysis and Design with the Unified Process Objectives  Describe the activities of the requirements discipline  Describe the difference.
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 Lecture 5 Requirements Investigation and Analysis 1 BTEC HNC Systems Support Castle College 2007/8.
5-1 © Prentice Hall, 2004 Chapter 5: Determining Object-Oriented Systems Requirements Object-Oriented Systems Analysis and Design Joey F. George, Dinesh.
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
Systems Development Life Cycle
Investigating System Requirements
Objectives Describe the activities of the requirements discipline
Systems Planning and Analysis
Fundamentals of Information Systems, Sixth Edition
Systems Analysis and Design
Introduction to Requirements
Systems Analysis and Design in a Changing World, 6th Edition
The System Development Life Cycle
Systems Development Life Cycle
Presentation transcript:

1 ISA&D7‏/8‏/2013

2 ISA&D7‏/8‏/2013 Information Gathering Prototypes Structured Walkthrough

3 ISA&D7‏/8‏/2013 Distribute questionnaires to stakeholders Review existing reports Interview and discuss processes with users Observe and document business processes Build prototypes

4 ISA&D7‏/8‏/2013 We need to obtain information that will enable us to build the logical model of the new IS What Are the Business Processes? How is the Business Processes Performed? What Information is required?

5 ISA&D7‏/8‏/2013

6 ISA&D7‏/8‏/2013 Serves two purposes: Provides a preliminary understanding of processes involved in a company Can be useful in conjunction with interviews Can be used to develop interview questions

7 ISA&D7‏/8‏/2013

8 ISA&D7‏/8‏/2013 Team members meet with individuals or groups of users One of the most effective ways to understand business functions and rules Can be time consuming and resource expensive To be effective you should be organized in three areas: (1) preparing for the interview (2) conducting the interview (3) following up the interview

9 ISA&D7‏/8‏/2013

10 ISA&D7‏/8‏/2013

11 ISA&D7‏/8‏/2013 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

12 ISA&D7‏/8‏/2013 Prototype is an initial working model of a larger, more complex system Used for many purposes: To test feasibility To help identify processing requirements To compare different design and interface alternatives

13 ISA&D7‏/8‏/2013 Characteristics of Prototypes: Operative: a prototype should be a working model, with some real functionality Focused: a prototype should be focused on a single objective Quick: the prototype should be built and modified quickly

14 ISA&D7‏/8‏/2013

15 ISA&D7‏/8‏/2013 Thank you ??????