Inception

The inception phase is concerned with establishing the scope of the problem and defining a vision for the solution. For a large project this phase can include a “Consulting Phase”, so both the client and Teravision's team can better understand the complete environment of the client's problem, taking into account the whole spectrum of complex relationships that usually surrounds an enterprise-level organization. Possible deliverables for this phase are:

problem, eliminate the most evident risks
identified during inception, and develop a more detailed project plan. By the end of the elaboration phase, Teravision's team aims to have a general understanding of the entire project, having all the pieces in place to actually start building the solution on the next phase. Some of the deliverables of this phase are:

• Detailed Use-Case diagram
• Class diagram

Construction

At the construction phase we build the actual software product. This phase of the project is not carried out on a linear fashion like on the traditional software development model; instead we build the product following a series of iterations or “short goals”, arranging presentations with the client at the end of each goal to review the completion of a specific number of use-cases that were part of the iteration. This constant communication between Teravision's team and the client is what helps us to refine the software application to guarantee that the solution we're building matches exactly the requirements of the client. Deliverables for the construction phase are:

• The actual running system (although during the first iterations/goals the system might have limited functionality)
• Updated use-case, sequence and class diagrams (adding new elements that were designed and created during this phase)
• A QA testing matrix that describes each test case that the QA team executed with the software application, so those tests can be repeated into the client's environment.

Transition

The transition phase of the process is concerned with moving the final software product into the client's environment. This phase begins only when the software product is fully tested inside Teravision's environment and the main goal here is to have the product completely up and running within the client's environment, so we can repeat the QA testing matrix to certify that the application is fully operational on the client's side.

Typical activities for this phase can include:

• Beta-releases or pilot programs
• Factory-testing, that is having the product running in parallel with the legacy system that the product is replacing (if any)
• User training
• Data migration (converting data from legacy systems to be used with the new product)