Wentworth
Institute of Technology
Requirements Engineering for Software and Systems
Solid requirements engineering has increasingly been recognized as the key to improved, on-time, and on-budget delivery of software and systems projects. New software tools are emerging that are empowering practicing engineers to improve their requirements engineering habits. However, these tools ar...
Saved in:
| Main Author: | |
|---|---|
| Other Authors: | |
| Format: | Electronic eBook |
| Language: | English |
| Published: |
Milton :
Auerbach Publishers, Incorporated,
2009.
|
| Edition: | 4th ed. |
| Series: | Applied Software Engineering Ser.
|
| Subjects: | |
| Online Access: |
Full text (Wentworth users only) |
MARC
| LEADER | 00000nam a2200000uu 4500 | ||
|---|---|---|---|
| 001 | w3013276 | ||
| 005 | 20230831153822.0 | ||
| 006 | m o d | ||
| 007 | cr cnu---unuuu | ||
| 008 | 220326s2009 xx o ||| 0 eng d | ||
| 019 | |a 1305840320 | ||
| 035 | |a (OCoLC)1306055224 |z (OCoLC)1305840320 | ||
| 035 | |a (OCoLC)on1306055224 | ||
| 037 | |a 9781000593815 |b O'Reilly Media | ||
| 040 | |a EBLCP |b eng |c EBLCP |d ORMDA | ||
| 049 | |a WENN | ||
| 049 | |a WENN | ||
| 050 | 4 | |a QA76.758 | |
| 082 | 0 | 4 | |a 005.1 |
| 100 | 1 | |a Laplante, Phillip A. | |
| 245 | 1 | 0 | |a Requirements Engineering for Software and Systems |h [electronic resource]. |
| 250 | |a 4th ed. | ||
| 260 | |a Milton : |b Auerbach Publishers, Incorporated, |c 2009. | ||
| 300 | |a 1 online resource (429 p.). | ||
| 336 | |a text |b txt |2 rdacontent | ||
| 337 | |a computer |b c |2 rdamedia | ||
| 338 | |a online resource |b cr |2 rdacarrier | ||
| 490 | 1 | |a Applied Software Engineering Ser. | |
| 500 | |a Description based upon print version of record. | ||
| 500 | |a 4 Writing the Requirements Document. | ||
| 505 | 0 | |a Cover -- Half Title -- Title Page -- Copyright Page -- Table of Contents -- Preface -- Acknowledgments -- Authors -- 1 Introduction to Requirements Engineering -- Motivation -- What Is Requirements Engineering? -- You Probably Don't Do Enough Requirements Engineering -- What Are Requirements? -- Requirements vs. Features vs. Goals -- Requirements Classifications -- Requirements Level Classification -- Requirements Specifications Types -- Functional Requirements -- Nonfunctional Requirements -- Domain Requirements -- Domain Vocabulary Understanding -- Requirements Engineering Activities | |
| 505 | 8 | |a Requirements Elicitation/Discovery -- Requirements Analysis and Agreement -- Requirements Representation -- Requirements Validation -- Requirements Management -- Bodies of Knowledge -- The Requirements Engineer -- Requirements Engineer Roles -- Requirements Engineer as Software or Systems Engineer -- Requirements Engineer as Subject Matter Expert -- Requirements Engineer as Architect -- Requirements Engineer as Business Process Expert -- Ignorance as Virtue -- Role of the Customer -- Problems with Traditional Requirements Engineering -- Complexity -- Gold-Plating and Ridiculous Requirements | |
| 505 | 8 | |a Obsolete Requirements -- Four Dark Corners -- Difficulties in Enveloping System Behavior -- The Danger of "All" in Specifications -- Exercises -- References -- 2 Preparing for Requirements Elicitation -- Product Business Goals and Mission Statements -- Encounter with a Customer -- Identifying the System Boundaries -- Context Diagrams -- Stakeholders -- Negative Stakeholders -- Stakeholder Identification -- Stakeholder Identification Questions -- Rich Pictures -- Stakeholder/User Classes -- Stakeholders vs. Use Case Actors -- User Characteristics -- Customer Wants and Needs | |
| 505 | 8 | |a What Do Customers Want? -- What Don't Customers Want? -- Why Do Customers Change Their Minds? -- Stakeholder Prioritization -- Communicating with Customers and Other Stakeholders -- Managing Expectations -- Stakeholder Negotiations -- Uncovering Stakeholder Goals -- Exercises -- Note -- References -- 3 Requirements Elicitation -- Introduction -- Requirements Elicitation -- First Step -- Elicitation Techniques Survey -- Brainstorming -- Card Sorting -- Crowdsourcing -- Designer as Apprentice -- Domain Analysis -- Ethnographic Observation -- Goal-Based Approaches -- Group Work -- Interviews | |
| 505 | 8 | |a Introspection -- Joint Application Design -- Laddering -- Protocol Analysis -- Prototyping -- Quality Function Deployment -- Questionnaires/Surveys -- Repertory Grids -- Reverse Engineering -- Scenarios -- Task Analysis -- Use Cases -- User Stories -- Viewpoints -- Workshops -- Eliciting Nonfunctional Requirements -- Elicitation Summary -- Which Combination of Requirements Elicitation Techniques Should Be Used? -- Prevalence of Requirements Elicitation Techniques -- Eliciting Hazards -- Misuse Cases -- Antimodels -- Formal Methods -- Exercises -- Note -- References | |
| 520 | |a Solid requirements engineering has increasingly been recognized as the key to improved, on-time, and on-budget delivery of software and systems projects. New software tools are emerging that are empowering practicing engineers to improve their requirements engineering habits. However, these tools are not usually easy to use without significant training. Requirements Engineering for Software and Systems, Fourth Edition is intended to provide a comprehensive treatment of the theoretical and practical aspects of discovering, analyzing, modeling, validating, testing, and writing requirements for systems of all kinds, with an intentional focus on software-intensive systems. It brings into play a variety of formal methods, social models, and modern requirements writing techniques to be useful to practicing engineers. The book is intended for professional software engineers, systems engineers, and senior and graduate students of software or systems engineering. Since the first edition, there have been made many changes and improvements to this textbook. Feedback from instructors, students, and corporate users was used to correct, expand, and improve the materials. The fourth edition features two newly added chapters: "On Non-Functional Requirements" and "Requirements Engineering: Road Map to the Future." The latter provides a discussion on the relationship between requirements engineering and such emerging and disruptive technologies as Internet of Things, Cloud Computing, Blockchain, Artificial Intelligence, and Affective Computing. All chapters of the book were significantly expanded with new materials that keep the book relevant to current industrial practices. Readers will find expanded discussions on new elicitation techniques, agile approaches (e.g., Kanpan, SAFe, and DEVOps), requirements tools, requirements representation, risk management approaches, and functional size measurement methods. The fourth edition also has significant additions of vignettes, exercises, and references. Another new feature is scannable QR codes linked to sites containing updates, tools, videos, and discussion forums to keep readers current with the dynamic field of requirements engineering. | ||
| 650 | 0 | |a Software engineering. | |
| 650 | 0 | |a System design. | |
| 650 | 0 | |a Engineering systems |x Specifications. | |
| 650 | 0 | |a Computer software |x Specifications. | |
| 650 | 0 | |a Requirements engineering. | |
| 700 | 1 | |a Kassab, Mohamad H. | |
| 776 | 0 | 8 | |i Print version: |a Laplante, Phillip A. |t Requirements Engineering for Software and Systems |d Milton : Auerbach Publishers, Incorporated,c2009 |z 9780367654528 |
| 830 | 0 | |a Applied Software Engineering Ser. | |
| 951 | |a 3013276 | ||
| 994 | |a 92 |b WEN | ||
| 999 | f | f | |i 5a1fd925-9d3a-5754-8b95-517b1aa837ad |s 20a72677-a747-537c-b2a7-1b5587109b11 |t 0 |
| 952 | f | f | |a Wentworth Institute of Technology |b Main Campus |c Wentworth Library |d Ebooks |t 0 |e Safari |h Other scheme |
| 856 | 4 | 0 | |t 0 |u https://go.oreilly.com/wentworth-institute-of-technology/library/view/-/9781000593815/?ar |y Full text (Wentworth users only) |