Adaptable Process Model Checklists: Feasibility Analysis
	IMPORTANT NOTICE: The complete Adaptable Process Model (APM) is provided for informational purposes and for assessment by potential users. The APM is copyrighted material and may not be downloaded, copied, or extracted for use in actual project work. The full hypertext (html) version of the APM may be licensed for use and customization within your organization. Contact R.S. Pressman & Associates, Inc. for complete licensing information.
	Feasibility Analysis All projects are feasible–given unlimited resources and infinite time! Unfortunately, the development of a computer-based system or product is more likely plagued by a scarcity of resources and difficult (if not downright unrealistic) delivery dates. It is both necessary and prudent to evaluate the feasibility of a project at the earliest possible time. During system engineering (SEPA 5/e, Chapter 10), three primary areas of interest are considered: Economic feasibility. An evaluation of development cost weighed against the ultimate income or benefit derived from the developed system or product. Technical feasibility. A study of function, performance, and constraints that may affect the ability to achieve an acceptable system. Legal feasibility. A determination of any infringement, violation, or liability that could result from development of the system. For this checklist, the more questions that elicit a negative response, the higher the risk that project/product feasibility is questionable. Economic feasibility. Have the benefits associated with the product/system/service been identified explicitly? Have the benefits been quantified in dollar terms? Does the configuration represent the most profitable solution? Can it be marketed successfully? Will ultimate payoff justify development risk? What is the risk associated with cost and schedule estimates? Technical feasibility. Are all elements of the system configuration understood? Can the configuration be built within pre-established cost and schedule bounds? Does the technology exist to develop all elements of the system? Does the system rely on proven technologies? Are all interfaces clearly defined? Are function and performance assured? Can the configuration be adequately maintained? Do technical resources exist? What is the risk associated with the technology? Can quality assurance be adequately performed on all elements of the system? Does the proposed configuration properly interface with the system's external environment? Are machine to machine and human to machine communication handled in an intelligent manner? Legal feasibility. Does this configuration introduce undue liability risk? Can proprietary aspects be adequately protected? Is there potential infringement? Return to Checklist Table of Contents