Features of the QA Model / Part 2: Difference between revisions
From Ameise-en
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
* The model is very complex, and a lot of calculations have to be performed. Therefore, the execution of several commands may take a lot of time. | * The model is very complex, and a lot of calculations have to be performed. Therefore, the execution of several commands may take a lot of time. | ||
* All commands, which are not immediately confirmed with a feedback after a proceed | * All commands, which are not immediately confirmed with a feedback after a proceed will not be executed. This may be due to problems of command recognition or the model does not allow an action because of the current situation. | ||
* Exceptions: | * Exceptions: | ||
| Line 24: | Line 24: | ||
====Integration==== | ====Integration==== | ||
*Do not forget to implement the code. A delivery to the customer is only possible if at least 50% of the requirements have been integrated. | * Do not forget to implement the code. A delivery to the customer is only possible if at least 50% of the requirements have been integrated. | ||
{{NavigatorBar|Features of the QA Model/Part 1|Commands}} | {{NavigatorBar|Features of the QA Model/Part 1|Commands}} | ||
Revision as of 18:42, 12 May 2013
Model
- The model is very complex, and a lot of calculations have to be performed. Therefore, the execution of several commands may take a lot of time.
- All commands, which are not immediately confirmed with a feedback after a proceed will not be executed. This may be due to problems of command recognition or the model does not allow an action because of the current situation.
- Exceptions:
- "finish/quit activity" does not give a feedback if the developer has no job.
- "show available developers" does not give a feedback if there are no free developers available.
- "show hired employees" do not give a feedback if no developers are hired.
- "integrate" requires that at least 50% of the requirements have been implanted into the code. Otherwise, the commando will not be executed.
Work Packages
- Big tasks are fragmented into work packages. These packages enable parallel working, but it does not make sense to let several developers working on one package.
Errors in Documents
- Errors that are found in reviews or tests are not correcting themselves!
- If a document is submitted and there are already several following documents accrued, it is possible to hire a developer to correct all errors of this documents ("correct all documents").
Integration
- Do not forget to implement the code. A delivery to the customer is only possible if at least 50% of the requirements have been integrated.
