All methods are geared toward clients' specific needs.

Requirements:

The first step in all our projects is to confirm in writing the client's needs. Once the specifications are approved, the next phase begins.

Preliminary Design:

The next step is to produce a design in cooperation with the client. This is also confirmed in writing and must be confirmed in writing before proceeding.

Detailed Design:

This step is technical and usually involves a detailed project plan. It may include Pert and/or Gantt charts that define critical paths and points of risk. A formal risk analysis may also be part of this design step. From the project plan, detailed budget and delivery dates are created.

Execution:

In the case of client applications, rapid prototyping may be used to verify critical designs and/or high risk tasks. This may also include testing the human interface by the client and/or his customers. Sometimes this process is called the whirlpool method of development as the parts of the project may be changed and retested many times to optimize the final product. Coding, debugging, and re-coding are part of this step.

Testing:

Quality Assurance may include a test plan specification that is created after the requirements are approved. If there is a failure, the problem, such as software bug, is identified and corrected. This may involve changing the design or re-executing the existing design.

Training:

User-training is essential. This must be done prior to deployment, unless the new system is running in parallel with the old system. In which case untrained users can use the old system until training is complete.

Deployment:

Deployment may require a written plan, depending upon the complexity of the application and the requirements of porting live data into the new system. This plan must always include a roll back option in the event of a failed deployment.

Final System Testing:

Prior to the new system going online, there is a final system test and acceptance of the hardware, software, and documentation by the client.

Support and Maintenance:

Support and maintenance is available as specificed in the contract.

• Documentation requirements are stated in the original requirement process, (see step 1 above).
• The preliminary design process involves choosing operating systems, hardware, languages, tools, and methods.
• Clients need to understand the code written in the languages chosen and the risks and benefits.
• Soft Works Ltd. recommends languages, operating systems, hardware, tools and methods that are both standardized and self documenting where possible.