PROOF OF CONCEPT


EVALUATION • FEASIBILITY TESTS • PROTOTYPE DEVELOPMENT
VALUABLE LESSONS LEARNED • CHECKING RISKS • MORE PRECISE CALCULATIONS
Fotolia_60348307_grey
Are all our requirements feasible?
Does our strategy function in the real world?
Have we thought of everything?
How do we cope with new technologies?
How do we proceed in practice?
Where could there be problems?
How can we remove anything that's still unclear?
questions
questions
As part of the proof of concept workshop, we work together to test particularly important scenarios to prove the purely technical viability of the project and to estimate its complexity and the programming effort that will be required. Prototypes of essential and critical program functions are implemented, especially those that could prove to be a show stoppers, for example, access to a legacy system or an external solution, special interface features, interfaces to other programs, performance and load testing, etc. This will provide a wide range of tremendously valuable insights.
 
After this workshop, not only will you know how to proceed in developing with Java and RapidClipse, but you will also have a good idea of how complex your project actually is, how fast you can proceed working with RapidClipse, how long you can expect your team to require to complete the development with the technologies being used, whether your team might need to acquire additional expertise or bring in support, and especially if your budget is realistic.
 
A proof of concept also helps to identify unforeseen technical risks, conceptual, and also organisational deficiencies early on and address issues as they emerge. Above all, after this endurance test, you will be able to make a final decision with a clear conscience.
 
Duration: 1-5 days (depending on the project)

PROCESS

■ Evaluatiion helpful tools and frameworks
■ Set up of development and test environments
■ Development of diagnostically prototypes
■ Implementation of necessary key-features
■ Execution of load tests
■ Testing of interfaces
■ Implementation of critical use cases
■ Clarification of open questions questions by examples