Software Requirement Elicitation by Aime - Pankamol Srikaew - What is Requirement Elicitation? - Why? - Importance of Requirement Elicitation - Challenges of Requirement Elicitation - Types of Requirement - 5 Steps to Extract Requirement - Applying with Agile - Requirement Management and Tools This presentation is related to Object Oriented Software Engineering book by David C. Kung

1. Software Requirement
Elicitation
- Aime -

2. Content
● What is Requirement Elicitation?
● Why? - Importance of Requirement
Elicitation
● Challenges of Requirement
Elicitation
● Types of Requirement
● 5 Steps to Extract Requirement
● Applying with Agile
● Requirement Management and Tool

3. WHAT

4. IS

5. “Requirement Elicitation”

6. “Requirement Analysis”

7. Requirements vs Constraints
describe
what we
want to
happen
describe real-
world limits or
boundaries
around what we
want to happen

8. SRSSoftware Requirement Specification

9. Introduction
Overall Description
Specific Requirement
Functional Requirement
Non-Functional Requirement
User Interface
Glossary
Content of SRS

10. WHY

11. Important of Software Requirement Elicitation

12. Different users have differents requirement
37% of software development failure is on requirement
“Many Project fail because of wrongly identified or inadequately stated
requirement”
“The hardest single part of building a software system is deciding precisely
what to build”
Importance of Software Requirement Elicitation

13. Software development in general is a wicked problem
Customer and users do not know what software can do and can not express
their needs
Communication barrier between customer/user and development team
Non-functional requirement are not identified or understated
Requirement Change ...
Challenges of Software Requirement Elicitation

14. TYPEof Requirement

15. MUST, SHALL, WILL

16. Functional
Requirement
Non-Functional
Requirement

17. Functional
Requirement
Non-Functional
Requirement
Performance Requirement
Quality Requirement
Safety Requirement
Security Requirement
Interface Requirement
ETC.

18. Non-Functional Requirement - Performance
“rental service must responses the request
to user within 0.5 milliseconds”

19. Non-Functional Requirement - Quality
“The service must be available to response
99% of time”

20. Non-Functional Requirement - Safety
“The system must save the transaction and
can recover history transaction if it fails”

21. Non-Functional Requirement - Security
“The system must encrypt all data that
transmit over the internet”

22. Non-Functional Requirement - Interface
“Rent button must be red and lighter when
cursor is hovering on it”

23. 5 STEPsfor Software Requirement Elicitation

24. 1. Collecting Information
2. Constructing model
3. Deriving requirement & constraint
4. Conducting
Feasibility
Study
5. Review

25. 1. Collecting Information
2. Constructing model
3. Deriving requirement & constraint
4. Conducting
Feasibility
Study
5. Review
1. Collecting Information

26. Step 1 : Collecting Information
1. What information needs to be collect?
2. What are the available information-collection method and techniques?
3. What are the guideline for information gathering

27. Step 1 : Collecting Information - Cont.
Information-Collection Activity should aim to acquire :
● Information about application
● Business Process
● Application Domain

28. Step 1 : Collecting Information - Cont.
Information-Collection Techniques
● Customer Presentation
● Literature Survey
● Study of Existing Business Procedure and Forms
● Stakeholders Survey
● User Interviewing
● Writing User Stories

29. Step 1 : Collecting Information - Cont.
User Story Form
“As a ______, I want to ________”
User Story Example
“As a manager, I want to assign each part of work to each specific employee”
“As a manager, I want to broadcast weekly schedule too all employee”
“As an employee, I want to contact with manager via personal message”
“As an employee, I want to commute with other employee via Live Chat”

30. 1. Collecting Information
2. Constructing model
3. Deriving requirement & constraint
4. Conducting
Feasibility
Study
5. Review
2. Constructing model

31. Step 2 : Constructing Model
“REAL WORLD
APPLICATION ARE
COMPLEX”

32. Step 2 : Constructing Model
CLASS
DIAGRAM

33. Step 2 : Constructing Model
USE CASE
DIAGRAM

34. Step 2 : Constructing Model
SEQUENCE
DIAGRAM

35. Step 2 : Constructing Model
STATE
DIAGRAM

36. Step 2 : Constructing Model
ACTIVITY
DIAGRAM

37. 1. Collecting Information
2. Constructing model
3. Deriving requirement & constraint
4. Conducting
Feasibility
Study
5. Review
3. Deriving requirement & constraint

38. Step 3 : Deriving Requirements & Constraints
Information have to be analyzed to satisfy the needs.
Identifying Needs from the Wishlists
Identifying Needs to Satisfy Business Goals
Deriving Requirement from Needs
Deriving Requirement from Analysis Model
Numbering Requirements and Constraints
Prioritizing Requirements

39. 1. Collecting Information
2. Constructing model
3. Deriving requirement & constraint
4. Conducting
Feasibility
Study
5. Review
4. Conducting
Feasibility
Study

40. Step 4 : Conducting Feasibility Study
Team Ability Budget Schedule

41. 1. Collecting Information
2. Constructing model
3. Deriving requirement & constraint
4. Conducting
Feasibility
Study
5. Review5. Review

42. Step 5 : Reviewing Requirement Specification
Technical Review Expert Review Customer Review
● Incompleteness
● Inconsistency
● Ambiguity
● Redundancy
● Intractability
● Infeasibility
● Incorrectness
● Inaccurate
● Inappropriate
● Inconsistent
● Policy
● Standard
● Law
● Rules
● Behavior
● Correctness
● Meet the needs
● User Interface
● All Function
● All Non-Function

43. AGILE
Applying with

44. AGILE
WHY?

45. AGILE REDUCE ...
COST TIME

46. BECAUSE ...
Customer Collaboration Change Handling Modeling

47. Requirements
&
MANAGEMENT
TOOLS

49. Q&A