Executing the projects

The business systems we produce for our clients leverages the latest software technology and the production of this software is the responsibility of our Enterprise Solutions division. When our work builds upon a client’s existing infrastructure, we handle the integration of our products with legacy systems and maybe liaise with third–party software providers. During the implementation of a project, we choose specific methodologies and we complete the following separate phases:
Requirements Analysis. The Enterprise Solutions division cooperates closely with the customer. By meeting our client’s representatives we become familiar with the customer’s business, as a practice to track down any unachievable from technical point of view requirements that may put at risk the whole project. The deliverable of this phase is a Requirements Analysis Document which will be used as the basis for the design of the systems software components.

Design Phase We plan the detailed structure of the software, including core functionality, user interfaces, databases and integration with third–party systems. We use proven methodologies (such as the Unified Modelling Language-UML or the Microsoft Solution Framework-MSF) but we are not dogmatically constrained by them. One best practise we extensively implement is the use of “case specifications”; these help forming a common understanding between the end user and the developer.
Implementation We use approved change request and debugging methodologies, as well as documentation tools to monitor our progress towards the agreed project plan and achieve the company goals of audit ability. Thus, we ensure the baseline quality of code released for testing, virtually eliminating the need for in depth investigation of “show–stopping” problems.		Testing Phase Our testing methodology is based on multiple paradigms; we approach system testing using several different perspectives: “Risk Based Testing” which is an important part of the process, we prioritise effort and the allocation of resources according to the potential impact of the problem on the customer’s business. We also employ “Regression Testing” to ensure existing quality is maintained when new features are added, “Exploratory testing” which often pinpoints software “bugs” that slip formal design processes, as well as traditional “Test Case Based Testing” tools.