Feasibility Analysis

While researching the subject I came to realize the best course of action is to follow an established outline for the feasibility analysis. Once I determined which outline worked best the approach on how to deliver the message or communicate the problem statement progressively was my next concern. Based on the requirements for this course I chose an outline that can be easily adjusted if necessary throughout the course from the article written by Tim Bryce, Managing Director of M. Bryce Associates (MBA) entitled, Elements of a Good Feasibility Study (Bryce, 2008). As a result, the outline presented in the article will support the project objectives.

This information will be used to support conclusions and augment our course materials of Systems Analysis & Design with UML, version 2.0, written by Alan Dennis, Barbara Haley and David Tegarden and the Project Management Book of Knowledge, Chapter 11 Project Risk Management and Chapter 12 Project Procurement Management. References to PMBOK in its entirety will be made throughout the coursework as needed; however primary focus for assignment details will most likely come from Chapters 11-Project Risk Management (PMI, 2013 (a)) and 12-Project Procurement Management of PMBOK (PMI, 2013 (b)).

Collectively the information will be used to complete the Feasibility Outline. This information will provide concise input for the project scope, and will be used to develop a current analysis of the problem. Relevant information will serve as inputs for requirement gathering that will provide the information for the Requirements Statement, where outputs will provide the framework on how to define software and system implementation and use.

Once the problem is identified the approach is addressed using a “build vs. buy” analysis, where existing structures and viable commercial alternatives are presented and either one approach is chosen or a combination of aspects i.e., staffing with contractors or using an outside agency for...