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 31: | Line 31: | ||
__NOEDITSECTION__ | __NOEDITSECTION__ | ||
[[de:Besonderheiten des Modells/2]] | [[de:Besonderheiten des Modells/2]] | ||
[[en:Features of the | [[en:Features of the QA Model/Part 2]] | ||
<!-- | <!-- | ||
[[sk:Hlavná stránka]] | [[sk:Hlavná stránka]] | ||
[[fr:Accueil]] | [[fr:Accueil]] | ||
--> | --> |
Revision as of 20:29, 8 May 2013
Model
- The model is very complex and a lot of calculations have to be performed. Because of that, the execution of the several commands may take a lot of time.
- All commands, which are not immediately confirmed with a feedback after a proceed were not 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 does 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 works are demounted into work packages. These packages enable parallel working but it does not make sense to let several people working on one package.
Errors in document
- Errors that are found in reviews or tests are not correcting themselves!
- If an document is submitted and there are already several follow-up documents accrued, it is possible to hire a person to correct all errors of this documents ("correct all documents").
Integration
- Don’t forget to implement the code. A delivery to the customer is only possible if at least 50% of the requirements have been integrated.