Usability – a core value

Modern – Microsoft .NET and C#, a productive environment

Workflow integration – a leap beyond just shared data...

Allows our clients (the software developers) to

Extend mainstream workflows with proprietary IP

Focus on the added value, not the infrastructure

Fast and efficient from conception to end user delivery

The stability promise

Ocean has stability as one of its quality attributes. The stability promise is a promise to the consumers of Ocean that they will be able to focus on developing functionality and minimize the effort spent on porting to new versions of the framework. A published Ocean API will not be changed or removed for at least two full yearly sets of releases after it has been published. Before any stable API can be changed or removed, it will be marked as obsolete for at least one full yearly set of releases, which will produce compiler warnings and thus allow consumers of Ocean a grace period to upgrade their modules.

Some APIs may be tagged as “SubjectToChange”. “SubjectToChange” APIs are exempt from the stability promise. The “SubjectToChange” tag will typically be used for major new API developments and/or APIs that we know are likely to change for other reasons, and where we expect a few releases to converge to a sustainable stable API.

The stability implication

Upon the release of a new version of Ocean existing client modules that did not rely on deprecated or “SubjectToChange” Ocean APIs will only need a recompile with the new version to continue working. The typical porting effort for an Ocean module is in the order of a few minutes.