Lifecycle Methodologies and Tools

The Fruition development team adopts project methodologies based on the client's project specifications and requirements. Fruition has extensive expertise on the following methodologies:

Waterfall Model

This life-cycle model demands a systematic, sequential approach to software development that begins at the Customer's software requirements and progresses through analysis, design, coding, testing and post development warranty and is considered an ideal choice when the user's software requirements are clearly stated at the inception of the project.

Object Oriented Model

Each Object Oriented Development Project that is taken up by Fruition may go through all or some of the phases of the Software Development Life Cycle (SDLC) defined by Fruition's QMS procedures. This methodology is used to define the activities and work products for each phase and in projects where the development tasks arrive as work packets. The phases of execution, the associated work products, verification and validation criteria for each of the relevant phases shall be at par with this methodology.

Prototyping Model

This methodology defines a mechanism to handle concept building and / or prototyping projects and is used by Fruition in complex projects in order to understand requirements better, to reduce design risks and to share the user interface with the Customer. Concept building projects are typically of an R&D type, where the goal is to arrive at an optimal solution based on a short description of requirements by the Customer. 'Throwaway' or 'Evolutionary' prototyping (Spiral Model) are used depending on whether the model would be discarded after use or would be adapted after use until it eventually evolves into the product.

Incremental Model

The Incremental model of development is an evolutionary model that combines the elements of the linear sequential model (Waterfall model) and the iterative philosophy of Prototyping and is considered ideal for a project that is complex by nature having large business components and interfaces with third party business applications, requiring high availability, and tight security. It also helps in managing the technology risks by spreading the risk across successive increments. This unique methodology has the distinct advantage of getting developed, quality assured and demonstrable functionality at the end of each iteration, which can be improved upon with successive iterations to get the desired functionality. In other words, early increments are "stripped down" versions of the final product, but they do provide capability that serves the user and also provide a platform for evaluation by the user.

Software projects are inherently complex, risky and require careful planning. Planning software includes development, estimates, staged development, requirements capture and risk and change management control procedures, business case studies, user interface prototypes and overall project control.

Proper planning ensures that the project does not move away from its targeted goals while the customer gets a clear definition of the project and is in the know of the project status and has ready access to project deliverables at any point of time.

We follow well defined and systematic procedures and processes in our project execution:

Prototypes & Staged Deliveries

• Projects that define deliverables in terms of prototype, phases or stages identify risks and constraints early on and are able to plan and implement counter measures with greater success.
• Customers who receive small releases regularly during the project gain trust more easily than those who are in the 'dark' and are awaiting the end of the project for a whole set of deliverables that may be delivered in whatsoever form.
• The functionality is developed and delivered in stages thus ensuring that the most important function is delivered at the earliest.
• Reduces the possibility of estimation errors
• Project visibility to customers and upper management increases

 Quality policy

     " To understand Customer's Business problems and to deliver Quality, Effective Software Products, Solutions and Services through Innovation and inspirations drawn from domain expertise gained by continuous R&D to provide better overall solution" 

At Fruition quality does not happen by accident, Quality is planned and is an important part of life at Fruition.  Quality is assured in every activity at Fruition.  Quality is an ever-extending goal - the better you are, the better you need to be. The management of the quality process is infinite, and marked only by milestones, never by completion! Fruition recognizes that, to fulfill our goal of self-evident quality, we need to constantly improve our deliverables to match the increasing expectations of our customers.  With standardization being the key to all growth - professional, personal and financial. Fruition reviews all its processes periodically and enhances them regularly.

Fruition follows Software Quality Assurance process at every phase of a project development cycle and this is assures quality at every step.  Our Quality Engineers ensure that every solution delivered by us exceeds international standards for quality.

The Quality procedures and processes include:

• Test Planning
• Test Cases and Test Scripts creation
• Automated and Manual Functional Testing
• Regression Testing
• Test Results Reporting
• Performance Testing
• Bottlenecks Analysis