How We Work
ADS have been creating custom
solutions for nearly 20 years and we firmly believe the key to a
successful solution is not simply the application of technology
but the thorough understanding of the Client's business
processes and requirements. A well thought out system that fits
your current processes as closely as possible will be more
effective, quicker to learn and easier to operate.
Whether you are starting from scratch or
improving on previous solutions we will work very closely with
you explore the various possibilities and help you evaluate the
merits and limitations to determine to most effective solution.
We always speak plain English and avoid
the technical "jargon" wherever possible to really focus on the
business and what you need from any system. All technologies
have limitations as well as benefits and we help you assess
any practical implications in straight business terms so you can
make informed choices.
The Design & Development Process
This overview will give you a feel for the design and
development process we follow when working directly for the end
user Client; (the process will be different when we undertake
subcontract work to specification)
- Create a Workflow Diagram to show
the business process
A workflow diagram is a logical
representation of the business process with events listed in
the way they normally occur. For example, a customer makes a
telephone order, the operator searches for an existing
customer record, or creates a new one, before creating a new
order and adding the order items, applying the appropriate
discounts and payment terms. Processes that may appear
relatively simple at a glance may actually be quite involved
and describing them in the workflow diagram ensures all
aspects of the process are considered.
- Create a Context Model to show
interaction between the application and users, peripherals,
other programs etc
This is a diagram that graphically
represents the application data and any entity that will
interact with it. e.g. Users, remote users, web customers,
printers and other peripherals, other applications etc. Each
entity represents some functionality that requires
developing, e.g. Users will require a user interface;
interaction with Sage Accounts might require an import/export
facility or an integration module.
- Create a "Wire Frame" Prototype
of the System
The next step is for us to use the
Workflow and Context Model diagrams as a blueprint to create a
simple, non-functional, user interface that the Client can use
to visualise how the system will look and operate. This is
called the "wire frame" as it is starts to define the "shape"
of the finished system but is still very easy to modify.
Normally there is a process of "modification and review" with
each version of the model gaining an increasing level of
detail.
The wire frame can be created quickly and inexpensively and
allows the client to verify that our understanding and
interpretation is correct.
Once the wire frame process is
complete we start the work to define the data structures and
add the real functionality behind all the controls and
features shown or described in the wire frame prototype. We
provide interim versions at regular intervals for the Client
to review progress and validate each stage of development.
Once the system has all the
functionality completed we submit a Beta version for Client
testing. Any remaining issues that arise are addressed and
final changes implemented.
Once all changes have been made we
submit a final version of the system for Acceptance Testing
where the Client will fully test and formally accept the
system.
Once formally accepted we will fully
deploy the system for normal operational use.
- Ongoing Maintenance and Support
For total peace of mind we offer
maintenance and support contracts that ensure you always get
the assistance you need, when you need it. You also benefit
from routine maintenance to keep your system fully optimised
and up to date.
|