|
Software development is a logical
structured process and the financial benefits
of detailed planning at the beginning of a project
are seen later on during the project roll out.
For example, a general rule of thumb is, every
change or revision made during the planning stages
of the project will cost 1 unit, say £100,
and as the project progresses that same change
or amendment will cost an increasing amount until,
final delivery of a solution is imminent the cost
can escalate to 100 units, in this case £10,000.
For this reason you can be assured
that Edge Impact's software consultants will ask
as many questions as possible and discuss your
project in detail during the early stages. We
will challenge your own ideas about how your solutions
can best be achieved and only when we have a complete
understanding of your expectations will implementation
begin supported by a full schedule of work with
guaranteed timescale's, milestones and deliverables.
Planning in this way might take a while, however,
over many years we have proven that this approach
results in a shorter time to delivery than where
effective planning is compromised.
| Key
stages of the development process |
| Stage
1. First meeting |
Personnel:
- Account Manager
- Senior Web/Software Developer
- Client |
The
initial meeting between the client
and Edge Impact, designed to allow
both parties to become accustomed
to each others style and requirements. |
|
| |
 |
|
| Stage
2. Specification, analysis compilation |
Personnel:
- Account Manager
- Design Operative
- Development Operative |
The
account manager will draw up a proposal
document, based upon the analysis
of any information supplied by the
client in Stage 1. At this stage the
development schedule, costing's and
parameters will be laid down for each
party to discuss |
|
| |
 |
|
| Stage
3. Proposal submission |
Personnel:
- Account Manager
- Client |
The
proposal document created in Stage
2, is presented to the client for
approval. If any changes are required,
the document is re submitted to Stage
2 for amendments. The aspects covered
by this stage may include the functionality
of any system or 'look and feel' of
a website. |
|
| |
 |
|
| Stage
4. Proposal sign off |
Personnel:
- Account Manager
- Client |
Once
both parties are happy with what is
to be developed and the time and cost
scales, the proposal document is signed
off by the client. This now forms
the binding document over which the
development will follow. |
|
| |
 |
|
| Stage
5. Development |
Personnel:
- Account Manager
- Design Operative
- Development Operative |
The
product is developed according to
the signed off proposal document,
by the design and development staff.
All core systems are developed by
skilled employees working closely
together in partnership. All changes
to any system or design are recorded,
to enable backward steps to be undertaken
if required. |
|
| |
 |
|
| Stage
6. Draft submission |
Personnel:
- Account Manager
- Design Operative
- Development Operative |
The
finished product is supplied to the
client in a draft format. If any changes
are required, the product is re-submitted
to stage 5 for amendment. |
|
| |
 |
|
| Stage
7. Draft acceptance |
Personnel:
- Account Manager
- Design Operative
- Development Operative
- Client |
Client
is satisfied with the final product,
based upon the signed off proposal. |
|
| |
 |
|
| Stage
8. Quality assurance |
Personnel:
- Quality Assurance Manager
- Account Manager
- Design Operative
- Development Operative |
The
product is fully checked and tested
for any hidden errors or bugs which
have surfaced after sign off. If any
are found, the product is re-submitted
to Stage 5 for actioning. |
|
| |
 |
|
| Stage
9. Finished product acceptance |
Personnel:
- Account Manager
- Client |
The
product is now ready for delivery.
The client tests the system thoroughly
in order to ensure it fully meets
the specifications put forward in
Stage 1. Once all is in order the
system is delivered in Stage 10. |
|
| |
 |
|
| Stage
10. Delivery of product/completion |
Personnel:
- Account Manager
- Development Operative
- Client |
| The product is delivered
from the testing environment to the
'live' environment where is is expected
to operate. |
|
| Back
to top of page |
|