extra work or rework?
<--- Score
86. What is the cost of rework?
<--- Score
87. What happens if cost savings do not materialize?
<--- Score
88. Are there measurements based on task performance?
<--- Score
89. Do the benefits outweigh the costs?
<--- Score
90. Does management have the right priorities among projects?
<--- Score
91. What does a Test Case verify?
<--- Score
92. Are missed Software Performance Engineering opportunities costing your organization money?
<--- Score
93. Did you tackle the cause or the symptom?
<--- Score
94. Are supply costs steady or fluctuating?
<--- Score
95. What would be a real cause for concern?
<--- Score
96. What details are required of the Software Performance Engineering cost structure?
<--- Score
97. When are costs are incurred?
<--- Score
98. What disadvantage does this cause for the user?
<--- Score
99. Where is the cost?
<--- Score
100. What do people want to verify?
<--- Score
101. What are the uncertainties surrounding estimates of impact?
<--- Score
102. What is the Software Performance Engineering business impact?
<--- Score
103. Are there any easy-to-implement alternatives to Software Performance Engineering? Sometimes other solutions are available that do not require the cost implications of a full-blown project?
<--- Score
104. Are Software Performance Engineering vulnerabilities categorized and prioritized?
<--- Score
105. What are the current costs of the Software Performance Engineering process?
<--- Score
106. What are your primary costs, revenues, assets?
<--- Score
107. Are indirect costs charged to the Software Performance Engineering program?
<--- Score
108. What would it cost to replace your technology?
<--- Score
109. Are you able to realize any cost savings?
<--- Score
110. How are costs allocated?
<--- Score
111. What is measured? Why?
<--- Score
112. How can a Software Performance Engineering test verify your ideas or assumptions?
<--- Score
113. How do you verify if Software Performance Engineering is built right?
<--- Score
114. What could cause you to change course?
<--- Score
115. How do you quantify and qualify impacts?
<--- Score
116. What measurements are being captured?
<--- Score
117. Have design-to-cost goals been established?
<--- Score
118. What measurements are possible, practicable and meaningful?
<--- Score
119. Among the Software Performance Engineering product and service cost to be estimated, which is considered hardest to estimate?
<--- Score
120. When should you bother with diagrams?
<--- Score
121. How will you measure success?
<--- Score
122. What could cause delays in the schedule?
<--- Score
123. How frequently do you track Software Performance Engineering measures?
Конец ознакомительного фрагмента.
Текст предоставлен ООО «ЛитРес».
Прочитайте эту книгу целиком, купив полную легальную версию на ЛитРес.
Безопасно оплатить книгу можно банковской картой Visa, MasterCard, Maestro, со счета мобильного
