This paper presents procedural guidance for performing activities of creative problem-solving within systems engineering. We have applied this method in four case studies in different domains, slightly varying the techniques applied. This paper describes the experience gained and gives recommendations. Furthermore, the procedure integrates itself seamlessly into an overall systems development f...

The field of Requirements Engineering (RE) is arguably one of the most crucial areas in the development of systems in support of organisational structures and processes. Eliciting, negotiating, analysing and validating are RE processes that rely on appropriate abstraction mechanisms. This paper focuses on a specific modelling approach, that of Business Process Modelling (BPM), and the use of a ...

One of the biggest risks in software requirements engineering is the risk of overemphasizing one quality attribute requirement (e.g., performance) at the expense of others at least as important (e.g., evolvability and portability). This paper describes an exploratory knowledge-based tool for identifying potential conflicts among quality attributes early in the software/system life cycle. The Qu...

DISCLAIMER: This publication is based on sources and information believed to be reliable, but the AAPM and the editors disclaim any warranty or liability based on or relating to the contents of this publication. The AAPM does not endorse any products, manufacturers , or suppliers. Nothing in this publication should be interpreted as implying such endorsement. All rights reserved. No part of thi...

Many software projects fail because early life-cycle defects such as ill-defined requirements are not identified and removed. Therefore, quality assurance (QA) techniques for defect detection and prevention play an important role. The effectiveness and efficiency of QA approaches has been empirically evaluated. In this paper we discuss QA techniques optimized for requirements negotiations. In p...

Misuse cases are like use cases, but with bad intent. They can be used when defining non-quality attributes. This paper describes the main concepts concerning misuse cases and shows ways to present them. A literature study is performed to find answers to research questions.

The classical notion of requirements quality focuses on Adequacy1, Unambiguity, Completeness, Consistency, Verifiability, Modifiability and Traceability (IEEE 1993). In practice however, most requirements specifications do not meet these qualities. One could argue that this is only a problem of applying the right methods and processes and that we should improve our requirements processes until ...

The ground thermal properties and the heat-transfer efficiency of the borehole heat exchanger (BHE) system are key parameters for designing ground-coupled systems. Proper design of such systems requires good knowledge of these parameters, providing an efficient and economic operation. For this purpose a test procedure known as Thermal Response Test (TRT) was developed in 1996 at the Oklahoma St...

The paper presents a process modelling-based Requirements Engineering Framework, where advanced requirements engineering techniques are combined with software quality modelling approaches to better assist and drive analysts and stakeholders to an early definition and validation of the desired system functionality and quality attributes, while supporting the redesign of the application context t...

ABSTRACT Software quality requirements defined in the requirements analysis stage should be implemented in the final products, such as source codes and system deployment. To guarantee this meta-requirement, quality requirements should be considered in the intermediate stages, such as the design stage or the architectural definition stage. We propose a novel method for checking whether quality r...