Page 356 - Software and Systems Requirements Engineering in Practice

q
u
i

R
e
e
n
t
r
e
m
&

S
r
e

e
m
s
y
s
t
s
n

P
:

I
t
i
c
r
a
c
g
i
n

E
n
i
n
g
e
e
r
f
S
w
t
o
318
318 S o f t w a r e & S y s t e m s R e q u i r e m e n t s E n g i n e e r i n g : I n P r a c t i c e e
a
stakeholder classes, 141, 142 unsuitable, 42
stakeholder representative, untrained analysts, 42
141, 142 working with analysts, 47
stakeholders. See also domain working with
experts developers, 238
availability of, 44–45 state tables, 57–58
brainstorming sessions, 55–58 storyboarding, 246–248
challenges, 234, 243–244 storyboards, 244
conflicts/inconsistencies, 48, strategies, 132, 146, 150–154
237–238, 244 subcontracting, 5
defined, 140, 141 subgoals, 202
eliciting input from, 181, subject matter experts, 4, 6–7, 148
186–187 suitability, 136
examples of, 140 “sunny day” scenarios, 128
failing to accurately identify, suppliers, 270–271
43–44 SUT (system under test),
feedback comments, 186, 221, 222
244–245 swim lanes, 224
formal review by, 186 SysML modeling technique, 79
handling conflicts, 243–244 system architects, 259
identifying, 7, 41–44, 68, system boundaries, 45–46
141–142 system life cycle process, 35–37
inconsistencies among, 244 “system of systems” approach,
individuals, 141 264–265, 266
language/communication system requirements,
issues, 47–48, 68 130–132, 237
normalizing inputs, 181–182, system testing. See
188–189 requirements-driven
prioritizing/ranking system testing
requirements, 53–55, 69 system under test (SUT),
problems/issues, 41–48 221, 222
questionnaires sent to, 180–181 Systems Requirements
rapid iteration of feedback, Specification (SRS), 95
244–245
reconciling inputs, 182, T
188–189 tabular elicitation techniques,
reviewing models, 229 56–58
selecting significant, 140–142 taxonomies, 21–27
“smart ignoramus,” 41, 68 attributes, 24
understanding of product described, 21
needs, 46–47 examples of, 22–23