For application development and IT infrastructure projects, our methodology typically follows a set of phases to develop a functional specification that outlines the infrastructure requirements or desired functionality of the application, tool, or feature. Subsequent project phases involve programming, implementing, testing, and training as required to meet the demands of the functional specification. Software and IT infrastructure projects at Wadeware typically adhere to the following major project phases.

Discovery

Our software developers collaborate with each client to develop a functional specification that meets the customer’s requirements during the Discovery phase of the project. Product research and baseline requirements of the customer environment are typically defined during this phase of the project. The team then submits the initial draft of the specification to the client for approval.

Architecture

Based on the approved initial draft of the specification, the development team then evaluates and refines the architecture design for the project deliverables and adds this information to the functional specification to obtain customer approval. Researched configuration requirements are documented.

Implementation

After the client approves the architecture design and software requirements in the functional specification, our team of developers starts programming the desired functionality into an Alpha version of the project deliverable for review. Plans on how to deploy and migrate the project deliverable to meet the requirements of the customer are also defined and documented as needed during this project phase.

If the project requires a specific programming language or interoperability with other programs, our team develops a solution to meet these project objectives as described in the functional specification.

Lab/Pilot

The development team incorporates the feedback from the Alpha review cycle to release a Beta version of the project deliverable for customer review that may consist of a lab or pilot of the software. The project then repeats the feedback-revision cycle, and tests are performed to troubleshoot the software and its deployment plan. All team members and the customer provide input during these review phases of the project, which contribute to the final deliverable.

Training

Training materials may be developed during this phase of the project as required by the client to facilitate a smooth handoff of the final deliverable in the client’s environment.

Deployment

After all parties approve the tested functionality of the final deliverable it is delivered to the customer for deployment, which signals completion of the project.