**4.1. KMoS-RE© analysis**

According to Maalej and Thurimella [24], managing requirements knowledge is about efficiently identifying, accessing, externalizing and sharing domain and technical knowledge by and to all involved in the project, including analysts, developers, and domain specialists, which is closely related to a full perspective of KM. The rationality of the KMoS-RE© strategy is based on the fundamental issues described as follows:


### **4.2. KMoS-RE© applied to real ISD cases**

The KMoS-RE© strategy has been applied in the development of solution of several real ISD cases:


### **4.3. Discussion**

**4.1. KMoS-RE© analysis**

98 Knowledge Management Strategies and Applications

of belief and the PoK matrix.

**4.2. KMoS-RE© applied to real ISD cases**

is based on the fundamental issues described as follows:

identifying knowledge that could be tacit, and hence hidden.

solution-solvers and domain specialists through socialization.

According to Maalej and Thurimella [24], managing requirements knowledge is about efficiently identifying, accessing, externalizing and sharing domain and technical knowledge by and to all involved in the project, including analysts, developers, and domain specialists, which is closely related to a full perspective of KM. The rationality of the KMoS-RE© strategy

• The flow of activities in the KMoS-RE© strategy is based on the knowledge evolution model KEM-RE, which is based on the knowledge evolution spiral proposed by Nonaka. The evolution spiral knowledge has the aim of facilitating the conversion of tacit knowledge to explicit. In addition, the incorporation of techniques such as the identification of presuppositions and the classification of verbs according the Bloom's taxonomy make easier-

• Representing requirements knowledge targets an efficient information access and artefact reuse within and between projects. The KMoS-RE© strategy proposes several artefacts in order to represent different views of the system. They can be accessed and shared by all involved in the project. Although several requirements elicitation proposals use lexical, conceptual models, use cases models and scenarios, few of them combine those techniques in a strategy. Besides, the KMoS-RE© strategy proposes two innovative artefacts: the record

• Sharing requirements knowledge improves the collaboration among all involved in the project and ensures that their experiences do not get lost. The knowledge spiral in which the activities of the KMoS-RE© strategy are based compels to sharing the knowledge among

• Reasoning about requirements and their interdependencies aims at detecting inconsistencies and deriving new knowledge. Externalizing the knowledge through the development of the different artefacts let the solution-solver reason and internalized the domain knowledge.

The KMoS-RE© strategy has been applied in the development of solution of several real ISD cases: • **Software development for complex domains**. This is a complex and creative activity in which software developers should understand, as soon as possible, the knowledge of a domain in which generally are neophytes. Then, combine this knowledge with their own technical knowledge in order to reach a solution that meets clients' expectations. The KMoS-RE© strategy has been used to develop a cognitive rehabilitation system for sclerosis multiple patients [6]. • **Soft computing**. This artificial intelligence (AI) subarea includes several techniques that are suitable for solutions in ISD, since it is tolerant of imprecision, uncertainty, partial truth and approximation. A complex problem in soft computing is how to elicit the knowledge of specialists in order to incorporate it in an appropriate representation and to reach correct solutions. A case-based reasoning system to support heating ventilation and air condition-

ing (HVAC) design decisions was developed using the KMoS-RE© strategy [8].

Nowadays, the negative effects of inappropriate, incorrect and ambiguous requirements have been widely studied and are well known. Despite the vast quantity of proposals, methods, techniques and tools, requirements elicitation is still an open problem, as shown by many projects that do not fulfil clients' expectations or that exceed the development time due to bad elicited requirements. Thus, there are still clear opportunities to improve.

The application of the KMoS-RE© strategy in real ISD cases has showed that its characteristics are clear contributions to the requirements elicitation area, as it is described as follows:


adaptation that is based on goals elicitation approach [26], the knowledge audit model [25] and the social network analysis [27].

• **Algorithmic**. Despite its generality and adaptability, the KMoS-RE© strategy is algorithmic in the sense that the process of its implementation is well defined and limited, so the requirements engineers do not need a deep knowledge about the theoretical concepts of knowledge management. Most of the cases showed in the previous section were led by undergraduate engineering students [8]. Although a process of awareness of the issues of informal structured domains is always recommended.

Finally, we would like to emphasize that the most important contribution of the KMoS-RE© strategy is that it does not try to work against human nature; it recognizes its capabilities and limitations and builds the best proposal based on that. Thus, according to the below and the valuable results of the application of the KMoS-RE© strategy in several and different contexts, it can already be considered as a serious approach for requirements elicitation knowledge.
