Advices of the Support Tools

From Ameise-en

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. Hackerl.gif
The author itself should perform the correction of documents. 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
The previous phase should be corrected in referenc to the review, befroe starting the next phase. Hackerl.gif Hackerl.gif
Only after a successful correction of a proceeded review, a new review can be proceeded Hackerl.gif
A correction shuold be made after performing a test. Hackerl.gif Hackerl.gif
The customer should participate in specification- and manual reviews. Hackerl.gif
The manual should be written in an early phase of the project. Hackerl.gif
Do not execute personal changes all the time. Hackerl.gif
The activity and utilization of your developers should be observed. Hackerl.gif
The employment of staff should be observed in each single phase. Hackerl.gif
Employees should not be removed prematurely from a phase. Hackerl.gif
Removing employees should be considered accurate. Hackerl.gif
Employees should get activities which the are qualified for. Hackerl.gif
Incomplete documents should be subjected to a further review. Hackerl.gif