- Page 1 and 2:
NASA/SP-2007-6105 Rev1 NASA Systems
- Page 3 and 4:
NASA/SP-2007-6105 Rev1 Systems Engi
- Page 5 and 6:
Table of Contents Preface..........
- Page 7 and 8:
Table of Contents 5.3.2.4 Verifcati
- Page 9 and 10:
Table of Contents 7.1.3.1 Acquisiti
- Page 11 and 12:
Table of Contents Figures 2.0-1 SE
- Page 13 and 14:
Table of Contents N-2 Peer reviews/
- Page 15:
Preface Since the writing of NASA/S
- Page 18 and 19:
Acknowledgments Steven Kennedy, NAS
- Page 21 and 22:
2.0 Fundamentals of Systems Enginee
- Page 23 and 24:
2.1 The Common Technical Processes
- Page 25 and 26:
2.3 Example of Using the SE Engine
- Page 27 and 28:
carry a crew of seven, etc. During
- Page 29 and 30:
Tier 0 Tier 1 Tier 2 Tier 3 1 2 3 4
- Page 31 and 32:
level up. Depending on complexity,
- Page 33 and 34:
activities. Figure 2.3-7 represents
- Page 35:
Te process of fnding the most cost-
- Page 38 and 39:
3.0 NASA Program/Project Life Cycle
- Page 40 and 41:
3.0 NASA Program/Project Life Cycle
- Page 42 and 43:
3.0 NASA Program/Project Life Cycle
- Page 44 and 45:
3.0 NASA Program/Project Life Cycle
- Page 46 and 47:
3.0 NASA Program/Project Life Cycle
- Page 48 and 49:
3.0 NASA Program/Project Life Cycle
- Page 50 and 51:
4.0 System Design then changes to t
- Page 52 and 53:
4.0 System Design ences, the Nation
- Page 54 and 55:
4.0 System Design successful missio
- Page 56 and 57:
4.0 System Design structure for def
- Page 58 and 59:
4.0 System Design 4.2 Technical Req
- Page 60 and 61:
4.0 System Design Table 4.2‑1 Ben
- Page 62 and 63:
4.0 System Design a slight relaxati
- Page 64 and 65:
4.0 System Design decomposition and
- Page 66 and 67:
4.0 System Design Table 4.2‑2 Req
- Page 68 and 69:
4.0 System Design chitecture can be
- Page 70 and 71:
4.0 System Design system (e.g., har
- Page 72 and 73:
4.0 System Design FFBDs are used to
- Page 74 and 75:
4.0 System Design ably complete set
- Page 76 and 77:
4.0 System Design technology must b
- Page 78 and 79:
4.0 System Design programmatic revi
- Page 80 and 81:
4.0 System Design Product Validati
- Page 82 and 83:
4.0 System Design that can occur wi
- Page 84 and 85:
4.0 System Design Table 4.4‑1 ILS
- Page 86 and 87:
4.0 System Design Requirements Def
- Page 89 and 90:
5.0 Product Realization Tis chapter
- Page 91 and 92:
5.1 Product Implementation Product
- Page 93 and 94:
Te technical team should also ensur
- Page 95 and 96:
e assessed. All noncompliances must
- Page 97 and 98:
5.2.1.1 Inputs Product Integration
- Page 99 and 100:
mentation; quality assurance record
- Page 101 and 102:
5.3 Product Verifcation Te Product
- Page 103 and 104:
Types of Testing 5.3 Product Verifc
- Page 105 and 106:
activities). Te fnal element of ver
- Page 107 and 108:
Variations, anomalies, and out-of-c
- Page 109 and 110:
Confguration Verifcation Confgurati
- Page 111 and 112:
ments so that the completed procedu
- Page 113 and 114:
facilities are available for portio
- Page 115 and 116:
commands issued by the guidance and
- Page 117 and 118:
From Product Verifcation Process To
- Page 119 and 120:
is the same as the name of the meth
- Page 121 and 122:
mended corrective actions and resol
- Page 123 and 124:
Te rigor and techniques used to ver
- Page 125 and 126:
system component, system assembly,
- Page 127 and 128:
ials are involved, special labeling
- Page 129 and 130:
6.0 Crosscutting Technical Manageme
- Page 131 and 132:
from the program, and the desired s
- Page 133 and 134:
Hardware-in-the-Loop (HWIL) must be
- Page 135 and 136:
verge to the schedule targets estab
- Page 137 and 138:
If a cost cap or fxed cost profle e
- Page 139 and 140:
nonvoting participants. Ad hoc memb
- Page 141 and 142:
should contain the project’s Prod
- Page 143 and 144:
Error 1: Functions Without Products
- Page 145 and 146:
What costs should be counted? How
- Page 147 and 148:
To integrate the costs being estima
- Page 149 and 150:
6.2 Requirements Management Require
- Page 151 and 152:
that will satisfy the applicable pr
- Page 153 and 154:
Identify the relevant stakeholders
- Page 155 and 156:
esponsible for interfacing systems,
- Page 157 and 158:
6.4 Technical Risk Management Te Te
- Page 159 and 160:
Communicate, deliberate, and docume
- Page 161 and 162:
Control Track CRM Process Identify
- Page 163 and 164:
Example Sources of Risk In the “i
- Page 165 and 166:
sessment (PRA) Procedures for NASA
- Page 167 and 168:
planned TPM values, and does so in
- Page 169 and 170:
6.5 Confguration Management Confgur
- Page 171 and 172:
FUNCTIONAL BASELINE Major Architect
- Page 173 and 174:
6.5 Confguration Management CONFIGU
- Page 175 and 176:
porated documentation changes” th
- Page 177 and 178:
Identifcation/defnition of data req
- Page 179 and 180:
▶ A framework for data fow within
- Page 181 and 182:
Table 6.6‑1 Technical Data Tasks
- Page 183 and 184:
in 22 CFR 120.11). It also does not
- Page 185 and 186:
managers need visibility into the p
- Page 187 and 188:
maining program or project risk (co
- Page 189 and 190:
to share ideas and resolve issues,
- Page 191 and 192:
Mission Concept Review Te MCR will
- Page 193 and 194:
Mission Defnition Review (Robotic M
- Page 195 and 196:
Preliminary Design Review Te PDR de
- Page 197 and 198:
Production Readiness Review A PRR i
- Page 199 and 200:
Test Readiness Review A TRR ensures
- Page 201 and 202:
Operational Readiness Review Te ORR
- Page 203 and 204:
Post‑Launch Assessment Review A P
- Page 205 and 206:
Decommissioning Review Te DR confrm
- Page 207 and 208:
Functional and Physical Confguratio
- Page 209 and 210:
When either schedule variance or co
- Page 211 and 212:
worth tracking can be identifed thr
- Page 213 and 214:
Defne MOPs for each identifed MOE.
- Page 215 and 216:
6.8 Decision Analysis Te purpose of
- Page 217 and 218:
High Stakes: High stakes are involv
- Page 219 and 220:
Decision Matrix attery Example for
- Page 221 and 222:
Work products of decision analysis
- Page 223 and 224:
During the early life-cycle phases,
- Page 225 and 226:
An Example of a Trade Tree for a Ma
- Page 227 and 228:
Another mechanism is limiting the n
- Page 229 and 230:
In even moderately complicated prob
- Page 231 and 232:
An example of a utility function fo
- Page 233:
OBJECTIVES HIERARCHY PERFORMANCE ME
- Page 236 and 237:
7.0 Special Topics 7.1.2.1 Develop
- Page 238 and 239:
7.0 Special Topics # NPR 7123.1 Pro
- Page 240 and 241:
7.0 Special Topics # NPR 7123.1 Pro
- Page 242 and 243:
7.0 Special Topics Table 7.1‑2 St
- Page 244 and 245:
7.0 Special Topics 7.1.3.5 Writing
- Page 246 and 247:
7.0 Special Topics Table 7.1‑4 Ri
- Page 248 and 249:
7.0 Special Topics Table 7.1‑5 Ty
- Page 250 and 251:
7.0 Special Topics that expands the
- Page 252 and 253:
7.0 Special Topics 7.2 Integrated D
- Page 254 and 255:
7.0 Special Topics neering skills t
- Page 256 and 257:
7.0 Special Topics commercial appli
- Page 258 and 259:
7.0 Special Topics multi-Center dis
- Page 260 and 261:
7.0 Special Topics 7.3 Selecting En
- Page 262 and 263:
7.0 Special Topics 7.3.8 Backward C
- Page 264 and 265:
7.0 Special Topics 7.4 Human Factor
- Page 266 and 267:
7.0 Special Topics NASA Program/Pro
- Page 268 and 269:
7.0 Special Topics Table 7.4‑1 Hu
- Page 270 and 271:
7.0 Special Topics Table 7.4‑1 Hu
- Page 272 and 273:
7.0 Special Topics Table 7.4‑1 Hu
- Page 274 and 275: 7.0 Special Topics 7.5 Environmenta
- Page 276 and 277: 7.0 Special Topics of Science and T
- Page 278 and 279: 7.0 Special Topics the entire histo
- Page 280 and 281: 7.0 Special Topics Industry practi
- Page 282 and 283: Appendix A: Acronyms INSRP Interage
- Page 284 and 285: Appendix B: Glossary Term Defnition
- Page 286 and 287: Appendix B: Glossary Term Defnition
- Page 288 and 289: Appendix B: Glossary Term Defnition
- Page 290 and 291: Appendix B: Glossary Term Defnition
- Page 292 and 293: Appendix B: Glossary Term Defnition
- Page 294 and 295: Appendix B: Glossary Term Defnition
- Page 296 and 297: Appendix B: Glossary Term Defnition
- Page 298 and 299: Appendix C: How to Write a Good Req
- Page 300 and 301: Appendix D: Requirements Verifcatio
- Page 302 and 303: Appendix E: Creating the Validation
- Page 304 and 305: Appendix F: Functional, Timing, and
- Page 306 and 307: Appendix F: Functional, Timing, and
- Page 308 and 309: Appendix F: Functional, Timing, and
- Page 310 and 311: Appendix F: Functional, Timing, and
- Page 312 and 313: Appendix G: Technology Assessment/I
- Page 314 and 315: Appendix G: Technology Assessment/I
- Page 316 and 317: Appendix G: Technology Assessment/I
- Page 318 and 319: Appendix H: Integration Plan Outlin
- Page 320 and 321: Appendix I: Verifcation and Validat
- Page 322 and 323: Appendix J: SEMP Content Outline Sy
- Page 326 and 327: Appendix K: Plans Activity Plan....
- Page 328 and 329: Appendix L: Interface Requirements
- Page 330 and 331: Appendix N: Guidance on Technical P
- Page 332 and 333: Appendix N: Guidance on Technical P
- Page 334 and 335: Appendix O: Tradeof Examples Table
- Page 336 and 337: Appendix P: SOW Review Checklist W
- Page 338 and 339: Appendix P: SOW Review Checklist I
- Page 340 and 341: Appendix Q: Project Protection Plan
- Page 342 and 343: References International Organizati
- Page 344 and 345: References Kurke, M. I. “Operatio
- Page 346 and 347: Bibliography Eslinger, Suellen. Sof
- Page 348 and 349: Bibliography —. NPR 8705.4, Risk
- Page 350 and 351: Index acceptance verifcation, 91 ac
- Page 352 and 353: Index Echo balloons, 17 EFFBDs (enh
- Page 354 and 355: Index certifcation, 104 cost, 128,
- Page 356 and 357: Index reviews CDR, 25, 77, 178 CERR
- Page 358 and 359: Index components of, 39 integration