| |
| Many people imagine that the development of a computer
system is primarily a 'programming' task. This is far from the truth - at PW
Systems we estimate that roughly a third of our time is actually spent
producing code.
Instead, the majority of our efforts go into ensuring that we fully
understand the 'problem space' and that the solutions we develop will be
optimal for the client's business. We also appreciate the importance of the 'human issues'
surrounding an implementation, and so we stress the importance of
user-involvement, training and support in all phases of a project. |
Below, we describe some of the typical project processes. Most projects will
include elements of all of these processes, although of course, to varying
degrees.
 |
ANALYSIS
We will work with you to analyze your current
situation and to identify various means to attain your goals. This phase is generally
non-technical in nature and involves discussions of current and desired business
practices and operating environments. You may
have done much of this work already.
|
 |
DESIGN
Having decided on the project's goals, we will
design one or more systems capable of attaining those goals. We will explain
these designs to you, and describe the advantages/ disadvantages of each. Often,
we can quickly produce system prototypes that allow us to demonstrate on a
computer screen exactly how the system might look and function - these can be
very useful focal points for further discussions. |
 |
DEVELOPMENT
This is the 'programming' phase. All of our
programs are developed using the highest professional standards. This ensures
that the programs work correctly, and that they are easily modifiable in case
your requirements should change at some later stage. All our clients are given
full access to the source code of the programs so that they have full control.
We also provide system documentation explaining how the system works.
This again ensures that the client remains "in the driving seat". |
 |
TESTING
Before any critical software is released, it
is important for it to be fully tested. We will work with your users to perform
the required level of testing. This can often involve doing 'dry runs' of
processing through the system. For example, a selection of Customer Orders may
be chosen to be processed through the system to ensure that they are handled
correctly. |
 |
USER TRAINING
In our experience, the 'people' issues
surrounding the implementation of a new system can be as important as the
technical issues. Your staff must be receptive of the new system for it to be
deemed a success. To ensure this, we recommend that staff be involved in the
design and testing of the system, and that they receive full training before
the system is implemented. |
 |
IMPLEMENTATION
Some of the issues that may need to be
addressed here include: configuring servers, networks and PC clients;
transferring existing data into the new system and administering system security
(creating user accounts and allocating system privileges). |
 |
SUPPORT
In business, few things remain constant. New
laws, practices or opportunities may require you to modify your working
practices. Or you may later have new ideas to extend the functionality of the
system as originally built. Our systems are built assuming that future
change will happen, and we'll be there to help when it does.
|
|