10
Ambiguity and Specificity Ambiguity and Specificity Sriram Mohan/ Steve Chenoweth Chapters 23, 24 - Requirements Text 1

Ambiguity and Specificity Sriram Mohan/ Steve Chenoweth Chapters 23, 24 - Requirements Text 1

Embed Size (px)

Citation preview

Page 1: Ambiguity and Specificity Sriram Mohan/ Steve Chenoweth Chapters 23, 24 - Requirements Text 1

Ambiguity and SpecificityAmbiguity and Specificity

Sriram Mohan/ Steve ChenowethChapters 23, 24 - Requirements Text

1

Page 2: Ambiguity and Specificity Sriram Mohan/ Steve Chenoweth Chapters 23, 24 - Requirements Text 1

ProblemProblem

Specification must be easy to understand and must be clear.◦ Balancing the two might be difficult

◦ Must be easy enough for the client to understand

◦ Must be unambiguous for the developers

2

Page 3: Ambiguity and Specificity Sriram Mohan/ Steve Chenoweth Chapters 23, 24 - Requirements Text 1

Light Box ExerciseLight Box Exercise

After On pushed but before Off pushed system is termed “power on”.

After Off pushed but before On pushed system is termed “power off”.

Since most recent On press if count has been pressed an Odd/Even number of times, Odd/Even shall be lit.

If either light burns out, the other shall flash every 1 second.

3

Count

On Off

Even Odd

Power

Page 4: Ambiguity and Specificity Sriram Mohan/ Steve Chenoweth Chapters 23, 24 - Requirements Text 1

4

Off

On

Off

On

Duty Cycle B

Duty Cycle A

0 1 2 3 4 5 6

Page 5: Ambiguity and Specificity Sriram Mohan/ Steve Chenoweth Chapters 23, 24 - Requirements Text 1

Techniques for DisambiguationTechniques for Disambiguation

How do we detect it?◦ Memorization technique

◦ Emphasis technique or Keyword Technique How do we avoid it?

◦ Use natural language if possible

◦ Use pictures and diagrams to illustrate intent

◦ Communicate – When in doubt ask?

◦ Augment with technical specs

5

Page 6: Ambiguity and Specificity Sriram Mohan/ Steve Chenoweth Chapters 23, 24 - Requirements Text 1

Technical Methods for Specifying RequirementsTechnical Methods for Specifying Requirements

Finite State Machines

6

Page 7: Ambiguity and Specificity Sriram Mohan/ Steve Chenoweth Chapters 23, 24 - Requirements Text 1

Technical Methods for Specifying RequirementsTechnical Methods for Specifying Requirements

Decision Tables and Decision Trees

7

Page 8: Ambiguity and Specificity Sriram Mohan/ Steve Chenoweth Chapters 23, 24 - Requirements Text 1

Technical Methods for Specifying RequirementsTechnical Methods for Specifying Requirements

Entity Relationship Diagrams◦ You will get extra credit for Milestone 3 if you develop an ER

diagram.

8

Page 9: Ambiguity and Specificity Sriram Mohan/ Steve Chenoweth Chapters 23, 24 - Requirements Text 1

Technical Methods for Specifying RequirementsTechnical Methods for Specifying Requirements

Pseudo code◦ What is it?

◦ We will use it for our design phase in 371. For each function(s) that results from an use case, you

must provide the following information◦ Name

◦ Arguments

◦ Return Type

◦ Pseudo code You must also develop an architecture diagram.

9

Page 10: Ambiguity and Specificity Sriram Mohan/ Steve Chenoweth Chapters 23, 24 - Requirements Text 1

System Architecture DiagramSystem Architecture Diagram

10

Bloomington Ford Database

Ford Main Module

Authentication Module

DB Connector Module

Exception

Handler Module

Utilities Generator Module

Blue Log Module

White Log Module

Find Module

Reports Module

Maintenance Module

Help Module