Cargando…
Requirements writing for system engineering /
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 techniq...
| Clasificación: | Libro Electrónico |
|---|---|
| Autor principal: | |
| Formato: | Electrónico eBook |
| Idioma: | Inglés |
| Publicado: |
[Berkeley, CA] :
Apress,
2016.
|
| Colección: | 2016 Springer EBA Collection.
|
| Temas: | |
| Acceso en línea: | Texto completo (Requiere registro previo con correo institucional) |
MARC
| LEADER | 00000cam a2200000 i 4500 | ||
|---|---|---|---|
| 001 | OR_ocn961454188 | ||
| 003 | OCoLC | ||
| 005 | 20231017213018.0 | ||
| 006 | m o d | ||
| 007 | cr cnu---unuuu | ||
| 008 | 161029s2016 cau ob 001 0 eng d | ||
| 040 | |a EBLCP |b eng |e pn |c EBLCP |d YDX |d GW5XE |d N$T |d STF |d OCLCQ |d UPM |d COO |d OCLCF |d IDB |d IOG |d OTZ |d UAB |d K6U |d IAD |d JBG |d ICW |d MERUC |d ILO |d ICN |d LIV |d ESU |d OCLCQ |d VT2 |d U3W |d REB |d D6H |d VVB |d KSU |d INT |d AU@ |d WYU |d LEAUB |d LQU |d OCLCQ |d UKAHL |d BRF |d OCLCO |d OCLCQ |d IDEBK |d UMI |d CEF |d DEBBG |d UKMGB |d GZN |d DCT | ||
| 015 | |a GBB8L6585 |2 bnb | ||
| 016 | 7 | |a 019127023 |2 Uk | |
| 019 | |a 961205218 |a 962434709 |a 964904061 |a 965707728 |a 967622365 |a 968205794 |a 1005802433 |a 1011951476 |a 1048173053 |a 1056938031 |a 1066634638 |a 1086431595 |a 1103274259 |a 1105191942 |a 1204059275 | ||
| 020 | |a 9781484220993 |q (electronic bk.) | ||
| 020 | |a 1484220994 |q (electronic bk.) | ||
| 020 | |z 9781484220986 | ||
| 020 | |z 1484220986 | ||
| 024 | 7 | |a 10.1007/978-1-4842-2099-3 |2 doi | |
| 024 | 8 | |a 10.1007/978-1-4842-2 | |
| 029 | 1 | |a AU@ |b 000058910105 | |
| 029 | 1 | |a AU@ |b 000059802119 | |
| 029 | 1 | |a AU@ |b 000061961732 | |
| 029 | 1 | |a AU@ |b 000072975092 | |
| 029 | 1 | |a CHNEW |b 000913028 | |
| 029 | 1 | |a GBVCP |b 897166094 | |
| 029 | 1 | |a UKMGB |b 019127023 | |
| 035 | |a (OCoLC)961454188 |z (OCoLC)961205218 |z (OCoLC)962434709 |z (OCoLC)964904061 |z (OCoLC)965707728 |z (OCoLC)967622365 |z (OCoLC)968205794 |z (OCoLC)1005802433 |z (OCoLC)1011951476 |z (OCoLC)1048173053 |z (OCoLC)1056938031 |z (OCoLC)1066634638 |z (OCoLC)1086431595 |z (OCoLC)1103274259 |z (OCoLC)1105191942 |z (OCoLC)1204059275 | ||
| 037 | |a 974915 |b MIL | ||
| 050 | 4 | |a QA76.758 | |
| 072 | 7 | |a COM |x 013000 |2 bisacsh | |
| 072 | 7 | |a COM |x 014000 |2 bisacsh | |
| 072 | 7 | |a COM |x 018000 |2 bisacsh | |
| 072 | 7 | |a COM |x 067000 |2 bisacsh | |
| 072 | 7 | |a COM |x 032000 |2 bisacsh | |
| 072 | 7 | |a COM |x 037000 |2 bisacsh | |
| 072 | 7 | |a COM |x 052000 |2 bisacsh | |
| 072 | 7 | |a UMZ |2 bicssc | |
| 082 | 0 | 4 | |a 004 |2 23 |
| 049 | |a UAMI | ||
| 100 | 1 | |a Koelsch, George, |e author. | |
| 245 | 1 | 0 | |a Requirements writing for system engineering / |c George Koelsch. |
| 264 | 1 | |a [Berkeley, CA] : |b Apress, |c 2016. | |
| 300 | |a 1 online resource (409 pages) | ||
| 336 | |a text |b txt |2 rdacontent | ||
| 337 | |a computer |b c |2 rdamedia | ||
| 338 | |a online resource |b cr |2 rdacarrier | ||
| 347 | |a text file | ||
| 347 | |b PDF | ||
| 588 | 0 | |a Online resource; title from PDF title page (EBSCO, viewed December 5, 2016). | |
| 504 | |a Includes bibliographical references and index. | ||
| 505 | 0 | |a At a Glance; Contents; About the Author; Acknowledgments; Part I: The Foundation of Requirements; Chapter 1: The Importance of Requirements; Requirements Conventions Used in the Book; Projects Used in This Book; FBI Record Management Project; Radiation Dosimetry Project; Basic Definitions; Definitions of Requirements-Related Terms; How Long Does It Take Requirements Engineers to & What Makes a Good RE?; Personality Traits; Patience; Clarity of Thought; Flexibility; Extrovertism; Confidence; Negative Traits; Good Communications Skills; Responsiveness; Translator; Moderator. | |
| 505 | 8 | |a PersuasivenessSummary; Challenges for Writing Effective Requirements; Insufficient Requirements; Scope; Requirements Creep; Volatility; Stove-Piped Requirements; Users Are Not Sure What They Need; User Needs Not Satisfied; Multiple Interpretations Cause Disagreements; Are the Requirements Verifiable?; Wasted Time and Resources Building the Wrong Functions; Summary; References; Exercises; Exercise 1; Exercise 2; Chapter 2: What Makes a Good Requirement?; Understanding Requirements; The Form of a Requirement; Dealing with Negatives in Requirements; Attributes of a Good Requirement; Accurate. | |
| 505 | 8 | |a AtomicParent-Child Requirements; Complete; Completeness of an Individual Requirement; Completeness of a Group of Requirements; Concise; Consistent; Does Not Conflict with Other Requirements; Does Not Duplicate Other Requirements; Independent; Stand on Its Own; Implementation Independent; Prioritized; Realistic; Traceable; Traceability ; Traced to a Source; Unambiguous; Ambiguity in General; Subjective Terminology; Troublesome Parts of Speech; Passive Voice; Understandable by Stakeholders; Unique; Verifiable; Testing; Inspection; Demonstration; Simulation; Analysis; Wrap-Up of Verifiable. | |
| 505 | 8 | |a One More Attribute: Modifiable Capability Within a Requirement; Types of Errors That Can Occur with Requirements; Dangerous or Toxic Requirements; Extra, Superfluous Requirements; Incomplete Requirements; Others; References; Exercises; Exercise 1; Exercise 2; Exercise 3; Exercise 4; Exercise 5; Chapter 3: Specialized Language; The Use of Language; Defining Specialized Terms; Acronyms and Abbreviations; Summary; Exercises; Exercise 1; Exercise 2; Part II: Types of Requirements; Chapter 4: Functional Requirements; Understanding Types of Requirements; Types of Functional Requirements. | |
| 505 | 8 | |a Business RulesTransactions; Transaction Entry; Transaction Change; Transaction Errors; Administrative Functions; Authentication; Authorization Levels; Audit Tracking; External Interfaces; Certification Requirements; Searching and Reporting Requirements; Compliance, Legal, or Regulatory Requirements; Historical Data; Archiving; Structural; Algorithms; Database; Power; Network; Infrastructure; Backup and Recovery; Summary; Exercises; Exercise 1; Exercise 2; Chapter 5: Nonfunctional Requirements; The Types of Nonfunctional Requirements; Architectural; Capacity; Constraints; Documentation. | |
| 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 | ||
| 590 | |a O'Reilly |b O'Reilly Online Learning: Academic/Public Library Edition | ||
| 650 | 0 | |a Requirements engineering. | |
| 650 | 0 | |a Systems engineering. | |
| 650 | 6 | |a Ingénierie des exigences. | |
| 650 | 6 | |a Ingénierie des systèmes. | |
| 650 | 7 | |a systems engineering. |2 aat | |
| 650 | 7 | |a COMPUTERS |x Computer Literacy. |2 bisacsh | |
| 650 | 7 | |a COMPUTERS |x Computer Science. |2 bisacsh | |
| 650 | 7 | |a COMPUTERS |x Data Processing. |2 bisacsh | |
| 650 | 7 | |a COMPUTERS |x Hardware |x General. |2 bisacsh | |
| 650 | 7 | |a COMPUTERS |x Information Technology. |2 bisacsh | |
| 650 | 7 | |a COMPUTERS |x Machine Theory. |2 bisacsh | |
| 650 | 7 | |a COMPUTERS |x Reference. |2 bisacsh | |
| 650 | 7 | |a Requirements engineering. |2 fast |0 (OCoLC)fst01743780 | |
| 650 | 7 | |a Systems engineering. |2 fast |0 (OCoLC)fst01141455 | |
| 650 | 7 | |a Project management. |2 bicssc | |
| 650 | 7 | |a Business mathematics & systems. |2 bicssc | |
| 650 | 7 | |a Systems analysis & design. |2 bicssc | |
| 650 | 7 | |a Information architecture. |2 bicssc | |
| 650 | 7 | |a Software Engineering. |2 bicssc | |
| 650 | 2 | |a Management Information Systems | |
| 773 | 0 | |t Springer eBooks | |
| 776 | 0 | 8 | |i Printed edition: |z 9781484220986 |
| 830 | 0 | |a 2016 Springer EBA Collection. | |
| 856 | 4 | 0 | |u https://learning.oreilly.com/library/view/~/9781484220993/?ar |z Texto completo (Requiere registro previo con correo institucional) |
| 938 | |a Askews and Holts Library Services |b ASKH |n AH32378174 | ||
| 938 | |a ProQuest Ebook Central |b EBLB |n EBL4722291 | ||
| 938 | |a EBSCOhost |b EBSC |n 1366178 | ||
| 938 | |a YBP Library Services |b YANK |n 13230374 | ||
| 938 | |a ProQuest MyiLibrary Digital eBook Collection |b IDEB |n cis36771404 | ||
| 994 | |a 92 |b IZTAP | ||