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

2010 ◽  
pp. 2-34 ◽  
Author(s):  
Dines Bjørner
Keyword(s):  
Software Development ◽  
Requirements Engineering ◽  
Domain Engineering

scholarly journals Validation of RP-SPF Framework: A Systematic Method for Requirements Reuse in Software Product Lines

2019 ◽  
Vol 9 (1) ◽  
pp. 3423-3426
Keyword(s):  
Software Development ◽  
Requirements Engineering ◽  
Domain Engineering ◽  
Product Line ◽  
Product Lines ◽  
Systematic Method ◽  
Product Families ◽  
Software Product ◽  
Application Engineering ◽  
Line Engineering

Reuse of requirements is crucial activity in software development especially across software product line engineering (SPLE), which involves two main processes known as domain engineering and application engineering. With these two processes SPLE enables systematic reuse of requirements through proper planning and development. This paper presents methodology and result of survey of experts for validating a proposed systematic requirement reuse approach named requirements pattern for software product families (RP-SPF) framework. During the survey, 14 experts in requirements engineering (RE), SPLE and software development responded and gave their opinions on RP-SPF framework. The result of the survey shows that RP-SPF approach is suitable and can effectively improve requirements engineering activities of SPLE.

The Role of Nonmonotonic Representations in Requirements Engineering

1998 ◽  
Vol 08 (03) ◽  
pp. 385-399 ◽  
Author(s):  
Grigoris Antoniou
Keyword(s):  
Software Engineering ◽  
Knowledge Representation ◽  
Requirements Engineering ◽  
Nonmonotonic Reasoning ◽  
Default Reasoning ◽  
Requirements Prioritization ◽  
Evolving System ◽  
System Requirements

This paper discusses the significance of nonmonotonic reasoning, a method from the knowledge representation area, to mainstream software engineering. In particular, we discuss why the use of defaults in specifications is an adequate way of addressing some of the most important problems in requirements engineering, such as: The problem of identifying and dealing with inconsistencies; evolving system requirements; requirements prioritization; and the quality of specifications with respect to naturalness and compactness. We argue that these problems need to be addressed in a principled, formal way, and that default reasoning provides adequate mechanisms to deal with them.

Die Rolle von Features und Aspekten in der Softwareentwicklung (The Role of Features and Aspects in Software Development)

2008 ◽  
Vol 50 (2) ◽  
Author(s):  
Sven Apel
Keyword(s):  
Software Development

ZusammenfassungFeature-orientierte Programmierung (FOP) und Aspekt-orientierte Programmierung (AOP) sind komplementäre Technologien. Obwohl beide auf die Modularität von so genannten querschneidenden Belangen abzielen, so tun sie dies auf unterschiedliche Art und Weise. Im Rahmen der Arbeit wurde beobachtet, dass FOP und AOP kombiniert werden können, um ihre individuellen Schwächen zu überwinden. Die Arbeit schlägt mit Aspekt-basierten Featuremodulen und Aspektverfeinerung zwei Techniken zur Symbiose von FOP und AOP vor. Beide Techniken werden in einer Fallstudie evaluiert und entsprechende Programmierrichtlinien zum Einsatz von FOP und AOP werden abgeleitet. Schlussendlich wird mittels der Analyse von acht AspectJ-Programmen unterschiedlicher Größe die Frage beantwortet, wie Implementierungsmechanismen der FOP und der AOP heutzutage Verwendung finden.

Sign in / Sign up

Export Citation Format

Share Document