Difference between revisions of "Advices of the Support Tools"

From Ameise-en
 
(22 intermediate revisions by 3 users not shown)
Line 1: Line 1:
In der folgenden Liste werden die Hinweise in Bezug auf das verwendete QS-Modell aufgelistet und den Unterstützungswerkzeugen zugeordnet, die der Spieler vom Ratgeber und väterlichen Freund bekommt, um auf Problemsituationen hingewiesen zu werden bzw. diese vermeiden zu können.
+
{{NavigatorBar|The Friendly Peer|Starting the Simulator}}
  
  
  
====Zuteilung der identifizierenden Hinweise zu den Unterstützungswerkzeugen====
+
The following list includes support tool advice relevant for the used QA model. Trainees get the advice directly from the advisor or the friendly peer, to identify and avoid difficult situations.
 +
 
 +
====Allocation of the identifying Advice on the Support Tools====
  
 
{|
 
{|
|- style="bgcolor:#FFFFCA" |
+
|-
| style="text-align:center;background:#FFFFCA" | '''Hinweis'''  
+
| style="text-align:center;background:#FFFFCA" | '''Advice'''  
| style="text-align:center;background:#FFFFCA" colspan="2" | '''Werkzeug(e)'''
+
| style="text-align:center;background:#FFFFCA" colspan="2" | '''Tool(s)'''
 
|-
 
|-
 
| style="width:60%;text-align:center;background:#FFFFCA" |  
 
| style="width:60%;text-align:center;background:#FFFFCA" |  
| style="width:20%;text-align:center;background:#FFFFCA" | '''väterl. Freund'''
+
| style="width:20%;text-align:center;background:#FFFFCA" | '''Friendly Peer'''
| style="width:20%;text-align:center;background:#FFFFCA" | '''Ratgeber'''
+
| style="width:20%;text-align:center;background:#FFFFCA" | '''Advisor'''
 +
|-
 +
| style="text-align:left;background:#DDE9FF"  | The author should not be used as a reviewer.
 +
| style="text-align:center;background:#DDE9FF" | {{cross}}
 +
| style="text-align:center;background:#DDE9FF" |
 +
|-
 +
| style="text-align:left;background:#FFFFCA"  |The author of a document should also correct it himself/herself.
 +
| style="text-align:center;background:#FFFFCA" | {{cross}}
 +
| style="text-align:center;background:#FFFFCA" |
 
|-
 
|-
| style="text-align:left;background:#DDE9FF"  | Der Autor sollte nicht als Gutachter eingesetzt werden.
+
| style="text-align:left;background:#DDE9FF"  | Previous phases should not be forgotten.
 
| style="text-align:center;background:#DDE9FF" | {{cross}}
 
| style="text-align:center;background:#DDE9FF" | {{cross}}
 
| style="text-align:center;background:#DDE9FF" | {{cross}}
 
| style="text-align:center;background:#DDE9FF" | {{cross}}
 
|-
 
|-
| style="text-align:left;background:#FFFFCA"  | Der Autor sollte nicht als Gutachter eingesetzt werden.
+
| style="text-align:left;background:#FFFFCA"  | The previous phase should be finished before starting the next phase.
 
| style="text-align:center;background:#FFFFCA" | {{cross}}
 
| style="text-align:center;background:#FFFFCA" | {{cross}}
 
| style="text-align:center;background:#FFFFCA" | {{cross}}
 
| style="text-align:center;background:#FFFFCA" | {{cross}}
 +
|-
 +
| style="text-align:left;background:#DDE9FF"  | The previous phase should be checked before starting the next phase.
 +
| style="text-align:center;background:#DDE9FF" | {{cross}}
 +
| style="text-align:center;background:#DDE9FF" | {{cross}}
 +
|-
 +
| style="text-align:left;background:#FFFFCA"  | Documents developed during the previous phase should be corrected based on the relevant review reports before starting the next phase.
 +
| style="text-align:center;background:#FFFFCA" | {{cross}}
 +
| style="text-align:center;background:#FFFFCA" | {{cross}}
 +
|-
 +
| style="text-align:left;background:#DDE9FF"  | A new review can only be performed after a successful correction based on a preceded review.
 +
| style="text-align:center;background:#DDE9FF" | {{cross}}
 +
| style="text-align:center;background:#DDE9FF" |
 +
|-
 +
| style="text-align:left;background:#FFFFCA"  | After each test, corrective tasks have to be performed.
 +
| style="text-align:center;background:#FFFFCA" | {{cross}}
 +
| style="text-align:center;background:#FFFFCA" | {{cross}}
 +
|-
 +
| style="text-align:left;background:#DDE9FF"  | The customer should participate in reviews of specification and manuals.
 +
| style="text-align:center;background:#DDE9FF" | {{cross}}
 +
| style="text-align:center;background:#DDE9FF" |
 +
|-
 +
| style="text-align:left;background:#FFFFCA"  | Writing the manuals should be already started in early phases.
 +
| style="text-align:center;background:#FFFFCA" | {{cross}}
 +
| style="text-align:center;background:#FFFFCA" |
 +
|-
 +
| style="text-align:left;background:#DDE9FF"  | Do not change employees frequently.
 +
| style="text-align:center;background:#DDE9FF" | {{cross}}
 +
| style="text-align:center;background:#DDE9FF" |
 +
|-
 +
| style="text-align:left;background:#FFFFCA"  | The activities and workload of your developers should be observed.
 +
| style="text-align:center;background:#FFFFCA" | {{cross}}
 +
| style="text-align:center;background:#FFFFCA" |
 +
|-
 +
| style="text-align:left;background:#DDE9FF"  | Staff assignment should be observed in each single phase.
 +
| style="text-align:center;background:#DDE9FF" | {{cross}}
 +
| style="text-align:center;background:#DDE9FF" |
 +
|-
 +
| style="text-align:left;background:#FFFFCA"  | Employees should not be removed prematurely from a phase.
 +
| style="text-align:center;background:#FFFFCA" | {{cross}}
 +
| style="text-align:center;background:#FFFFCA" |
 +
|-
 +
| style="text-align:left;background:#DDE9FF"  | Removing employees should be thought about carefully.
 +
| style="text-align:center;background:#DDE9FF" | {{cross}}
 +
| style="text-align:center;background:#DDE9FF" |
 +
|-
 +
| style="text-align:left;background:#FFFFCA"  | Employees should be assigned to activities which they are qualified for.
 +
| style="text-align:center;background:#FFFFCA" | {{cross}}
 +
| style="text-align:center;background:#FFFFCA" |
 +
|-
 +
| style="text-align:left;background:#DDE9FF"  | Incomplete documents should be subjected to a further revision.
 +
| style="text-align:center;background:#DDE9FF" |
 +
| style="text-align:center;background:#DDE9FF" | {{cross}}
 
|}
 
|}
  
 +
 +
{{NavigatorBar|The Friendly Peer|Starting the Simulator}}
 +
 +
[[de:Hinweise der Unterstützungswerkzeuge]]
 +
[[en:Advices of the Support Tools]]
 
[[Category:Tutorial]]
 
[[Category:Tutorial]]
 
__NOTOC__
 
__NOTOC__
 
__NOEDITSECTION__
 
__NOEDITSECTION__

Latest revision as of 15:13, 11 August 2013


The following list includes support tool advice relevant for the used QA model. Trainees get the advice directly from the advisor or the friendly peer, to identify and avoid difficult situations.

Allocation of the identifying Advice on the Support Tools

Advice Tool(s)
Friendly Peer Advisor
The author should not be used as a reviewer. Hackerl.gif
The author of a document should also correct it himself/herself. Hackerl.gif
Previous phases should not be forgotten. Hackerl.gif Hackerl.gif
The previous phase should be finished before starting the next phase. Hackerl.gif Hackerl.gif
The previous phase should be checked before starting the next phase. Hackerl.gif Hackerl.gif
Documents developed during the previous phase should be corrected based on the relevant review reports before starting the next phase. Hackerl.gif Hackerl.gif
A new review can only be performed after a successful correction based on a preceded review. Hackerl.gif
After each test, corrective tasks have to be performed. Hackerl.gif Hackerl.gif
The customer should participate in reviews of specification and manuals. Hackerl.gif
Writing the manuals should be already started in early phases. Hackerl.gif
Do not change employees frequently. Hackerl.gif
The activities and workload of your developers should be observed. Hackerl.gif
Staff assignment should be observed in each single phase. Hackerl.gif
Employees should not be removed prematurely from a phase. Hackerl.gif
Removing employees should be thought about carefully. Hackerl.gif
Employees should be assigned to activities which they are qualified for. Hackerl.gif
Incomplete documents should be subjected to a further revision. Hackerl.gif