Page 343 - Software and Systems Requirements Engineering in Practice

305
x
e
n
d
I I n d e x 305
derivation metric, 206 collaboration web site, 267–269
design models, 74, 81, 115, communications concerns,
117–120 267–269
design package structure, 115 global projects, 260
DesignAdvisor tool, 120 managing RE efforts, 266–267
deterministic state, 58 OEMs, 270–271
Developer role, 201 overview, 258–259
developers suppliers, 270–271
communication issues, 12 time differences and, 260
prototypes and, 234–238, tips for, 271–272
248–250 tools for, 267–269
requirements and, 13, 42 distributed teams, 86, 100,
role of, 201 169, 259
working with stakeholders, 238 document classification
development costs, 178 taxonomies, 25
development life cycle, 229–230 document dependency
DFDs (data flow diagrams), 59, 60 diagrams, 131
diagrams document management, 217
activity, 105, 106, 224, document production, 129
225–227, 244 documentation, 217, 222
artifact visibility on, 101 documenting decisions,
clarity/completeness, 113 199, 200
class, 224 domain experts, 5, 48, 245,
collaboration, 105–107 250–251. See also stakeholders
context, 99–101 domain models, 164, 165
description/status, 100–101 downward compatibility, 13
DFDs, 59, 60 dynamic tailoring, 34
document dependency, 131
hyperlinks, 102, 103–104 E
package, 224 ECOs (engineering change
REAM, 27–30 orders), 196
sequence, 107–109 ECRs (engineering change
UML, 226–227 requests), 196
use case, 102–104, 107, 141, effectiveness, 137
223–224 efficiency, improving, 230
disposable prototypes, 239 electrical safety requirements, 14
distributed modeling, 98 elicitation, 39–71
distributed projects, 261–266 vs. analysis, 40
distributed requirements brainstorming sessions, 55–58
engineering, 257–273 business goals, 49–51
challenges, 210, 267–269 business rules, 62–63