System requirements analysis / Jeffrey O. Grady.

ISBN:

9780120885145

9780080457857

9781280628481

Title:

System requirements analysis / Jeffrey O. Grady.

Author:

Grady, Jeffrey O.

Personal Author:

Grady, Jeffrey O.

Publication Information:

Physical Description:

1 online resource (xxii, 455 pages) : illustrations

General Note:

Includes index.

Contents:

TABLE OF CONTENTS -- 1PART 1, INTRODUCTION -- 2PART 2, REQUIREMENTS FOUNDATION -- 3PART 3, TRADITIONAL STRUCTURED ANALYSIS -- 4PART 4, COMPUTER SOFTWARE STRUCTURED ANALYSIS -- 5PART 5, SPECIFICATION CONTENT STANDARDS -- 6PART 6, REQUIREMENTS MANAGEMENT -- 7PART 7, COMPUTER APPLICATIONS -- 8PART 8, CLOSING.

Local Note:

eBooks on EBSCOhost

Subject Term:

Systems engineering.

System analysis.

Format:

Electronic Resources

Electronic Access:

Click here to view

Publication Date:

2006

Publication Information:

Available:*

Shelf Number	Material Type	Copy	Shelf Location	Status
620.001171 22	1:E-BOOK	1	1:ONLINE	Searching... Unknown

Bound With These Titles

On Order

Summary

Systems Requirement Analysis gives the professional systems engineer the tools to set up a proper and effective analysis of the resources, schedules and parts that will be needed in order to successfully undertake and complete any large, complex project. The text offers the reader the methodology for rationally breaking a large project down into a series of stepwise questions so that a schedule can be determined and a plan can be established for what needs to be procured, how it should be obtained, and what the likely costs in dollars, manpower and equipment will be in order to complete the project at hand. Systems Requirement Analysis is compatible with the full range of engineering management tools now popularly used, from project management to competitive engineering to Six Sigma, and will ensure that a project gets off to a good start before it's too late to make critical planning changes. The book can be used for either self-instruction or in the classroom, offering a wealth of detail about the advantages of requirements analysis to the individual reader or the student group.

Author Notes

Jeffrey O. Grady is the Owner of JOG System Engineering, a consulting and teaching company, and an Adjunct Professor at the University of California, San Diego. He was formerly the manager of systems development at GD Space Systems. He is the author of ten books in the systems engineering field. Jeff is an INCOSE Fellow, Founder, and ESEP. Jeff worked as an employee for Librascope, Ryan Aeronautical, General Dynamics Convair, and General Dynamics Space Systems. He has consulted in systems engineering for many companies, developing military and commercial products. He has taught hundreds of system engineering courses for universities, short course companies and for his own company.

List of Illustrations	p. xv
List of Tables	p. xix
Preface	p. xxi
Acknowledgments	p. xxiii
1 Part 1, Introduction	p. 1
1.1 Introduction to System Requirements Analysis	p. 3
1.1.1 The Human Foundation	p. 4
1.1.2 What Is a System?	p. 4
1.1.3 What Is System Development?	p. 5
1.1.4 The Fundamental System Relation	p. 6
1.1.5 What Is System Requirements Analysis?	p. 7
1.1.6 System Requirements Analysis Timing Considerations	p. 9
1.1.7 Development Approaches	p. 10
1.1.8 Degree of Precedence Alternatives	p. 11
1.1.9 Organizational Alternatives	p. 11
1.1.10 Data Environment Alternatives	p. 13
1.1.11 Some History and References	p. 13
1.1.12 Overview of the Book	p. 14
1.1.13 How to Get the Most Out of the Book	p. 17
1.2 System Development Process Overview	p. 18
1.2.1 The Ultimate Process Step - The Enterprise Vision	p. 19
1.2.2 Product-Line Effects	p. 20
1.2.3 Customer-Base Effects	p. 20
1.2.4 Structured Process Analysis and Process Definition Expansion	p. 21
1.2.5 Documentation Media	p. 24
1.2.6 Lower-Tier Development Functionality	p. 24
1.2.7 Grand Systems Synthesis, F42	p. 32
1.2.8 Grand Systems Verification, F44	p. 32
1.2.9 Grand Systems Sustainment, F48	p. 36
1.2.10 Use Product System, F47	p. 36
1.2.11 Manage Program, F49	p. 36
1.2.12 Assure Product and Process Quality, F46	p. 37
1.3 Process Variations	p. 38
1.3.1 The Situation	p. 39
1.3.2 Alternative Sequence Models	p. 42
1.3.3 Concentrated Versus Distributed Customer Base	p. 42
1.3.4 Precedented Versus Unprecedented Systems	p. 42
1.3.5 The Three Gross Models	p. 43
1.3.6 The Lowest Common Denominator	p. 44
2 Part 2, Requirements Foundation	p. 45
2.1 Requirements Fundamentals	p. 47
2.1.1 Primitive Requirements Statement	p. 48
2.1.2 Requirements Value Definition Methods	p. 51
2.1.3 Requirements Derivation	p. 53
2.1.4 Kinds of Requirements	p. 54
2.1.5 Requirements in Time	p. 55
2.1.6 The Remaining Road	p. 56
2.2 Requirements Traceability Relationships	p. 57
2.2.1 Requirements Are Not Islands	p. 58
2.2.2 Vertical Traceability	p. 58
2.2.3 Longitudinal Traceability	p. 62
2.2.4 Requirements Traceability to Process	p. 63
2.2.5 Grand System Traceability	p. 65
2.2.6 Traceability Reporting	p. 66
2.2.7 Traceability Audits	p. 68
2.3 Requirements Allocation, Margins, and Budgets	p. 69
2.3.1 Requirement Value Determination	p. 70
2.3.2 Requirements Allocation	p. 70
2.3.3 Margin Management	p. 70
2.3.4 Budget Management	p. 73
2.4 Requirements Analysis Strategies	p. 74
2.4.1 The Four Strategies	p. 75
2.4.2 Freestyle Strategy	p. 75
2.4.3 Cloning Strategy	p. 75
2.4.4 Question and Answer Strategy	p. 78
2.4.5 Structured Analysis Strategy	p. 78
3 Part 3, Traditional Structured Analysis	p. 81
3.1 System Beginnings	p. 83
3.1.1 What's in a Name?	p. 84
3.1.2 In the Beginning	p. 84
3.1.3 The Meaning of the Term	p. 84
3.1.4 Unprecedented System Definition	p. 84
3.1.5 Trade Studies	p. 91
3.1.6 Rigor Versus Creativity	p. 93
3.1.7 Precedented System Definition	p. 93
3.1.8 Concluding Reviews	p. 94
3.2 A General Theory of Structured Analysis	p. 95
3.2.1 What Is Structured Analysis?	p. 96
3.2.2 Structured Analysis Goals	p. 96
3.2.3 Where Does It Appear in the Process?	p. 96
3.2.4 Comparative Overview of Approaches	p. 99
3.2.5 Polyfaceted View of Problem Spaces	p. 99
3.2.6 Entry Facet Differences	p. 100
3.2.7 An Entry Continuum	p. 101
3.2.8 Model Documentation	p. 101
3.2.9 Completeness and Avoiding Model Madness	p. 102
3.2.10 Detailed Coverage of Models	p. 104
3.3 Functional Analysis	p. 105
3.3.1 The Heritage of Structured Analysis	p. 106
3.3.2 Form Follows Function	p. 106
3.3.3 Functional Flow Analysis	p. 108
3.4 Product and Process Performance Requirements Analysis and Allocation	p. 118
3.4.1 Preliminaries	p. 119
3.4.2 Requirements Development Strategies	p. 120
3.4.3 The General Plan	p. 120
3.4.4 Transition to Process Analysis	p. 121
3.4.5 Primitive Statement and Transform	p. 123
3.4.6 Value Identification	p. 123
3.4.7 Product Class Differences	p. 123
3.4.8 Guidelines	p. 124
3.4.9 Verification Planning Analysis (VPA)	p. 125
3.4.10 Logistics Support Analysis	p. 127
3.4.11 Allocation of Functionality	p. 128
3.4.12 Performance Requirements Analysis Preceding Function Allocation	p. 136
3.4.13 RAS-Centered Requirements Analysis	p. 136
3.4.14 Process Summary	p. 136
3.5 Architecture Synthesis	p. 138
3.5.1 Introduction to Architecture	p. 139
3.5.2 Architecture Block Diagramming	p. 139
3.5.3 Diagramming Fundamentals	p. 140
3.5.4 Architecture Element Coding	p. 141
3.5.5 Sheet Cross-Referencing	p. 142
3.5.6 Alternative Organizational Structures	p. 142
3.5.7 Implementation Notes and Responsibility	p. 143
3.5.8 Architecture Crossing Conditions	p. 143
3.5.9 Reversing Traditional Structured Analysis	p. 145
3.6 Interface Identification and Definition	p. 148
3.6.1 Introduction to Interface Analysis	p. 149
3.6.2 Interface Identification	p. 150
3.6.3 Identification Work Products	p. 152
3.6.4 Interface Media and Requirements Definition	p. 159
3.6.5 Interface Documentation	p. 161
3.6.6 Interface Responsibility	p. 162
3.7 Specialty Engineering Requirements Analysis	p. 168
3.7.1 Serial Versus Parallel Work Pattern	p. 169
3.7.2 The Generic Specialty Engineering Process	p. 169
3.7.3 Engineering Specialty Activities Overview	p. 175
3.7.4 Science Projects and Natural Systems	p. 184
3.8 Environmental Requirements Analysis	p. 187
3.8.1 Overview	p. 188
3.8.2 Environmental Categories	p. 188
3.8.3 Environmental Requirements Models	p. 190
3.8.4 Time Analysis	p. 195
3.8.5 Environmental Requirements Capture	p. 199
3.8.6 Environmental Impact	p. 199
3.9 Functional Analysis Alternatives	p. 200
3.9.1 Variations Covered	p. 201
3.9.2 Functional Analysis Variations	p. 201
3.9.3 State and Event Analysis	p. 206
3.9.4 Mathematical Models	p. 210
3.9.5 Scenarios, Strings, and Threads Analysis	p. 211
3.9.6 Process Analysis	p. 212
3.9.7 Quality Function Deployment	p. 227
3.10 RAS-Complete and RAS-Centered Analysis	p. 231
3.10.1 A System Defined	p. 232
3.10.2 Descriptors of Interest	p. 232
3.10.3 System Functionality	p. 232
3.10.4 Performance Requirements Derivation and Allocation	p. 234
3.10.5 Conventional RAS Limitations	p. 234
3.10.6 The Beginning of the Complete RAS	p. 234
3.10.7 System Architecture	p. 235
3.10.8 Allocation Pacing Alternatives	p. 235
3.10.9 System Relations	p. 236
3.10.10 The System Environment	p. 237
3.10.11 Environmental Relation Algorithm	p. 238
3.10.12 Specialty Engineering and RAS Complete	p. 241
3.10.13 Verification Extension	p. 242
3.10.14 Conclusions	p. 242
3.11 Traditional Structured Analysis Documentation	p. 243
3.11.1 The Common Failure	p. 244
3.11.2 SDD Content and Format	p. 244
3.11.3 Recommended Responsibility Pattern	p. 246
4 Part 4, Computer Software Structured Analysis	p. 249
4.1 Introduction	p. 251
4.1.1 Computer Software Development Environment	p. 252
4.1.2 Software Development Models for Analysis	p. 252
4.1.3 Model Comparisons	p. 253
4.1.4 Design and Manufacturing Differences	p. 253
4.1.5 Software Deficit Disorder	p. 253
4.2 Computer Processing Oriented Analysis	p. 255
4.2.1 A Little History	p. 256
4.2.2 Flowcharts and Other Things	p. 256
4.2.3 Modern Structured Analysis	p. 256
4.2.4 Hatley-Pirbhai Real-Time Extension	p. 260
4.2.5 Transform from Models to Software Entities and Their Requirements	p. 260
4.2.6 Are These Models Appropriate Only for Software?	p. 260
4.3 Data-Oriented Analysis	p. 262
4.3.1 Data Augmentation of Modern Structured Analysis	p. 263
4.3.2 Relational Database Development	p. 263
4.3.3 Transition to Specification	p. 264
4.3.4 DoD Architecture Framework	p. 264
4.4 Object-Oriented Analysis	p. 265
4.4.1 The Early Combined Analysis Techniques	p. 266
4.4.2 Early Object-Oriented Analysis	p. 267
4.4.3 Function-Driven Early OOA	p. 269
4.4.4 Unified Modeling Language (UML)	p. 270
4.4.5 Moving to Specification	p. 274
4.5 System Modeling Using the Dod Architecture Framework	p. 275
4.5.1 Background	p. 276
4.5.2 Overview	p. 276
4.5.3 Framework Products	p. 277
4.5.4 Other Related Efforts	p. 284
4.5.5 Architecture Product Interrelationships	p. 284
4.5.6 The Six-Step Architecture Description Process	p. 285
4.6 Structured Analysis Fusion and Reunification	p. 288
4.6.1 Functional Flow or Die!	p. 289
4.6.2 Structured Analysis Boundaries	p. 290
4.6.3 Expanding Zigzag	p. 291
4.6.4 Evolution of the Ultimate Method	p. 292
4.6.5 Model-Driven Development	p. 292
5 Part 5, Specification Content Standards	p. 295
5.1 Specification Development Fundamentals	p. 297
5.1.1 Overview	p. 298
5.1.2 DoD Specifications under MIL-STD-490A	p. 298
5.1.3 MIL-STD-961D Specification Standard	p. 303
5.1.4 MIL-STD-961E	p. 303
5.1.5 Other Requirements Document Types	p. 303
5.1.6 Coverage of Specifications	p. 304
5.1.7 One- and Two-Part Specifications	p. 304
5.1.8 A Strange Specification Format	p. 305
5.2 General Specification Style Guide	p. 306
5.2.1 Style, Format, and Identification of Military Specifications	p. 307
5.2.2 Paragraph Numbering and Identification	p. 308
5.2.3 Footnotes	p. 309
5.2.4 Contractual and Administrative Requirements	p. 309
5.3 Specification Content Guidance	p. 312
5.3.1 MIL-STD-490A Content Standard	p. 313
5.3.2 MIL-STD-961D Content Standard	p. 319
5.3.3 MIL-STD-961E Content Standard Delta	p. 320
5.3.4 Software Specification Standards	p. 320
5.3.5 A Standard For the Ultimate Simplicity	p. 321
5.3.6 An Updated Content Standard	p. 321
5.4 Applicable Documents Analysis	p. 329
5.4.1 Introduction to Applicable Documents	p. 330
5.4.2 Initiation of the Program-Applicable Documents List	p. 331
5.4.3 Detailed Process Description	p. 333
5.4.4 Team Tailoring	p. 337
5.4.5 System Engineering Standards Relating to Requirements Analysis	p. 337
5.5 Part II Specifications	p. 339
5.5.1 The Part Situation	p. 340
5.5.2 Specification Timing	p. 340
5.5.3 Military Standards	p. 341
5.5.4 Part II Specification Content Development	p. 341
6 Part 6, Requirements Management	p. 343
6.1 Process Overview from a Management Perspective	p. 345
6.1.1 Introduction	p. 346
6.1.2 Program Preparation	p. 347
6.1.3 Program Implementation	p. 352
6.1.4 Program Closeout	p. 365
6.2 Requirements Risk Management	p. 367
6.2.1 Validation and Risk	p. 368
6.2.2 The Validation Time Span	p. 369
6.2.3 Avoiding a Null Solution Space	p. 370
6.2.4 Validation Process Description	p. 371
6.2.5 Validation Responsibility and Leadership	p. 380
6.2.6 Validation Expectations	p. 380
6.2.7 Validation Methods	p. 383
6.2.8 Product Representations	p. 386
6.2.9 Whole Program Phases	p. 389
6.3 Requirements Value Management	p. 390
6.3.1 Requirements Value Determination	p. 391
6.3.2 TBD/TBR Management	p. 391
6.3.3 Margin Management	p. 392
6.3.4 Budgets	p. 393
6.4 Requirements Integration	p. 394
6.4.1 Who's in Charge?	p. 395
6.4.2 Item Process View	p. 395
6.4.3 Aggregate Requirements Integration	p. 395
6.4.4 Engineering Specialty Integration Overview	p. 397
6.4.5 Interface Requirements Analysis Integration	p. 397
6.4.6 Environmental Requirements Analysis Integration	p. 399
6.4.7 Process Requirements Integration	p. 399
6.5 Interface Requirements Management	p. 400
6.5.1 Internal Interface Control	p. 401
6.5.2 Subcontractor Interface Control	p. 401
6.5.3 Associate Contractors	p. 401
6.5.4 Interface Integration Responsibility	p. 402
6.5.5 Interface Audit	p. 402
6.5.6 Some Nonstandard Interface Concepts	p. 403
6.6 Requirements Verification Management	p. 406
6.6.1 The Three-Step Process	p. 407
6.6.2 The V Words	p. 407
6.6.3 Verification Classes	p. 407
6.6.4 Verification Methods	p. 408
6.6.5 Qualification Verification	p. 409
6.6.6 Acceptance Verification	p. 409
6.6.7 System Test and Evaluation Verification	p. 410
6.6.8 Management Matrices	p. 410
6.7 Specification Development, Review, and Approval	p. 412
6.7.1 Specification Development Controls	p. 413
6.7.2 Specification Publishing	p. 414
6.7.3 Specification Archiving, Distribution, and Access	p. 414
6.7.4 Specification Change Management	p. 418
6.7.5 The Special Case of Interface Requirements Documentation	p. 420
6.7.6 Electronic Style Guide	p. 427
7 Part 7, Computer Applications	p. 429
7.1 The Computer Tool Infrastructure	p. 431
7.1.1 Why Have We Waited So Long?	p. 432
7.1.2 Evolution of Methods	p. 432
7.1.3 The Computer Tool Environment	p. 433
7.1.4 Requirements and Specifications Electronic Environment	p. 433
7.1.5 Networking and Workgroup Computing	p. 434
7.1.6 A Basic Requirements Database	p. 435
7.1.7 Traceability Hooks	p. 436
7.1.8 Verification Tracking Tool	p. 436
7.1.9 Requirements Management Data Fields	p. 437
7.1.10 External Model Hooks	p. 438
7.1.11 Traceability to Process	p. 438
7.1.12 Data Integrity	p. 440
7.2 Computer Tools for Requirements Analysis	p. 441
7.2.1 A Little history	p. 442
7.2.2 Buy or Build	p. 442
7.2.3 Available Tools and Their Features	p. 442
7.2.4 Features not Generally Supported	p. 443
7.2.5 Implementation Suggestions	p. 444
8 Part 8, Closing	p. 445
8.1 Where Have We Been?	p. 447
8.1.1 What Is the Essence of Our Story?	p. 448
8.1.2 Overcoming Impediments to SRA Success	p. 449
Acronyms	p. 451
Index	p. 453

Available:*

Bound With These Titles

On Order

Summary

Summary

Author Notes

Table of Contents