Good software processes are designed to identify problems early in the development lifecycle and correct them immediately to ensure the project’s success. Research has shown that errors not identified in the requirements phase or design phase can cost the organization as much as 100 times the initial estimate to correct the problem in the Development or Deployment stage than it does to correct the issue in the Definition & Design stage. Our process is designed to streamline the decision making process, identify issues, and gain acceptance as early in the project lifecycle as possible.

Each phase is described in greater detail below:

Requirement Specification – The activity of committing requirements to writing. During this phase, user needs are identified and discussed. Both the client and development team acquire a detailed understanding of what’s required.

High Level Design – This is the phase where the structure of the system and all the highlevel details are identified.

Critical Design – The High Level Design Document is further dissected to reveal all the required relationships and key values for the tool. During this phase the development team is trying to develop a clear understanding of the desired functionality for the system and lastly identify key milestones to validate that the application is being developed as required.

Code – The activity in software development comprising detail design, coding and unit testing. During this phase, code review will take place at the key milestones identified during the critical design phase to ensure usability and validate functionality.

Test - During this phase the project team along with the client team will develop test cases to determine if the system is operating correctly. Test cases describe a series of activities and expected results that mimic a typical transaction to ensure operability.

Deployment – System rollout, user documentation is completed and the tool is ready for distribution.

Return to continue learning more about our process.