Concurrent users
Unlimited
Authorized users
Authorized users
Document Delivery Supplied
Can lend chapters, not whole ebooks
Title
Hardware and software projects troubleshooting : how effective requirements writing can save the day / George Koelsch.
Edition
Second edition.
ISBN
9781484298305 (electronic bk.)
1484298306 (electronic bk.)
9781484298299
1484298292
Published
Berkeley, CA : Apress, 2023.
Language
English
Description
1 online resource (xxv, 562 pages) : illustrations
Other Standard Identifiers
10.1007/978-1-4842-9830-5 doi
Call Number
TA180
Dewey Decimal Classification
624.068
Summary
Learn how to create good requirements when designing hardware and software systems. While this book emphasizes writing traditional "shall" statements, it also provides guidance on use case design and creating user stories in support of agile methodologies. The book surveys modelling techniques and various tools that support requirements collection and analysis. You'll learn to manage requirements, including discussions of document types and digital approaches using spreadsheets, generic databases, and dedicated requirements tools. Good, clear examples are presented, many related to real-world work the author has performed during his career. More importantly, you will learn how these techniques can prevent the problems that occur during requirements development. Most of all, you will learn how good requirements governance will greatly increase the success of development projects by getting all people involved to eliminate the adverse impacts to requirements throughout the development lifecycle. Hardware and Software Projects Troubleshooting covers techniques for defining user needs, so you can determine which combination of approaches to use for your projects. You'll also learn how to analyze the different development methodologies so that you can determine the advantages and disadvantages of different requirements approaches and implement them correctly as your needs evolve. Unlike most requirements books, this one teaches writing both hardware and software requirements because many projects include both areas. To exemplify this approach, two example projects are developed throughout the book, one focusing on hardware, and the other on software. You will: Focus on how to eliminate or mitigate requirements problems Understand the 14 techniques for capturing all requirements Address software and hardware needs; because most projects involve both Ensure all statements meet the 16 attributes of a good requirement Differentiate the 19 different functional types of requirements, and the 31 non-functional types Write requirements properly based on extensive examples of good 'shall' statements, user stories, and use cases Employ modelling techniques to mitigate the imprecision of words Install requirements governance to significantly improve project success.
Bibliography, etc. Note
Includes bibliographical references and index.
Access Note
Access limited to authorized users.
Source of Description
Online resource; title from PDF title page (SpringerLink, viewed December 15, 2023).
Available in Other Form
Print version: 9781484298299
Introduction.-Part I: The Foundation of Requirements
1. The Importance of Requirements
2. What Makes a Good Requirement?
3. Specialized Language
.-Part II: Types of Requirements
4. Functional Requirements
5. Non-Functional Requirements
6. Lists of Items and the Order of Steps and Data Elements
7. Data Interfaces and Documents
8. Physical Requirements.-Part III: Cradle to Grave Requirements
9. How to Collect Requirements
10. User Interface Requirements
11. Managing Requirements.-Part IV: Alternatives to Shall Requirements
12. Supplementing or Replacing Standard Requirements
13. User Stories
14. Use Cases
15. Requirements Governance - 16. Revisiting Requirement Problems and Their Solutions.-Part V: Appendixes
17. A: Acronyms and Abbreviations
18. B: Requirements Documents
19. C: Section 508 Compliance
20: Glossary
21. Bibliography.
