Computer Systems Engineering A Complete Guide - 2020 Edition. Gerardus Blokdyk

Score

      52. How many trainings, in total, are needed?

      <--- Score

      53. Who needs what information?

      <--- Score

      54. What do employees need in the short term?

      <--- Score

      55. What does Computer Systems Engineering success mean to the stakeholders?

      <--- Score

      56. How do you recognize an Computer Systems Engineering objection?

      <--- Score

      57. What information do users need?

      <--- Score

      58. To what extent does each concerned units management team recognize Computer Systems Engineering as an effective investment?

      <--- Score

      59. Is the quality assurance team identified?

      <--- Score

      60. Who else hopes to benefit from it?

      <--- Score

      61. Think about the people you identified for your Computer Systems Engineering project and the project responsibilities you would assign to them, what kind of training do you think they would need to perform these responsibilities effectively?

      <--- Score

      62. Which issues are too important to ignore?

      <--- Score

      63. What resources or support might you need?

      <--- Score

      64. When a Computer Systems Engineering manager recognizes a problem, what options are available?

      <--- Score

      65. What extra resources will you need?

      <--- Score

      66. Is the need for organizational change recognized?

      <--- Score

      67. Are there regulatory / compliance issues?

      <--- Score

      68. How are the Computer Systems Engineering’s objectives aligned to the group’s overall stakeholder strategy?

      <--- Score

      69. Do you need to avoid or amend any Computer Systems Engineering activities?

      <--- Score

      70. What vendors make products that address the Computer Systems Engineering needs?

      <--- Score

      71. What training and capacity building actions are needed to implement proposed reforms?

      <--- Score

      72. What would happen if Computer Systems Engineering weren’t done?

      <--- Score

      73. What are the timeframes required to resolve each of the issues/problems?

      <--- Score

      74. What is the recognized need?

      <--- Score

      75. How do you identify the kinds of information that you will need?

      <--- Score

      76. Do you have/need 24-hour access to key personnel?

      <--- Score

      77. Who should resolve the Computer Systems Engineering issues?

      <--- Score

      78. Does the problem have ethical dimensions?

      <--- Score

      79. What is the Computer Systems Engineering problem definition? What do you need to resolve?

      <--- Score

      80. Which needs are not included or involved?

      <--- Score

      81. How can auditing be a preventative security measure?

      <--- Score

      82. What are the expected benefits of Computer Systems Engineering to the stakeholder?

      <--- Score

      83. Do you know what you need to know about Computer Systems Engineering?

      <--- Score

      84. Will new equipment/products be required to facilitate Computer Systems Engineering delivery, for example is new software needed?

      <--- Score

      85. What Computer Systems Engineering capabilities do you need?

      <--- Score

      86. Which information does the Computer Systems Engineering business case need to include?

      <--- Score

      87. Who needs budgets?

      <--- Score

      88. Whom do you really need or want to serve?

      <--- Score

      89. Are there any specific expectations or concerns about the Computer Systems Engineering team, Computer Systems Engineering itself?

      <--- Score

      90. Are there Computer Systems Engineering problems defined?

      <--- Score

      91. What activities does the governance board need to consider?

      <--- Score

      92. As a sponsor, customer or management, how important is it to meet goals, objectives?

      <--- Score

      93. Where is training needed?

      <--- Score

      94. What situation(s) led to this Computer Systems Engineering Self Assessment?

      <--- Score

      95. Why is this needed?

      <--- Score

      96. What is the problem and/or vulnerability?

      <--- Score

      97. Who are your key stakeholders who need to sign off?

      <--- Score

      98. How are you going to measure success?

      <--- Score

      99. Did you miss any major Computer Systems Engineering issues?

      <--- 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 Computer Systems Engineering 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. How do you manage unclear Computer Systems Engineering requirements?

      <--- Score

      2. Are task requirements clearly defined?

      <--- Score

      3. How was the ‘as is’ process map developed, reviewed, verified