Business Modeling
The process of solution conception, implementation and delivery starts with the Business Modeling and Requirement Analysis. This is a process to define the scope and set the business context. During this period we work in conjunction with the client to understand their requirement and propose a detailed solution. This process results in the following deliverables:
A context model – This shows how the solution fits in the entire scenario. The context model is often in the form of a Data-Flow diagram. Use cases model – This is a top-level business requirements model. It helps in designing the quality analysis parameters.
Domain model – This is the class diagram or data diagram that helps in determining the business entities.
Business process – This model shows the flow of data among the several business entities present in the system.

Developing of the solution
We follow an iterative software development process that ensures we work very closely with the client. There is a defined process of change management, which helps us to attain post-SRS changes faster. The development process is based on templates and components thereby resulting in development of repository, which is maintained based on the terms of agreement with the client.
The major deliverables for this phase are the following: Periodic status reports Alpha Delivery for the solution

Requirement Analysis
This is the research and analysis part of the process. In this phase the business model is fleshed out and each top-level requirement is identified and modeled. This is also a phase of extensive documentation. The principle deliverable of this phase is the Software Requirements Specification (SRS).

Deployment and Implementation
This is a post-testing phase and is marked by the “Gold Delivery” or the“Release” of the solution. During the entire process of development and testing there is continuous communication with the client. This ensures that the deployment is based on the client's expectation and it is in accordance to the business context identified in the beginning of the solution development phase
(See Business Modeling ).

Testing of the solution
This is the Quality Analysis process and is marked by numerous pre-release deliveries such as alpha, beta, release candidates, etc. The principle activity in this phase is the implementation feedback of the Quality Analysis performed on the developing solution.
The Quality Analysis is primarily done on the “Use Cases” created as a part of the Business Modeling . The process of Quality Analysis is a recurring process and is performed top-down on all the iterations. The critical components of the solution are kept in lower iterations to ensure repetitive and continual Quality Analysis.

Support and Maintenance
Kinis Solutions provide a limited-time free support for the solution, which is mutually decided with the client at the beginning of the solution development phase. This involves installation of the solution, documentation of all the user aspects of the solution and online support services. Clients also have the option of engaging us for further maintenance. This is a completely separate activity from solutions development. 

Solution Designing and Prototyping
The requirements identified so far are transformed into software model designs. These models are then brought together to form the architecture of the entire solution. This process results in the development of the Technical Specifications Document, which is often accompanied by a Look and Feel Document to define the graphical layout of the solution.Based on the client's requirement and the complexity of the solution a prototype is made and is delivered for the following purposes:
Better understanding of the product
To assess the feasibility of the solution
To understand the implementation environment issues