1. Business Modeling
Pluriva uses Business Modeling discipline to completely understand the organization in which the system will be deployed. From the beginning, we establish a communication channel between the business model and the software engineering. Understanding the business means we understand the structure and the dynamics of the client organization, the current problems, and possible improvements on the IT side.
Using for example Rational Requirements Composer and Rational Software Architect

2. Requirements
The goals of the Requirements discipline are:
Working closely with the client to understand his needs;
Defining the scope of the project;
Identifying and prioritizing new or changed requirements.
We use this discipline to have a groundwork for organizing and efficiently managing requirements and project document information.
Using for example Rational Requirements Composer and Rational RequisitePro

3. System Design
The output of the System Design discipline is a design and analysis model. Pluriva performs this activity to decide how the source code would be structured and written. The system designed by Pluriva needs to perform the tasks and functions specified in the use-case descriptions and to fulfill all its requirements.
In order to get projects done on time, within budget and at the best quality level, we strengthen the ability to capture the requirements and develop a performing yet modifiable software system.
Using for example Rational Software Architect

4. Implementation
We organize the implementation process in subsystems, prearranged in layers. The goal of the Implementation discipline is to apply classes and objects in terms of components (source files, binaries, executables, and others).
This phase also includes testing the developed components as units and the integration of the results produced by individual implementers  into an executable system.

5. Deployment and Documentation
The Deployment Discipline is Pluriva's tool to deliver the software to its end users and to successfully produce product releases. Our specialists cover a wide range of activities, including creating external releases of the software, distributing the software, packaging the software, packaging the business application, installing the software, and providing help to users.
The user documentation written by Pluriva’s engineers describes each feature of the program, and assists the user in realizing the features.
We use different IDE (Integrated Development Environment ), for example Rational Software Architect or Microsoft Visual Studio

6. Security
We are able to implement centralized user authentication and authorization management for different online portal and business initiatives.  We provide advanced security capabilities to address key Web vulnerabilities and support flexible strong and risk-based authentication.
In our projects, we define and manage a centralized authentication, access, and audit policy for a broad range of business initiatives such as employee, customer and partner portals, CRM systems, e-procurement, cross-company single sign-on (SSO) projects, and outsourcing projects.
Using for example IBM Tivoli (TIM / TAM) and Web Seal

7. Test
Quality Manager is used for defect management, test management and planning;
Performance Tester is an automating testing tool for validating application & system performance;
Functional Tester is an automating testing tool for validating application & system functionalities;
Service Tester is an automating testing tool for validating application & system on the web servce level;
AppScan – validates the security of the system.
Using for example IBM Rational solutions

Phases:
Performance Tester is used on the System Test and Acceptance Test phases;
Functional Tester is used on the Acceptance Test phase;
Service Tester is used on the System Test phase.

8. Configuration & Change Management
Using the Configuration & Change Management discipline, we manage the following activities: Change requests, Planning configuration control, Setting up the CM environment, Monitoring and reporting configuration status, Changing and delivering configuration items and Managing baselines and releases.
Configuration management is our tool for the methodical structuring of the products. Artifacts such as documents need to be under version control and these changes must be visible.
Using for example Rational Team Concert

9. Components Integration
We manage various synchronous and asynchronous integration flows, including business rules and business processes.
Using for example Websphere MQ and Websphere Business Integration Modeller.

10. Application Lifecycle Management
Over all the software development process, it does apply the application lifecycle management, starting from business modeling and requirements and going to deploy and testing.
Using for example Rational Team Concert or Microsoft Team Foundation Server