Provide a brief one-page summary describing the purpose, methods, issues, and results of the feasibility study.
This chapter provides the purpose of the feasibility study, the background of the proposed project, the methodology used for performing the study, and any reference materials used in conducting the feasibility study.
Feasibility may not be an issue for some small software development projects. A full-scale feasibility study is not required when feasibility is obvious. If the proposed project has clear-cut requirements, will be developed on an existing platform, and has minimal risks associated with it, a feasibility review may be all that is necessary. If a feasibility review is conducted in place of a full-scale study, the information in this work product may be reduced to a feasibility statement (refer to chapter 4 for additional information).
Describe the purpose of the feasibility study.
Provide a brief history of the project.
Describe the methodology that was used to perform the feasibility study.
Identify the sources of information/reference materials that were used to conduct the feasibility study, such as:
This chapter describes the current automated or manual procedures being used; the project stakeholders objectives for the proposed system; issues that remain to be resolved; and general assumptions and constraints that were required for performing the study (e.g., “The system must be developed in time for the next budget call.”).
This section describes any existing systems and the associated manual and automated business processes.
Describe the current operations.
Identify the physical environment (hardware and software) being used for the existing system or business processes.
Include a description of the user organization(s) that use the system or business processes.
This section presents a general description of the proposed system and the major performance objectives. Include the objectives and high-level requirements the system will be designed to meet. Describe whether the system will be fully automated or include some manual activities, the functionality the system will provide, the general processes and operations that are required, the expected system end products, and an estimated timeline for system development and implementation. A high-level justification for the system can be included.
This section provides a summary of important issues that may affect the development and operation of the system, such as the use of data bases; processing and data flow; information access and retrieval; data communication; workload volume and system capacity; system interfaces; security, privacy and control; and training.
This section presents the assumptions or constraints that will affect the proposed system, such as:
This chapter describes the viable alternatives for the system. Each alternative should have its own section within the chapter. One alternative should always be to maintain the “status quo,@ which is the continuation of the existing system and processes. Describe and quantify the benefits and costs for each alternative. Compare alternatives using standard analysis of benefits and costs methods to include constraints, limitations, dependencies, and risks. Cost, benefit, and summary matrices can be presented either within the chapter or in an appendix.
This section defines the alternative and describes how it would satisfy the system requirements. If specific software tools or techniques are advocated, describe them in the context of the overall proposed system.
Include the following types of information:
Identify the benefits and costs associated with this alternative. Provide adequate cost and benefit information to enable each alternative to be evaluated and compared with the other alternatives.
This section is repeated for each alternative considered as a possible solution to meet the stated requirements.
Identify the evaluation criteria that will be used to judge the suitability of alternatives to satisfy requirements. Compare each alternative=s benefits and costs to determine whether it is feasible and cost effective to build the proposed system, and which approach is most desirable.
In this chapter present all final recommendations and conclusions resulting from the study. Identify and justify the recommended approach. Summarize the most viable platform configuration, and present the estimated lifecycle costs for the system and the schedule for the project plan. Provide the primary reasons for rejecting each of the other proposed alternatives.
If a feasibility review was conducted in place of a full-scale study, the information in this work product may be reduced to a feasibility statement with the following information.
Include comparison charts, matrices, vendor materials, and graphics that support the study findings.