Picture 1 of 1
Picture 1 of 1
Hardware and Software Projects Troubleshooting : How Effective Requirements Writing Can Save the Day by George Koelsch (2023, Trade Paperback)
Bargain Book Stores (1135733)
99.2% positive feedback
Price:
$63.48
Free shipping
Returns:
30 days returns. Seller pays for return shipping.
Condition:
Your Privacy. ISBN: 9781484298299. Your source for quality books at reduced prices. Condition Guide. Item Availability.
- Buy It NowHardware and Software Projects Troubleshooting: How Effective Requirements Writi
Oops! Looks like we're having trouble connecting to our server.
Refresh your browser window to try again.
About this product
Product Identifiers
PublisherApress L. P.
ISBN-101484298292
ISBN-139781484298299
eBay Product ID (ePID)9062508766
Product Key Features
Number of PagesXxv, 562 Pages
Publication NameHardware and Software Projects Troubleshooting : How Effective Requirements Writing Can Save the Day
LanguageEnglish
Publication Year2023
SubjectSoftware Development & Engineering / General, Project Management, General, Software Development & Engineering / Project Management
TypeTextbook
Subject AreaMathematics, Computers, Business & Economics
AuthorGeorge Koelsch
FormatTrade Paperback
Dimensions
Item Weight38.9 Oz
Item Length10 in
Item Width7 in
Additional Product Features
Edition Number2
Dewey Edition23
Number of Volumes1 vol.
IllustratedYes
Dewey Decimal005.14
Table Of ContentIntroduction.-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.
SynopsisLearn 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 developmentlifecycle. 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. What You Will Learn 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 meetthe 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 Who This Book Is For Requirements engineers who want to improve and master their craft, as well as students and those employed in government or other organizations at all levels.
LC Classification NumberQA76.758
All listings for this product
Be the first to write a review
