Page 345 - Software and Systems Requirements Engineering in Practice

307
d
I
e
x
n
I n d e x 307
Fowler, Martin, 77 importance of, 282–283
FPA (function point analysis), 16 MDRE and, 281–282, 283
FTA (Federal Transit metrics, 279
Administration), 276, 277 overview, 276
function point analysis (FPA), 16 reflecting activities in RDB,
function point counting, 67, 85 280–281
function point metrics, 16, 67 risk assessment, 277
function points, 16 terminology, 276–277
functional proposals, 242 vs. threat modeling, 284
functional requirements. See also hazard analysis reviews, 281
NFRs hazards, 277
component, 177 Hewlett-Packard, 204
described, 127 hierarchical requirements
implementing, 5 structure, 293–294
integration of, 170 hierarchies, requirements, 215,
vs. nonfunctional 293–294
requirements, 4 hub-and-spoke
FURPS+ taxonomy, 169–170 organization, 262
hyperlinks, 102, 103–104
G
global analysis, 146–154, 160 I
global projects, 260 IDEF (Integration DEFinition),
Global Studio Project (GSP), 4, 78
262, 265 IEEE 830 Standard, 9
glossaries, 21, 22, 28, 37, 215. See IEF (Information Engineering
also terminology Facility), 67
Glossary of Terms, 36, 215 impact, 148
goal model, 81, 89 impact analysis, 197
goal modeling, 49–51, 78, implementation model, 74, 81
145–146, 153 included use cases, 59
goal-based traceability, 202 incompleteness, 217
goals, business. See business goals incremental product
government regulations, 3 development, 67–68
GSP (Global Studio Project), independent variables, 155
262, 265 Information Engineering Facility
guidelines, 199 (IEF), 67
inspections, 129
H installability, 137
HA. See hazard analysis installers, 140
hazard analysis (HA), 276–283 integrated model, 130–132
defined, 277 Integration DEFinition (IDEF),
identifying hazards, 277–280 4, 78