|
|
|
 |
 |

|
| Whilst the
technical aspects of understanding the
hardware and the know how of how to
write useful programs is essential, what's often more important is the
understanding of what's actually needed
(or even desirable) for any business operation. This is because most
technical skills generally share common
understanding and may be readily
learned. |
|
| Your business
however, and the way your operation
runs, is probably unique, or at least,
is likely to have many unique aspects to
it. For software to contribute,
rather than detract, from the
advancement of your business, it needs to
fit. It needs to do what you actually
need it to. We take the time to
understand the nuances of your operation
wherever this matters. |
|
| If you're
thinking about getting computers to do
something specific to assist you in the
operation of your organisation, here are a few
questions that you may wish to consider: |
|
|
|
 |
|
Is what I need to do really
outside the scope of standard
applications? |
 |
|
Can I strategically
re-arrange my workflow and do without
new software? |
 |
|
Do I really understand the
true costs of implementation? |
 |
|
How will future changes in
my operation affect how the software
works? |
 |
|
Is the software I propose in
some sort of critical path, how can I
avoid this? |
 |
|
I've read a lot about free
open source applications, what are the
true costs? |
 |
|
How do I accurately specify
what I need? |
|
|
|
|
 |
|
|
|
|
 |
 |

|
| Unlike many
consultant organisations, we do not need
to contract-out software development.
In some situations however it
may make sense to out-source. However, if
this is the path we recommend for part,
or the whole, of any particular project,
all work is specified and fully vetted
by us, and we take full responsibility
for it. |
|
| Before we
embark on any new project we will satisfy
ourselves that 1). we are
able to do the work. 2). we
have the necessary resources to allocate
to the project at the time they are
needed. 3). that we can meet
any agreed time for deliverables, and
lastly 4). that you fully
understand what you're getting and how
much it costs. |
|
| We will usually
agree to participate in your project
when the specification has been mutually
approved. We will do whatever is
required to ensure that you fully understand our offer. The specification
will generally form the basis of our own
working documentation and it will
contain not only the detail of software
function but also what technologies we
will employ, how these are to be used
and what results you can
expect. |
|
| Wherever
possible we use technologies that
compliment your existing resources.
Standard SQL database structures such as
MS SQL Server or MySQL with the
appropriate front-end usually serves for
most applications. GUI's are
designed from scratch, and for Microsoft
platforms these will generally be
written using Visual Studio currently
targeting .NET 2.0+. Sun / IBM
development tools recommended for Java, Unix, Linux and variants
ensure interoperability. Deployment can
either be a custom solution, or
more commonly on Microsoft O/S's, the MSI
or Click-Once technologies can be
utilised. |
|
 |
|
|
|
|
|
 |

|
| In addition to the approved
specification and derived working
documents, We strive to ensure that the
software user has all the information
required to use and get the best
from the application. Complete,
context sensitive, on-line documentation
is provided as standard, additional
Guide Notes and Quick-Start guides can
be supplied where appropriate. These may
be printed if some kind of installation is required. |
|
|

|
|
 |
| Ensuring that a new application or software system works as it should can be a time consuming and costly business. Whilst the code may work exactly as technically specified, inevitably anomalies arise that need addressing. Such deviations on code function are almost never trapped by test tools. |
|
| Getting you involved saves not only time, but it can be important to identify glitches and bugs. The aim is to catch these early enough in the development cycle so that they are dealt with,
prior to first trial deployment. |
|
| In some cases we are able to automate
part of the testing process. This is done by means writing specific test routines to
check things such as data field integrity in databases, error trapping, error handling, data rate performance and so on. Such techniques work well in certain situations but in others a more manual approach can be more cost effective because a trade off exists in the time spent writing (and debugging) test routines. |
|
| The strategy used for first
trial deployment of the software will vary. Typically the software will take over a partial area of operation together with a settling-in period. We recognise the need to respond quickly to needed code changes at this sometimes critical time in the development cycle. |
|
|
|
|
 |
 |

|
| Maintenance issues are extremely varied. A rolling programme that would suit a large internal system, for example, may not be applicable to less complex stand-alone applications where the function doesn’t often change. Again, software that is sold as a product will likely require periodic updates
of a type that do not fall into either of the categories mentioned
above. |
|
| Chelsfield Consultants have been maintaining software in the field for many years. We understand the pitfalls of having to update against a backdrop of ever moving technology and O/S platforms. The need, in many cases, to maintain backward compatibility in the code, for things such as file
structure, we appreciate is a clear
concern. |
|
| There are a number of steps that we would recommend a consumer of custom software to take in order to mitigate some of the less desirable aspects of the software life-cycle.
An ideal scenario might be that your organisation may be able to directly undertake code maintenance itself.
This is sometimes possible if new
technologies can be grafted in to your
own organisation, or after a period of
training, both of which we can arrange. Otherwise there are a number of alternatives including the engagement of third parties including Chelsfield in this role. |
|
 |
| The integrity of software
and data is a key issue in most corporate organisations. Whilst a number of reputable vendors
offer systems that are technically secure, there is insufficient emphases on the human aspects of the
chain which is by far the weakest link in almost all security measures adopted.
However, many simple things can, and should, be done to tighten the security of systems prior to considering increasing the technical complexity. |
|
| All software written by Chelsfield is protected by proven proprietary encryption mechanisms. Such techniques have been developed by us and are now sold as software library components. Where necessary and appropriate in any system design consideration, we try to factor in human behaviour so that circumventing the technology becomes less likely. |
|
| We have been involved with computer based security systems for over thirty years. If you would like to know what Chelsfield can do for you, why not request a system security audit.
Click here for more information |
|
|