001484759 000__ 05249cam\\2200553\i\4500
001484759 001__ 1484759
001484759 003__ OCoLC
001484759 005__ 20240117003336.0
001484759 006__ m\\\\\o\\d\\\\\\\\
001484759 007__ cr\un\nnnunnun
001484759 008__ 231215s2023\\\\caua\\\\ob\\\\001\0\eng\d
001484759 019__ $$a1412643249$$a1413377716
001484759 020__ $$a9781484298305$$q(electronic bk.)
001484759 020__ $$a1484298306$$q(electronic bk.)
001484759 020__ $$z9781484298299
001484759 020__ $$z1484298292
001484759 0247_ $$a10.1007/978-1-4842-9830-5$$2doi
001484759 035__ $$aSP(OCoLC)1414374570
001484759 040__ $$aGW5XE$$beng$$erda$$epn$$cGW5XE$$dEBLCP$$dORMDA$$dYDX$$dOCLKB$$dOCLCO
001484759 049__ $$aISEA
001484759 050_4 $$aTA180
001484759 08204 $$a624.068$$223/eng/20231215
001484759 1001_ $$aKoelsch, George,$$eauthor.
001484759 24510 $$aHardware and software projects troubleshooting :$$bhow effective requirements writing can save the day /$$cGeorge Koelsch.
001484759 250__ $$aSecond edition.
001484759 264_1 $$aBerkeley, CA :$$bApress,$$c2023.
001484759 300__ $$a1 online resource (xxv, 562 pages) :$$billustrations
001484759 336__ $$atext$$btxt$$2rdacontent
001484759 337__ $$acomputer$$bc$$2rdamedia
001484759 338__ $$aonline resource$$bcr$$2rdacarrier
001484759 504__ $$aIncludes bibliographical references and index.
001484759 5050_ $$aIntroduction.-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.
001484759 506__ $$aAccess limited to authorized users.
001484759 520__ $$aLearn 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.
001484759 588__ $$aOnline resource; title from PDF title page (SpringerLink, viewed December 15, 2023).
001484759 650_6 $$aIngénierie des exigences.
001484759 650_6 $$aIngénierie des systèmes.
001484759 650_0 $$aRequirements engineering.$$xInsurance requirements$$0(DLC)sh 85041668
001484759 650_0 $$aSystems engineering.
001484759 655_0 $$aElectronic books.
001484759 77608 $$iPrint version: $$z1484298292$$z9781484298299$$w(OCoLC)1395067871
001484759 852__ $$bebk
001484759 85640 $$3Springer Nature$$uhttps://univsouthin.idm.oclc.org/login?url=https://link.springer.com/10.1007/978-1-4842-9830-5$$zOnline Access$$91397441.1
001484759 909CO $$ooai:library.usi.edu:1484759$$pGLOBAL_SET
001484759 980__ $$aBIB
001484759 980__ $$aEBOOK
001484759 982__ $$aEbook
001484759 983__ $$aOnline
001484759 994__ $$a92$$bISE