Use suitable tools to make your projects transparent and fully traceable – throughout all phases

For the development, testing and operation of software, a variety of tools are used to support and document the associated activities. Some important categories of tools are:

  • Application Lifecycle Management (ALM): ALM describes the path of a software through all phases of the software lifecycle from the collection of requirements to the operation of the software. Typically, ALM includes the categories listed below or at least can be integrated.
  • Requirements management: This includes the structured collection and management of requirements and ideally combines this with traceability to the functions and artefacts implemented in the development process.
  • Test management: Test management includes all activities for planning and steering as well as controlling test activities (for details, see the link to the insert test management page).
  • Error management: The structured recording and processing of errors (“bugs”) is the task of error management.
  • Test automation: This term covers tools and frameworks for automated software testing (for details see insert link to the test automation page).
  • Code analysis: These are tools that can be used to perform static code analysis. The source code is subjected to a series of formal checks that allow certain types of errors to be detected even before the software in question is checked by further (manual) testing (for details, see the link to the insert software quality page).

The selection and introduction of a suitable tool is of great importance for the efficiency and quality of the development and testing process as well as the operation of software. Benefit from our expertise in this area.

How we proceed with the tool selection and implementation

  • Identification of the relevant stakeholders
  • Determination of the relevant processes and interfaces
  • Survey of functional and non-functional requirements
  • Creation of an evaluation matrix for the selection of the tool
  • Conducting a market analysis
  • Creation of a longlist
  • Derivation of a shortlist for the actual tool selection
  • Application of the evaluation matrix
  • Workshops with selected providers
  • Selection of the tool
  • Application of the tool in one or more pilot projects
  • Integration into existing processes and tools
  • Implementation of Lessons-learned workshops
  • If necessary, customising of the tool to the individual needs
  • Creation of a training and operating concept
  • Development of an implementation plan including pilot groups
  • Extension to all relevant users
  • Documentation for system operation

We advise you in all phases of tool selection and implementation. In doing so, we apply a proven procedure which we adapt to the task at hand on a case-by-case basis.

The selection of a tool is a step-by-step decision-making process based on clearly defined milestones or interim results:

  • In the requirements analysis, the functional, non-functional, technical and possibly also economic requirements are to be recorded and documented in a structured manner. An evaluation matrix is to be created from these requirements, which enables a comprehensible and transparent decision to be made. On the one hand, this matrix includes knock-out criteria, the non-fulfilment of which means the exclusion of the respective tool from the further decision-making process. On the other hand, a prioritisation and selective evaluation for the various requirements is defined.
  • Based on a market analysis, a longlist of suitable tools is drawn up as part of a pre-selection process. By applying knock-out criteria as well as meeting important requirements, this longlist can be reduced to a shortlist.
  • The requirements defined in the evaluation matrix are sent to the tool manufacturers and their feedback is evaluated. In addition, workshops including live demonstrations are often held. Based on this information, the selective evaluation and, as a consequence, the tool selection is carried out.
  • It is then recommended that a proof of concept (PoC) be carried out. In this, the tool is used in a representative pilot project and tested “thoroughly” in practice. The experience gained from this project should be evaluated, e.g. in order to be able to make corrections (customising) to the tool or the usage process. In addition, the tool will be integrated into the existing IT landscape.
  • A well planned introduction and training is crucial for the acceptance of the chosen tool. This concerns both the success in practical use and an orderly regular operation.

Advantages of test management

Optimal use of your resources

Through a defined selection process, the (internal) resources are used optimally and the effort for the stakeholders involved is reduced.

High transparency

A well documented selection process creates transparency for the selection process and avoids lengthy and costly decision-making processes.

Use of best practices

Deposit of best practice models for the standardisation and quality improvement of work results.

Reduced risk

A systematic process for tool selection significantly reduces the risk of acquiring an unsuitable or inefficient tool.

Our experience – how our customers benefit from our expertise

As an IT consulting company with 50 years of experience, PTA has many years of expertise in tool selection. Our customers include medium-sized and large companies from a variety of industries, who use our customised test automation systems to sustainably increase their innovation rate and productivity.

Do not leave your success to chance

Rely on the experience and know-how of PTA for continuous quality assurance.