Presentation is loading. Please wait.

Presentation is loading. Please wait.

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

Similar presentations


Presentation on theme: "Using Domain Ontology as Domain Knowledge for Requirements Elicitation Haruhiko Kaiya & Motoshi Saeki A model description by Roel Esten."— Presentation transcript:

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

2 Content Topic Related Literature Product Deliverable Diagram Example

3 Topic - Name Using Domain Ontology as Domain Knowledge for Requirements Elicitation Cited 88 times since 2006

4 Topic - Authors Haruhiko Kaiya Associate professor @ Shinsu University ±100 publications Motoshi Saeki Professor @ Saeki Lab Edited a book with Sjaak ±200 publications

5 Topic - Origins based on the academic fields of: Requirements Engineering & Domain Ontologies

6 Topic - Purpose Creating a method that complements requirements documents in specific domains Without using a domain expert!

7 Topic – Main phases

8 Related Literature Two categories: 1. Development of domain ontologies & 2. Application of ontological techniques to requirements engineering

9 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)

10 Related Literature Domain model to express the meaning of requirements (Greenspan, Mylopoulos, & Borgida, 1994) Refine quality of requirements through Thesaurus (Kato et al., 2003)

11 Product Deliverable Diagram

12

13 Example A felon registration system

14 Example Step 1: Create or find a DO for a registration system specific to felons (DAML ontology library)

15 Example Step 2: Gather initial requirements e.g. Every felon needs a unique identifier Every felon needs to have a foto Etc…

16 Example Step 3: Map the requirements you created onto a DO

17 Example Step 4: Calculate the 4 quality measures Is it complete? Is it correct? Is it consistent? Is it ambiguous?

18 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 components State & number New Req: Every felon needs a state name Every felon needs a number

19 Example Step 6: Go back to step 2

20 Questions?


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

Similar presentations


Ads by Google