5 ONTOLOGICAL INFLUENCE ON REQUIREMENT ENGINEERING The first step in requirement engineering

1400 Words6 Pages
5 ONTOLOGICAL INFLUENCE ON REQUIREMENT ENGINEERING
The first step in requirement engineering process is requirements elicitation. Requirements should be gathered first then it can be analyzed, modeled and documented. In the requirement elicitation process, requirements are gathered through interviews, questionnaires, workshops, user observations, prototyping, brainstorming, use cases etc. Requirement elicitation practice can be used to the fullest extent when we follow some guidelines; some of those guidelines are,
• People who can help in specifying the requirements and understanding the organizational prejudice must be identified.
• Define the computer architecture or operating system into which the system will be placed.
• Requirement
…show more content…
5.2.1 Problems:
There are two types of issues in Requirements Analysis.
Stakeholder issues:
• No proper understanding of needs
• No commitment of previous requirements
• Poor communication
• Users are technically unsophisticated
Engineer/developer issues:
• Analysts and end users may have different vocabularies

5.2.2 Ontologies help tackle these challenges:
One of the important goals of Requirement Analysis is to develop a high quality requirement specification document.
Ontologies help in developing high quality requirement specification document.
In order to have the possibility of automating semantic analysis we can map requirement specification and ontological elements.
Nowadays, ontology techniques are applied in many application domains because relationships, concepts and their categorizations can be represented by ontologies in real word.

5.3 Requirement Documentation:
Requirement documentation describes what particular software does or what it shall do. This document will be used throughout development phase to communicate what the software does or what it shall do.
Requirement documentation is also used as an agreement or as a foundation of an agreement on what the software shall do.
5.3.1Problems:
The proven challenge of requirement documentation is variation and complexity .
Requirements may be insinuate and hard to uncover.
It is difficult to understand how much and what kind
Get Access