A prescriptive approach to qualify and quantify customer value for value-based requirements engineering

Recently, customer-based product development is becoming a popular paradigm. Customer expectations and needs can be identified and transformed into requirements for product design with the help of various methods and tools. However, in many cases, these models fail to focus on the perceived value that is crucial when customers make the decision of purchasing a product. In this paper, a prescriptive approach to support value-based requirements engineering (RE) is proposed, describing the foundations, procedures and initial applications in the context of RE for commercial aircraft. An integrated set of techniques, such as means-ends analysis, part-whole analysis and multi-attribute utility theory is introduced in order to understand customer values in depth and width. Technically, this enables identifying the implicit value, structuring logically collected statements of customer expectations and performing value modelling and simulation. Additionally, it helps to put in place a system to measure customer satisfaction that is derived from the proposed approach. The approach offers significant potential to develop effective value creation strategies for the development of new product

Confidence: Its role in dependability cases for risk assessment

Society is increasingly requiring quantitative assessment of risk and associated dependability cases. Informally, a dependability case comprises some reasoning, based on assumptions and evidence, that supports a dependability claim at a particular level of confidence. In this paper we argue that a quantitative assessment of claim confidence is necessary for proper assessment of risk. We discuss the way in which confidence depends upon uncertainty about the underpinnings of the dependability case (truth of assumptions, correctness of reasoning, strength of evidence), and propose that probability is the appropriate measure of uncertainty. We discuss some of the obstacles to quantitative assessment of confidence (issues of composability of subsystem claims; of the multi-dimensional, multi-attribute nature of dependability claims; of the difficult role played by dependence between different kinds of evidence, assumptions, etc). We show that, even in simple cases, the confidence in a claim arising from a dependability case can be surprisingly low

Generic approach for deriving reliability and maintenance requirements through consideration of in-context customer objectives

Not all implementations of reliability are equally effective at providing customer and user benefit. Random system failure with no prior warning or failure accommodation will have an immediate, usually adverse impact on operation. Nevertheless, this approach to reliability, implicit in measurements such as ‘failure rate’ and ‘MTBF’, is widely assumed without consideration of potential benefits of pro-active maintenance. Similarly, it is easy to assume that improved maintainability is always a good thing. However, maintainability is only one option available to reduce cost of ownership and reduce the impact of failure. This paper discusses a process for deriving optimised reliability and maintenance requirements through consideration of in-context customer objectives rather than a product in isolation

Virtualisation of the test environment for signalling

ERTMS is a well-known, well-performing technology applied all over the world but it still lacks flexibility when it comes to authorisation and certification procedures. The key of its success in the future lies as much in cost reduction as in simplification of placing in service procedures. This holds true for the implementation of a new subsystem and even more so for new software releases related to subsystems already in service. Currently the placing in service process of ETCS components and subsystems requires a large amount of tests due to the complexity of the signalling systems and the different engineering rules applied. The S2R Multi-Annual Action Plan states that the effort and time consumption of these onsite tests are at least 30% for any particular project. VITE research project (VIrtualisation of the Test Environment) aims at reducing these onsite tests to a minimum while ensuring that laboratory tests can serve as evidence for valid system behaviour and are accepted by all stakeholders involved in the placing in service process. This paper presents the first VITE results

System analysis approach to deriving design criteria (loads) for Space Shuttle and its payloads. Volume 1: General statement of approach

Space shuttle, the most complex transportation system designed to date, illustrates the requirement for an analysis approach that considers all major disciplines simultaneously. Its unique cross coupling and high sensitivity to aerodynamic uncertainties and high performance requirements dictated a less conservative approach than those taken in programs. Analyses performed for the space shuttle and certain payloads, Space Telescope and Spacelab, are used a examples. These illustrate the requirements for system analysis approaches and criteria, including dynamic modeling requirements, test requirements control requirements and the resulting design verification approaches. A survey of the problem, potential approaches available as solutions, implications for future systems, and projected technology development areas are addressed

Composing features by managing inconsistent requirements

One approach to system development is to decompose the requirements into features and specify the individual features before composing them. A major limitation of deferring feature composition is that inconsistency between the solutions to individual features may not be uncovered early in the development, leading to unwanted feature interactions. Syntactic inconsistencies arising from the way software artefacts are described can be addressed by the use of explicit, shared, domain knowledge. However, behavioural inconsistencies are more challenging: they may occur within the requirements associated with two or more features as well as at the level of individual features. Whilst approaches exist that address behavioural inconsistencies at design time, these are overrestrictive in ruling out all possible conflicts and may weaken the requirements further than is desirable. In this paper, we present a lightweight approach to dealing with behavioural inconsistencies at run-time. Requirement Composition operators are introduced that specify a run-time prioritisation to be used on occurrence of a feature interaction. This prioritisation can be static or dynamic. Dynamic prioritisation favours some requirement according to some run-time criterion, for example, the extent to which it is already generating behaviour