Читать книгу Software Reliability A Complete Guide - 2020 Edition - Gerardus Blokdyk - Страница 9

Оглавление

CRITERION #3: MEASURE:

INTENT: Gather the correct data. Measure the current performance and evolution of the situation.

In my belief, the answer to this question is clearly defined:

5 Strongly Agree

4 Agree

3 Neutral

2 Disagree

1 Strongly Disagree

1. What could cause delays in the schedule?

<--- Score

2. How do you verify the authenticity of the data and information used?

<--- Score

3. At what cost?

<--- Score

4. How do you verify and develop ideas and innovations?

<--- Score

5. Are the Software reliability benefits worth its costs?

<--- Score

6. What measurements are being captured?

<--- Score

7. What are the estimated costs of proposed changes?

<--- Score

8. What causes investor action?

<--- Score

9. What is measured? Why?

<--- Score

10. When are costs are incurred?

<--- Score

11. How do you verify the Software reliability requirements quality?

<--- Score

12. What are your customers expectations and measures?

<--- Score

13. What are the operational costs after Software reliability deployment?

<--- Score

14. What harm might be caused?

<--- Score

15. Do you have any cost Software reliability limitation requirements?

<--- Score

16. Is the cost worth the Software reliability effort ?

<--- Score

17. What are the types and number of measures to use?

<--- Score

18. What drives O&M cost?

<--- Score

19. How do you verify your resources?

<--- Score

20. How is performance measured?

<--- Score

21. What do people want to verify?

<--- Score

22. What is the cause of any Software reliability gaps?

<--- Score

23. How will costs be allocated?

<--- Score

24. Do you have a flow diagram of what happens?

<--- Score

25. What are you verifying?

<--- Score

26. How frequently do you track Software reliability measures?

<--- Score

27. What relevant entities could be measured?

<--- Score

28. Does management have the right priorities among projects?

<--- Score

29. Where is the cost?

<--- Score

30. How can you manage cost down?

<--- Score

31. What are the costs?

<--- Score

32. Are Software reliability vulnerabilities categorized and prioritized?

<--- Score

33. Which Software reliability impacts are significant?

<--- Score

34. What does losing customers cost your organization?

<--- Score

35. What is your decision requirements diagram?

<--- Score

36. How will measures be used to manage and adapt?

<--- Score

37. How can you measure Software reliability in a systematic way?

<--- Score

38. What are the uncertainties surrounding estimates of impact?

<--- Score

39. Among the Software reliability product and service cost to be estimated, which is considered hardest to estimate?

<--- Score

40. What causes extra work or rework?

<--- Score

41. Which measures and indicators matter?

<--- Score

42. How to cause the change?

<--- Score

43. What evidence is there and what is measured?

<--- Score

44. How will success or failure be measured?

<--- Score

45. What are the Software reliability key cost drivers?

<--- Score

46. Are you taking your company in the direction of better and revenue or cheaper and cost?

<--- Score

47. What is the total cost related to deploying Software reliability, including any consulting or professional services?

<--- Score

48. Are supply costs steady or fluctuating?

<--- Score

49. Which costs should be taken into account?

<--- Score

50. How is progress measured?

<--- Score

51. What would be a real cause for concern?

<--- Score

52. Do you have an issue in getting priority?

<--- Score

53. What causes innovation to fail or succeed in your organization?

<--- Score

54. Why do the measurements/indicators matter?

<--- Score

55. When should you bother with diagrams?

<--- Score

56. How sensitive must the Software reliability strategy be to cost?

<--- Score

57. Are you aware of what could cause a problem?

<--- Score

58. What does a Test Case verify?

<--- Score

59. Are there measurements based on task performance?

<--- Score

60. How do you verify if Software reliability is built right?

<--- Score

61. How much does it cost?

<--- Score

62. Have design-to-cost goals been established?

<--- Score

63. What is the cost of rework?

<--- Score

64. What can be used to verify compliance?

<--- Score

65. How will effects be measured?

<--- Score

66. What are the costs and benefits?

<--- Score

67. Do you effectively measure and reward individual and team performance?

<--- Score

68. How do you measure lifecycle phases?

<--- Score

69. How do you measure variability?

<--- Score

70. How do you verify performance?

<--- Score

71. What are the costs of reform?

<--- Score

72. Have you included everything in your Software reliability cost models?

<--- Score

73. Where is it measured?

<--- Score

74. Do you verify that corrective actions were taken?

<--- Score

75. What are allowable costs?

<--- Score

76. How is the value delivered by Software reliability being measured?

<--- Score

77. What are your primary costs, revenues, assets?

<--- Score

78. Is there an opportunity to verify requirements?

<--- Score

79. How can you reduce the costs of obtaining inputs?

<--- Score

80. Is it feasible to quantify software reliability with reasonable confidence?

<--- Score

81. Did you tackle the cause or the symptom?

<--- Score

82. When a disaster occurs, who gets priority?

<--- Score

83. Are you able to realize any cost savings?

<--- Score

84. Have you made assumptions about the shape of the future, particularly its impact on your customers and competitors?

<--- Score

85. What are your operating costs?

<--- Score

86. What disadvantage does this cause for the user?

<--- Score

87. How can a Software reliability test verify your ideas or assumptions?

<--- Score

88. Does a Software reliability quantification method exist?

<--- Score

89. What methods are feasible and acceptable to estimate the impact of reforms?

<--- Score

90. Are actual costs in line with budgeted costs?

<--- Score

91. What could cause you to change course?

<--- Score

92. How do you verify and validate the Software reliability data?

<--- Score

93. What tests verify requirements?

<--- Score

94. What are hidden Software reliability quality costs?

<--- Score

95. Who is involved in verifying compliance?

<--- Score

96. Who should receive measurement reports?

<--- Score

97. Are the units of measure consistent?

<--- Score

98. What are the costs of delaying Software reliability action?

<--- Score

99. Do you aggressively reward and promote the people who have the biggest impact on creating excellent Software reliability services/products?

<--- Score

100. What users will be impacted?

<--- Score

101. What are your key Software reliability organizational performance measures, including key short and longer-term financial measures?

<--- Score

102. What is the Software reliability business impact?

<--- Score

103. What happens if cost savings do not materialize?

<--- Score

104. What is the total fixed cost?

<--- Score

105. How will you measure success?

<--- Score

106. How long to keep data and how to manage retention costs?

<--- Score

107. Are missed Software reliability opportunities costing your organization money?

<--- Score

108. What is an unallowable cost?

<--- Score

109. How do you measure efficient delivery of Software reliability services?

<--- Score

110. Was a business case (cost/benefit) developed?

<--- Score

111. How can you measure the performance?

<--- Score

112. Is the solution cost-effective?

<--- Score

113. How are measurements made?

<--- Score

114. How do you prevent mis-estimating cost?

<--- Score

115. How will you measure your Software reliability effectiveness?

<--- Score

116. Where can you go to verify the info?

<--- Score

117. What does your operating model cost?

<--- Score

118. Do the benefits outweigh the costs?

<--- Score

119. How will your organization measure success?

<--- Score

120. Are there any easy-to-implement alternatives to Software reliability? Sometimes other solutions are available that do not require the cost implications of a full-blown project?

<--- Score

121. What potential environmental factors impact the Software reliability effort?

<--- Score

122. Are there competing Software reliability priorities?

<--- Score

123. What do you measure and why?

<--- Score

124. Are indirect costs charged to the Software reliability program?

<--- Score

125. What would it cost to replace your technology?

<--- Score

126. How do you quantify and qualify impacts?

<--- Score

127. What details are required of the Software reliability cost structure?

<--- Score

128. How can you reduce costs?

<--- Score

129. How do your measurements capture actionable Software reliability information for use in exceeding your customers expectations and securing your customers engagement?

<--- Score

130. Who pays the cost?

<--- Score

131. What are the strategic priorities for this year?

<--- Score

132. Why do you expend time and effort to implement measurement, for whom?

<--- Score

133. What causes mismanagement?

<--- Score

Add up total points for this section: _____ = Total points for this section

Divided by: ______ (number of statements answered) = ______ Average score for this section

Transfer your score to the Software reliability Index at the beginning of the Self-Assessment.

Software Reliability A Complete Guide - 2020 Edition

Подняться наверх