For projects that will evolve based on experience, or user feedback, we recommend a less traditional methodology that breaks a larger project into a number of very small, but self-sufficient, phases.

This methodology, known as extreme programming (XP), facilitates the rapid development of building blocks that then are used to build an overall system. Starting with a basic, but useful system, XP builds upon it one building block at a time. This enables adjustments in the specifications or priorities of newer modules based on the experience from using the parts already done.  

Development of given building block is normally done by a team of two developers.  One developer will be  the primary coder, while the other provides a second pair of eyes to suggest alternative solutions, coding techniques and catch mistakes.  The two would usually switch roles for he next building block.  This coding technique helps improve development time, and greatly reduce the time to go through Quality assurance.

The basic or foundation system, while minimal, must contain enough of the desired functionality to perform some basic functions and support itself to the extent that it can be fully tested and pass Quality Assurance.  We would normally develop the first phase using our Standard Development Methodology (as described in an earlier post).  We would then develop all the subsequent phases using the XP Development Methodology.

This methodology can result in a large scale solution that better meets the needs of our customer, since the design is based on feedback from use of the system as it continues to evolve and due to the efficient and rapid rollout of each building block.

iDigiSys performs application development services using a very specific, proven methodology. This helps to ensure that all participating parties are in agreement as to project specifications, and that the project is completed as our client envisions and delivered on schedule.  This process applies equally to all development projects whether they are website development or business software applications.

The development of a software application is done as a controlled project with a Project Manager and with well-defined phases and milestones. This team effort is lead by the iDigiSys Project Manager. The Project Manager drives the project, schedules appropriate reviews, provides communication regarding project status, and serves as the primary point of contact relating to project control issues.

Throughout the development cycle the Project Manager maintains a Project Management Website, which is available to all interested parties. This Website ensures that everyone is up to date on project specifications plans, progress, issues and deliverables - anywhere, any time!

Our projects are comprised of seven formal stages:

1. Requirements Discovery
2. Requirements Definition
3. Application Design
4. Development
5. Quality Assurance
6. Final Review
7. Roll Out

By adhering to the discipline of this process we ensure that the applications we build are done on-time, within budget and on target to your requirements.  These stages are described below:

1.  Requirements Discovery
During Discovery, which is normally of short duration, iDigiSys will work with you to develop a Project Requirements Overview document. The Requirements Overview is a high-level scope of work with enough information to include a preliminary budget and schedule. Once you have signed off on the Requirements Overview, iDigiSys will establish a Project Management Website and begin the formal process described below.

The deliverable from this phase is:

• Proposal to the client

2. Requirements Definition
Upon acceptance of the iDigiSys proposal the client and iDigiSys jointly develop the Requirements Definition of the website or software application. iDigiSys documents the project components and their relationships (logical flow of control) based primarily upon the business requirements defined by our client. All elements of the website or application are carefully documented in a System Requirements Specification and then signed off by all parties prior to commencement of development.

The deliverables at the end of Website Definition include:

• System Requirements Specification document
• Final Project Schedule
• Final Project Budget

3. Application/website design
Layout and page/screen design is done during this phase. Considerations will include appropriate look and feel, human factors considerations for ease of use, clear and understandable navigation and logical process flow.  Database design and server-based processing programs are also designed during his phase.

Deliverables at the end of Website/Application Design include:

• Page contents definition
• Samples of page layouts

4.  Development
iDigiSys develops the coding, programming and graphics in this phase. The client can review limited parts of the system during this phase at the Project Management Website to ensure that development is resulting in the desired "look and feel" and functionality.

The development and coding of server-based processing programs to be used in conjunction with the client-based user interface are also part of development. Typically, server programming is for content management, data processing programs, database queries, and report generation programs.

iDigiSys performs testing on each Website unit to ensure that:

• Layouts are to specifications
• The application behaves appropriately on between the server and he client
• Programs perform to specifications

Deliverables at the end of the Website Development phase include an Alpha release of:

• All pages/screen
• Graphics
• Forms
• Databases
• Functionality (programs)

5.  Quality Assurance
iDigiSys Quality Assurance tests the product on widely used browsers with a variety of display resolutions to assure that the product behaves properly in all environments. At the end of this phase iDigiSys delivers the finished product to our client in the form of a Beta Release.

Deliverables include a Beta release of:

• All pages/screens
• Graphics
• Forms
• Databases
• Functionality (programs)

6.  Final Review
Based on feedback on the Beta release from the client and careful comparison to the System Requirements Specification document, iDigiSys makes appropriate final changes to the application. The end of this phase is product compliance to all the prescribed specifications.

Deliverable is:

• Signed Customer acceptance

7.  Roll Out
iDigiSys, working with our customer, will assist in any server set-up, database seeding, conversion and user training required to deploy the application/website.