Features of the QA Model / Part 2

<<

Features of the QA Model/Part 1

Commands

>>

Model

• The model is very complex, and a lot of calculations have to be performed. Because of that, the execution of 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 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 follow- up 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.

<<

Features of the QA Model/Part 1

Commands

>>