MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_NextPart_01C76323.97E9B6F0" This document is a Single File Web Page, also known as a Web Archive file. If you are seeing this message, your browser or editor doesn't support Web Archive files. Please download a browser that supports Web Archive, such as Microsoft Internet Explorer. ------=_NextPart_01C76323.97E9B6F0 Content-Location: file:///C:/36484DE5/feasibilityReportExample.htm Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="us-ascii" Feasibility Report Template

Feasibility Report

<= /o:p>

Desirability Analysis of the Avail= able Options:

The following table delineates the available options for solving the software system problem.=

Option	Description
Status Quo=	Leave the = current system in place as-is; Project is cancelled.
New System=	Develop new system; Project is a go.
Purchase	Purchase s= ystem and integrate/customize as needed; Project would need to be redefined.
Re-Enginee= r	Re-Enginee= r the existing system; Project would need to be redefined.

The following table delineates the target solution characteristics that are desired and were used as criteria in the analysis process.

Characteristic<= /p>	Description
Availabili= ty	Availabili= ty =3D Mean_time_to_failure/(Mean_time_to_failure + Mean_time_to_repair) =3D 99.999% for desired solution system<= /i>
Cost<= /o:p>	Estimated = cost of option (in dollars for any comparisons/calculations) =3D $3M purchase + $5K/yr maintenance
Maintainab= ility	Ability to= quickly resolve and deliver fixes to the deployed system. Must be no more than 24 hours for desired solution system
Performanc= e	Performance expectations =3D any user operati= on can be performed within 2 seconds of wallclock time
Person-Hou= rs	Estimated = amount of person-hours to develop desired solution system =3D 3 person-months or 2160 person-hours (optimistic estimate)
Risk<= /o:p>	Risk avers= ion =3D medium for this project
Security	Amount of = security functionality. Sophisticati= on of security functionality =3D Very b= asic (simple) security for desired solution system.
Usability<= o:p>	Ease of us= e =3D user proficiency achieved within 40 = hours of training

The following table delineates the options in their order of desirability.

Option	Option Desirability Value<= /span>
Status Quo=	0.151102
New System=	*0.375916*
Purchase	0.364182
Re-Enginee= r	0.108801

Feasibility Analysis of Options by= Order of Desirability:

The following table delineates the driving requirements for the software system that is needed.

Driving Requirement=	Description
Availabili= ty	99.999% for desired solution system
Maintainab= ility	No more th= an 24 hours for desired solution system
Performanc= e	Any user o= peration can be performed within 2 seconds of wallclock time
Security	Very basic (simple) security for desired solution system.
Usability<= o:p>	User profi= ciency achieved within 40 hours of training

The following table delineates the known constraints for the software system that is needed.<= /span>

Constraint	Description
Cost<= /o:p>	Approximat= ely $2.5M dollars
Personnel<= o:p>	Staff of 9= ; 6 months to deliver 1500 SLOC
Risk<= /o:p>	Some risk = is tolerable – medium risk aversion

Conclusion of the feasibility stud= y.

Best option: &= nbsp; Developing a new system

Best option feasible?:= Yes

The following table gives an over= view of ranking results along with how the ranking was determined.

Option	Desirability Ranking	Reason
Status Quo=	3	The curren= t system has intermittent failures, is difficult to maintain, and has insufficient performance characteristics. This option has the least up-front cost, but will likely cost much more in the future. This is essentially= the no-go option. The customer = has demanded efficiency improvements that are outside of the bandwidth of mere process improvements. The customer wants and needs better tools.
New System=	1	The new sy= stem, as currently envisioned, will achieve 5-9s availability, will be easy to maintain, and will provide ample performance. This option has the greatest up-= front cost. This system seems to present the best cost to benefits ratio in light of characteristics the customer has emphasized as part of their vision for a valid solution syst= em.
Purchase	2	A COTS sol= ution would likely provide the highest initial availability and perhaps an init= ial cost advantage. Maintenance= and usability; however, would be fettered by a dependency on COTS product and COTS vendor limitations. Al= though a reasonable cost to benefits ratio results from this option, it is likel= y to rigid of a framework to achieve the customer’s desired usability.
Re-Enginee= r	4	Re-enginee= ring is a compromise approach that would provide some gain in maintainability, performance, and usability at a reduced cost as compared to developing a = new system or purchasing a COTS system (or composing a system from COTS produ= cts) and then modifying the COTS-based system to meet requirements. It is likely to produce the least benefit in regards to cost of all of the options.

The following table verifies that= the best option is feasible by indicating whether or not it satisfies the known project constraints.

Constraint	Constraint Description	Satisfied by Best Option?<= /span>
Dollar Cos= t	The budget= for this project is approved at $2.5 million dollars although some addition funding can be provided if rationale is approved.	yes
Staffing	Our current software engineering staff is at 9. We are not approved to increase our staff numbers. A new system is estimated at 150= 0 SLOC and is to be delivered in 6 calendar months.	yes
Risk Toler= ance	Our organi= zation and the customer are willing to tolerate some risk with this project as indicated in the dollar cost constraint description. Overall, risk aversion seems low= .	yes

The following table verifies that= the best option is feasible by indicating whether or not it provides posi= tive responses to key go/no-go questions.

Key Question	Response
Does propo= sed system contribute to objectives of customer?	yes
Can system= be implemented with available technology?	yes
Can system= be integrated with existing systems in target environment?=	yes

------=_NextPart_01C76323.97E9B6F0 Content-Location: file:///C:/36484DE5/feasibilityReportExample_files/header.htm Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="us-ascii"

Feasibility = Report Example &= nbsp; &nbs= p; SWEN6837

Page = 2 of = 4 &= nbsp; &nbs= p; &= nbsp; 3/10/2007

------=_NextPart_01C76323.97E9B6F0 Content-Location: file:///C:/36484DE5/feasibilityReportExample_files/filelist.xml Content-Transfer-Encoding: quoted-printable Content-Type: text/xml; charset="utf-8" ------=_NextPart_01C76323.97E9B6F0--