|
Page 3 of 3
What to Bring to the
Development Table
Most valuable to developers are insights into
how the application will look and function.
What really helps are wire frame designs and
page layouts, says Chomko. Wire frames
are simple diagrams (these can be completed
with a tool like Visio or even a simple pencil
and paper) that include the layout of the page,
information you would like included on the
page, and links or buttons that will be on the
page. Descriptions of what will happen when
the links or buttons are clicked are very helpful
in understanding the events that can
occur on a page.
Chomko suggests another aspect vital to
the early development process: the creation of
a site map, representing the pages that are part
of the application, created in Visio or even
PowerPoint. He also suggests that if you are
currently utilizing any existing solutions (a
database tool like Microsoft Access) it is helpful
for developers to review working copies, as
it helps to determine the scope of the project.
Finally, give thought as to who will have
access to the application and how. Planning
for security roles early in the process is important
because it affects the entire application.
Custom Software Expectations
When you set out to buy a custom software
solution, the specifications you outline are the
baseline from which the developers start
working. Create detailed specifications and
you'll get a better representation of your initial
ideas. Create a rough outline and you'll
most likely receive a deliverable that is not
exactly what you had in mind. The lesson
here should be that good results require participation
from both sides.
If you care about the results, then you have
to be involved through the process or empower
a trustworthy employee to make sure it
meets your expectations, says Chomko. It is
imperative that those interacting with developers
[are] familiar with the goals and requirements
of the system
developers are not
mind readers and need to be given exact
details on how your business works.
The way to ensure that you receive the
software that will work for you, your enterprise
and your consumers is to understand
the scope of your own project. Specifications
that fit the bill typically include detailed modeling,
for example, block flowcharts. When
designing specifications, it's imperative to
consider flexibility and scalability to accommodate
for future growth and unexpected
changes to the system. A great deal of care
should be spent setting out specifications for
the project that takes these issues into consideration
as well as the design, function and
security of the software application.
|
