Difference between revisions of "The QA - Model"

From Ameise-en
 
(One intermediate revision by one other user not shown)
Line 3: Line 3:
  
  
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 and therefore the model is called Quality Assurance - Model (QA - Model).
+
The '''QA - Model''' is the first and fully developed model that is used for SESAM simulation runs. The model focuses on the development of software in small to medium sized projects. To be precise, it is primary focused on quality assurance measurements and therefore the model is called Quality Assurance - Model (QA - Model).
 +
 
 +
From trainees, the QA - Model requires proper staffing as well as the monitoring progress and quality control. Thereby, analysis, the specification, the system and module design, code, and the manual as well as the integration and delivery of the system have to be performed. In addition, all documents have to be reviewed and corrected. Also, module, integration, system and acceptance tests have to be performed. Trainees are also responsible for hiring employees, assigning tasks to them, and releasing them back into the pool of developers.  
  
The QA - Model requires a proper procedure from 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 delivery 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. Trainees are also responsible for hiring employees, assign tasks to them and release them.
 
  
  
 
{| style="width:100%;background:#FFFFCA;padding:0.5em" |
 
{| style="width:100%;background:#FFFFCA;padding:0.5em" |
 
|-  
 
|-  
| All of this is carried out under the model, depending on time and within the budget!
+
| All of this has to be done on time and within the budget!  
 
|}
 
|}
  
  
 
===Waterfall Model===
 
===Waterfall Model===
The [[Waterfall Model]] was chosen and has been extended by additional structural and analytical measures. The model leaves it to the trainees to decide in which '''order''' they perform the various activities. Possible procedures in the QA - Model are shown in the following figure:
+
The [[Waterfall Model]] was chosen and has been extended by additional structural and analytical measures. The model leaves it up to the trainees to decide in which '''order''' they perform the various activities. Possible phases in the QA - Model are shown in the following figure:
  
  
Line 21: Line 22:
 
 
  
The dashed arrows between the activities indicate that trainees do not have to act according to the waterfall model. While there is a predefined sequence between the phases, the trainees are not forced to act like that.
+
The dashed arrows between the activities indicate that trainees do not have to act according to the waterfall model. While there is a predefined sequence between the phases, the trainees are not forced to follow them at all.  
  
  
 
===Code-and-Fix Approach===
 
===Code-and-Fix Approach===
However, the trainees are at least forced to create an '''Analyzing Document ''' and to do the '''Implementation '''. All other phases between analysis and implementation can be skipped. Thus, trainees can not be deterred from trying the Code-and-Fix approach.
+
A code-and-fix approach is possible; however, the trainees are at least forced to create an '''Analyzing Document ''' and to do the '''Implementation '''. All other phases (between analysis and implementation) can be skipped. Thus, trainees are not retained from trying out the Code-and-Fix approach.
  
Furthermore  '''Rollbacks''' to previous phases are possible, as long as the document to be jumped, still contains errors.
+
Furthermore  '''Rollbacks''' to previous phases are possible, as long as the document created in that phase, still contains some errors which are not corrected.  
  
  
 
{| style="width:100%;background:#FFFFCA;padding:0.5em" |
 
{| style="width:100%;background:#FFFFCA;padding:0.5em" |
 
|-  
 
|-  
| Documents with remaining errors can be checked and corrected as often as necessary!
+
| 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 the documents, as many activities as needed can be performed.  
+
It is important to note that the correction after a review has to be successfully completed before starting a new review. After correcting the document, all other activities can be executed in the usual manner.  
  
  

Latest revision as of 15:36, 16 May 2013


The QA - Model is the first and fully developed model that is used for SESAM simulation runs. The model focuses on the development of software in small to medium sized projects. To be precise, it is primary focused on quality assurance measurements and therefore the model is called Quality Assurance - Model (QA - Model).

From trainees, the QA - Model requires proper staffing as well as the monitoring progress and quality control. Thereby, analysis, the specification, the system and module design, code, and the manual as well as the integration and delivery of the system have to be performed. In addition, all documents have to be reviewed and corrected. Also, module, integration, system and acceptance tests have to be performed. Trainees are also responsible for hiring employees, assigning tasks to them, and releasing them back into the pool of developers.


All of this has to be done on time and within the budget!


Waterfall Model

The Waterfall Model was chosen and has been extended by additional structural and analytical measures. The model leaves it up to the trainees to decide in which order they perform the various activities. Possible phases in the QA - Model are shown in the following figure:


Possible Procedures in the QA - Model


The dashed arrows between the activities indicate that trainees do not have to act according to the waterfall model. While there is a predefined sequence between the phases, the trainees are not forced to follow them at all.


Code-and-Fix Approach

A code-and-fix approach is possible; however, the trainees are at least forced to create an Analyzing Document and to do the Implementation . All other phases (between analysis and implementation) can be skipped. Thus, trainees are not retained from trying out the Code-and-Fix approach.

Furthermore Rollbacks to previous phases are possible, as long as the document created in that phase, still contains some errors which are not corrected.


Documents can be checked and corrected as often as necessary!


It is important to note that the correction after a review has to be successfully completed before starting a new review. After correcting the document, all other activities can be executed in the usual manner.