Software Engineering

L
LOOP, 193
LOOP EXIT, 193
M
Mean time between failure (MTBF), 195
Measured product performance (software 
implementation), 51
Modeling, 234
Modeling and simulation, 24–27
physical architecture, 215–216
MTBF. 
See 
Mean time between failure (MTBF)
N
Needs and expectations. 
See 
Stakeholders’ needs 
and expectations
Nomenclature registry, 74
O
Operational analysis tasks, 144–147
computing environment characteristics, 146–147
external interfaces, 147
identifying concepts, 145
operational scenarios, 145–146
Operational durability, 232–233, 243
Optimization opportunities, 200
OR, 193
Organizational work packages, 133
P
PAR. 
See 
Preliminary architecture review (PAR)
PBS. 
See 
Product breakdown structure (PBS)
PDSS process test effort (post-development 
processes), 50
Performance allocation
functional analysis and allocation, 186, 198–200
performance budgets, 199
resource budgets, 199–200
requirement management, 169–170
Performance allocation confirmation (requirements 
baseline), 50
Performance budgets, 199

---

347
Index
Performance evaluations, physical architecture, 
217–222
Personal identification number (PIN), 193
Physical architecture, 44, 51, 203, 205
structural design considerations, 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 solution, 205–207
integration strategy, 209–211
structural unit specifications, 209
structural units, 207–209
technical data package, 211
verification and validation (V&V) practice, 272–273
integrated software configuration, 272–273
structural configuration, 272
Physical configuration audit, 40, 335, 340
PIN. 
See 
Personal identification number (PIN)
Plan, 11
Post-development processes (requirements 
baseline), 47–48
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
Preliminary architecture review (PAR), 36
Preliminary design review, 37
Preliminary stage software architecture, 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
Process engineering change packages, 279–281
change evaluation packages, 279–280
change request or proposal, 279
Product analysis tasks, 147–152
data persistence needs, 151
data processing conditional logic, 150–151
data security needs, 151–152
data storage transactions, 152
functional behaviors, 148–150
measures of performance, 152
modes of operation, 148
resource utilization needs, 150
Product architecture, 53
Product breakdown structure (PBS), 64–65
Product interface requirements (requirements 
baseline), 47
Product operational characteristics (requirements 
baseline), 47
Product performance characteristics (requirements 
baseline), 47
Product physical characteristics (requirements 
baseline), 47
Product qualification requirements (requirements 
baseline), 47
Product requirements review (PRR), 35
Product testing readiness review, 39
Product testing stage, 39–40
acceptance testing readiness review, 39–40
testing readiness review, 40
Programmer productivity, 242
Programming, 99, 100
t
–101
t
, 101
Programming language technical capabilities,  
242
Project analysis tasks, 140–144
goals and objectives, 141–142
prioritizing needs, 144
stakeholders' needs and expectations, 142–144
success criteria, 142
Project and technical planning, 75–77
project plans, 77
technical organization plans, 75–77
Project budget, 55–56
Prototyping, 24–25, 27, 222–225
comparison of strategies, 26
t
considerations, 224–225
disadvantages, 223–224
evolutionary, 223
extreme, 223
incremental, 223
physical architecture, 222–225
rapid, 223