At Jeenec Technologies we believe that the optimal methodology followed during a project life cycle depends on a variety of factors: nature of project, project criticality, project priorities, and project size to name a few. Since these factors vary from project to project we follow the notion that every project deserves its own tailored process and methodology.

Irrespective of the nature of the solution desired and the spectrum of technologies involved, Jeenec Technologies tries to adhere to some generic practices and procedures during the entire project life cycle. These generic practices and procedures have been framed keeping in mind our "Bridging Tomorrow" approach that adds value to our client's organization and maximizing their return on investment.

Information is received from the client which is well defined set of requirements or an idea or concept. More information is captured through interview, survey or by building prototypes. This information is analyzed, organized put together in an orderly fashion for crystallization of problem definition which further evolves as a Bigger Picture of the project. Analysis of the Bigger Picture is carried out taking the "Bridging Tomorrow" approach. The interaction with the client and the involvement of the developers during this stage varies based on the familiarity of the client with the solution desired. A user requirement document is generated which is approved jointly by the client.

Based on the user requirement document a model is constructed describing 'what' the solution has to do, if necessary prototypes are also developed for clarification purposes. Based on the model a Preliminary Project Plan is constructed which outlines the rest of the project. The model is then transformed into an architectural design by allocating functions to the software components and defining the control and data flow between them. Several iterations of the design are carried out to identify technically difficult and critical parts of the design. Prototyping of these parts of the project may be necessary to confirm to the basic design assumptions. If required alternate designs are proposed and the architectural design is confirmed.

Based on the architectural design the coding, testing and documentation for the development of the solution is carried out. The software user manuals are produced concurrently with the coding and testing. As the coding and testing progresses to the lower levels of the design the subsections to the software user manuals are added. Integration and system testing activities are performed and test checks are carried out on software quality. The application is ported to testing systems and acceptance tests are carried out. The application is demonstrated to provide the required capabilities and can be provisionally accepted.

The application is them entered into operations and carefully monitored to confirm that it meets all requirements. After final acceptance the application may be modified to correct undetected errors or because of new requirements that might arise.

During the entire project life cycle detailed documentation is maintained. High quality standards are followed at all stages in a project life cycle.