A CMMI Level 3 Company
Quick Links
Related Links
UVJ Technologies

We use a software development process that is fully documented and constantly improved. It is based on best practices and industry standards like Agile-Scrum, Test Driven Developement, ProtoType Developement Model, Iterative-Incremental Model etc. We follow CMMI as the process model and maintain all process areas belonging to CMMI v1.2 maturity level 3. This process enables us to successfully develop projects within your budget and time frames and, of course, with world-class quality.

  • Our Software Development Approach
  • Our Process Model-CMMI
Software Development Approaches
  • Inception
  • Elaboration
  • Construction
  • Transition

software Development Approach

We have a defined process for project management and related process. Our Offshore development model has shown successful deliveries for more than 6 years. We were able to execute and deliver customer driven development using agile development models. The following are the basic phases in most of the project development.

  • Inception

Start of the project and initial requirements collection. Takes about 5-10% of the project.

  • Elaboration

Requirements collection and analysis, planning, creation of design and architecture of the system take place in this phase. Takes about 20-30% of the time.

  • Construction

The biggest part, where most of coding, development, and testing are performed. Takes about 50-70% of time.

  • Transition

It is when the results of our work are delivered to the customer and the product is installed. Takes about 10% of time.

These four stages are the integral part of any project. But then, depending on complexity of a project, its budget, and customer's goals, a project may or may not contain some parts, like user documentation preparation, extended technical documentation development, extra testing, etc.

This means that our process is flexible and can be customized according to your specific needs.

CMMI Advantages
  • Produce quality products or services
  • Enhance customer satisfaction
  • Implement cost savings and best practices


UVJ has achieved CMMI level 3 on Oct 2009. By enabling CMMI v 1.2 we are able to improve the whole project development as well as organizational development. CMMI Process has applied to the whole organization with the exception of Staff Augmentation and Customer support [IT Enabled] projects.

Our Software Engineering Process Group (SEPG) is an organization's focal point for software process improvement activities. SEPG and Quality Assurance perform assessments of organizational capability, develop plans to implement needed improvements, coordinate the implementation of those plans, and measure the effectiveness of these efforts.

CMMI Advantages

Produce quality products or services

UVJ's CMMI model has a strong focus on quality-related activities including requirements management, quality assurance, verification, and validation.CMMI provided a foundation for our enterprise-wide improvement and added new emphasis on our products and services as well as process emphasis on both process capability and organizational maturity by enabling measurement and analysis activities.

Enhance customer satisfaction

Meeting cost and schedule targets with high-quality products that are validated against customer needs is a good formula for customer satisfaction. That is the reason why UVJ specifically looks at the customer satisfaction metrics through surveys and feedbacks. We have good feedback process system to improve our customer satisfaction measurements and services improvements. Our CMMI reference model addresses all of these ingredients through its emphasis on planning, monitoring, and measuring, and the improved predictability that comes with more capable processes.

Implement cost savings and best practices

UVJ's all processes that are documented, measured, and continuously improved are perfect candidates for becoming best practices, resulting in cost savings for the organization. We encourage measurement as a managerial tool. By using the historical data collected to support schedule estimation, an organization can identify and widely deploy practices that work, and eliminate those that don't.