GATHERING REQUIREMENTS

1
GATHERING REQUIREMENTS

• PRESENTATION BY
• JEMAL KHELIL
• PRESENTED AT
• CFICSE-RMC

2
Gathering Requirements

• The Process Of Gathering Requirements
• The Difficulties Of Gathering Requirements

3
How Do I Get The Users NeedIdentified?

• Putting Together A Requirement Modeling Team
• Good Subject Matter Experts
• Good Facilitators
• Good Scribes

4

• Choosing Good Subject Matter Experts
• Know The Business
• Think Logically
• Communicate Well
• Includes The User Community

5

• Choosing Good Facilitators
• Have Good Meeting Skills
• Understand The Requirement Modeling Process
• Ask Valid, Intelligent Questions

6

• Choosing Good Scribes
• Listen Well
• Have Good Written Communication Skills
• Have Good Oral Communication Skills

7

• The Requirement Modeling Team Will
• Conduct Interview
• Cary out Requirement Discovering Session
• Collect, Document And Manage Requirement

8

• The Requirement Modeling Team Should
• Organize Complex Information Into Understandable
  Subject Area
• Translate Technical Language Into Business
  Language And Vice Versa

9
How Can I be Sure Ive Got It All,And Got It
Right?

• Use Validation Checklist
• Is It Accurate
• Is It Complete
• Is IT Clear

10
Difficulties

• Hidden Assumptions
• Domain Knowledge of The Developer
• Incorrect Assumptions Made By Customer
• Vagueness

11

• Imprecision
• The customer or Developer Do Not Choose Their
  Words Carefully
• Example
• This Field Should Not Be There(in the report)

12

• Domain Jargon - Miscommunication
• Customer - Overloaded Terms
• EX. authorize, approve, Concur
• Developer - Too Much Computer Jargon
• EX. Is this Client/Server application

13
What To Avoid

• Avoid The Following Requirements Traps
• Confusion What A Requirement Is
• Inadequate Customer Involvement
• Vague And Ambiguous Requirements
• Building Functionality No One Uses
• Unprioritized Requirement
• Inadequate Change Process

14
Summary

• Rapid Convergence
• Requirement Specialty
• Modern Techniques