Skip to main content
Fachgebiete
Automobil + Motoren Bauwesen + Immobilien Business IT + Informatik Elektrotechnik + Elektronik Energie + Nachhaltigkeit Finance + Banking Management + Führung Marketing + Vertrieb Maschinenbau + Werkstoffe Versicherung + Risiko
DE
EN
Bücher
Zeitschriften
Themenseiten
Organisationspsychologie Projektmanagement Marketing Smart Manufacturing
Weitere Formate
Podcasts Webinare Technik Webinare Wirtschaft Kongresse Veranstaltungskalender Awards
Jetzt Einzelzugang starten
Zugang für Unternehmen
Referenzkunden
SLX-Digitalkonferenz: Zukunftswerkstatt 2024

Mehr Umsatz mit Top-Kontakten

Am 7. Mai erfahren Sie, wie Vertriebsteams Leadgenerierung, Leadnurturing und Leadstrategien effizient steuern können.
Erweiterte Suche
Anmelden
nach oben

2011 | Buch

Introduction Kapitel lesen Erstes Kapitel lesen

Requirements Engineering

verfasst von: Elizabeth Hull, Ken Jackson, Jeremy Dick

Verlag: Springer London

Enthalten in: Springer Professional "Wirtschaft+Technik" , Springer Professional "Technik" , Springer Professional "Wirtschaft"

Einloggen, um Zugang zu erhalten
insite
SUCHEN

Über dieses Buch

Using the latest research and driven by practical experience from industry, the third edition of this popular book provides useful information to practitioners on how to write and structure requirements. • Explains the importance of Systems Engineering and the creation of effective solutions to problems • Describes the underlying representations used in system modelling and introduces the UML2 • Considers the relationship between requirements and modelling • Covers a generic multi-layer requirements process • Discusses the key elements of effective requirements management • Explains the important concept of rich traceability In this third edition the authors have updated the overview of DOORS to include the changes featured in version 9.2. An expanded description of Product Family Management and a more explicit definition of Requirements Engineering are also included. Requirements Engineering is written for those who want to develop their knowledge of requirements engineering, whether practitioners or students.

Inhaltsverzeichnis

Frontmatter
Chapter 1. Introduction
Abstract
If ever systems development projects needed a “fair wind”, they certainly do so today. Fast-changing technology and increased competition are placing ever-increasing pressure on the development process. Effective requirements engineering lies at the heart of an organisation’s ability to guide the ship and to keep pace with the rising tide of complexity.
Elizabeth Hull, Ken Jackson, Jeremy Dick
Chapter 2. A Generic Process for Requirements Engineering
Abstract
This chapter introduces the concept of a process for the development of systems. It starts by examining the way in which systems are developed. This leads to the identification of a development pattern that can be used in many different contexts. This development pattern is expressed as a generic process and is explained in some detail. Subsequent chapters indicate how the generic process can be instantiated for specific purposes. The relationship between process models and information ­models is also explored and an information model for the generic process is developed.
Elizabeth Hull, Ken Jackson, Jeremy Dick
Chapter 3. System Modelling for Requirements Engineering
Abstract
System modelling supports the analysis and design process by introducing a degree of formality into the way systems are defined. During system development it is often the case that pictures are used to help visualize some aspects of the development. Modelling provides a way of formalising these representations, through ­diagrams, by not only defining a standard syntax, but also providing a medium for understanding and communicating the ideas associated with system development.
Elizabeth Hull, Ken Jackson, Jeremy Dick
Chapter 4. Writing and Reviewing Requirements
Abstract
Requirements engineering is a technical process. Writing requirements is therefore not like other kinds of writing. It is certainly not like writing a novel, or a book like this; it is not even like the kind of “technical writing” seen in instruction manuals and user guides.
Elizabeth Hull, Ken Jackson, Jeremy Dick
Chapter 5. Requirements Engineering in the Problem Domain
Abstract
The problem domain is the domain in which a system is going to be used. Therefore it is important to look at requirements from an operational point of view. A system or any other product enables somebody or some equipment to do something. It is this enabling aspect that is at the heart of requirements engineering in the problem domain.
Elizabeth Hull, Ken Jackson, Jeremy Dick
Chapter 6. Requirements Engineering in the Solution Domain
Abstract
The solution domain is where engineers use their ingenuity to solve problems. The primary characteristic that differentiates the solution domain from the problem domain is that, invariably requirements engineering in the solution domain starts with a given set of requirements. In the problem domain requirements ­engineering starts with a vague objective or wish list. The extent to which the input requirements for the solution domain are “well formed” depends upon the quality of the people within the customer organisation that developed them. In an ideal world, all the requirements would be clearly articulated, individual test able requirements.
Elizabeth Hull, Ken Jackson, Jeremy Dick
Chapter 7. Advanced Traceability
Abstract
So often, the real rationale for a particular design, and the deeper understanding of how the components of a system work together to achieve an end result, remain in the minds of the engineers. Months or years later, when the original designers have long since moved on, or their memory has dimmed, the loss of that understanding may seriously impede the ability to evolve, maintain or reuse the system.
Elizabeth Hull, Ken Jackson, Jeremy Dick
Chapter 8. Management Aspects of Requirements Engineering
Abstract
The management of the requirements engineering process is similar to the management of any other endeavour. Before starting out it is necessary to understand what needs to be done. We need to know the sorts of activities that must be undertaken. We need to know whether there are any dependencies between the activities, e.g. whether one activity can only commence when another one has been completed. We need to know what kinds of skills are required to perform the activities.
Elizabeth Hull, Ken Jackson, Jeremy Dick
Chapter 9. DOORS: A Tool to Manage Requirements
Abstract
Systems engineers and managers need the right instruments to assist them with the requirements management process. A variety of tools currently exist. This chapter presents an overview of one of these tools – IBM Rational® DOORS® (Version 9.2). DOORS (Dynamic Object Oriented Requirements System) is a leading requirements management tool used by tens of thousands of engineers around the world. The tool was originally created by QSS Ltd, Oxford and is now developed and marketed by IBM.
Elizabeth Hull, Ken Jackson, Jeremy Dick
Backmatter
Metadaten
Titel
Requirements Engineering
verfasst von
Elizabeth Hull
Ken Jackson
Jeremy Dick
Copyright-Jahr
2011
Verlag
Springer London
Electronic ISBN
978-1-84996-405-0
Print ISBN
978-1-84996-404-3
DOI
https://doi.org/10.1007/978-1-84996-405-0