Our Methodology

We applies strict and formalized process with continuous effort to improve it. The factors we value the most are efficiency and simplicity. Our Methodology Of Working is As Follows:

Quote request

Clients task can be set in two ways - "a wish" and specification. "A wish" means a very rough outline about what has to be done (for example, "I want a better looking web site"). Specification is a written document that exactly defines requirements for the software to be implemented. Typical quote request we receive is something in between.

Documents:

1. Request for Quote received from client in any form.
2. Understanding scope and nature of work to be done.

Quote.

Depending on the level of details of project specification We studies requirements document (if available) or develops a high-level requirements specification on its own. Interaction with the client on this stage is done in the form of Questionnaire and typically requires up to email rounds back and force to clarify the task. Performance requirements are also defined at this stage. After high-level specification is available we make our quote for its implementation. Draft project plan (with major milestones defined) is also provided at this stage.

Documents:

1. Questionnaire used to clarify scope of work.
2.. Initial project plan

Signing a Statement of Work (Contract)

Client signs the project based on the quote. Signed contract can be either faxed or scanned and sent by email. .

Detailed specification of Requirements

Upon signing detailed requirements, specification and workflow model is developed. Time needed to settle upon the detailed requirements depends on the nature of the project and client availability.

Prototyping (graphical design, interface, implementation ideas) is also done at this stage.

Project plan

Once agreed on the detailed requirements a detailed project plan is developed by Integrio and agreed with the client. Project plan defines all tasks to accomplish within the project. All further activities are to be done based on it. Deliverables: 1. Project plan (Microsoft 98/2000)

Design definition

At this stage description of the internal construction of the modules that are developed as part of the project is done. This includes internal class diagrams, data structures, modules, dependencies, and 3rd party components.

Implementation and quality assurance

Implementation is done according with the project plan. It is usually broke down into several major milestones at which system is either packed and delivered by email or is setup at server. Client feedback is captured using online bug and request tracking system used (preferably) or in other form convenient for him (such as plain email or Excel sheet); requirements document is updated accordingly. Whether potential change requests that may happen at this stage affect contract costs or not depends on their number and nature. Implementation milestones:

Release

Release of the tested product with all the functionality implemented. System is ether delivered by ftp / email or is installed at customer server or at Primex Infotech hosting facilities.

Deliverables:

1. Functional system (compiled classes, executables)
2. Source codes
3. Documentation
4. Testing report
5. Performance report

Acceptance

Upon successful customer testing project is accepted and considered as complete.

Maintenance

Maintenance is provided as agreed, usually as a fixed maintenance contract.

Changes

Post-acceptance changes to the product are done at client request .