Rôle of Domain Engineering in Software Development—Why Current Requirements Engineering Is Flawed !

Bjørner, Dines

doi:10.1007/978-3-642-11486-1_2

Cited by 15 publications

(7 citation statements)

References 17 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…To achieve those goals, a multi-level domain ontology was developed. The "Multi-level Domain Ontology", whose main concepts are represented in Figure 3, relies on previous studies on domain ontologies [40] [41]. The ontology was designed to be easily extensible by sub-ontologies, depending on the domain at hand.…”

Section: Ontologies In Aman-damentioning

confidence: 99%

Using the AMAN-DA method to generate security requirements: a case study in the maritime domain

et al. 2017

View full text Add to dashboard Cite

Abstract. [Context and motivation]Security requirements are known to be "the most difficult of requirements types", and potentially the ones causing the greatest risk if they are not correct. One approach to requirements elicitation is based on the reuse of explicit knowledge. AMAN-DA is a requirement elicitation method that reuses encapsulated knowledge in security and domain ontologies to produce security requirements specifications.[Question/Problem] The main research question addressed in this paper is to what extent is AMAN-DA able to generate domain specific security requirements? [Principal idea/results] Following a well-documented process, a case study related to the maritime domain was undertaken with the goal to demonstrate the utility and effectiveness of AMAN-DA for the elicitation and analysis of domain specific security requirements. The usefulness of the method was also evaluated with a group of twelve experts.[Contribution] The paper demonstrates the elicitation of domain specific security requirements by presenting the AMAN-DA method and its application. It describes the evaluation and reports some significant results and their implications for practice, and future research, especially for the field of knowledge reuse in requirements engineering.

show abstract

Section: Ontologies In Aman-damentioning

confidence: 99%

Using the AMAN-DA method to generate security requirements: a case study in the maritime domain

et al. 2017

View full text Add to dashboard Cite

show abstract

“…For this purpose, the strategy is based on the following premise: "To develop a software system, it is necessary to understand the requirements, and to educe the requirements, it is necessary to understand the domain" [12]. The strategy is composed by three sequential phases: domain modeling, system modeling and specification developing [13]:…”

Section: Kmos-re Strategymentioning

confidence: 99%

Requirements engineering based on knowledge: a comparative case study of the KMoS-RE strategy and the DMS process

Olmos-Sánchez

Rodas-Osollo

Martínez

et al. 2015

Rev. Fac. Ing. Antioquia

View full text Add to dashboard Cite

“…According to this definition, a software system is embedded in an application domain, so its usefulness depends on the problems that it can solve and on the objectives that it can achieve in this domain. The importance of the application domain in RE has been analyzed in several works [4], [5] and [6].…”

Section: Introductionmentioning

confidence: 99%

A Strategy to Requirements Engineering Based on Knowledge Management

Sanchez

Rodas-Osollo

2013

2013 Mexican International Conference on Computer Science

View full text Add to dashboard Cite

In Informal Structured Domains not all concepts and their relations are formally defined, the most of the problems does not have algorithms to obtain solutions, and the domain specialists use large amounts of tacit knowledge to solve problems.These characteristics generate ambiguous, inappropriate and incomplete requirements that could increase the development time of a software system. In order to minimize these problems, we propose a Requirements Engineering strategy based on knowledge management. As a case study, the strategy was used to the development of a software system, which evaluates the cognitive impairment in patients with sclerosis multiple.

show abstract

Rôle of Domain Engineering in Software Development—Why Current Requirements Engineering Is Flawed !

Cited by 15 publications

References 17 publications

Using the AMAN-DA method to generate security requirements: a case study in the maritime domain

Using the AMAN-DA method to generate security requirements: a case study in the maritime domain

Requirements engineering based on knowledge: a comparative case study of the KMoS-RE strategy and the DMS process

A Strategy to Requirements Engineering Based on Knowledge Management

Contact Info

Product

Resources

About