Knowledge based requirement engineering for one-of-a-kind complex systems

Ratchev, Svetan; Urwin, Esmond Neil; Müller, Dieter; Pawar, Kulwant S.; Moulek, I.

doi:10.1016/s0950-7051(02)00027-8

Cited by 30 publications

(11 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…The knowledge acquisition and sharing for requirement engineering (KARE) [15,16] methodology is aimed at supporting the RE process in a one-of-a-kind environment. The RE process ( Figure 1) starts with an invitation to tender (ITT) and finishes with a requirements baseline.…”

Section: Overview Of the Kare Methodologymentioning

confidence: 99%

Knowledge-enriched Requirement Specification for One-of-a-kind Complex Systems

Ratchev

Pawar

Urwin

et al. 2005

Concurrent Engineering

View full text Add to dashboard Cite

Requirement engineering (RE) process is becoming a key factor for the success of complex one-of-a-kind products. The RE process is commonly viewed as an early system engineering phase with a major bearing on response time, quality, and cost. This study reports on the knowledge acquisition and sharing for requirement engineering (KARE), approach for requirement specification of one-of-a-kind complex systems. The approach provides a generic view of key RE processes clustered into three groups of activities -requirements elicitation, analysis, and negotiation. The process is supported by a set of knowledge functions aimed at facilitating the requirement engineers in matching customer requirements to product characteristics. At the analysis stage, the customer requirements are transformed into product requirements, which can be compared to existing company knowledge, for example, previous products, technology platforms, and production capabilities. The specified product requirements are then interactively evaluated and negotiated against customer and supplier performance indicators.

show abstract

Section: Overview Of the Kare Methodologymentioning

confidence: 99%

Knowledge-enriched Requirement Specification for One-of-a-kind Complex Systems

Ratchev

Pawar

Urwin

et al. 2005

Concurrent Engineering

View full text Add to dashboard Cite

show abstract

“…In fact, the misinterpretation and mistakes may cause significant a posteriori system refactoring, which result in scheduling overruns and increasing the projects costs [10]. The traditional system requirement approach does not support [11,12,13]:…”

Section: Problem Statementmentioning

confidence: 99%

“…In [12], the complexity of translating customer needs in functional or nonfunctional requirements is demonstrated, because the customers or stakeholders environment was associated with a different requirement environment than the requirements analyst (RA). Thus, RE emerges as a cooperative, interactive and incremental process to elicitation, negotiation and documentation of the requirements and constraints of complex systems.…”

Section: Cross-requirements Interoperation Issue In a Single Domain/smentioning

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

“…As application software has become more complicated and large scale, developing eCRM thus requires the following different approaches from traditional approaches [1] Software requirements engineering is one of the most important phases in software development process [48,50]. Requirements engineering basically consists of the understanding and representation of the problem to be solved and the requirements elicitation for the problem [51,57].…”

Section: Introductionmentioning

confidence: 99%

A strategy-based process for effectively determining system requirements in eCRM development

Hung

2009

Information and Software Technology

View full text Add to dashboard Cite

Knowledge based requirement engineering for one-of-a-kind complex systems

Cited by 30 publications

References 3 publications

Knowledge-enriched Requirement Specification for One-of-a-kind Complex Systems

Knowledge-enriched Requirement Specification for One-of-a-kind Complex Systems

Towards a Conceptual Framework for Requirements Interoperability in Complex Systems Engineering

A strategy-based process for effectively determining system requirements in eCRM development

Contact Info

Product

Resources

About