Advices of the Support Tools: Difference between revisions
From Ameise-en
Jump to navigationJump to search
No edit summary |
|||
| Line 1: | Line 1: | ||
{{NavigatorBar|Friendly peer|Starting the Simulator}} | |||
The following list includes various advices for the relevant OS-Model which are associated to the support tools. Trainees get this advices directly from the advisor or the friendly-peer, to indicate and avoid difficult situations. | The following list includes various advices for the relevant OS-Model which are associated to the support tools. Trainees get this advices directly from the advisor or the friendly-peer, to indicate and avoid difficult situations. | ||
| Line 80: | Line 84: | ||
| style="text-align:center;background:#DDE9FF" | {{cross}} | | style="text-align:center;background:#DDE9FF" | {{cross}} | ||
|} | |} | ||
{{NavigatorBar|Friendly peer|Starting the Simulator}} | |||
[[de:Hinweise zu den Unterstützungswerkzeugen]] | [[de:Hinweise zu den Unterstützungswerkzeugen]] | ||
Revision as of 19:25, 3 May 2013
The following list includes various advices for the relevant OS-Model which are associated to the support tools. Trainees get this advices directly from the advisor or the friendly-peer, to indicate and avoid difficult situations.
Allocation of the identifying advices on the support tools
| Advice | Tool(s) | |
| Friendly-Peer | Advisor | |
| The author should not be used as a consultant. | 
|
|
| The author itself should perform the correction of documents. |
|
|
| Previous phases should not be forgotten. |
|
|
| The previous phase should be finished,before starting the next phase. |
|
|
| The previous phase should be checked,before starting the next phase. |
|
|
| The previous phase should be corrected in referenc to the review, befroe starting the next phase. |
|
|
| Only after a successful correction of a proceeded review, a new review can be proceeded |
|
|
| A correction shuold be made after performing a test. |
|
|
| The customer should participate in specification- and manual reviews. |
|
|
| The manual should be written in an early phase of the project. |
|
|
| Do not execute personal changes all the time. |
|
|
| The activity and utilization of your developers should be observed. |
|
|
| The employment of staff should be observed in each single phase. |
|
|
| Employees should not be removed prematurely from a phase. |
|
|
| Removing employees should be considered accurate. |
|
|
| Employees should get activities which the are qualified for. |
|
|
| Incomplete documents should be subjected to a further review. |
| |
