Proof-of-Concept: Test Data Management

Interested in our products and Test Data Management solutions? There is no need to go all-in when there are still obstacles to evaluate.
Proof-of-concept targets projects or departments that either has a legacy system running or only have the necessity for a new system. The main idea is to prove that the products and solutions provided can fulfill requirements towards the Test Data Management solution.
Typically, the scope of a proof-of-concept is limited to basic system functionality plus features or data processing of concern. The idea is to provide an end-to-end prototype for evaluation by the stakeholders underlaying that the Test Data Management solution fulfills critical requirements.

Information Consolidation and Scope

We offering an initial workshop to identify the challenges and identify a solution that fits the purpose. If requirements are clear, we will engage in a contracted Proof-of-Concept.

The PoC targets to implement a limited system that shows that crucial parts of the use-case or key features can be met by our software. Challenges could be consolidating data sources, specific data exports, common data views, work-flows, or analysis integration.

PoC Development

With the scope being defined, we start development. First, an application model is developed. It holds all information in the right place and is designed to fulfill the requirements. Next, we are developing the importer software to read, validate and store the data. This allows us to have a second workshop to present and evaluate results with generic components (ODS Server, Manatee Web, and HQL).

Once done, we focus on development efforts that are needed to fulfill the determined scope of PoC. Usually, this can be the implementation of interfaces, specific exports, components to integrate algorithms or web-based workflows.

Presentation and Evaluation

We usually deliver and install the PoC project on-premises. The results are presented and discussed with the customer. Also, out-of-scope requirements are discussed and an outlook is given on how this fits into the solution. A delivery includes:

• Importer Software
• Avalon ODS Server
• Manatee Web Application
• HQL

The PoC Delivery comes with free licenses to evaluate the functionality and present it to the users and stakeholders of the system. Thus, the customer can import some more data and gather interest and further momentum for the project.

Phases of Proof-of-Concept

Phases Content Content Exchange of Information • Introduction of the project
• Discussion of the challenges
• Understanding of HighQSoft products
• Delivery of test data for analysis
• Determining whether HighQSoft is the right partner
• Gathering materials for an PoC offer
Phase 1:
Information Consolidation & PoC Scope
A PoC is not a productive system.
• Detailed technical discussions
• Defining Data Sources
• Defining Import Process
• Limiting feature scope
• Information for application model and importer development is gathered
• Detailed scope for feature development is set
Step 2:
Import Development & Evaluation
• Project Setup
• Application Model development
• Importer Development
• Development of PoC Scope
• PoC Distribution for Download Step 3:
Delivery & Onsite Installation
• Delivery and Presentation • Proof on how the Test Data Management system fits into the customer environment Evaluation Period • Evaluation Phase • Next steps?

HighQSoft GmbH

Black-und-Decker-Straße 17c
D-65510 Idstein

Skip to toolbar