Skip to main content

Define Requirements

  • Chapter
  • First Online:
An Introduction to Design Science
  • 2112 Accesses

Abstract

The second activity of the method framework is Define Requirements. The goal is to identify and outline an artefact that can address the explicated problem and to elicit requirements for this artefact. In other words, the activity addresses the question: What artefact can be a solution for the explicated problem and which requirements for this artefact are important to the stakeholders? This chapter describes how to answer the question using research methods as well as practice-oriented methods. We also introduce a number of generic artefact qualities that can be used for informing requirements elicitation and validation.

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

Access this chapter

eBook
USD 16.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 16.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info
Hardcover Book
USD 69.99
Price excludes VAT (USA)
  • Durable hardcover edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

References

  • Checkland P, Scholes J (1990) Soft systems methodology in practice. Wiley, Chichester

    Google Scholar 

  • Chung L, do Prado Leite JCS (2009) On non-functional requirements in software engineering. In: Borgida AT et al. (eds) Conceptual modeling: foundations and applications. Lecture notes in computer science. Springer, Berlin, pp. 363–379

    Google Scholar 

  • Dick J, Hull E, Jackson K (2017) Requirements engineering, 4th edn. Springer, Berlin

    Book  Google Scholar 

  • Glinz M (2007) On non-functional requirements. In: Requirements engineering conference, 15th IEEE international, pp. 21–26

    Google Scholar 

  • Keil M, Tiwana A (2006) Relative importance of evaluation criteria for enterprise systems: a conjoint study. Inf Syst J 16(3):237–262

    Article  Google Scholar 

  • Pohl K (2010) Requirements engineering: fundamentals, principles, and techniques, 1st edn. Springer, Berlin

    Book  Google Scholar 

  • Sommerville I, Sawyer P (1997) Requirements engineering: a good practice guide, 1st edn. Wiley, New York

    MATH  Google Scholar 

  • Tuunanen T, Peffers K (2018) Population targeted requirements acquisition. Europ J Inf Syst 27(6):686–711

    Article  Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Rights and permissions

Reprints and permissions

Copyright information

© 2021 Springer Nature Switzerland AG

About this chapter

Check for updates. Verify currency and authenticity via CrossMark

Cite this chapter

Johannesson, P., Perjons, E. (2021). Define Requirements. In: An Introduction to Design Science. Springer, Cham. https://doi.org/10.1007/978-3-030-78132-3_6

Download citation

  • DOI: https://doi.org/10.1007/978-3-030-78132-3_6

  • Published:

  • Publisher Name: Springer, Cham

  • Print ISBN: 978-3-030-78131-6

  • Online ISBN: 978-3-030-78132-3

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics