SOA development process

Rebecca development process introduction


rebecca Copy 1500x1680


Rebecca development process is a simple and easy framework defined by Pymma’s architects to design and develop application and architecture with a services orientation. The main principle of Rebecca is to be a simple and structured approach understandable by teams and people working in IT. We designed Rebecca neither for reorganizing companies’ IT infrastructure nor to structure global enterprise architectures. Rebecca goal aims to help teams involved in a service oriented projects, make easier communication between stakeholder, business, development and support. Rebecca does not attempt to replace PM method (agile or not) but its purpose is to structure and organize service oriented projects and avoid the main pitfalls found in this kind of project. Rebecca is easy to understand and does not require a strong methodology background. We tried to ward off the complexity found in many development processes. To keep Rebecca simple, short and useful for each one, the user can easily inject in the process backgrounds and feedbacks from external sources and a large latitude is let to personal initiative define steps and to-dos. Rebecca users could start with a predefine template and refine it when their background increases. They can take advantage of external consultant’s skill to refine steps and to-dos.


Rebecca mecanism
Tasks example
Preliminary task

Rebecca development process






Rebecca relies on the mechanism popularized by TOGAF and described in the document above. The process defined main tasks, their objectives, inputs, outputs and to-dos. We replace the name “step” defined in TOGAF by “to-do” since we find it more explicit. During the project development, tasks exchange documents and to-dos through the central repository as well. In TOGAF specifications, Tasks’ name and number are well defined, ditto for the steps. On its part, Rebecca does not come with these constraints. A project team can start Rebecca from scratch or use standard tasks and to-dos template such as the ones defined by Pymma and upgraded by the users ‘community. Pymma’s templates are the result of many years of work on SOA and integration projects. Likewise, anyone can determine his own projects and to-dos accurate with his task and his own context. Rebecca imposes neither task number, nor name, nor to-dos. These parameters could be defined regarding the project scope, teams’ skill and background of the involved in the project. Pymma provides a template with our best practices that can be enrich during the project development.

Rebecca tasks example




Pymma defines 9 tasks in its service oriented development process.



Rebecca Preliminary task



It is the preliminary step in the process

It is a mandatory step

Prepare and install the process

Fix Project rules and objectives



Gather all the documents useful for the process and project

  • Business requirement
  • Budget
  • EA rules
  • Security rules
  • Output

  • Confirmation feasibility
  • Project Organisation
  • Process definition
  • Team definition resources needed


Check Business objectives

Stakeholders and Sponsors

Stakeholders objectives

Sponsors expectations


Fix project scope

Regarding the budget

Competency in your team



Confirm project feasibility

Confirm feasibility


Evaluate internal competency and skill

Evaluate needs for external resources


Non functionnal objectives 

  • Performance
  • Security
  • SLA
  • Project Organisation

  • Team definition
  • Competency

Project governance

  • Governance criteria
  • Governance organisation
  • People and teams