Using Domain Ontology as Domain Knowledge for Requirements Elicitation Haruhiko Kaiya & Motoshi Saeki A model description by Roel Esten.

Using Domain Ontology as Domain Knowledge for Requirements Elicitation

Haruhiko Kaiya & Motoshi Saeki

A model description by Roel Esten

Content

Topic

Related Literature

Product Deliverable Diagram

Example

Topic - Name

Using Domain Ontology as Domain Knowledge for Requirements Elicitation

Cited 88 times since 2006

Topic - Authors

Haruhiko Kaiya

Associate professor @ Shinsu University±100 publications

Motoshi Saeki

Professor @ Saeki LabEdited a book with Sjaak

±200 publications

Topic - Origins

based on the academic fields of:

Requirements Engineering&

Domain Ontologies

Topic - Purpose

Creating a method that complements requirements documents in specific domains

Without using a domain expert!

Topic – Main phases

1. obtain requirements

3. Evaluate the quality of the requirements

4. Update the list of requirements according to

evaluation steps

2. Map requirements onto domain ontology

4a. Completeness4d. Consistency

4b. Unambiguous4c. Correctness

Related Literature

Two categories:

1. Development of domain ontologies&

2. Application of ontological techniques to requirements engineering

Related Literature

ORE framework Method to conceptualize DO’s(Gomez-Perez, Fernandez, & de Vicente, 1996)

Several less scientific tools to create DO’s(Volz, et al., 1970 & Miller, 1980)

Related Literature

Domain model to express the meaning of requirements

(Greenspan, Mylopoulos, & Borgida, 1994)

Refine quality of requirements through Thesaurus

(Kato et al., 2003)

Product Deliverable Diagram

Create Domain Ontology

Gather Requirements

Map requirements onto DO

Evaluate requirements

Calculate completeness

Calculate correctness

Calculate concistency

Calculate unambiguity

Update requirements

Update ‘apply’ and ‘perform’ connections

Update ‘is-a’ ‘has-a’ and ‘require’ connections

Remove ambiguation

Remove incorrect mappings

Remove contradictions

[requirements quality sufficient]

[else]

REQUIREMENTS DOCUMENT

CompletenessCorrectnessConcistencyUnambiguityQuality

DOMAIN ONTOLOGY

11..*

Stakeholder

REQUIREMENT

DOMAIN-REQUIREMENT

MAPPING

1..*

1

Calculate requirements quality

1

Example

A felon registration system

Example

Step 1: Create or find a DO for a registration system

specific to felons(DAML ontology library)

Example

Step 2: Gather initial requirements

e.g. Every felon needs a unique identifier

Every felon needs to have a fotoEtc…

Example

Step 3: Map the requirements you created onto a DO

Example

Step 4: Calculate the 4 quality measures

Is it complete?Is it correct?

Is it consistent?Is it ambiguous?

Example

Step 5:When the measures are not sufficiently high

Update the list of requirements

DO says that each unique identifier is composed of two componentsState & number

New Req: Every felon needs a state name Every felon needs a number

Example

Step 6:Go back to step 2

Questions?