| FreiSoft's Software Development Methodology breaks the
software development lifecycle into four iterative phases that are milestone
driven. |
 |
| The purpose of the Envisioning Phase is to build a shared
vision of the project between Freisoft and the client. This vision includes a
mutual understanding of the business needs being addressed, clearly identified
solutions that meet the customer's expectations, and a solid estimation of the
project constraints. At the end of this phase, Freisoft and the client agree
on: |
-
A broad understanding of the business needs that will be met by the product
-
The vision of the product
-
The design goals for the product
-
The risks that may be incurred by undertaking the product
-
An initial concept of the business solution
|
| The Planning Phase is the point at which Freisoft and the
client agree on the project deliverables. This provides an opportunity to
establish priorities and set expectations, and serves essentially as a contract
between Freisoft and the client. During this phase a Functional and Technical
Specification will be generated. These documents serve as the blueprints for
project development. Every feature that is requested of the project will be
included in these specifications. At the end of this phase, Freisoft and the
client agree on: |
-
What should be built into the business needs Prioritization of features
-
How long it should take to complete the project
-
How the product will be built
-
The product architecture
-
The risks of building the product
-
The milestones and deliverables along the way
|
| The goal of the Developing Phase is to deliver an application
that meets all stated expectations and is ready for internal testing. At the
end of the Developing Phase, Freisoft and the client agree on: |
-
The fact that the planned feature set has been developed
-
The baseline materials needed to support user performance
-
The fact that development and functional tests have produced a baseline
scope-complete release
-
How the product will be tested and deployed throughout the organization,
including beta releases and testing.
|
| During the Stabilizing Phase, all known issues are resolved
prior to delivery, and any tasks needed for support and ongoing maintenance of
the product are completed. At the end of the Stabilizing Phase, Freisoft and
the client agree on:
|
-
Product stability and resolution of all known bugs
-
Customer acceptance of the product
-
Transfer of ownership for long-term management and support
-
A change in focus to the next release, if desired.
|
