• English
  • Français

ngimg0

 

METHOD

 

 

Software development industrialization requires a certain procedure, which means that the implementation of an adapted and progressive methodology is necessary. Besides the composition of a quality assurance plan (QAP), we also endorse the following principal methods:
Before we present ideas for improvements, we help our clients determine their level of maturity in relation testing and software quality. Following the results of this audit, we are able to define improvement objectives, as well as the means to reach the established goals.

TMMi
The TMM (Test Maturity Model) is one of the methods we use.
The TMM or TMMi method is based on the CMMi approach, but specifically focuses on the management of the testing process in the company’s R&D department.
5 levels of maturity are defined.
 

 

=

 


 

Level 1 (Initial): At this level, testing is once again considered to be a part of the debugging procedure.
There is no formalized process, tool or dedicated team. The main objective is to show that the software works.
Level 2 (Definition): Testing is a clearly defined and self-directed process in relation to development teams. Structuring the process is accomplished through the creation of a test strategy and test plans based on requirements. The main purpose of testing is to demonstrate that the specification requirements have been implemented. The tests, however, are often executed late in the software development process, usually during the coding procedures.
Level 3 (Integration): Formalizing test plans begins when the specifications are established. The test strategy integrates risk management and is based on documented requirements. The testing profession is recognized. In addition to verifying the requirements, tests are more oriented towards detecting bugs.
Level 4 (Management and Assessment): The testing process is clearly defined and measurable. Assessment of the software is completed through the use of quality principles, such as reliability, usability and maintainability. The use of tools (testing database, non-regression test automation, etc.) takes place during the test process.
Level 5 (Optimization): The improvement of the process is ongoing and the concepts for productivity and the prevention of quality control shortcomings are integrated in the approach.
TPI
The TPI model is another approach founded on established principles regarding the improvement of testing procedures.
The model defines practical issues involved in evaluating the level of testing maturity in an organization and the progressive improvement of procedures.
The model is an international standard for the improvement of testing procedures.
The model is frequently used in organizations that want to achieve the CMM 3 level (Capacity Maturity Model or the model for developing software capabilities) in the area of testing.
Twenty key sectors are included in the model and each key sector has several levels of maturity, all of which are represented in a matrix of maturity. Monitor points are included at every level. Suggestions for improvement resulting in the achievement to a certain level are also included in the model.
Return experience of ALL4TEST consultants also allows us to adapt these methods according to the limitations of small businesses (SME) in order to allow them to initiate this quality approach in a less restrictive and quicker manner.
 
 
CMMI
 
The CMM is a frame of reference for key practices to be implemented for companies that develop software. Its purpose is to guide companies in their approach for improving procedures. The “Capability Maturity Model” became a reference because of the increasing support associated with these procedures. Subsequently, the CMMi has been recognized as the successor to CMM and has a much broader influence than its predecessor, especially in the area of software development, which is found in other sectors, particularly in systems engineering and software acquisition.
In partnership with the lead CMMI appraisers of ALL4TEC, we help our clients in the process of implementing a CMMI approach within their organizations, especially for the purpose of evaluating results or procedures for tests and traceability.