aavanor_logo                                          

     Quality  
Our development methodology places a huge emphasis on Quality Assurance and very high OOP's coding standards.
Clarity in Requirements
Systematic Development
  Development Process
  Development Phases
Assurance through Testing
    
 
Systematic Development
During Requirement analysis phase

At Aavanor we follow a solution oriented development methodology designed to minimize project risks and development time.

We focus on business solutions that fulfill business goals, instead of merely providing technical solutions. All our applications are built on the basis of this philosophy.

We have defined processes for requirements capture, analysis, design, development, testing and deployment. We generate UML diagrams representing the

  • Use Case Model
  • Analysis Model.
  • Design Model.
  • Implementation Model and
  • Test Model.
Quality in development is ensured by the following Phases
Project Phase Quality Process Owner Document Tool
High level Design System architecture design, Database design, Design of UML class

 
System Architect/ Design Prototype, SRS, Use case documents UML tools, Data Modeling tools for database design
Detail Design Pseudocode, Class, Object, follow coding standard Development Prototype, SRS, UML Diagram UML tool
Coding & Unit test
 
Follow coding standards and use tools to ensure adherence to standards, and evaluate quality of code

Write test scripts and use unit test tool to test
 
Development Prototype, SRS, UML Class Diagram Development IDE like Eclipse and VS.NET

Tools to ensure better quality of code such as
Check Style and PMD Unit test tool like Junit and Nunit

Build Process Build the module/project using build tool like Ant, Nant Development Classes, Objects, programs Build Tools like Ant, Nant
Integration
 
Integrate all program and test module/project wise Development Unit test results  
Deployment Plan the details of deployment procedures and deploy at clients place Development Prototype, SRS,
Source code, Deployment Plan
 
UAT Get the Sign off from client. Transition of application to the maintenance Development Prototype, SRS