The QA - Model

From Ameise-en
Revision as of 14:48, 19 April 2013 by Toffler (talk | contribs) (Created page with "The '''QA-model''' is the first fully developed model, that is used for SESAM-simulation. The model is focused on the development of software for small to medium projects. To be ...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

The QA-model is the first fully developed model, that is used for SESAM-simulation. The model is focused on the development of software for small to medium projects. To be precise it is primary focused on quality assurance measurements. Because of this, the model is called quality assurance-model (QA-model).

The QA-model requires a proper procedure from the trainees for filling vacancies as well as the progress and quality control. The analysis, the specification, the coarse and fine design, code, and the manual as well as the integration and delivering of the system have to be performed. In addition, all documents have to be reviewed. Module, integration, system and acceptance tests also have to be performed. The trainee is also responsible for hiring employees, assign tasks to them and dismiss them.


All of this is carried out under the model dependent time and budget constraints!


Waterfall model

As process model, the waterfall model was chosen, where this has been extended by additional structural and analytical measures. The model leaves it to the trainees to decide in which order he performs the various activities. The possible procedures in the QA-model are shown in the following figure:


Possible procedures in the QA-model


The dashed arrows between the activities indicate that the trainee not necessarily have to act according to the waterfall model. While there is a predefined sequence between the phases, the trainee is not forced to act like that.


Code-and-Fix approach

However, he is at least forced to create an analyzing document and to do the implementation . All other phases between analysis and implementation can be skipped. Thus, the player can not be deterred from trying the code-and-fix approach.

Furthermore rollbacks to previous phases are possible, as long as the document to be jumped, still contains errors.


Erroneous documents can be checked and corrected as often as necessary!


It is important that the correction of a review has to be successfully completed before a new examination of the same document can be performed. After correcting as many activities as needed can be performed.