|
Home
>
1. Introduction
>
1.5 Organizing a System Proposal
|
Previous
Next
|
|
|
|
|
Understanding what it takes to build a system
proposal.
|
|
Outlines current system, including a brief history
of current application and operational
functionality.
|
|
|
|
|
|
|
|
Describes the way the proposed system will be
develop and who, what, where, when and why. The summary
should also contain a summary of recommendations as well because
most of the time they only read summaries.
|
|
Describes proposed methods and procedures.
Outlines aspects that are part of a previous or existing system and
how the proposed system will improve the current application.
Also describes who or what was studied and the questions,
interviews and sample data that was observed.
|
|
This area describes what was found out about the
people and systems need for all the methods described from the
previous section. Its best to discuss conclusions to the
workers experience and begin to develop alternatives solutions
which is described in the next section.
|
|
This area addresses multiple solutions described
in the outline based upon the results founds. This area
should contain multiple solutions or alternatives based upon the
results of the studies.
The solutions should clearly indicate who should
implement the solution, equipment if needed and effort needed to
fulfill the duty for each solution.
|
|
After the different solutions are recommended then
you should prioritizes those solutions and give recommendations as
to which one best fits the projects needs.
|
|
This area is a brief statement that is almost
identical to the executive summary and presents the final
recommendations and if goals can be met. It is important here
to be positive in your summary.
|
|
This area covers specific areas of interests that
different users and managers find to be beneficial in helping them
make their decision.
|
|
|
|
|