Skip to main content
SpringerLink
Log in

Requirements Engineering

  • Chapter
  • First Online:
Concise Guide to Software Engineering

Part of the book series: Undergraduate Topics in Computer Science ((UTICS))

Abstract

This chapter discusses requirements engineering and discusses activities such as requirements gathering, requirements elicitation, requirements analysis, requirements management, and requirements verification and validation.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Log in via an institution
Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 49.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Notes

  1. 1.

    It is desirable that the user or system requirements describe what is to be provided rather than how it is to be provided. That is, in theory, design or implementation information should be excluded in the specification. However, in practice, it is sometimes difficult to exclude all design information (e.g. consider the case where a system needs to work with an existing system).

  2. 2.

    It may involve getting end-users to talk about how they currently do a certain task and brainstorming on better ways in which the proposed system can do the same task.

  3. 3.

    Conflicts are inevitable as stakeholders will have different needs, and so discussion and negotiation are required to resolve these conflicts and achieve consensus.

  4. 4.

    Essentially, the mathematical language provides the facility to prove that certain properties are true of the specification, and that certain undesirable properties are false in the specification.

  5. 5.

    This principle is named after the medieval philosopher, William of Ockham.

References

  1. I. Jacobson, G. Booch, J. Rumbaugh, The Unified Software Modelling Language User Guide (Addison-Wesley, Reading, 1999)

    Google Scholar 

  2. G. O’Regan, A Practical Approach to Software Quality (Springer, New York, 2002)

    Google Scholar 

  3. T. Kuhn, The Structure of Scientific Revolutions (University of Chicago Press, Chicago, 1970)

    Google Scholar 

  4. M.M.A. Airchinnigh, Conceptual models and computing. PhD Thesis. Department of Computer Science, University of Dublin. Trinity College, Dublin, 1990

    Google Scholar 

Download references

Author information

Authors and Affiliations

  1. SQC Consulting, Cork, Ireland

    Gerard O’Regan

Authors
  1. Gerard O’Regan
    View author publications

    You can also search for this author in PubMed Google Scholar

Corresponding author

Correspondence to Gerard O’Regan .

Rights and permissions

Reprints and permissions

Copyright information

© 2017 Springer International Publishing AG

About this chapter

Cite this chapter

O’Regan, G. (2017). Requirements Engineering. In: Concise Guide to Software Engineering. Undergraduate Topics in Computer Science. Springer, Cham. https://doi.org/10.1007/978-3-319-57750-0_3

Download citation

  • DOI: https://doi.org/10.1007/978-3-319-57750-0_3

  • Published:

  • Publisher Name: Springer, Cham

  • Print ISBN: 978-3-319-57749-4

  • Online ISBN: 978-3-319-57750-0

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics

Search

Navigation