Software engineering


Deployment lifecycle embodies the manifestation of a component services to facilitate a business model. The service components of the system architecture are designed, implemented, integrated an deployed. Each service component may be developed independently in parallel up to a point at which integration is required to satisfy deployment requirements. Testing of individual components and integrated versions are required during design, implementation and deployment phases.

Policy Design, Implementation and Itegration

Policy design and implementation provision the successful integration and deployment of an enterprise architecture. Policies uphold transactional communication between essential business services based on requirements for security, reliability, quality of service and performance. Protocols and complex conversations for policy are orchestrated through the design and implementation of ESB workflows.

Architecture - Event Driven

Architecture consists of specifications for software, hardware and networks for a particular business solution. Architectural artifacts present the structural components of a solution for an significant business challenge. Scope, requirements and use case provide essential inputs to develop meaningful document artifacts for a successful solution.

Use Case

Use case describes the context or process wherein a product or product component, subpart, is used within. Hence the use case specifies the function or operation of each deliverable product or component. Use case is specified in a procedural outline with logical branches and sub-cases to describe various conditions in the operation of a product or component. UML, pseudocode or a procedural language can be used to document the use case. Actors or user roles in the use case demonstrate interactions of the product or component with external entities.

Supply Cloud

OVium uses web service technology to integrate purchasers and suppliers. OVium implements XSD message discovery protocols, REST, and standard oriented WSDL protocols such such as WS-*, Transaction, Reliability, Policy, Security, Trust as BPEL. For simple implementations with limited service dialogue, REST provisions information transactions adequately however for more complex purchase requisition workflows, WSDL provides the necessary formalism, with WS-RS extensions for ad hoc REST requirements.


Cloud computing along with knowledge and social network development require message workflow dependencies to be orchestrated between endpoints. Hence cloud resources require dialogue between a group of endpoints beyond simple point-to-point message transaction. OVium supports orchestration with enterprise service bus (ESB) technology to route messages while coordinating pipeline or workflow. Multiple ESB's can share or load-balance orchestration efforts from distinct processing or geographic endpoints.


OVium embraces process methodology to facilitate full cycle deployment and maintenance of products for clientele. The Ovium process methodology is proven in software development life-cycles (SDLC) and in the implementation of large corporate processes. To this purpose "Agile" and Rational Unify Process (RUP) methodologies influence OVium's approach to shape product life cycles, both internally or externally managed.

Cloud Navigation

OVium develops solutions for a variety of application domains, including supply chain, brand development, green energy, bio-informatics and social networking. Global economy expansion relies to an increasing extent on emerging market products and information resources that offer significant advantages.

Syndicate content