In this paper, we discuss an approach to system requirements engineering, which is based on using models of the responsibilities assigned to agents in a multi-agency system of systems. The responsibility models serve as a basis for identifying the stakeholders that should be considered in establishing the requirements and provide a basis for a structured approach, described here, for informatio...

E-health is a rising research area in the public health, business and medical informatics sectors and refers to health and information services that are delivered or improved by using the Internet and other related information technologies. Various aspects of e-health are discussed in the literature; however, there is a research gap in the areas of system requirements engineering and ehealth bu...

In this paper, we present an approach for the automatic verification of software requirements specifications. This approach is based on the representation of software requirements in XML and the usage of the XSLT language not only to automatically generate requirements documents, but also to verify some desired quality properties and to automatically compute some metrics. These ideas have been ...

Often during the requirements engineering (RE) process, the value of a requirement is assessed, e.g., in requirement prioritisation, release planning, and trade-off analysis. In order to support these activities, this research evaluates Goal Oriented Requirements Engineering (GORE) methods for the description of a requirement’s value. Specifically, we investigate the goal-to-goal contribution r...

This paper is concerned with software requirements evolution in industrial settings. The discussion provides new insights in requirements engineering. This paper highlights the problem of empirically understanding and modelling requirements evolution.

Many applications that are developed do not completely fulfil the requirements of their stakeholders. This can be a result of inadequate requirements elicitation and poorly defined requirements. Many solutions, including model-driven inspired ones, have been proposed to improve the elicitation of the requirements, though many of them are not yet widely used in practice as they require training ...

[Context and Motivation] The word “creativity” is used widely in business and academia, but its meaning may differ greatly depending on context. This may cause confusion in the minds of requirements engineers who have to determine which kinds of creativity are relevant to their project and which creativity tools to use. [Question/Problem] The main goal of this work is to understand why and how ...

e-Health is a rising research area in the intersection of public health and business sectors which refers to health and information services that are delivered or improved by using the Internet and other related information and communication technologies. Various aspects of e-Health are discussed in the literature; however, there is a research gap in the areas of system requirements engineering...

Interviews with IS developers suggest that requirements analysis is rarely perceived as a cooperative activity. Instead it is often seen as a process of extracting requirements from passive clients (as terms such as “requirements capture” and “requirements engineering” imply). A more cooperative approach which recognises requirements analysis as a negotiative process between analyst(s) and clie...