Features of the QA Model / Part 1: Difference between revisions

From Ameise-en
Jump to navigationJump to search
No edit summary
No edit summary
 
(7 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{NavigatorBar|Using the Advisor|Features of the QA Model/Part 2}}
{{NavigatorBar|Using the Advisor|Features of the QA Model / Part 2}}




To better understand a simulation run, the features of the model will be presented in the following sentences.
For a better understanding of simulation runs, features particular to the QA - Model will be presented in the following.




====Project Planning====
====Project Planning====
* The concept is based on the waterfall model, so the phases of the waterfall model should be respected.
* 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 ressources the same way as you would plan them in a real project. All employees are equipped with an adequate knowledge.
* 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.




====Simulation Time====
====Simulation Time====
* The least displayed date shows the current day. All entered actions occure on this day.
* 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.
* 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 considers weekends, but it does not consider holidays, vacation or days of illness.


* The model does automatically change from summertime to wintertime and vice versa. The current season is shown in the date.
* The time automatically changes from summertime to wintertime and vice versa.  




====Proceed====
====First Proceed====
* After starting a new simulation run, a "'''proceed'''" has to be executed. The task occours afterwards. Earlier entered orders won't be executed resp. the model could provide incorrect results.
* After starting a new simulation run, a "'''proceed'''" will occur automatically. Afterwards, the task description will be displayed.  
 


====Resources====
====Resources====
* If a new activity is refered 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 refered to him again.
* 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 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 ignored until the developer is available again.


* A developer is '''only''' able to do one task at the same time. This means, he cant design and coding parallely. '''Reviews''' are the only exceptions.
* 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.




{{NavigatorBar|Using the Advisor|Features of the QA Model/Part 2}}
{{NavigatorBar|Using the Advisor|Features of the QA Model / Part 2}}


[[de:Besonderheiten des Modells/1]]
[[de:Besonderheiten des Modells/1]]
[[en:Features of the QA Model/Part 1]]
[[en:Features of the QA Model / Part 1]]
[[Category:Tutorial]]
[[Category:Tutorial]]
__NOTOC__
__NOTOC__
__NOEDITSECTION__
__NOEDITSECTION__

Latest revision as of 15:32, 16 May 2013


For a better understanding of simulation runs, features particular to the QA - Model will be presented in the following.


Project Planning

  • 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.


Simulation Time

  • 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.


First Proceed

  • After starting a new simulation run, a "proceed" will occur automatically. Afterwards, the task description will be displayed.

Resources

  • 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.