Crumbs: Home - SW_Dev_Proc
- Req Engr
- Assess Feas
- Feas Ana
Given a most desired
before that option can be acted upon, it must be analyzed regarding its
feasibility. The option that appeals most to the
developing organization might not be what the customer actually wants
or can even afford. The developing organization must ensure
tools requirements, skill set requirements, and resources exist to
implement the chosen option.
Cost, person-hours, and
risk-aversion contraints expressed by the customer must also be met by
whatever option is chosen in order for that option to be considered
feasible. An option that does not cooperate with a customer's
existing systems is completely impractical and thus not feasible.
An option that
solves a problem that is different than the problem conveyed by the
customer is the wrong option. Likewise, an option that seems
to solve the correct problem, but requires resources to implement that
are beyond those available to the project is not a viable option. The latter of these two cases; however, is potentially
salvageable. For instance: Given a most desirable option of developing a
new, replacement system as a solution to the customer problem, part of
the purpose of a feasibility study report is to propose changes to the
scope, budget, and schedule of a solution system project if deemed
necessary. Such proposed adjustments may also be accompanied
with suggested additional high-level requirements for the solution
system being considered.
No part of this work should be produced or used without the permission of the authors: Michael Turner and Dr. Sharon A White.