Goal-oriented requirements engineering: from system objectives to UML models to precise software specifications

Lamsweerde, Axel van

doi:10.1109/icse.2003.1201266

Cited by 391 publications

(797 citation statements)

References 7 publications

Supporting

Mentioning

781

Contrasting

Unclassified

Order By: Relevance

“…Similarly, in [16], representation techniques to document entities in the context of a system are suggested. Other approaches (e.g., [17], [18], [19]) have been proposed, which use documented context information for quality assurance, e.g., by evaluating development artifacts against assumptions about the context that may hold during runtime (i.e., goals in [17] and the world in [18]), or analyze the impact of context changes (see [19]). In all approaches, documenting context information is used as a reference artifact, against which other development artifacts can be validated.…”

Section: Related Workmentioning

confidence: 99%

Early Validation of Automation Plant Control Software using Simulation Based on Assumption Modeling and Validation Use Cases

Brandstetter

Froese

Tenbergen

et al. 2015

CSIMQ

View full text Add to dashboard Cite

Abstract. In automation plants, technical processes must be conducted in a way that products, substances, or services are produced reliably, with sufficient quality and with minimal strain on resources. A key driver in conducting these processes is the automation plant's control software, which controls the technical plant components and thereby affects the physical, chemical, and mechanical processes that take place in automation plants. To this end, the control software of an automation plant must adhere to strict process requirements arising from the technical processes, and from the physical plant design. Currently, the validation of the control software often starts late in the engineering process in many cases -once the automation plant is almost completely constructed. However, as widely acknowledged, the later the control software of the automation plant is validated, the higher the effort for correcting revealed defects is, which can lead to serious budget overruns and project delays. In this article we propose an approach that allows the early validation of automation control software against the technical plant processes and assumptions about the physical plant design by means of simulation. We demonstrate the application of our approach on the example of an actual plant project from the automation industry and present it's technical implementation.

show abstract

Section: Related Workmentioning

confidence: 99%

Early Validation of Automation Plant Control Software using Simulation Based on Assumption Modeling and Validation Use Cases

Brandstetter

Froese

Tenbergen

et al. 2015

CSIMQ

View full text Add to dashboard Cite

show abstract

“…[3], which is an AI system, and the Mine Safety Control System (MineSys.) [10], which is a real time control system. The use of three case studies in three different domains makes sure that our comparison results are not dependent on the domain.…”

Section: Comparison Methodologymentioning

confidence: 99%

“…This process introduces new requirements to M odel x , which make subsequent RE activities A simple example of adopting the conceptual feedback approach to get more requirements and reveal requirements acquisition opportunities in a UML class diagram is shown in Figure 2 and Figure 3. Through model transformations, the original UML class diagram shown in Figure 2 is augmented by requirements from the current state diagrams and sequence diagrams of a Mine Safety Control system [10]. The resulting augmented class diagram is shown in Figure 3.…”

Section: Introductionmentioning

confidence: 99%

A Comparison of Two Model Transformation Frameworks for Multiple-viewed Software Requirements Acquisition

Wei

2017

International Conferences on Software Engineering and Knowledge Engineering

View full text Add to dashboard Cite

Abstract-Multiple-viewed requirements modeling allows modelers to elicit the requirements of a system from different viewpoints. Requirements are then organized and encoded in different analysis models which collaboratively form an overall understanding of the system. Model transformations among those analysis models at this stage can be used as a way to acquire requirements knowledge, thus making the set of models complete and consistent. Two frameworks are found to support such requirements acquisition: the pairwise framework and the common representation framework. In practical applications, various factors need to be considered when requirements modelers choose between the two frameworks in order to acquire requirements by analysis model transformations. In this paper, we propose a set of criteria which provides a theoretical basis for comparing the two frameworks for their effectiveness of generating models and acquiring requirements in the context of multiple-viewed requirements modeling. The results of the comparison is then presented.

show abstract

“…A goal can be either fulfilled or not [11], and may depend on sub-goals through AND or OR refinements. Goal-oriented requirements engineering [8,11] focuses on goals which are "roughly speaking, precursors of requirements" [12]. Some goal-based modeling approaches, such as i* [13,14], also model the actors who hold these intentions.…”

Section: Goals Aspects and Reusementioning

confidence: 99%

“…Most variations of goal models in the literature use AND/OR trees to represent goal decomposition [6,11] and define a space of alternative solutions to the problem of satisfying a root-level goal. There are several proposals for goal analysis techniques.…”

Section: Goals Aspects and Reusementioning

confidence: 99%

Quality-Based Software Reuse

Leite

Liu

et al. 2005

Notes on Numerical Fluid Mechanics and Multidisciplinary Design

View full text Add to dashboard Cite

Abstract. Work in software reuse focuses on reusing artifacts. In this context, finding a reusable artifact is driven by a desired functionality. This paper proposes a change to this common view. We argue that it is possible and necessary to also look at reuse from a non-functional (quality) perspective. Combining ideas from reuse, from goal-oriented requirements, from aspect-oriented programming and quality management, we obtain a goal-driven process to enable the quality-based reusability.

show abstract

Goal-oriented requirements engineering: from system objectives to UML models to precise software specifications

Cited by 391 publications

References 7 publications

Early Validation of Automation Plant Control Software using Simulation Based on Assumption Modeling and Validation Use Cases

Early Validation of Automation Plant Control Software using Simulation Based on Assumption Modeling and Validation Use Cases

A Comparison of Two Model Transformation Frameworks for Multiple-viewed Software Requirements Acquisition

Quality-Based Software Reuse

Contact Info

Product

Resources

About