Below is a brief description of each phase of our methodology.

Definition Phase

The Definition Phase corresponds to the initial vision of the project. This is the phase of the project where the ideas and concepts for the new system or service are reviewed to determine whether they are practical and fit business requirements. At this phase all concerns and restraints should be addressed such as budgetary issues and any onsite location limits or needs.

Analysis Phase

Detailed logical models of business data and the processes needed to guide system development are created in the next stage.  We refer to this as the Analysis Phase.  A description of the technical architecture is refined to guide the allocation of computing resources and capabilities.  The Project Manager and the System Development Manager should continue to assess both business and technical risks and seek additional management support as necessary to manage those risks.  Both the Project Manager and the System Development Manager will document project risks and risk management activities in a Risk Management Matrix for future reference.  This phase works as a natural bridge between the definition and design phase and is a key to any project’s success.

Design Phase

Our design will show the major types of processing platforms and how they interconnect. The allocation of processing and storage resources is vital to ensuring that business requirements can be satisfied within the system’s boundary constraints to ensure future growth.  An analysis of the architecture's capabilities must be conducted at this time in order to determine performance and growth constraints in hardware, operating system software and utilities, and support software.  All external system interfaces and internal subsystem interfaces must be identified and defined.  This Design Phase must be completed and thoroughly worked through before moving onto the Delivery Phase.

Delivery Phase

The Delivery Phase takes place when the developed solution is completely integrated for the first time.  At this time a complete system test, or Integrated Functional Test, is performed based on documented test scripts. This phase proves that the system is ready for production use to fulfill business requirements. The performance and usage should be transparent back to the Design Specifications, Functional Specifications and User Requirements Documents. Only in this way can Shanetech know that they have satisfied the Client’s needs.

Acceptance Phase

A specified period of time is used in the Acceptance Phase to tests all aspects of the system in the client’s environment.  The key stakeholders execute detailed scripts to ensure compliance to their initial business requirements and operational objectives.  The utilization of these scripts is called the Acceptance Test Plan.  . This phase establishes to the business that the system is ready for production.

Operations Phase

At this phase, the developed solution has been thoroughly tested and documented and is ready to be released into production.  Source code should be compiled from the Code Library and the infrastructure will have passed Shanetech requirements.  All necessary documentation and support will be compiled for support of the solution.