Software Engineering

f
computing environment, 49
design decisions, 56–57
elements applied to, 11–12
functional architecture. 
See 
Functional architecture
physical architecture, 44, 51
post-development operational architecture, 62
post-development process architecture, 63
distribution process architecture, 63
sustainment process architecture, 63
training process architecture, 63
product architecture, 53–54, 62
product operational architecture, 62
project environment, 61–63
relationships and dependencies, 44–46
requirements baseline, 61–63
software requirements baseline, 48–49
stakeholder needs relationships and 
dependencies, 46–48
subarchitectural elements, 52
SWE-IPT, 44–45
testing and evaluation, 49–50
verification and validation (V&V) practice, 271–272
functional architecture, 271
physical architecture, 271–272
requirements baseline, 271
software implementation, 272
Software architecture definition
detailed, 306–307, 315–322
allocated baseline, 322
computing environment implementation, 319
post-development process implementation, 
319–320
products, 315–317
reviews and milestones, 321–322
software engineering, 317–318
software implementation, 318–319
testing and evaluation, 320–321
preliminary stage, 306–315
computing environment organization, 311–312
implementation organization, 311
post-development process organization, 312
products, 307–309
reviews and milestones, 314–315
SWE-IPT, 309–311
testing and evaluation organization, 312–314
purpose, 305–306
Software breakdown structure (SBS), 15–17, 31–34
Software component integration and testing stage, 39
integration readiness review, 39
product testing readiness review, 39
Software development
architecture-driven, 108–111
software as raw material, 95–98
technological evolution, 98–108
Agile Manifesto, 104–108
methods and standards, 101–105, 102
f
programming, 99, 100
t
–101
t
, 101
Software development process, 34–41
acceptance testing stage, 40–41
deployment qualification review, 40
deployment readiness review, 41
functional configuration audit, 40
physical configuration audit, 40
sustainment qualification review, 41
training qualification review, 41
critical architecture definition stage, 37–38
critical design review (CDR), 38
deployment design review, 37–38
detailed architecture review (DAR), 37
sustainment design review, 38
training design review, 38
preliminary architecture definition stage, 36–37
deployment strategy review, 36
preliminary architecture review (PAR), 36
preliminary design review, 37
sustainment strategy review, 37
training strategy review, 36
product testing stage, 39–40
acceptance testing readiness review, 39–40
testing readiness review, 40
requirements definition stage, 35–36
product requirements review (PRR), 35
software requirements review (SRR), 35–36
software component integration and testing stage, 
39
integration readiness review, 39
product testing readiness review, 39
software unit code and testing stage, 38–39
unit design review (peer evaluation), 38
unit qualification review (peer evaluation), 39

---

350
Index
Software engineering integrated product team 
(SWE-IPT), 12
preliminary stage software architecture, 309–311
software architecture, 44–45
Software implementation
computing environment tasks, 329
dry-run acceptance testing, 323–325
fabrication, 323–324
overview, 323, 325
post-development process tasks, 329–330
products, 325–327
reviews and milestones, 332–333
software engineering tasks, 327
tasks, 327–329
testing and evaluation tasks, 330–332
Software integration strategy. 
See 
Integration 
strategy
Software product baseline (SPB), 341
Software product baselines, 65–67
Software product requirement appropriateness 
(functional architecture), 48
Software requirements baseline, 48–49
Software requirements definition
analyze product alternatives, conflicts, and  
trade-offs, 296–297
computing environment implementation, 299
computing environment requirements 
specifications, 293–294
initial software behavioral model, 293, 295
operational model, 291–293, 295
post-development process implementation, 
299–300
product specification tree, 297–298
products, 292–295
project and technical plans, 298
purpose, 291
reviews, milestones, and baselines, 301–303
risk mitigation plans, 297
software engineering, 295–298
software implementation, 298–299
software interface requirements specifications, 294
software nomenclature register, 298
software post-development process concepts, 297
documents, 294
software requirements allocations, 297
software requirements review (SRR), 298
software requirements specifications (SRS), 293
software requirements traceability matrix, 294
software testing and evaluation, 294, 300–301
corrective action audit, 301
feasibility, challenges, constraints, and risks, 
300
quality assurance inspection and audits, 
300–301
quality assurance plan, 300
software requirements audit, 301
test audit, 301
test plan, 300
synthesize conceptual design alternatives, 
295–296
work breakdown structure, 297
Software requirements review (SRR), 35–36
Software requirements specifications, 10, 293
Software unit code and testing stage, 38–39
unit design review (peer evaluation), 38
unit qualification review (peer evaluation), 39
Software, defined, 272–273
SPB. 
See 
Software product baseline (SPB)
Specification tree, 17
complexity control mechanisms, 65
Specification, analysis, and synthesis (SAS), 
102–103
Stakeholder needs relationships and dependencies, 
46–48
Stakeholders' needs and expectations, 124–127, 
135–137, 142–144
Storyboarding, 234
Structural design considerations, physical 
architecture, 211–225
behavioral analysis, 216–217
design guidelines, 211–214
modeling and simulation, 215–216
performance evaluations, 217–222
prototyping, 222–225
trade-off analysis, 217
Structural design optimization (functional 
architecture), 51
Structural design solution, physical architecture, 
205–207
integration strategy, 209–211
structural unit specifications, 209
structural units, 207–209
technical data package, 211
Structural design verification (functional 
architecture), 51
Structural performance validation (requirements 
baseline), 51
Structural units, physical architecture, 207–209
specifications, 209
Subarchitectural elements, 52
Sustainment analysis tasks, 152–155
architectural guidelines and principles, 154–155
post-development process characteristics, 
153–154

---

351
Index
post-development process operational concepts, 
152–153
post-development process operational scenarios, 
153
Sustainment design review, 38
Sustainment qualification review, 41
Sustainment strategy review, 37
SWE-IPT. 
See 
Software engineering integrated 
product team (SWE-IPT)
Systems engineering, 7–8
principles and practices, 3–5
Systems monitoring procedures, 196–197
T
Technical data package (TDP), 335
physical architecture, 211
Technical merits, change evaluation, 281–282
Technical plan consequences, 283
Technical risk repository, 285
Technical work package consequences, 282–283
Technological evolution, 98–108
Agile Manifesto, 104–108
methods and standards, 101–105, 102
f
programming, 99, 100
t
–101
t
, 101
Technology availability (requirements baseline), 49
Test coverage (software product architecture), 49
Test sufficiency (requirements baseline), 49–50
Testing and evaluation, software architecture, 49–50
Testing readiness review, 40
Timeliness 
versus
 development costs (Stakeholder 
Needs), 48
Trade study, 250–251
architectural alternatives, 259–260
candidate alternatives, 250–251
documenting decisions, 261
evaluation, 259–261
execution strategy, 261
functional alternatives, 256–257
preferred course of action, 260–261
requirements alternatives, 256
scope, 250
structural alternatives, 257–258
success criteria, 251
Trade-off analysis, 22–24, 68–70
physical architecture, 217
Trade-study environment, 251–255
data collection and analysis mechanisms, 
253–255
experimental mechanisms, 252–253
procedures, 255
Training design review, 38
Training qualification review, 41
Training strategy review, 36
Trees
documentation, 17
specification, 17