Requirements Engineering / Edition 1

Paperback (Print)
Rent from
(Save 73%)
Est. Return Date: 07/24/2015
Buy Used
Buy Used from
(Save 39%)
Item is in good condition but packaging may have signs of shelf wear/aging or torn packaging.
Condition: Used – Good details
Used and New from Other Sellers
Used and New from Other Sellers
from $34.19
Usually ships in 1-2 business days
(Save 48%)
Other sellers (Paperback)
  • All (16) from $34.19   
  • New (8) from $46.65   
  • Used (8) from $34.19   


Essential comprehensive coverage of the fundamentals of requirements engineering

Requirements engineering (RE) deals with the variety of prerequisites that must be met by a software system within an organization in order for that system to produce stellar results. With that explanation in mind, this must-have book presents a disciplined approach to the engineering of high-quality requirements. Serving as a helpful introduction to the fundamental concepts and principles of requirements engineering, this guide offers a comprehensive review of the aim, scope, and role of requirements engineering as well as best practices and flaws to avoid.

  • Shares state-of-the-art techniques for domain analysis, requirements elicitation, risk analysis, conflict management, and more
  • Features in-depth treatment of system modeling in the specific context of engineering requirements
  • Presents various forms of reasoning about models for requirements quality assurance
  • Discusses the transitions from requirements to software specifications to software architecture

In addition, case studies are included that complement the many examples provided in the book in order to show you how the described method and techniques are applied in practical situations.

Read More Show Less

Product Details

  • ISBN-13: 9780470012703
  • Publisher: Wiley
  • Publication date: 3/23/2009
  • Edition description: New Edition
  • Edition number: 1
  • Pages: 712
  • Product dimensions: 7.40 (w) x 9.20 (h) x 1.60 (d)

Meet the Author

Axel van Lamsweerde is Professor in the Department of Computing Science at the Université catholique de Louvain (UCL), Belgium. He recently received the ACM SIGSOFT Outstanding Research Award for "deep and lasting contributions to the theory and practice of requirements engineering".

Read More Show Less

Table of Contents



Part I: Fundamentals of Requirements Engineering.

1. Setting the Scene.

1.1 What is requirements engineering?

1.2 Why engineer requirements?

1.3 Obstacles to good requirements engineering practice.

1.4 Agile development processes and requirementsengineering.


Notes and Further Reading.


2. Domain Analysis and Requirements Elicitation.

2.1 Identifying stakeholders and interacting with them.

2.2 Artefact-driven elicitation techniques.

2.3 Stakeholder-driven elicitation techniques.

2.4 Conclusion.


Notes and Further Reading.


3. Requirements Evaluation.

3.1 Inconsistency management.

3.2 Risk analysis.

3.3 Evaluating alternative options for decision making.

3.4 Requirements prioritization.

3.5 Conclusion.


Notes and Further Reading.


4. Requirements Specification and Documentation.

4.1 Free documentation in unrestricted natural language.

4.2 Disciplined documentation in structured naturallanguage.

4.3 Use of diagrammatic notations.

4.4 Formal specification.

4.5 Conclusion.


Notes and Further Reading.


5. Requirements Quality Assurance.

5.1 Requirements inspections and reviews.

5.2 Queries on a requirement database.

5.3 Requirements validation by specification animation.

5.4 Requirements verification through formal checks.

5.5 Conclusion.


Notes and Further Reading.


6. Requirements Evolution.

6.1 The time-space dimensions of evolution: Revisions andvariants.

6.2 Change anticipation.

6.3 Traceability management for evolution support.

6.4 Change control.

6.5 Runtime monitoring of requirements and assumptions fordynamic change.

6.6 Conclusion.


Notes and Further Reading.


7. Goal-Orientation in Requirements Engineering.

7.1 What are goals?

7.2 The granularity of goals and their relationship torequirements and assumptions.

7.3 Goal types and categories.

7.4 The central role of goals in the requirements engineeringprocess.

7.5 Where are goals coming from?

7.6 The relationship of goals to other requirements-relatedproducts and processes.


Notes and Further Reading.


Part II: Building System Models for RequirementsEngineering.

8. Moddeling System Objectives with Goal Diagrams.

8.1 Goal features as model annotations.

8.2 Goal refinement.

8.3 Representing conflicts among goals.

8.4 Connecting the goal model with other system views.

8.5 Modelling alternative options.

8.6 Goal diagrams as AND/OR graphs.

8.7 Documenting goal refinements and assignments withannotations.

8.8 Building goal models: Heuristic rules and reusablepatterns.


Notes and Further Reading.


9. Anticipating What Could Go Wrong: Risk Analysis on GoalModels.

9.1 Goal obstruction by obstacles.

9.2 Modelling obstacles.

9.3 Obstacle analysis for a more robust goal model.


Notes and Further Reading.


10. Moddeling Conceptual Objects with Class Diagrams.

10.1 Representing domain concepts by conceptual objects.

10.2 Entities.

10.3 Associations.

10.4 Attributes.

10.5 Built-in associations for structuring object models.

10.6 More on class diagrams.

10.7 Heuristic rules for building object models.


Notes and Further Reading.


11. Moddeling System Agents and Responsibilities.

11.1 What are agents?

11.2 Characterizing system agents.

11.3 Representing agent models.

11.4 Refinement of abstract agents.

11.5 Building agent models.


Notes and Further Reading.


12. Moddeling System Operations.

12.1 What are operations?

12.2 Characterizing system operations.

12.3 Goal operationalization.

12.4 Goals, agents, objects and operations: The Sematicpicture.

12.5 Representing operation models.

12.6 Building operation models.


Notes and Further Reading.


13. Moddeling System Behaviors.

13.1 Modelling instance behaviours.

13.2 Modelling class behaviours.

13.3 Building behaviour models.


Notes and Further Reading.


14. Integrating Multiple System Views.

14.1 A meta-model for view integration.

14.2 Inter-view consistency rules.

14.3 Grouping related view fragments into packages.


Notes and Further Reading.


15. A Goal-Oriented Model Building Method in Action.

15.1 Modelling the system-as-is.

15.2 Modelling the system-to-be.

15.3 Handling model variants for product lines.


Notes and Further Reading.


Part III: Reasoning About System Models.

16. Semi-Formal Reasoning for Model Analysis andExploitation.

16.1 Query-based analysis of the model database.

16.2 Semi-formal analysis of goal-oriented models.

16.3 Reasoning about alternative options.

16.4 Model-driven generation of the requirements document.

16.5 Beyond RE: From goal-oriented requirements to softwarearchitecture.


Notes and Further Reading.


17. Formal Specification of System Models.

17.1 A real-time temporal logic for specifying modelannotations.

17.2 Specifying goals in the goal model.

17.3 Specifying descriptive properties in the object model.

17.4 Specifying operationalizations in the operation model.

17.5 Back to the system’s semantic picture.


Notes and Further reading.


18. Formal Reasoning for Specification Construction andAnalysis.

18.1 Checking goal refinements.

18.2 Deriving goal operationalizations.

18.3 Generating obstacles for risk analysis.

18.4 Generating anti-goals for security analysis.

18.5 Formal conflict analysis.

18.6 Synthesizing behaviour models for animation and modelchecking.


Notes and Further Reading.





Requirements Document Generated from a Goal-Oriented Model.


Read More Show Less

Customer Reviews

Be the first to write a review
( 0 )
Rating Distribution

5 Star


4 Star


3 Star


2 Star


1 Star


Your Rating:

Your Name: Create a Pen Name or

Barnes & Review Rules

Our reader reviews allow you to share your comments on titles you liked, or didn't, with others. By submitting an online review, you are representing to Barnes & that all information contained in your review is original and accurate in all respects, and that the submission of such content by you and the posting of such content by Barnes & does not and will not violate the rights of any third party. Please follow the rules below to help ensure that your review can be posted.

Reviews by Our Customers Under the Age of 13

We highly value and respect everyone's opinion concerning the titles we offer. However, we cannot allow persons under the age of 13 to have accounts at or to post customer reviews. Please see our Terms of Use for more details.

What to exclude from your review:

Please do not write about reviews, commentary, or information posted on the product page. If you see any errors in the information on the product page, please send us an email.

Reviews should not contain any of the following:

  • - HTML tags, profanity, obscenities, vulgarities, or comments that defame anyone
  • - Time-sensitive information such as tour dates, signings, lectures, etc.
  • - Single-word reviews. Other people will read your review to discover why you liked or didn't like the title. Be descriptive.
  • - Comments focusing on the author or that may ruin the ending for others
  • - Phone numbers, addresses, URLs
  • - Pricing and availability information or alternative ordering information
  • - Advertisements or commercial solicitation


  • - By submitting a review, you grant to Barnes & and its sublicensees the royalty-free, perpetual, irrevocable right and license to use the review in accordance with the Barnes & Terms of Use.
  • - Barnes & reserves the right not to post any review -- particularly those that do not follow the terms and conditions of these Rules. Barnes & also reserves the right to remove any review at any time without notice.
  • - See Terms of Use for other conditions and disclaimers.
Search for Products You'd Like to Recommend

Recommend other products that relate to your review. Just search for them below and share!

Create a Pen Name

Your Pen Name is your unique identity on It will appear on the reviews you write and other website activities. Your Pen Name cannot be edited, changed or deleted once submitted.

Your Pen Name can be any combination of alphanumeric characters (plus - and _), and must be at least two characters long.

Continue Anonymously

    If you find inappropriate content, please report it to Barnes & Noble
    Why is this product inappropriate?
    Comments (optional)