Select a system for development that would benefit an Information Technology workplace. Prepare a 2–3 page plan for determining the feasibility of the systems development.
Feasibility Study Outline
Provides an overview of a business requirement or opportunity and determines if feasible solutions exist before full life-cycle resources are committed.
1.1 Origin of Request
This section identifies the originator and describes the circumstances that precipitated this project request. Provide the objectives of the Feasibility Study in clear, measurable terms.
1.2 Explanation of Requirement
This section describes the information management requirement in programmatic, technology-independent terms. It should state the specific deviations from the desired situation and the source and/or cause of the new requirement or opportunity. It describes any new information need(s) associated with the requirement or opportunity. The section should identify the cause(s) and effect(s) of the requirement or opportunity and validate the description of the requirement or opportunity with all affected organizations.
1.3 Organization Information
This section identifies the organization(s) mentioned in Section 1.1, Origin of Request, and the pertinent current procedures, information, and systems of those organizations. Provide descriptions of the relevant procedures and systems as appropriate.
The section should specify all organizational units involved, list the organizational unit(s) at all levels of the Service and external organizations that relate to the requirement or opportunity, and describe the pertinent mission area(s) and programmatic functions of each.
Provide a glossary of all terms and abbreviations used in the Feasibility Study. If the glossary is several pages in length, include it as an appendix to the study.
2.0 EVALUATION CRITERIA
This section states the criteria by which the alternatives will be evaluated. The criteria should make a distinction among characteristics that must be present in the system for it to be acceptable.
3.0 ALTERNATIVE DESCRIPTIONS
This section provides a description for each alternative proposed to handle the defined problem. It should describe the resources required, associated risk, system architecture, technology used, and the manual process flow for each alternative. The section should state at least two alternatives for each feasibility study– one being the alternative of doing nothing, if appropriate– and predict the anticipated benefits of each alternative and the likely effects of not taking action on the alternative. The section should also state benefits in terms of technical, operational, and economic feasibility.
has been added to your cart!
have been added to your cart!
You must log in and be a buyer of this download to submit a review.