Features of the QA Model / Part 1: Difference between revisions
From Ameise-en
Jump to navigationJump to search
No edit summary |
No edit summary |
||
Line 8: | Line 8: | ||
* The concept is based on the waterfall model, so the strict phases of the waterfall model should be respected. | * The concept is based on the waterfall model, so the strict phases of the waterfall model should be respected. | ||
* You have to plan your personal | * You have to plan your personal resources the same way as you would plan them in a real project. All employees are equipped with an adequate knowledge. | ||
====Simulation Time==== | ====Simulation Time==== | ||
* The | * The last displayed date 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. | * All dates have the same format: 'year/month/day/hour:minute'. Weekends will be skipped automatically by the model. | ||
Line 22: | Line 22: | ||
====Proceed==== | ====Proceed==== | ||
* After starting a new simulation run, a "'''proceed'''" has to be executed. The task occurs afterwards. Earlier entered commands won't be executed | * After starting a new simulation run, a "'''proceed'''" has to be executed. The task occurs afterwards. Earlier entered commands won't be executed respectively the model could provide incorrect results. | ||
====Resources==== | ====Resources==== | ||
* If a new activity is | * If a new activity is referred to a developer, which is not already adjusted, this activity will not be executed and an error - message appears. If the developer is adjusted afterwards, the activity has to be referred 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 useless until the developer is available 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 useless until the developer is available again. | ||
* A developer is '''only''' able to do one task | * A developer is '''only''' able to do one task after another. This means, he cant design and coding at the same time. '''Reviews''' are the only exceptions. | ||
Revision as of 15:29, 13 May 2013
For a better understanding of simulation runs, the features of the QA - Model will be presented in the following sentences.
Project Planning
- The concept is based on the waterfall model, so the strict phases of the waterfall model should be respected.
- You have to plan your personal resources the same way as you would plan them in a real project. All employees are equipped with an adequate knowledge.
Simulation Time
- The last displayed date 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 does consider weekends, but it does not consider holidays, vacation- or sick days.
- The model does automatically change from summertime to wintertime and vice versa. The current season is shown in the date.
Proceed
- After starting a new simulation run, a "proceed" has to be executed. The task occurs afterwards. Earlier entered commands won't be executed respectively the model could provide incorrect results.
Resources
- If a new activity is referred to a developer, which is not already adjusted, this activity will not be executed and an error - message appears. If the developer is adjusted afterwards, the activity has to be referred 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 useless until the developer is available again.
- A developer is only able to do one task after another. This means, he cant design and coding at the same time. Reviews are the only exceptions.