A framework for expressing the relationships between multiple views in requirements specification

Nuseibeh, Bashar; Kramer, Jeff; Finkelstein, Anthony

doi:10.1109/32.328995

Cited by 371 publications

(194 citation statements)

References 37 publications

(9 reference statements)

Supporting

Mentioning

189

Contrasting

Unclassified

Order By: Relevance

“…Besides scenarios, use cases [24] and viewpoints [18] are classical requirements engineering artefacts. In the context of participative design scenarios are the most suitable to focus on activities of stakeholder and on their (partial) execution through prototypes.…”

Section: Discussionmentioning

confidence: 99%

Adaptive development and maintenance of user-centric software systems

Pahl

2004

Information and Software Technology

View full text Add to dashboard Cite

A software system cannot be developed without considering the various facets of its environment. Stakeholders -including the users that play a central role -have their needs, expectations, and perceptions of a system. Organisational and technical aspects of the environment are constantly changing. The ability to adapt a software system and its requirements to its environment throughout its full lifecycle is of paramount importance in a constantly changing environment. The continuous involvement of users is as important as the constant evaluation of the system and the observation of evolving environments. We present a methodology for adaptive software systems development and maintenance. We draw upon a diverse range of accepted methods including participatory design, software architecture, and evolutionary design. Our focus is on user-centred software systems.

show abstract

Section: Discussionmentioning

confidence: 99%

Adaptive development and maintenance of user-centric software systems

Pahl

2004

Information and Software Technology

View full text Add to dashboard Cite

show abstract

“…For PWF, transformations between each pair of UML diagrams have been studied by many researchers [5] [7][8], and they collaboratively carried out a well-understood semantic description of model transformations in PWF. A summary of transformation rules between each pair of three UML diagrams is available in [11].…”

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

“…Finkelstein et al [14,37] describe a technique for inconsistency handling in requirements documents developed using multiple methods and notations for the same system. They combine the ViewPoints framework for perspective development and a logic-based approach to inconsistency handling.…”

Section: Requirements Reasoningmentioning

confidence: 99%

Semantics of trace relations in requirements models for consistency checking and inferencing

et al. 2009

View full text Add to dashboard Cite

Requirements traceability is the ability to relate requirements back to stakeholders and forward to corresponding design artifacts, code, and test cases. Although considerable research has been devoted to relating requirements in both forward and backward directions, less attention has been paid to relating requirements with other requirements. Relations between requirements influence a number of activities during software development such as consistency checking and change management. In most approaches and tools, there is a lack of precise definition of requirements relations. In this respect, deficient results may be produced. In this paper, we aim at formal definitions of the relation types in order to enable reasoning about requirements relations. We give a requirements metamodel with commonly used relation types. The semantics of the relations is provided with a formalization in first-order logic. We use the formalization for consistency checking of relations and for inferring new relations. A tool has been built to support both reasoning activities. We illustrate our approach in an example which shows that the formal semantics of relation types enables new relations to be inferred and contradicting relations in requirements documents to be determined.

show abstract

A framework for expressing the relationships between multiple views in requirements specification

Cited by 371 publications

References 37 publications

Adaptive development and maintenance of user-centric software systems

Adaptive development and maintenance of user-centric software systems

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

Semantics of trace relations in requirements models for consistency checking and inferencing

Contact Info

Product

Resources

About