Cargando…
Requirements Engineering for Software and Systems
Solid requirements engineering has increasingly been recognized as the key to improved, on-time, and on-budget delivery of software and systems projects. New software tools are emerging that are empowering practicing engineers to improve their requirements engineering habits. However, these tools ar...
| Clasificación: | Libro Electrónico |
|---|---|
| Autor principal: | |
| Otros Autores: | |
| Formato: | Electrónico eBook |
| Idioma: | Inglés |
| Publicado: |
Milton :
Auerbach Publishers, Incorporated,
2009.
|
| Edición: | 4th ed. |
| Colección: | Applied Software Engineering Ser.
|
| Temas: | |
| Acceso en línea: | Texto completo (Requiere registro previo con correo institucional) |
Tabla de Contenidos:
- Cover
- Half Title
- Title Page
- Copyright Page
- Table of Contents
- Preface
- Acknowledgments
- Authors
- 1 Introduction to Requirements Engineering
- Motivation
- What Is Requirements Engineering?
- You Probably Don't Do Enough Requirements Engineering
- What Are Requirements?
- Requirements vs. Features vs. Goals
- Requirements Classifications
- Requirements Level Classification
- Requirements Specifications Types
- Functional Requirements
- Nonfunctional Requirements
- Domain Requirements
- Domain Vocabulary Understanding
- Requirements Engineering Activities
- Requirements Elicitation/Discovery
- Requirements Analysis and Agreement
- Requirements Representation
- Requirements Validation
- Requirements Management
- Bodies of Knowledge
- The Requirements Engineer
- Requirements Engineer Roles
- Requirements Engineer as Software or Systems Engineer
- Requirements Engineer as Subject Matter Expert
- Requirements Engineer as Architect
- Requirements Engineer as Business Process Expert
- Ignorance as Virtue
- Role of the Customer
- Problems with Traditional Requirements Engineering
- Complexity
- Gold-Plating and Ridiculous Requirements
- Obsolete Requirements
- Four Dark Corners
- Difficulties in Enveloping System Behavior
- The Danger of "All" in Specifications
- Exercises
- References
- 2 Preparing for Requirements Elicitation
- Product Business Goals and Mission Statements
- Encounter with a Customer
- Identifying the System Boundaries
- Context Diagrams
- Stakeholders
- Negative Stakeholders
- Stakeholder Identification
- Stakeholder Identification Questions
- Rich Pictures
- Stakeholder/User Classes
- Stakeholders vs. Use Case Actors
- User Characteristics
- Customer Wants and Needs
- What Do Customers Want?
- What Don't Customers Want?
- Why Do Customers Change Their Minds?
- Stakeholder Prioritization
- Communicating with Customers and Other Stakeholders
- Managing Expectations
- Stakeholder Negotiations
- Uncovering Stakeholder Goals
- Exercises
- Note
- References
- 3 Requirements Elicitation
- Introduction
- Requirements Elicitation
- First Step
- Elicitation Techniques Survey
- Brainstorming
- Card Sorting
- Crowdsourcing
- Designer as Apprentice
- Domain Analysis
- Ethnographic Observation
- Goal-Based Approaches
- Group Work
- Interviews
- Introspection
- Joint Application Design
- Laddering
- Protocol Analysis
- Prototyping
- Quality Function Deployment
- Questionnaires/Surveys
- Repertory Grids
- Reverse Engineering
- Scenarios
- Task Analysis
- Use Cases
- User Stories
- Viewpoints
- Workshops
- Eliciting Nonfunctional Requirements
- Elicitation Summary
- Which Combination of Requirements Elicitation Techniques Should Be Used?
- Prevalence of Requirements Elicitation Techniques
- Eliciting Hazards
- Misuse Cases
- Antimodels
- Formal Methods
- Exercises
- Note
- References