Abstract
Writing good requirements is difficult. Interpreting bad requirements is even tougher. In this section we will define requirements from a couple of different perspectives, discuss how the different perspectives work together, and list some general recommendations about each. We will also cover the roles the developers play in the requirements process and why developing and interpreting requirements are important skills. As with many of the topics in this book, there are countless permutations of the concepts we are trying to cover and other works that are dedicated solely to the topic of requirements. Here we present a general overview with an emphasis on aspects that are important to developers from an enterprise or large organization perspective.
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsAuthor information
Authors and Affiliations
Rights and permissions
Copyright information
© 2014 Edward Crookshanks
About this chapter
Cite this chapter
Crookshanks, E. (2014). Software Requirements. In: Practical Software Development Techniques. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-0728-4_8
Download citation
DOI: https://doi.org/10.1007/978-1-4842-0728-4_8
Published:
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4842-0729-1
Online ISBN: 978-1-4842-0728-4
eBook Packages: Professional and Applied ComputingProfessional and Applied Computing (R0)Apress Access Books