001448646 000__ 03647cam\a2200469\i\4500
001448646 001__ 1448646
001448646 003__ OCoLC
001448646 005__ 20230310004249.0
001448646 006__ m\\\\\o\\d\\\\\\\\
001448646 007__ cr\cn\nnnunnun
001448646 008__ 220809s2022\\\\sz\\\\\\o\\\\\000\0\eng\d
001448646 019__ $$a1338198632$$a1338836757
001448646 020__ $$a9783031067396$$q(electronic bk.)
001448646 020__ $$a3031067398$$q(electronic bk.)
001448646 020__ $$z9783031067389
001448646 020__ $$z303106738X
001448646 0247_ $$a10.1007/978-3-031-06739-6$$2doi
001448646 035__ $$aSP(OCoLC)1340046845
001448646 040__ $$aGW5XE$$beng$$erda$$epn$$cGW5XE$$dYDX$$dEBLCP$$dUKAHL$$dOCLCQ
001448646 049__ $$aISEA
001448646 050_4 $$aQA76.758
001448646 08204 $$a005.1$$223/eng/20220809
001448646 1001_ $$aMeyer, Bertrand,$$d1950-$$eauthor.$$1https://isni.org/isni/0000000109003927
001448646 24510 $$aHandbook of requirements and business analysis /$$cBertrand Meyer.
001448646 264_1 $$aCham :$$bSpringer,$$c2022.
001448646 300__ $$a1 online resource (1 volume)
001448646 336__ $$atext$$btxt$$2rdacontent
001448646 337__ $$acomputer$$bc$$2rdamedia
001448646 338__ $$aonline resource$$bcr$$2rdacarrier
001448646 5050_ $$a1. Requirements: basic concepts and definitions -- 2. Requirements: general principles -- 3. Standard Plan for requirements -- 4. Requirements quality and verification -- 5. How to write requirements -- 6. How to gather requirements -- 7. Scenarios: use cases, user stories -- 8. Object-oriented requirements -- 9. Benefiting from formal methods -- 10. Abstract data types -- 11. Are my requirements complete? -- 12. Requirements in the software lifecycle.
001448646 506__ $$aAccess limited to authorized users.
001448646 520__ $$aMeyers Handbook of Requirements and Business Analysis is a comprehensive treatise providing the reader with all the principles and techniques necessary to produce effective requirements. Even the best design, implementation and verification are worthless if they are the solution to the wrong problem. Defining the problem properly is the task of requirements, also known as business analysis. To be successful, a project must apply to requirements the same engineering standards as to other parts of system construction. The Handbook presents a holistic view of requirements including four elements or PEGS: Project, Environment, Goals and System. One of its principal contributions is the definition of a Standard Plan for requirements documents, consisting of the four corresponding books and replacing the structure of the obsolete IEEE 1998 standard. The text covers both classical requirements techniques and advanced topics. The successive chapters address: fundamental concepts and definitions; requirements principles; the Standard Plan for requirements; how to write good requirements; how to gather requirements; scenario techniques (use cases, user stories); object-oriented requirements; how to take advantage of formal methods; abstract data types; and the place of requirements in the software lifecycle. The Handbook is suitable both as a practical guide for industry and as a textbook, with over 50 exercises and supplementary material available from the books site, including slides and links to video lectures (MOOCs).
001448646 588__ $$aDescription based on print version record.
001448646 650_0 $$aSoftware engineering.
001448646 655_0 $$aElectronic books.
001448646 77608 $$iPrint version:$$aMeyer, Bertrand, 1950-$$tHandbook of requirements and business analysis.$$dCham : Springer, 2022$$z9783031067389$$w(OCoLC)1328014288
001448646 852__ $$bebk
001448646 85640 $$3Springer Nature$$uhttps://univsouthin.idm.oclc.org/login?url=https://link.springer.com/10.1007/978-3-031-06739-6$$zOnline Access$$91397441.1
001448646 909CO $$ooai:library.usi.edu:1448646$$pGLOBAL_SET
001448646 980__ $$aBIB
001448646 980__ $$aEBOOK
001448646 982__ $$aEbook
001448646 983__ $$aOnline
001448646 994__ $$a92$$bISE