Model-Based Requirements Engineering

Holt, Jon; Perry, Simon; Brownsword, Mike

doi:10.1049/pbpc009e

Cited by 36 publications

(43 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…This paper takes as its start point the Approach to Contextbased Requirements Engineering (ACRE) [3]. ACRE has been applied very successfully at the systems level, but has not yet been applied at the system of systems level.…”

Section: Model-based Requirements Engineering For Systems Of Systemsmentioning

confidence: 99%

“…In order to realize these benefits, however, there are a number of areas that must be addressed [3].…”

Section: Introductionmentioning

confidence: 99%

“…In the world of systems of systems (SoSs) engineering, however, there is a dearth of well-developed approaches available. One example of this is the area of model-based requirements engineering (MBRE) where there are established approaches for MBRE at the systems level [3] and an acknowledged lack of approaches at the system of systems (SoS) level [5]. This paper addresses that need by providing a process-based approach to model-based requirements engineering for SoSs.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

A Model-Based Approach for Requirements Engineering for Systems of Systems

Holt

Perry

Payne

et al. 2015

IEEE Systems Journal

Self Cite

View full text Add to dashboard Cite

show abstract

Section: Model-based Requirements Engineering For Systems Of Systemsmentioning

confidence: 99%

“…In order to realize these benefits, however, there are a number of areas that must be addressed [3].…”

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

A Model-Based Approach for Requirements Engineering for Systems of Systems

Holt

Perry

Payne

et al. 2015

IEEE Systems Journal

Self Cite

View full text Add to dashboard Cite

show abstract

“…However, for [5] a single view model of the system does not explicitly fit all situation of the system life cycle. According to [5,7,26], these models or standards can be used to determine all phases of the life cycle, but they contain particular characteristics that make them more suitable for specific phases. For instance, the waterfall is suitable for defining phases, because this model uses the feedback concept ensuring and revising the information integrity during a single phase [27].…”

Section: Cross-systems Life Cycle Requirements Interoperation Issuementioning

confidence: 99%

“…While approaches such as model-based systems engineering (MBSE) have been studied in [6,7,8], for improving the definition of requirements based on models, there is still a semantic gap between all requirements definitions when they are defined in different domains for the same engineering project and requirement consistency management in different systems life cycle phases. In order to cope with this challenge, we are working to define a conceptual framework that aims to formally model requirements interoperation in term of impact and semantic equivalence or subsumption.…”

Section: Introductionmentioning

confidence: 99%

Towards a Conceptual Framework for Requirements Interoperability in Complex Systems Engineering

Szejka

Aubry

Panetto

et al. 2014

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. Requirements Engineering (RE) is an important activity in system engineering and produces, from the users' needs, specifications related to what the final system must be. This process in complex systems engineering is extremely intense, because there is a large number of stakeholders involved, with expertise deriving from heterogeneous domains. Moreover, requirements' improvements and variations are common during system life cycle phases. Thus, there is a risk of inconsistency of requirements during the engineering of a system. This paper provides a contribution in requirements engineering as it explores requirements interoperability in complex systems when multiples dimensions are involved. It discusses requirement management according to the cross-domains dimension, the cross-systems life cycle dimension, the crossrequirements dimension and the risk of inconsistency when three dimensions are involved simultaneously during the life cycle phases. The main result is an overview of the existing gaps in one and/or more dimensions allowing a discussion on the possibilities to cope with the problem of requirements inconsistency in multiples dimensions.

show abstract

3.2.2 Traceable Engineering of Fault‐Tolerant SoSs

Andrews

Ingram

Payne

et al. 2014

INCOSE International Symp

Self Cite

View full text Add to dashboard Cite

Abstract. Systems of systems (SoSs) are characterised by a challenging combination of continuous evolution, emergent behaviour and distributed, autonomous and independent constituents. The development of SoSs that can tolerate faults and harmful events is hampered by these and other complexities. Currently there is little in the way of methods or tools to help SoS developers to design fault-tolerant SoSs. In this paper we present a structured approach for capturing requirements for a fault-tolerant SoS and a fault modelling architectural framework (FMAF) that supports disciplined and reusable development of fault-tolerant architectures. We also provide a traceable mapping of the fault-tolerant requirements into SoS architectural designs. Finally we apply our techniques to a real-world SoS case study.

show abstract

Model-Based Requirements Engineering

Cited by 36 publications

References 0 publications

A Model-Based Approach for Requirements Engineering for Systems of Systems

A Model-Based Approach for Requirements Engineering for Systems of Systems

Towards a Conceptual Framework for Requirements Interoperability in Complex Systems Engineering

3.2.2 Traceable Engineering of Fault‐Tolerant SoSs

Contact Info

Product

Resources

About