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

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


====Model====
====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.
* The model is very complex, and a lot of calculations have to be performed. Therefore, the execution of several commands may take a certain amount 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.
* 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:
** finish/quit activity does not give a feedback if the developer has no job.
** "finish/quit activity" does not give a feedback if the developer has no job at all.
** show available developers does not give a feedback if there are no free developers available.
** "show available developers" does not give any feedback if there are no free developers available.
** show hired employees does not give a feedback if no developers are hired.
** "show hired employees" does not give any 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.
** "integrate" requires that at least 50% of the requirements have been implemented in the code. Otherwise, the commando will not be executed.




====Work packages====
====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.
* 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 document====
====Errors in Documents====
* Errors that are found in reviews or tests are not correcting themselves!
* 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").
* If a review/test report is submitted, and there were already several subsequent documents developed, it is possible to let a developer correct all errors of these subsequent documents("correct all documents").




====Integration====
====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.
* Do not forget to integrate 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}}
[[Category:Tutorial]]
[[Category:Tutorial]]
__NOTOC__
__NOTOC__
__NOEDITSECTION__
__NOEDITSECTION__
[[de:Besonderheiten des Modells/2]]
[[de:Besonderheiten des Modells/2]]
[[en:Features of the model/2]]
[[en:Features of the QA Model / Part 2]]
<!--
<!--
[[sk:Hlavná stránka]]
[[sk:Hlavná stránka]]
[[fr:Accueil]]
[[fr:Accueil]]
-->
-->

Latest revision as of 16:35, 16 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 certain amount 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 at all.
    • "show available developers" does not give any feedback if there are no free developers available.
    • "show hired employees" does not give any feedback if no developers are hired.
    • "integrate" requires that at least 50% of the requirements have been implemented in 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 review/test report is submitted, and there were already several subsequent documents developed, it is possible to let a developer correct all errors of these subsequent documents("correct all documents").


Integration

  • Do not forget to integrate the code. A delivery to the customer is only possible if at least 50% of the requirements have been integrated.
Retrieved from "https://ameise.aau.at/ameise/en/index.php?title=Features_of_the_QA_Model_/_Part_2&oldid=2015"