國立虎尾科技大學 |

Requirements writing for system engineering

紀錄類型:	書目-語言資料,印刷品 : Monograph/item
正題名/作者:	Requirements writing for system engineering/ by George Koelsch.
作者:	Koelsch, George.
出版者:	Berkeley, CA :Apress : : 2016.,
面頁冊數:	xxiii, 400 p. :ill., digital ; : 24 cm.;
Contained By:	Springer eBooks
標題:	Requirements engineering. -
電子資源:	http://dx.doi.org/10.1007/978-1-4842-2099-3
ISBN:	9781484220993

Requirements writing for system engineering
Koelsch, George.

Requirements writing for system engineering[electronic resource] /by George Koelsch. - Berkeley, CA :Apress :2016. - xxiii, 400 p. :ill., digital ;24 cm.

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. Revisiting Requirement Problems and Their Solutions -- Part V: Appendixes -- 16. A: Acronyms and Abbreviations -- 17. B: Requirements Documents -- 18. C: Section 508 Compliance -- 19: Glossary -- 20. Bibliography.

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 modeling 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 done during his career. Requirements Writing for System Engineering 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 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, Requirements Writing for System Engineering 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. This book Presents many techniques for capturing requirements. Demonstrates gap analysis to find missing requirements. Shows how to address both software and hardware, as most projects involve both. Provides extensive examples of "shall" statements, user stories, and use cases. Explains how to supplement or replace traditional requirement statements with user stories and use cases that work well in agile development environments.

ISBN: 9781484220993

Standard No.: 10.1007/978-1-4842-2099-3doiSubjects--Topical Terms:

878783
Requirements engineering.

LC Class. No.: QA76.758

Dewey Class. No.: 005.12

Requirements writing for system engineering
LDR:03590nam a2200313 a 4500 001 867875
003 DE-He213
005 20161020092135.0
006 m d
007 cr nn 008maaau
008 170720s2016 cau s 0 eng d
020 $a 9781484220993 $q (electronic bk.)
020 $a 9781484220986 $q (paper)
024 7 $a 10.1007/978-1-4842-2099-3 $2 doi
035 $a 978-1-4842-2099-3
040 $a GP $c GP
041 0 $a eng
050 4 $a QA76.758
072 7 $a UMZ $2 bicssc
072 7 $a COM051230 $2 bisacsh
082 0 4 $a 005.12 $2 23
090 $a QA76.758 $b .K77 2016
100 1 $a Koelsch, George. $3 1115036
245 1 0 $a Requirements writing for system engineering $h [electronic resource] / $c by George Koelsch.
260 $a Berkeley, CA : $b Apress : $b Imprint: Apress, $c 2016.
300 $a xxiii, 400 p. : $b ill., digital ; $c 24 cm.
505 0 $a 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. Revisiting Requirement Problems and Their Solutions -- Part V: Appendixes -- 16. A: Acronyms and Abbreviations -- 17. B: Requirements Documents -- 18. C: Section 508 Compliance -- 19: Glossary -- 20. Bibliography.
520 $a 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 modeling 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 done during his career. Requirements Writing for System Engineering 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 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, Requirements Writing for System Engineering 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. This book Presents many techniques for capturing requirements. Demonstrates gap analysis to find missing requirements. Shows how to address both software and hardware, as most projects involve both. Provides extensive examples of "shall" statements, user stories, and use cases. Explains how to supplement or replace traditional requirement statements with user stories and use cases that work well in agile development environments.
650 0 $a Requirements engineering. $3 878783
650 0 $a Systems engineering. $3 561164
650 1 4 $a Computer Science. $3 593922
650 2 4 $a Software Engineering. $3 669632
650 2 4 $a Project Management. $3 787187
650 2 4 $a Software Management. $3 1069200
650 2 4 $a Computer System Implementation. $3 669803
650 2 4 $a Management of Computing and Information Systems. $3 593928
710 2 $a SpringerLink (Online service) $3 593884
773 0 $t Springer eBooks
856 4 0 $u http://dx.doi.org/10.1007/978-1-4842-2099-3
950 $a Professional and Applied Computing (Springer-12059)