Methodology

Ceacon’s Global Delivery Model is based on a comprehensive process framework, the Rational Unified Process (RUP), which provides proven best practices for software and systems delivery and implementation and effective project management. RUP provides guidelines, templates, and examples for each team member in the system development process and also supports the standard Unified Modeling Language (UML).
RUP promotes iterative development and organizes the development of software and systems into four consecutive phases, each consisting of one or more executable iterations of the software at that stage of development.

Inception
Elaboration
Construction
Transition

Inception
During this phase, we establish the business case and delimit the project scope. To accomplish this, we assess your requirements, identify all external entities with which the system will interact and define the nature of this interaction at a high-level. The outcome is a scope document consisting of a general vision of the core project’s requirements, key features and main constraints.

Elaboration
The purpose of the elaboration phase is to analyze the problem domain (identified in the inception phase), establish the technical architecture foundation, develop the project plan, and eliminate the highest risk elements of the project.

The activities in this phase ensure that the architecture, requirements and plans are stable enough, and the risks are sufficiently mitigated, so we can predictably determine the cost and schedule for the completion of the development.

Construction
This is a manufacturing process where all remaining components and application features are developed and integrated into the product, and all features are thoroughly tested. During this phase, emphasis is placed on managing resources and controlling operations to optimize costs, schedules, and quality. The outcome of the construction phase is a product ready to put in hands of its end-users.

Transition
In this phase, the developed software product is transitioned to the user-community. The focus is on the activities required to place the software into the hands of the users. Typically, this phase includes several iterations, including beta releases, general availability releases, as well as bug-fix and enhancement releases. Considerable effort is expended in developing user-oriented documentation, training users, supporting users in their initial product use, and reacting to user feedback.