Fault Tolerant System A Complete Guide - 2020 Edition. Gerardus Blokdyk
Чтение книги онлайн.
Читать онлайн книгу Fault Tolerant System A Complete Guide - 2020 Edition - Gerardus Blokdyk страница 5
72. What are the expected benefits of Fault tolerant system to the stakeholder?
<--- Score
73. Who needs budgets?
<--- Score
74. Which needs are not included or involved?
<--- Score
75. Who needs to know?
<--- Score
76. How do you identify the kinds of information that you will need?
<--- Score
77. Who defines the rules in relation to any given issue?
<--- Score
78. Are problem definition and motivation clearly presented?
<--- Score
79. Who else hopes to benefit from it?
<--- Score
80. Do you have/need 24-hour access to key personnel?
<--- Score
81. Is it needed?
<--- Score
82. Which information does the Fault tolerant system business case need to include?
<--- Score
83. What are the timeframes required to resolve each of the issues/problems?
<--- Score
84. How do you assess your Fault tolerant system workforce capability and capacity needs, including skills, competencies, and staffing levels?
<--- Score
85. Does Fault tolerant system create potential expectations in other areas that need to be recognized and considered?
<--- Score
86. Is the quality assurance team identified?
<--- Score
87. Have you identified your Fault tolerant system key performance indicators?
<--- Score
88. What needs to be done?
<--- Score
89. What tools and technologies are needed for a custom Fault tolerant system project?
<--- Score
90. As a sponsor, customer or management, how important is it to meet goals, objectives?
<--- Score
91. Would you recognize a threat from the inside?
<--- 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 Fault tolerant system Index at the beginning of the Self-Assessment.
CRITERION #2: DEFINE:
INTENT: Formulate the stakeholder problem. Define the problem, needs and objectives.
In my belief, the answer to this question is clearly defined:
5 Strongly Agree
4 Agree
3 Neutral
2 Disagree
1 Strongly Disagree
1. Who approved the Fault tolerant system scope?
<--- Score
2. Is the scope of Fault tolerant system defined?
<--- Score
3. What information do you gather?
<--- Score
4. When is the estimated completion date?
<--- Score
5. Are task requirements clearly defined?
<--- Score
6. Has anyone else (internal or external to the group) attempted to solve this problem or a similar one before? If so, what knowledge can be leveraged from these previous efforts?
<--- Score
7. How do you manage changes in Fault tolerant system requirements?
<--- Score
8. What is the scope?
<--- Score
9. Do you have a Fault tolerant system success story or case study ready to tell and share?
<--- Score
10. How was the ‘as is’ process map developed, reviewed, verified and validated?
<--- Score
11. Is it clearly defined in and to your organization what you do?
<--- Score
12. Is the improvement team aware of the different versions of a process: what they think it is vs. what it actually is vs. what it should be vs. what it could be?
<--- Score
13. Are there any constraints known that bear on the ability to perform Fault tolerant system work? How is the team addressing them?
<--- Score
14. What is the scope of the Fault tolerant system work?
<--- Score
15. Has everyone on the team, including the team leaders, been properly trained?
<--- Score
16. How have you defined all Fault tolerant system requirements first?
<--- Score
17. What is the worst case scenario?
<--- Score
18. Scope of sensitive information?
<--- Score
19. Is the Fault tolerant system scope complete and appropriately sized?