Features of the QA Model / Part 1
For a better understanding of simulation runs, features particular to the QA - Model will be presented in the following.
- The model is based on empirical data on projects using a phase-driven model(like the waterfall model), so the sequence of phases should be applied in the correct order.
- You have to plan your personal resources the same way as you would plan them in a real project. All employees are equipped with adequate knowledge and skills.
- The actual date displayed shows the current day. All entered actions occur on this day.
- All dates have the same format: 'year/month/day/hour:minute'. Weekends will be skipped automatically by the model.
- The model considers weekends, but it does not consider holidays, vacation or days of illness.
- The time automatically changes from summertime to wintertime and vice versa.
- After starting a new simulation run, a "proceed" will occur automatically. Afterwards, the task description will be displayed.
- If a new activity is assigned to a developer, who has not been previously employed, this activity will not be executed and an error message will appear. If the developer is being hired afterwards, the activity has to be assigned to him again.
- If the developer is released, he/she is not available for a random period of time between 21 and 60 days. The order "hire" will be ignored until the developer is available again.
- A developer is only able to do one task after another. This means, he/she cannot design and code at the same time. Reviews are the only activities which can be carried out in parallel with another task. It is highly advisable to wait for a developer to finish his/her actual activity before a new task will be assigned.