PRPL w07s01 Requirement Analysis

Requirement AnalysisDian Ira Putri Hutasoit

Institut Teknologi DelSitoluama, Laguboti,Sumatera Utara

2

IF YOU REMEMBER ...

● Requirement is a statement of what the system must do or a characteristic it must have

● Requirement types: – Functional requirement– Non-functional requirement

3

INTRODUCTION

● The systems development process transforms the existing (as is) system into the proposed (to be) system

● Requirements determination:– convert high level business requirements (from the system request) into detailed requirements– 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

4

INTRODUCTION

Requirements determination (con't):– The iterative process of object-oriented IS analysis and design is effective because:

❏ Small batches of requirements can be identified and implemented incrementally

❏The system will evolve over time

5

REQUIREMENT DEFINITION

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

6

REQUIREMENT DEFINITION

7

DETERMINING REQUIREMENTS

● Business & IT personnel need to collaborate● The basic process of analysis is divided into:

1. Understanding the as-is system2. Identifying improvements3. Developing requirements for the to-be system

8

DETERMINING REQUIREMENTS

● Strategies for requirement analysis:– Root cause analysis– Duration analysis– Activity-based costing– Informal benchmarking– Outcome analysis– Technology analysis– Activity elimination

9

DETERMINING REQUIREMENTS– Root cause analysis with Fishbone Diagram

Illustration: Smartbear 10

DETERMINING REQUIREMENTS– Fishbone Diagram Example

Illustration: Targer.golden-dragon.co 11

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

12

REQUIREMENTS GATHERING● Process is used to:

– Uncover all requirements (those uncovered late in the process are more difficult to incorporate)– Build support and trust among users

● Which technique(s) to use?– Interviews– Joint Application Development (JAD)– Questionnaires

● – Document analysis– Observation

13

SYSTEM PROPOSAL● Combines all material created in planning & analysis ● Included sections:

– Executive summary • ■ Provides all critical information in summary form ■ Helps busy executives determine which sections they

need to read in more detail

14

SYSTEM PROPOSAL

● Included sections (con't): – The system request – The work plan – The feasibility analysis – The requirements definition – Current models of the system (expected to evolve)

15

SYSTEM PROPOSAL

16

CREDITS: This presentation template was created by Slidesgo, including icons by Flaticon, infographics & images by Freepik

THANKSPlease keep this slide for attribution

17