Features of the QA Model / Part 2

From Ameise-en
Revision as of 21:33, 17 April 2013 by Toffler (talk | contribs) (Created page with "====Model==== * The model is very complex. A lot of calculations have to be performed. Because of that, the execution of the several commands may take a lot of time. * All comma...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

Model

  • The model is very complex. 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 at the time at which an error report is submitted already several follow-up projects accrued, it is possible to hire a person to correct all of this projects ("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.
Retrieved from "https://ameise.aau.at/ameise/en/index.php?title=Features_of_the_QA_Model_/_Part_2&oldid=1080"