Concepts Concrete Concepts Example Motivation Conclusion and Perspectives Andreas Metzger – SAM 2002 – Aberystwyth, Wales – June, 2002 1 Motivation 1 Application of Prototyping Final System Idea Validation (Product Test) Validation (Prototype Test) Verification (e.g. Inspection) Verification (Prototype Test) Prototype Creation Requirements Specification Problem Description System Prototype Prob...

A t the 1996 and 1997 International Conferences on Software Engineering, three of the six keynote addresses identified negotiation techniques as the most critical success factor in improving the outcome of software projects. At the USC Center for Software Engineering, we have been developing a negotiationbased approach to software system requirements engineering, architecture, development, and ...

We report on the application of the use-case modeling technique to identify and specify the user requirements of the MammoGrid project in an incremental and controlled iterative approach. Modeling has been carried out in close collaboration with clinicians and radiologists with no prior experience of use cases. The study reveals the advantages and limitations of applying this technique to requi...

Requirements engineering is known to be a key factor for the success of software projects. Inside this discipline, goal-oriented requirements engineering approaches have shown specially suitable to deal with projects where it is necessary to capture the alignment between system requirements and stakeholders’ needs, as is the case of datawarehousing projects. However, the mere alignment of data-...

Extending Requirements Engineering modelling and formal analysis methodologies to cope with Security Requirements has been a major effort in the past decade. Yet, only few works describe complex case studies that show the ability of the informal and formal approaches to cope with the level complexity required by compliance with ISO-17799 security management requirements. In this paper we presen...

A major task in designing systems development is the systematic elaboration of functional system requirements and their integration into the environment of the overall technical system. The main challenge is to handle the versatile tasks of coordinating the communication and consolidation of the various stakeholder requirements of the different involved diciplines and derive a common definition...

The goal of requirements engineering is to create a complete, consistent requirements specification of a desired system in order to establish the requirements at an abstract level. Business process modeling in the early phases of requirement engineering is rather useful. This paper examines business process modeling for the development of information systems. It presents the role of Business Pr...

eParticipation systems are often directly targeted at citizens. However, as a group of potential users, citizens form a heterogeneous and unpredictable group, which makes requirements elicitation a challenging issue. Based on recently developed ideas for wide audience requirement engineering (WARE), this chapter discusses and elaborates a method for eliciting citizen requirements for eParticipa...

Guidance plays a crucial role in requirements engineering (RE) as this task is both ill defined and highly intellectual. The guidance approach presented in this paper consists of supporting requirements engineers by a collection of enactable guidelines embodied in a computer environment. The key characteristics of the approach is its intention orientation. Guidance can be provided once the inte...

Requirements engineering education at universities is a fairly difficult issue for various reasons. Among the most prominent causes is a lack of authenticity, i.e. too artificial settings that do not adequately mirror the complexity of realworld situations. We present an approach to requirements engineering education that tries to avoid some of these shortcomings, in particular by including req...