Requirements Determination

Slides:



Advertisements
Similar presentations
Chapter 3: Requirements Determination
Advertisements

The System Development Life Cycle
Systems Analysis Chapter 4.
Chapter 7 CASE Tools and Joint and Rapid Application Development.
© Copyright 2011 John Wiley & Sons, Inc.
DEVELOPING ENTERPRISE APPLICATIONS
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
© Prentice Hall CHAPTER 9 Application Development by Information Systems Professionals.
Fundamentals of Information Systems, Second Edition
Systems Analysis Requirements determination Requirements structuring
Karolina Muszyńska Based on
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Database System Development Lifecycle Transparencies
Slide 1 IS6112 – Application Modelling and Design.
Introduction to Systems Analysis and Design Trisha Cummings.
Foundation Degree IT Project Methodologies (for reference)
INFORMATION SYSTEM APPLICATIONS System Development Life Cycle.
Pertemuan 5 Pengembangan Teknologi Informasi Matakuliah: H0402/PENGELOLAAN SISTEM KOMPUTER Tahun: 2005 Versi: 1/0.
Managing the development and purchase of information systems (Part 1)
Transaction Processing Systems and System Development Life Cycle
Systems Investigation and Analysis
Part3 Database Analysis and Design Techniques Chapter 04- Overview of Database Planning, Design and Administration Database Systems Lu Wei College of Software.
CIS 321—IS Analysis & Design Chapter 4: Analysis— Investigating System Requirements.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Chapter 14 Information System Development
System Analysis and Design Dr. Taysir Hassan Abdel Hamid Lecture 5: Analysis Chapter 3: Requirements Determination November 10, 2013.
2Object-Oriented Analysis and Design with the Unified Process The Requirements Discipline in More Detail  Focus shifts from defining to realizing objectives.
PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.
CIS 499 Senior Seminar Introduction to IT project management.
Systems Life Cycle. Know why it is necessary to evaluate a new system Understand the need to evaluate in terms of ease-of- use, appropriateness and efficiency.
Slide 1 Requirements Determination Chapter 5. Slide 2 Objectives ■ Understand how to create a requirements definition. ■ Become familiar with requirements.
Software Development Life Cycle by A.Surasit Samaisut Copyrights : All Rights Reserved.
Topics Covered Phase 1: Preliminary investigation Phase 1: Preliminary investigation Phase 2: Feasibility Study Phase 2: Feasibility Study Phase 3: System.
IS Analysis and Design. SDLC Systems Development Life Cycle Break problems into management review stages Control cost and time Works best with well understood.
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.
12/10/15.  It is a Cross Life Cycle Activity (CLCA) that may be performed at any stage ◦ In fact, some part of it (e.g. risk analysis and management)
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 7 Determining.
2 nd Knowledge Area : Project Scope Management. Importance of Good Project Scope Management 1995 CHAOS study cited user involvement, a clear project mission,
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights.
Systems Development Life Cycle
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
Chapter 4: Requirements Determination 11 Januari 2016.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
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.
MANAGEMENT INFORMATION SYSTEM
The System Development Life Cycle
Systems Development Life Cycle
Requirements Determination
Systems Analysis and Design 3rd Edition
Information Systems Development
TIM 58 Chapter 3, continued: Requirements Determination Ch
Requirements Determination
CASE Tools and Joint and Rapid Application Development
Fundamentals of Information Systems, Sixth Edition
Chapter 5 Determining System Requirements
TIM 58 Chapter 3: Requirements Determination
Systems Analysis and Design
The System Development Life Cycle
Investigating System Requirements
Chapter 5 Determining System Requirements
Essentials of Systems Analysis and Design Fourth Edition
Foundation Degree IT Project
MANAGING THE DEVELOPMENT AND PURCHASE OF INFORMATION SYSTEMS
Chapter 4 Determining System Requirements
Systems Development Life Cycle
Applied Software Project Management
UNIT No- III- Leverging Information System ( Investing strategy )
Presentation transcript:

Requirements Determination

Introduction The systems development process transforms the existing (as is) system into the proposed (to be) system Requirements determination The single most critical step of the entire SDLC Changes can be made easily in this stage Most (>50%) system failures are due to problems with requirements The iterative process of OOSAD is effective because: Small batches of requirements can be identified and implemented incrementally The system will evolve over time

Requirements Determination Purpose: to convert high level business requirements (from the system request) into detailed requirements that can be used as inputs for creating models What is a requirement? A statement of what the system must do or a characteristic it must have Will later evolve into a technical description of how the system will be implemented Types: Functional: relates to a process or data Non-functional: relates to performance or usability

Requirements Definition Functional & non-functional requirements listed in outline format May be prioritized Provides information needed in subsequent workflows Defines the scope of the system

Sample of Requirements Definition

Determining Requirements Business & IT personnel need to collaborate Strategies for problem analysis: Root cause analysis Duration analysis Activity-based costing Informal benchmarking Outcome analysis Technology analysis Activity elimination

Determining Requirements Requirements are best determined by systems analysts and business people together Techniques for identifying requirements Interviews, questionnaires and/or observation Joint application development (JAD) Document analysis

Creating a Requirements Definition Determine the types of functional and non-functional requirements applicable to the project Use requirements-gathering techniques to collect details Analysts work with users to verify, change and prioritize each requirement Continue this process through analysis workflow, but be careful of scope creep Requirements that meet a need but are not within the current scope can be added to a list of future enhancements

Problems in Requirements Determination Analyst may not have access to the correct users Requirements specifications may be inadequate Some requirements may not be known in the beginning Verifying and validating requirements can be difficult

Requirements Analysis Strategies Problem analysis Ask users to identify problems with the current system Ask users how they would solve these problems Good for improving efficiency or ease-of-use Root cause analysis Focus is on the cause of a problem, not its solution Create a prioritized list of problems Try to determine their causes Once the causes are known, solutions can be developed

Requirements Analysis Strategies(Cont.) Duration analysis Determine the time required to complete each step in a business process Compare this to the total time required for the entire process Large differences suggest problems that might be solved by: Integrating some steps together Performing some steps simultaneously (in parallel) Activity-based costing Same as duration analysis but applied to costs Informal benchmarking Analyzes similar processes in other successful organizations

Requirements Analysis Strategies(Cont.) Outcome analysis What does the customer want in the end? Technology analysis Apply new technologies to business processes & identify benefits Activity elimination Eliminate each activity in a business process in a “force-fit” exercise

The System Proposal Combines all material created in planning & analysis Included sections: Executive summary Provides all critical information is summary form Helps busy executives determine which sections they need to read in more detail The system request The workplan The feasibility analysis The requirements definition Current models of the system (expected to evolve)