|
|
|
Index - Major Sections
Site Map
Product and Services _______________ Index - Same Level Subject
Index - Child Subjects |
Introduction
The
software will be developed by using the “prototyping” method. Prototyping
consists of building an experimental system rapidly and inexpensively for end
users to evaluate. It is a method of building a preliminary design, trying it
out, refining it, and trying again. Prototyping is most useful when there is
some uncertainty about requirements or design solutions. This is particularly
true of decision-oriented applications, where requirements tend to be very
vague. By interacting with the
prototype, users can develop a template to create the final system. Since most
users cannot describe their requirements fully on paper prototyping allows them
to work with a system in order to determine exactly what they need. The
methodology anticipates that they will change their minds; these changes can be incorporated easily and inexpensively
during an early stage of development. This project will go beyond the conception
and generality phase that is so common to many “development books” and will
attempt to give real practical examples of methods of implementation and
completed systems. This is the benefit of using a prototype.
Prototyping
is more likely to produce systems that fulfill user requirements. It promises to
eliminate excess development costs and design flaws that occur where
requirements are not fully captured the first time around. User satisfaction and
morale are usually heightened because users can be presented with an actual
working system, preliminary though it may be, in a very short period of time.
Prototyping
is a four-step process:
Step
1. Identify the user’s basic requirements.
Step
2. Develop a working prototype
Step
3. Use the prototype
Step
4. Revise and enhance the prototype.
Steps
In
Step 1.
First
the decision-makers and planners at the highest levels will be interviewed to
determine the informational requirements for sound decision making. This
information gathering process will be continued down through each level until
the lowest levels are reached. Specific information requirements are identified
through formal interviews with both senior and line management personnel. Local
and regional health care units will be questioned thoroughly because it is here
where all the information will gathered and be ultimately used. At this lowest
level the system interacts with the clients directly and it is here that is the
best place to obtain primary data. It is also at this level that management
involvement obtains the best results.
In
Step 2.
The
completed system will be developed, not as a hierarchical system, but as a
system where each health care unit contributes to all the others. At the first
level of healthcare delivery, computerized systems using a client/server with an
open-architect format will be implemented. The client/server system will give
the health care system the freedom to mix-and-match components at almost any
level. The client/server system can also be scaled horizontally or vertically.
While allowing the server code and server data to be kept at the highest level,
which results in cheaper maintenance and the guarding of shared data integrity,
the client computer remain personal and independent. To keep costs down, leading
health care organizations will be contacted for review of their systems,
application software packages will be investigated, and data will be standardized
as much as possible. However, flexibility will be built into the system so that
each unit may have its own “form” of entry.
In other places programs will be developed using off-the-shelve
open-ended software such as Microsoft
Access. In addition to being less expensive, many users are already familiar
with a graphical user interface. This system will be implemented to be able to
input directly to the highest level of decision making in the health sector.
Step
3. Use the prototype.
The
users will be encouraged to work with the system in order to determine how well
the prototype meets his or her needs and to make suggestions for improving the
prototype
Step
4. Revise and enhance the prototype.
The
system builders note all changes requested by the user and refine the prototype
accordingly.
Additional
research will be undertaken by communication with existing companies that have
produced “hospital” systems and will be asked to help in the development.
There is no benefit in trying to “reinvent the wheel.” It is believed that a
prototype can be developed quickly and inexpensively using what already exists.
|
|
|