Home > Quality Policy and Process
Quality Policy and Process


Quality Policy

“We are committed to remain proactive in developing competitive solutions and systems while unceasingly endeavoring to exceed customer expectations by involving the right people and adopting the right process, methodology and productivity improvement tools, in a flexible manner.”

Quality Objectives & Initiatives

We are ISO 9001:2015 certified company and strictly adhere to the processes enlisted in the Quality Management System (QMS) Manual. The QMS manual is updated regularly for continual improvement.

Spend sufficient time in specification study and prepare efficient design for the project considering possible changes in the project’s requirements that could crop up in future.

  • Regularly conduct design and source code reviews
  • Prepare unit test and integration test specifications by considering all the possible test cases and conduct testing based on customer’s specifications
  • Prepare simulation environment for testing depending on the project scenario
  • Follow coding rules diligently
  • Maintain regular communication with the client and document the same throughout the SDLC
  • Striving towards continuously enhancing customer satisfaction
  • Ensure timely completion of projects by adhering to well-defined process and performance metrics
  • Deliver services that meet customer’s needs and requirements


Process Methodologies

Nichi-In adopts a customer centric interactive approach based development methodology that guarantees superior customer experience with respect to time, cost, and quality. We also adopt the appropriate business model such as Offshore, Onsite or a mix of both, that suits the requirement best. 


Highly-Skilled Project Management Team

Project Managers, Leaders and the Team in general have rich onsite and offshore experience and follow a well-defined delivery model which has matured over the years.


Development Model

We adopt methodologies flexibly based on the requirement of the project and the customer’s reciprocation. Some of the commonly used models are Agile, Waterfall, Prototyping and Spiral models.


Agile Models (Scrum/XP)

  • Though there are many agile models but in order to provide maximum benefits to customers, we particularly prefer Scrum and Extreme Programming (XP)
  • With Extreme Programming (XP), changes in a project can be smoothly incorporated in a cost-effective manner without disturbing the development process cycle
  • With Scrum, cross-functional teams develop software products in an iterative, incremental manner in cycles of work called Sprints. Each Sprint is incremented usable software. With completion of the Sprint, the final software is ready for customer demonstration.
  • Depending on the project needs, we also follow a hybrid model that incorporates the benefits of XP and Scrum methods to provide maximum gains associated with the project.


Waterfall Model

Waterfall model is a well-structured model. Here, development progresses steadily downwards, completing each phase in a sequential manner. The next phase of development starts on the achievement of defined goals of the previous phase.


Prototyping Model

In the prototyping model, an early approximation of the final product or system (termed as a prototype) is built, tested and delivered to customer for evaluation. Any suggestion made by the customer on improvements on the prototype is implemented and send to customer for re-evaluation. This process continues until an acceptable prototype is achieved from which the complete product or system is  developed. The model works best in the scenario when all requirements related to the project is obscure or not known in detail ahead of time.


Spiral Model

Spiral model encompasses the features of waterfall and prototyping model while giving emphasis to risk analysis. It is best suited for large, complicated projects.


Review Development Process

  • Reviewing by walk-through format that is assuming the program flow by visualizing the specifications and finding bugs or loopholes
  • Reviewing source code
  • Applying top-down testing for program modules
  • Implementing third party testing


Quality Monitoring Through Constant Review

  • Requirement definition review
  • Basic design review
  • Detailed design review
  • Code review
  • Test plan review