When the client wants a predictive method, we recommend the so called "V" method:

 The white squares are the responsibility of the Stakehold while the red squares are the responsibility of the IT team.

1. Opportunity Analysis:

Analysis of the project's objectives and content; identification of the project's strategic issues; risk management, project organization, Return On Investment's calculation.

2. Feasibility study:

When the Opportunity Analysis is positive, the company has to make the feasibility study, which means: identify the project's objectives and constraints; make a detailed description of the existing situation; propose new scenarios to improve the existing situation; organize the change-management; define an action plan.

3. Functional Requirements Analysis :

This is the most important step, and leads to the Request For Proposal. If the company is satisfied with a rough description of its needs, no doubt she will encounter problems (see below).

The major challenge of any IT project lies in the communication between the client and the IT team : While the client complains that the IT team does not execute the client's requirements; the IT team becomes creasy because of the customer always changes his mind.
To resolve this major difficulty, COREAN uses UML's graphs as a translator tool between the customer and the IT team.
Indeed UML is the perfect tool for modeling business processes, in a way understandable by the customer through its various graphics. In the same time, UML is an IT language, allowing the IT team to understand the project. UML is the ideal tool to enable the client and the IT team to understand each other.

4. Functional Requirement Solution

The Functional Requirement Solution is the analysis created by the IT team, describing what has to be done. One it is validated by the client, it replaces the contract specifications. It is therefore essential for the client to exactly understand what lies in this document, otherwise he risks to endorse a project that
actually does not fit his need without any legal recourse against the IT supplier. COREAN supports his customer in verifying that this detailed study respects the client's whishes.

8. Validation

While functional tests are in charge of the client, the Stakeholder has to validate the product. in comparison with the Functional Requirement Analysis (which had been validated by the Stakeholder in step 4). COREAN supports customers in identifying how to test the product, and how to manage the IT supplier team during this stage.