Page 214 - Software and Systems Requirements Engineering in Practice

180 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

Define Questionnaires
This activity defines the questionnaire that will be sent to the stakeholders
for their inputs. Requirements engineers will also use it during the on-
site requirements elicitation meetings to collect the stakeholder inputs.
One major artifact used in this activity is illustrated in Table 6.1. The
table as shown here is not complete, but it provides sufficient information
for showing how we can structurally organize the stakeholders’ inputs.
The data filled in Table 6.1 is for illustration purposes and may not be
fully consistent and realistic. An example row may represent only a

Small Medium Large
Configuration Configuration Configuration
# of server
computers 1 4 10
# of local client
computers 3 8 20
# of remote client
computers 10 30 100
# of managed
objects 2000 40,000 100,000
Hard-disk needs
Networking
conditions (Mbps) 100 100 1000
UI Display Needs
Operator screens 3 12 40
Picture size (pixel) 1600 × 1200 6400 × 4800 6400 × 4800
Performance Needs
Normal load
Peak load
Burst load
Burst period
Burst load
Archiving Needs
# of archive
servers 0 1 2
# of redundant
servers 0 4 10
. . .

TABLE 6.1 Example NFR Questionnaire