Software Engineering

343
Index
A
Acceptance testing, 39–41
computing environment implementation 
organization, 339
deployment qualification review, 40
deployment readiness review, 41
functional configuration audit, 40
overview, 335
physical configuration audit, 40
post-development process organization, 339
products, 336–337
reviews and milestones, 340–341
deployment readiness review, 340–341
functional configuration audit, 340
physical configuration audit, 340
software engineering, 337–338
software implementation organization, 338–339
sustainment qualification review, 41
test and evaluation organization, 339–340
problem reports, 340
test procedures, 339–340
test reports, 340
training qualification review, 41
Agile Manifesto, 104–108
AND, 192
Architectural assessment, 186, 200
architectural complexity, 200
optimization opportunities, 200
requirements fulfillment, 200
software performance, 200
Architectural complexity, 200
Architectural consequences, 282
Architectural elements, configuration 
administration, 277–278
Architectural permanence, 232, 242–243
Architectural simplicity, 232, 243
Architectural status, configuration administration, 
278
Architecture. 
See 
Software architecture
Artifacts, software architecture, 53, 53
f
Auditing architectural change progress, 284
B
Behavioral analysis, 186, 189–198
elements to be addressed, 189–190
identify control behaviors, 192–193
identify data flows, 191–192
identify data persistence and retention functions, 
197–198
identify data processing procedures, 193–194
identify data retention capacity requirements, 197
identify data security procedures, 197
identify failure conditions, 194–196
identify functional scenarios, 190
identify functional sequences, 190
identify resource prerequisites, 194
identify systems monitoring procedures, 196–197
physical architecture, 216–217
Budgets
performance, 199
resource, 199–200
C
CBA. 
See 
Cost-benefit analysis (CBA)
CDR. 
See 
Critical design review (CDR)
Change assimilation, 283–284
appraising project situation, 284
auditing architectural change progress, 284
change notification package, 283–284
Change control, 20–22
Change evaluation, 281–283
architectural consequences, 282
technical merits, 281–282
technical plan consequences, 283
technical work package consequences, 282–283
Change evaluation packages, 279–280
Change history repository, 285
Change notification package, 283–284
Change proposal, 22
Change request, 22
Change request or proposal, 279
Code, 272–273
Complexity analysis, 185–189
Complexity control mechanisms, 63–74
documentation tree, 65
measures, 70
product breakdown structure (PBS), 64–65
requirements traceability guidelines, 67–68
software product baselines, 65–67
specification tree, 65
trade-off analysis, 68–70
work breakdown structure (WBS), 63–64
Note
: Page numbers followed by “
f
” and “
t
” refer to figures and tables, respectively.

---

344
Index
Computing environment, software architecture, 49
Configuration administration, 277–279
architectural elements, 277–278
architectural status, 278
Configuration management, 20–22
Content mapping, 234
Control behaviors, 192–193
AND, 192
ITERATE, 193
LOOP, 193
LOOP EXIT, 193
OR, 193
Control practice
change assimilation, 283–284
appraising project situation, 284
auditing architectural change progress, 284
change notification package, 283–284
change evaluation, 281–283
architectural consequences, 282
technical merits, 281–282
technical plan consequences, 283
technical work package consequences, 
282–283
configuration administration, 277–279
architectural elements, 277–278
architectural status, 278
overview, 275
process engineering change packages, 279–281
change evaluation packages, 279–280
change request or proposal, 279
repository control, 284–285
change history repository, 285
engineering artifact repository, 285
technical risk repository, 285
tasks, 275–276, 276
f
Cost
complete software reuirement, 130–131
post-development processes, 131
testing product, 131
Cost-benefit analysis (CBA), 22
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
Critical design review (CDR), 38, 230
D
DAR. 
See 
Detailed architecture review (DAR)
Data flows, 191–192
Data items, 177
Data persistence and retention functions, 197–198
Data persistence needs, 151
Data processing conditional logic, 150–151
Data processing procedures, 193–194
Data retention capacity requirements, 197
Data security needs, 151–152
Data security procedures, 197
Data storage transactions, 152
Data store, 179
Deployment data package (DDP), 335
Deployment design review, 37–38
Deployment qualification review, 40
Deployment readiness review (DRR), 41, 335–336, 
340–341
Deployment strategy review, 36
Design
defined, 11–12
impediments to. 
See 
Software development
Design challenges, functional architecture, 175–176
Design chasm, 236
Design conceptualization, 228, 230–235
abstract structural components, 233
abstract user interface mechanisms, 233–235
architectural design guidelines, 230–233
Design correlation, 228, 238–244
architectural alternatives, 240–241
architectural integrity, 242–243
implementation challenges, 241–242
performance benchmarks, 238–239
structural design deficiencies, 239–240
sustainment challenges, 242
Design guidelines, physical architecture, 211–214
Design manifestation, 228–229, 244
engineering assemblages, 244
structural configuration elements, 244
structural design configuration, 244
Design resolution, 228, 235–238
fundamental structural elements, 235–236
integrating components, 236
software reuse opportunities, 236–238
Design synthesis
design conceptualization, 228, 230–235
abstract structural components, 233
abstract user interface mechanisms, 233–235
architectural design guidelines, 230–233
design correlation, 228, 238–244
architectural alternatives, 240–241
architectural integrity, 242–243
implementation challenges, 241–242
performance benchmarks, 238–239
structural design deficiencies, 239–240
sustainment challenges, 242
design manifestation, 228–229, 244

---

345
Index
engineering assemblages, 244
structural configuration elements, 244
structural design configuration, 244
design resolution, 228, 235–238
fundamental structural elements, 235–236
integrating components, 236
software reuse opportunities, 236–238
overview, 227, 230
technical data package (TDP), 229, 244–245
Detailed architecture review (DAR), 37
Detailed software architecture, 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
Development costs 
versus
 timeliness (Stakeholder 
Needs), 48
Documentation tree, 17
complexity control mechanisms, 65
Documenting
decisions, trade study, 261
functional architecture, 181–184
behavior model, 182–183
functional hierarchy, 181–182
functional timeline, 183
requirements allocation sheet (RAS), 184
resource utilization profile, 183–184
specifications, 184
verification and validation (V&V), 273
E
Empowerment, 83, 88–89
Engineering artifact repository, 285
Evolutionary prototyping, 223
External interface, functional architecture, 178
Extreme prototyping, 223
F
Fabrication, assembly, integration, and testing 
(FAIT), 102–103
Failure conditions,. behavioral analysis, 194–196
Failure modes and effects analysis (FMEA), 
195–196
FAIT.