TOPIC 6:

NATURAL LANGUAGE REQUIREMENTS

(Part 2)
 Recap on RE process

Documentation Validation &

Negotiation

Elicitation Management

RE core
activities
What we have learned?
PART II : NATURAL LANGUAGE REQUIREMENTS

TECHNIQUES TO AVOID AMBIGUITY

TECHNIQUE 1: GLOSSARY
Possible structure of Glossary Entry and
its Example
What is the benefit of Glossary?
TECHNIQUE 2: REQUIREMENTS TEMPLATE /
SYNTACTIC REQUIREMENTS PATTERN
Verb (Legal) Obligation Explanation
shall Duty / Requirement Legally binding
should Wish Strongly advised
will Intention Prospective / future
requirement
may Recommendation/wish Desirable but not necessary
Process Verb Noun
Register Registration
Transmit Transmission
Book Booking
 Requirements Template
Charaterize the System Activities

1. Autonomous / independent
– System starts and executes function autonomously
– Without user interaction
– Often processes such as report generation, archival or backup of data, notification of users or
external systems.
2. User Interaction
– System provides function as a service to the user of interact directly with the user.
3. Interface Requirement
– System executes a process depending on another system.
– System is passive and waits for external event.
– Typically receiving data / getting notified.
 Example Library System

The Library System shall

The Library System shall provide with the ability to

The Library System shall be able to

 Forum 3: Derive requirement

Print vehicle
reservation list

Reservation
clerk

Based on above use case diagram, derive requirement

that follows:
a) Type 1 for its internal process
b) Type 2
c) Type 3 if the use case has to interface with
Transportation system
 Forum 3: Derive requirement with
STEP 4 and STEP5

Based on above use case diagram, derive requirement

that follows:
a) Type 3 if the use case has to interface with
Transportation system and only allow during office
hour.
 LO

Process
verb
Template

Actvt

Objects

Legal/Temporal