Synchrotech Group

To pilot a BI or CPM project in an efficient way, we put in place the following dedicated organization:

Depending on the project size, the client may nominate an Application Business Owner (ABO) to transmit all the information that our team may need to do their work quickly and efficiently. This role is guarantee that all the end user’s requirements will be well provided by the solution put in place.

In the same time, Synchrotech may nominate a program manager (member of the steering committee), a project coordinator and project leaders. The role of the program manager is to make sure that the project is well aligned with the strategy and the global vision of the client. The project coordinator is dedicated to have a transversal vision of the project and to assure that every tasks or phases are serving the same objective. And finally, the project leaders are set to control the progress of each deployment parts.

All the actors are communicating together according to a formal procedure. The steering committee meets either every month, or according to the need and the program manager meets the ABO either every week, or at the end of a phase for having a project review.

A project review occurs at the end of each project phase to identify the current status of the project. The Project Review identifies the deliverables which have been produced and determines whether or not the project has met the objectives set. By implementing project reviews and putting in place all necessary "check-points" to monitor and control the project, we ensure its success.

Results will be documented by stating, whether the following points are achieved:

• Project currently delivering to schedule
• Budget allocated sufficient at this point
• Deliverables produced and approved
• Risks controlled and mitigated
• Issues identified and resolved
• Changes properly managed
• Project on track

The testing plan will be done at the following different levels:

1. Unit test, which is under the development team’s responsibility, aims to assure that all functions and features of a single unit transaction are performed as specified in the design document. It could cover a group of closely related unit transactions as a single object. Unit testing is performed in isolation by the team member responsible for programming.

2. Integration test, which is under the technical team’s responsibility, aims to ensure that all interacting subsystems in a system interface correctly with one another to produce the desired results.  Furthermore, in trying to reach this goal, integration tests will ensure that the introduction of one or more subsystems into the system does not have an adverse effect on existing functionalities.

3. Performance test, which is under the technical team’s responsibility, is planned and executed on all components for which performance requirements and targets have been agreed with the client.

4. Capacity test, which is under the technical team’s responsibility, assesses the application behaviour running with the conditions of a deployed solution (notably the volume of data and the simultaneous connexions of users). The capacity test may reveal insufficient material resources for instance or network bottlenecks.

5. Solution test, which is under the functional team’s responsibility, aims to ensure that the application performs as per the functional specifications, approved by the client. Solution Testing is performed, once the Integration testing has been completed. Depending on the project, any regression tests deemed necessary. This phase is necessary to ensure the coherence of figures, business rules and calculations. It consists of sanity checks.

6. User acceptance tests (UAT) are under key users’ responsibility. Test cases will be provided as support of the application testing and user validation.