Corpus ID: 17120781

Requirement Documents that Win the Race : Not Overweight or Emaciated but Powerful and in Shape

  title={Requirement Documents that Win the Race : Not Overweight or Emaciated but Powerful and in Shape},
  author={Kirstin Kohler and Barbara Paech},
Time-constrained projects ask for requirements approaches that are agile, i.e. adapted to the project needs and without comprehensive documentation. But how can this be achieved? Our approach provides the steps toward the solution of this question. It supports the identification of the essential content of the requirements document as well as the selection of the appropriate modeling technique. The essential content is determined by conducting a systematic risk analysis, which allows… Expand

Figures and Tables from this paper

Acknowledging the Implications of Requirements
This paper acknowledges that the SRS must be kept in a practical and useful state and introduces a programme of research aimed at developing a Requirements Profile that changes the emphasis of requirements engineering from defining the requirements to defining what is known about the requirements. Expand
Adapting a Requirements Engineering Process by Key Factors Estimation
In this chapter, a process for constructing and dynamically adapting a requirements process is proposed, focusing on the evolving factors. Expand
É possível substituir processos de Engenharia de Requisitos por Contagem de Pontos de Função?
An application of theEFPC method of software size estimation as a surrogate process for Requirements Engineering (RE) process, especially for the organizations which don’t apply a RE Process is presented. Expand
There is no accepted method today that integrates requirements engineering and object-oriented development for user interface and information-intensive systems. In this paper we present the majorExpand


Requirements engineering for time-to-market projects
  • Christopher McPhee, A. Eberlein
  • Engineering, Computer Science
  • Proceedings Ninth Annual IEEE International Conference and Workshop on the Engineering of Computer-Based Systems
  • 2002
The components of the essential RE process as well as many other insights into the practice of RE were identified by examining the current literature and by analyzing the data from 25 completed surveys concerning the area of RE. Expand
Requirements engineering in the year 00: a research perspective
The initial description of a complex safety-critical system is used to illustrate a number of current research trends in RE-specific areas such as goal-oriented requirements elaboration, conflict management, and the handling of abnormal agent behaviors. Expand
ACRE: selecting methods for requirements acquisition
The ACRE framework provides guidelines for requirements engineering practitioners using questions driven from a set of facets which define the strengths and weaknesses of each method. Expand
Extreme programming explained - embrace change
  • K. Beck
  • Computer Science, Engineering
  • 1990
You may love XP, or you may hate it, but Extreme Programming Explained will force you to take a fresh look at how you develop software. Expand
Why is it so difficult to introduce requirements engineering research results into mainstream requirements engineering practice?
  • H. Kaindl
  • Computer Science
  • Proceedings Fourth International Conference on Requirements Engineering. ICRE 2000. (Cat. No.98TB100219)
  • 2000
Mainstream practice in requirements engineering is to use one's favorite word processor to write down mostly unstructured text in natural language, even though some good experience exists that used RE results in real projects (see, e.g., [2, 3]). Expand
Writing effective use cases
The authors indulge in a long-winded literature survey of planning systems and provide proofs of necessity, consistency, and optimality of their framework, that practitioners will no doubt find tiresome as the book is given the flavour of a PhD thesis. Expand
Practical Software Requirements: A Manual of Content and Style
Practical instructions on how to distinguish requirements from design to provide clear solutions for clear solutions in the rapidly changing environment. Expand
Documentation of requirements for computer systems
A functional approach to specifying the requirements of a computer system is discussed, a refinement of the method used in the A-7 aircraft software requirements model document. Expand
The Riskit Method for Software Risk Management, version 1.00
This paper presents the Riskit method for software engineering risk management. This document contains the motivation for the method, description of the Riskit analysis graph and a detailedExpand
This article presents an infrastructure, called the experience factory , aimed at capitalization and reuse of life cycle experience and products. The experience factory is a logical and physicalExpand