Software Engineering

Q
QFD. 
See 
Quality function deployment (QFD)
Quality function deployment (QFD), 23–24
R
RAD. 
See 
Rapid Application Development  
(RAD)
Rapid Application Development (RAD), 104
Rapid prototyping, 223
Registry, 74
Regression testing (requirements baseline), 50

---

348
Index
Repository control, 284–285
change history repository, 285
engineering artifact repository, 285
technical risk repository, 285
Requirement analysis
operational analysis tasks, 144–147
computing environment characteristics, 146–147
external interfaces, 147
identifying concepts, 145
operational scenarios, 145–146
overview, 140
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
project analysis tasks, 140–144
goals and objectives, 141–142
prioritizing needs, 144
stakeholders' needs and expectations, 142–144
success criteria, 142
project assessment tasks
assess proposed changes, 156–157
project feasibility, 157
requirements sensitivity, 155
software test strategy, 155–156
requirements baseline, 157–158
sustainment analysis tasks, 152–155
architectural guidelines and principles, 154–155
post-development process characteristics, 
153–154
post-development process operational 
concepts, 152–153
post-development process operational 
scenarios, 153
Requirement management
change, 160–166
impact analysis, 162–164
project milestones, 164–165
time, 160–162
change control, 171–172
configuration audits, 172
decomposition and allocation, 168–170
component synthesis, 170
functional analysis, 169
performance allocation, 169–170
structural unit synthesis, 170
overview, 159–160
requirements traceability, 170–172
specifying requirements, 166–168
Requirements
analysis and specification, 127–132
balancing and deconflicting needs, 129
cost
complete software reuirement, 130–131
post-development processes, 131
testing product, 131
experienced software personnel, 132
maintaining scope of project, 129–132
organizational work packages, 133
overview, 121, 124
project planning, 134
resource identification, estimation, and 
allocation, 133
stakeholder needs and expectations, 124–127, 
135–137
task definition and scheduling, 132–133
technical planning, 133–134
timeline and task dependencies, 131–132
Requirements baseline, 48–49, 157–158
Requirements definition stage, 35–36
product requirements review (PRR), 35
software requirements review (SRR), 35–36
Requirements fulfillment, 200
Requirements traceability, 170–172
guidelines, 67–68
Resource budgets, 199–200
Resource prerequisites, behavioral analysis, 194
Resource utilization and conservation (software 
product architecture), 49
Resource utilization needs, 150
Risk management, 24
S
SBS. 
See 
Software breakdown structure (SBS)
Scope of post-development processes  
(post-development processes), 48
Scope of testing and evaluation effort (testing and 
evaluation), 48
Simulation, 24–27
physical architecture, 215–216
Software analysis
assessing project repercussions, 258–259
developmental implications, 258
execution strategies, 259
project implications, 258–259
conducting, 255–258
overview, 247–250, 249
f
trade study, 250–251
architectural alternatives, 259–260
candidate alternatives, 250–251

---

349
Index
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-study environment, 251–255
data collection and analysis mechanisms, 
253–255
experimental mechanisms, 252–253
procedures, 255
Software architecture, 11–12
artifacts, 53, 53