Difference between revisions of "Advices of the Support Tools"

From Ameise-en
 
(13 intermediate revisions by 2 users not shown)
Line 3: Line 3:
  
  
The following list includes various advices for the relevant OA-Model which are associated to the support tools. Trainees get these advices directly from the advisor or the friendly-peer, to indicate and avoid difficult situations.
+
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 advices on the support tools====
+
====Allocation of the identifying Advice on the Support Tools====
  
 
{|
 
{|
Line 13: Line 13:
 
|-
 
|-
 
| style="width:60%;text-align:center;background:#FFFFCA" |  
 
| style="width:60%;text-align:center;background:#FFFFCA" |  
| style="width:20%;text-align:center;background:#FFFFCA" | '''Friendly-Peer'''
+
| style="width:20%;text-align:center;background:#FFFFCA" | '''Friendly Peer'''
 
| style="width:20%;text-align:center;background:#FFFFCA" | '''Advisor'''
 
| style="width:20%;text-align:center;background:#FFFFCA" | '''Advisor'''
 
|-
 
|-
| style="text-align:left;background:#DDE9FF"  | The author should not be used as a consultant.
+
| 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" | {{cross}}
 
| style="text-align:center;background:#DDE9FF" |  
 
| style="text-align:center;background:#DDE9FF" |  
 
|-
 
|-
| style="text-align:left;background:#FFFFCA"  |The author itself should perform the correction of documents.
+
| 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" | {{cross}}
 
| style="text-align:center;background:#FFFFCA" |  
 
| style="text-align:center;background:#FFFFCA" |  
Line 28: Line 28:
 
| style="text-align:center;background:#DDE9FF" | {{cross}}
 
| style="text-align:center;background:#DDE9FF" | {{cross}}
 
|-
 
|-
| style="text-align:left;background:#FFFFCA"  | The previous phase should be finished, before starting the next phase.
+
| 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: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:center;background:#DDE9FF" | {{cross}}
 
| style="text-align:center;background:#DDE9FF" | {{cross}}
 
|-
 
|-
| style="text-align:left;background:#FFFFCA"  | The previous phase should be corrected in reference to the review, before starting the next phase.
+
| 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:center;background:#FFFFCA" | {{cross}}
 
| style="text-align:center;background:#FFFFCA" | {{cross}}
 
|-
 
|-
| style="text-align:left;background:#DDE9FF"  | Only after a successful correction of a proceeded review, a new review can be proceeded
+
| 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" | {{cross}}
 
| style="text-align:center;background:#DDE9FF" |  
 
| style="text-align:center;background:#DDE9FF" |  
 
|-
 
|-
| style="text-align:left;background:#FFFFCA"  | A correction should be made after performing a test.
+
| 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:center;background:#FFFFCA" | {{cross}}
 
| style="text-align:center;background:#FFFFCA" | {{cross}}
 
|-
 
|-
| style="text-align:left;background:#DDE9FF"  | The customer should participate in specification- and manual reviews.
+
| 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" | {{cross}}
 
| style="text-align:center;background:#DDE9FF" |  
 
| style="text-align:center;background:#DDE9FF" |  
 
|-
 
|-
| style="text-align:left;background:#FFFFCA"  | The manual should be written in an early phase of the project.
+
| 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" | {{cross}}
 
| style="text-align:center;background:#FFFFCA" |  
 
| style="text-align:center;background:#FFFFCA" |  
 
|-
 
|-
| style="text-align:left;background:#DDE9FF"  | Do not execute personal changes all the time.
+
| style="text-align:left;background:#DDE9FF"  | Do not change employees frequently.
 
| style="text-align:center;background:#DDE9FF" | {{cross}}
 
| style="text-align:center;background:#DDE9FF" | {{cross}}
 
| style="text-align:center;background:#DDE9FF" |  
 
| style="text-align:center;background:#DDE9FF" |  
 
|-
 
|-
| style="text-align:left;background:#FFFFCA"  | The activity and utilization of your developers should be observed.
+
| 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" | {{cross}}
 
| style="text-align:center;background:#FFFFCA" |  
 
| style="text-align:center;background:#FFFFCA" |  
 
|-
 
|-
| style="text-align:left;background:#DDE9FF"  | The employment of staff should be observed in each single phase.
+
| 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" | {{cross}}
 
| style="text-align:center;background:#DDE9FF" |  
 
| style="text-align:center;background:#DDE9FF" |  
Line 72: Line 72:
 
| style="text-align:center;background:#FFFFCA" |  
 
| style="text-align:center;background:#FFFFCA" |  
 
|-
 
|-
| style="text-align:left;background:#DDE9FF"  | Removing employees should be considered accurate.
+
| 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" | {{cross}}
 
| style="text-align:center;background:#DDE9FF" |  
 
| style="text-align:center;background:#DDE9FF" |  
 
|-
 
|-
| style="text-align:left;background:#FFFFCA"  | Employees should get activities which they are qualified for.
+
| 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" | {{cross}}
 
| style="text-align:center;background:#FFFFCA" |  
 
| style="text-align:center;background:#FFFFCA" |  
 
|-
 
|-
| style="text-align:left;background:#DDE9FF"  | Incomplete documents should be subjected to a further review.
+
| 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" |  
 
| style="text-align:center;background:#DDE9FF" | {{cross}}
 
| style="text-align:center;background:#DDE9FF" | {{cross}}
Line 88: Line 88:
 
{{NavigatorBar|The Friendly Peer|Starting the Simulator}}
 
{{NavigatorBar|The Friendly Peer|Starting the Simulator}}
  
[[de:Hinweise zu den Unterstützungswerkzeugen]]
+
[[de:Hinweise der Unterstützungswerkzeuge]]
[[en:Advices for the support tools]]
+
[[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