Engineering and managing software requirements
Our rough guess is there are 119,500 words in this book.
At a pace averaging 250 words per minute, this book will take 7 hours and 58 minutes to read. With a half hour per day, this will take 16 days to read.
How long will it take you?
This book will take an estimated to read at a reading speed averaging words per minute. With 30 minutes per day, this will take to read.
Enter your reading speedYou can take one of our WPM reading speed tests to find your reading speed.
Create a free account to track your reading progress, build your reading list, and set reading goals.
We earn a commission on purchases
Author
Contributions
- Aurum, Aybüke, 1957- - Contributor
- Wohlin, Claes. - Contributor
Publication
2005 - Springer, Berlin
Language
English
Word Count
119,500 words, Guess
Page Count
478 pages
Identifiers
- Open LibraryOL3480574M
- ISBN-103540250433
- OCLC Control Number60320817
- OCLC Control Numberengineeringmanag00auru
- Library of Congress Control Number2005927220
and 2 more
- LibraryThing7708731
- Goodreads1904342
Classifications
- DDC005.12
- LCCQA76.758 .E544 2005
Description
Requirements engineering is the process by which the requirements for software systems are gathered, analyzed, documented, and managed throughout their complete lifecycle. Traditionally it has been concerned with technical goals for, functions of, and constraints on software systems. Aurum and Wohlin, however, argue that it is no longer appropriate for software systems professionals to focus only on functional and non-functional aspects of the intended system and to somehow assume that organizational context and needs are outside their remit. Instead, they call for a broader perspective in order to gain a better understanding of the interdependencies between enterprise stakeholders, processes, and software systems, which would in turn give rise to more appropriate techniques and higher-quality systems. Following an introductory chapter that provides an exploration of key issues in requirements engineering, the book is organized in three parts. Part 1 presents surveys of state-of-the art requirements engineering process research along with critical assessments of existing models, frameworks and techniques. Part 2 addresses key areas in requirements engineering, such as market-driven requirements engineering, goal modeling, requirements ambiguity, and others. Part 3 concludes the book with articles that present empirical evidence and experiences from practices in industrial projects. Its broader perspective gives this book its distinct appeal and makes it of interest to both researchers and practitioners, not only in software engineering but also in other disciplines such as business process engineering and management science.
Subjects
Other Editions
- Engineering and managing software requirements
Similar Books
Reader Reviews
No reviews yet for this book.
Be the first to share your thoughts!