Feasibility Evidence Description (FED) for NDI/ Ncsversion 2.3

Feasibility Evidence Description (FED) for NDI/ NCSVersion 2.3

Feasibility Evidence Description (FED)

Leamos

Team number 7

Version History

• Created document, added section 5

• The document was created with the risks that the project faces and how to mitigate them.

• Modified section 5

• Fixed bugs as reported by David.

• Changed to template for NDI
• Added section 1,3,4.1, 4.2.1 and 4.2.2

• The risks have been modified post the win-win negotiation with the client. The section 1 has been added as part of the Core FC package. The project features are to be built on the Moodle platform hence is a NDI project.

• Added section 2, 5 and other sections of 4. Modified section 1, 4 based on the bugs

• The sections were added as part of the draft FC package. The bugs were modified as per the review given by the TA and the QA.

• Fixed bugs

• The document bugs were fixed, table descriptions were added.

• Changes made to all sections

• The changes were respect to the review during the ARB session.

Table of Contents

Feasibility Evidence Description (FED)

Version History

Table of Contents

Table of Tables

Table of Figures

1. Introduction

1.1Purpose of the FED Document

1.2Status of the FED Document

2. Process Feasibility

3. Risk Assessment

4. NDI/NCS Feasibility Analysis

4.1Assessment Approach

4.2Assessment Results

4.3Feasibility Evidence

5. Business Case Analysis

5.1Market Trend and Product Line Analysis

5.2Cost Analysis

5.3Benefit Analysis

5.4ROI Analysis

6. Conclusion and Recommendations

Table of Tables

Table 1: Rationales for Selecting Architected Agile Model

Table 2: Requirement Prioritization

Table 3: Risk Assessment

Table 4: NDI/NCS Products Listing

Table 5: Evaluation Criteria – NDI /NCS Attributes

Table 6: Evaluation Criteria - NDI/NCS features

Table 7: Evaluation Results Screen Matrix

Table 8: Level of Service Satisfiability Evidence

Table 9: Level of Service Implementation Strategy

Table 10: Capability Feasibility Evidence

Table 11: Evolutionary Feasibility Evidence

Table 12: Market Trend and Product Line Analysis

Table 13: Personnel Costs

Table 14: Hardware and Software Costs

Table 15: Benefits of xxx System

Table 16: ROI Analysis

FED_FCP_F11a_T07_V2.31Version Date: 10/23/11

Feasibility Evidence Description (FED) for NDI/ NCSVersion 2.3

Table of Figures

Figure 1: ROI Analysis Graph

FED_FCP_F11a_T07_V2.31Version Date: 10/23/11

Feasibility Evidence Description (FED) for NDI/ NCS Version 2.3

1.Introduction

1.1Purpose of the FED Document

The purpose of the FED document is to document the business case analysis of the Centro Latino Organization which includes the cost of the project being undertaken. It also points to the benefits/savings the project will bring to the organization and the timeline for the return of investment. The FED also describes the risks in the project and the plan to mitigate them.

1.2Status of the FED Document

Sections have been added for the Business analysis and the process feasibility. The risks have remained unchanged so far. All sections have been complete except section 6. The changes have been made to tailor it for the FC package.The risks have been modified as per the recent client visit.

2.Process Feasibility

Table 1: Rationales for Selecting NDI-intensive

Table 2: Requirement Prioritization

3.Risk Assessment

The risks that are being faced at this point of time are mentioned in the table below. The risk has been described and the Potential Magnitude (if the risk occurs), the loss (if the risk occurs) are mentioned for each risk. Also how we can mitigate the risk is mentioned in the last column.

Table 3: Risk Assessment

4.NDI/NCSFeasibility Analysis

4.1Assessment Approach

The client is currently using the Moodle 1.9 platform. All the requirements are to be built on the existing Moodle platform so no other NDI needs to be assessed. We have to work on the Moodle platform to complete all the requirements requested by the client.

For converting flash files to HTML5, we need to evaluate tools. There are many tools available in the market which can achieve this conversion including Wallaby, Swify, Flash to HTML5 Converter. The goal is to have a tool which can convert without having bugs. The converted HTML5 should work on all modern browsers. The strategy is to use trial versions and evaluate the tools.

4.2Assessment Results

4.2.1NDI/NCS Candidate Components (Combinations)

Table 4: NDI/NCS Products Listing

4.2.2Evaluation Criteria

Table 5: Evaluation Criteria – NDI /NCS Attributes

In the above table, the attributes and the weight of the criteria with respect to the other attributes are mentioned. The attributesare the most important attribute that the client wants of the NDI.

Table 6: Evaluation Criteria - NDI/NCS features

The above table mentions the most critical features we are expecting from the NDI features. The client has both .swf and .fla files. So if any .fla are missing, we should still be able to proceed with the .swf files. If an error occurred, the error should be logged so that we can trace and get more help from the vendor.

4.2.3Evaluation Results Screen Matrix

The below table indicates the results of the evaluation of attributes done on the 3 candidates.

Based on the values provided by the reviewer, clearly Wallaby is the preferred tool.

Table 7.1: Evaluation Results Screen Matrix (attributes)

The below table indicates the results of evaluations done on features of the 3 candidates. Wallaby and Swify are free, Flash to HTML5 has a license fee. Swify converts only small flash files. The flash files which need to convert are large and hence we cannot use Swify.

Table 7.2: Evaluation Results Screen Matrix (features)

4.3Feasibility Evidence

The capability feasibility of the requirements has been described below:

4.3.1Level of Service Feasibility

Table 8: Level of Service Satisfiability Evidence

Table 9: Level of Service Implementation Strategy

4.3.2Capability Feasibility

Table 10: Capability Feasibility Evidence

4.3.3Evolutionary Feasibility

Table 11: Evolutionary Feasibility Evidence

5.Business Case Analysis

5.1Market Trend and Product Line Analysis

Table 12: Market Trend and Product Line Analysis

5.2Cost Analysis

5.2.1Personnel Costs

Table 13: Personnel Costs

5.2.2Hardware and Software Costs

Table 14: Hardware and Software Costs

5.3Benefit Analysis

Table 15: Benefits of System

5.4ROI Analysis

10% increase in maintenance of the system. (Value assumed as given in EPG)

The table below gives an idea of how soon the return of investment will be returned to the client. Its calculates the cost and the benefits. The benefits outdo the cost eventually. The cost column is taken from the table 14 and the benefit is taken from table 16.

Table 16: ROI Analysis

Figure 1: ROI Analysis Graph