Feasibility Evidence Description (FED)

Transcription

1 Feasibility Evidence Description (FED) United Direct Marketing Team 9 Chun-Ling Chen Project manager/ Prototyper Chun-Pei Su Lifecycle Planner Shao-yen Cheng System Architect Yuan-Chang Chang Feasibility Analyst Stewart Allen IIV&V/ Requirements Engineer Yen-Kuo Kao Operational Concept Engineer November 24, 2012 FED_FCP_F12a_T09_V3.0.doc i

2 Version History Date Author Version Changes made Rationale 10/03/12 Yuan Chang Chang 1.0 Update section 5:Risk Assessment Identify the risks and mitigation plans 10/04/12 Shao Yen Cheng 1.1 Correct information on header and footer sections. Delete legacy information from the template file and correct version numbers. 10/09/12 Yuan Chang Chang 1.2 Update section 5:Risk Assessment Add contents in section 1 Correct reported errors and vague points in risk assessment section and add new contents in section 1 10/22/12 Yuan Chang Chang 2.0 Add contents in section 2,3,4 Add business case study, capability feasibility and evaluate the best developing process, 10/22/12 Shao Yen Cheng 2.1 Section 1.2, footer and header. Update the document status and correct typos. Update section 5:Risk 11/15/12 Yuan Chang Chang 2.2 Update section 2:business case analysis Update section 4:Process Feasibility Correct defects and update risks 11/24/12 Yuan Chang Chang 3.0 Add contents in section 6 Update section 2:business case Add content and correct reported defects. FED_FCP_F12a_T09_V3.0.doc ii

3 Table of Contents Feasibility Evidence Description (FED)...i Version History... ii Table of Contents... iii Table of Tables...iv Table of Figures...vi 1. Introduction Purpose of the FED Document Status of the FED Document Business Case Analysis Cost Analysis Benefit Analysis ROI Analysis Architecture Feasibility Level of Service Feasibility Capability Feasibility Evolutionary Feasibility Process Feasibility Risk Assessment NDI/NCS Interoperability Analysis Introduction Evaluation Summary...13 FED_FCP_F12a_T09_V3.0.doc iii

4 Table of Tables Table 1: Personnel Costs...2 Table 2: Hardware and Software Costs...3 Table 3: Benefits of UDI System...3 Table 4: ROI Analysis...4 Table 5: Level of Service Feasibility...5 Table 6: Capability Requirements and Their Feasibility Evidence...5 Table 7: Rationales for Selecting Architected Agile Mode...9 Table 8: Risk Assessment...12 Table 9: NDI Products Listing...13 Table 10: NDI Evaluation...13 FED_FCP_F12a_T09_V3.0.doc iv

5 FED_FCP_F12a_T09_V3.0.doc v

6 Table of Figures Figure 1: ROI Analysis Graph...4 FED_FCP_F12a_T09_V3.0.doc vi

7 1. Introduction 1.1 Purpose of the FED Document This document is to analyze the feasibility of this project. In section 2, we provide business case study including analysis of cost, benefit, and ROI to evaluate its market value, so that we can decide whether it is worth to make it or not. In section 3 and 4, we go into the analysis of the level of service, capability, evolutionary and process. It evaluates the feasibility of the functions that we would implement and help us prioritize the implementing order. In section 5, we provide risk assessment, listing the potential risk, rank and mitigating plan. In the last section, we list the NDIs and NCSs that we might use in this project and briefly describe its use. FED document is a report for us to evaluate the risk of the whole project. We can adjust our developing plan in advance according to it, assuring its success. 1.2 Status of the FED Document - This version (3.0) belongs to Development Commitment Package. FED_FCP_F12a_T09_V3.0.doc 1

8 2. Business Case Analysis 2.1 Cost Analysis Personnel Costs The personnel costs include the time effort of the client, user and maintainer of the project. The effort of the development team was not being considered. Activities Table 1: Personnel Costs Development Period (24 weeks) Valuation and Foundations Phases: Time Invested (CS577a, 12 weeks) Client: Time spent to discuss with the developing team via , phone, and other channels [3 hrs/week * 12 weeks *1 person] WinWin negotiation session [1.5 hrs * 2 times *1 person] Architecture Review Boards [2 hrs * 2 times * 1 person] Development and Operation Phases: Time Invested (CS577b, 12 weeks) Client: Meeting via , phone, and other channels [2 hrs/week * 12 weeks * 1 person] Architecture Review Boards and Core Capability Drive-through session [1.5 hrs * 3 times * 1 person] Deployment of system in operation phase [6 hrs * 2 times * 1 person] Training & Support Time Spent (Hours) $ Equivalent ($35/hour) 36 $ $105 4 $ $ $ $ $350 [5 hrs * 2 times * 1 person] Total 93.5 $ Maintenance Period (1 year) Maintenance [2 hrs/week * 52 weeks * 1 person] 104 $3640 Total 104 $3640 FED_FCP_F12a_T09_V3.0.doc 2

9 2.1.2 Hardware and Software Costs Table 2: Hardware and Software Costs Development phase Type Cost Rationale Software Notepad++ 0 Free software Software Aptana 0 Free software Hardware Web Host 0 In developing process, developing team would build everything on USC server which is free. Operation phase Type Cost Rationale Hardware Web Hosting $60/year The client needs to apply a web host for this website. Usually the fee is less than $5/month. Hardware Web Domain name $10/year To apply and keep a domain name for a website comes with a fee. 2.2 Benefit Analysis Following table summarizes the benefits in terms of number of hours of work saved mainly through automation of activities. Note that the values used are yet to be confirmed by the clients. Thus there will be changes after incorporating client's input. Table 3: Benefits of UDI System Current activities & resources used It would be easier to change the content of the website dynamically (4hr/month) Reduce the effort to trace clients latest requests. The system will notify the owner if there is a change in requests. (0.5hr/time*12times/month) Reduce the time to provide produce detailed information through E- mail. The website would generate a template dedicated to each client to view their product related information. (owner: 1.5hr/product * % Reduce Time Saved (Hours/Year) $ Equivalent ($35/hour) 80% % % FED_FCP_F12a_T09_V3.0.doc 3

10 5products/month) The client will not need to manage their outlook box with all of the attachment in there. 90% (15hr/month ) Total ROI Analysis The following table shows the cost and the benefit in the following 5 years. We can see that our client would achieve positive balance from Cost (developing): personnel cost = Cost (operation) : maintenance cost + hardware & software cost = 3710 Benefit : benefit analysis =11487 Table 4: ROI Analysis Year Cost Benefit Cumulative Cumulative (Effort Saved) Cost Benefit ROI Figure 1: ROI Analysis Graph FED_FCP_F12a_T09_V3.0.doc 4

11 3. Architecture Feasibility 3.1 Level of Service Feasibility Table 5: Level of Service Feasibility Level of Service Requirement LOS-1: Compatible to the browsers used by the majority of users. Product Satisfaction Product Strategies: Focus on the major browsers that users in this domain use to view the website. Process Strategies: Use as much as cross-template programming language as possible. Test this project on the major browsers. Analysis: The major browsers used by users in this domain are chrome, IE8 and IE9. Our team has related experience on these browsers. 3.2 Capability Feasibility Table 6: Capability Requirements and Their Feasibility Evidence Capability Requirement UC-1: User Login UC-2: User Logout UC-3: Create marketing director account UC-4: Delete marketing director account UC-5: View marketing Product Satisfaction Feasibility Evidence: Store the account and password in the database in advance. Every time users try to login, validate them with the stored information. Software/Technology used: HTML, Javascript, PHP Feasibility Evidence: We can use session to record user s login state. To logout, just mark the session state to logout. Feasibility Evidence: Use SQL statement insert into to add an account. : Feasibility Evidence: Use SQL statement delete to delete an account. FED_FCP_F12a_T09_V3.0.doc 5

12 director accounts UC-6: Create micro website UC-7: Edit Micro Website UC-8: Delete Micro Website UC-9: List Micro Websites and hit rates UC-10: View micro website UC-11: Viewing a package illustration on a micro website UC-12: Viewing case studies on a micro website UC-13: micro website link UC-14: Edit website content UC-15: Attaching files to the website content Feasibility Evidence: Use SQL statement select * from tablename to view director accounts in table. Feasibility Evidence: Use SQL statement to retrieve the related user information and show it in HTML. Feasibility Evidence: Use SQL statement update to edit the data stored in the database. Feasibility Evidence: Use SQL statement delete to delete the data stored in the database. Feasibility Evidence: Retrieve users information in the database and show them as a list of micro websites. Furthermore, to implement the hit counter, we leave a column in table to store this information which would increase each time when users click on the button linking to their own micro website. Feasibility Evidence: Retrieve user information from the database and show them in micro website form. Feasibility Evidence: Upload the proposal to the database and relate it to the corresponding micro website. Feasibility Evidence: Upload the case studies to the database and relate them to the corresponding micro website. Software/Technology used: , HTML, Javascript Feasibility Evidence: Create a button to send the containing the micro website link. Feasibility Evidence: Store website content in the database, which makes it editable by administrator. Feasibility Evidence: Create a uploading section for administrator to upload their files, and bind these files to the place they want to put.. FED_FCP_F12a_T09_V3.0.doc 6

13 UC-16: View proposal UC-17: Comment proposal UC-18: Sign an electronic signature on a proposal UC-19: Confirm electronic signature UC-21: Search the content of the website Software/Technology used: HTML Feasibility Evidence: Incorporating the proposal link into the micro website. Feasibility Evidence: Build proposal table in the database to manage the files and leave a column to store the comments relating to it. Software/Technology used: RSA Feasibility Evidence: Users generate their own private key to sign their proposals and give their public key to the website to validate their signature. Software/Technology used: RSA Feasibility Evidence: The website manages users public key. When users upload their files to the website, the website validate their signature with the public key. Feasibility Evidence: We can create a table to store all the website content. When we do search, we can just search this table. 3.3 Evolutionary Feasibility There is no evolutionary requirement as of now. FED_FCP_F12a_T09_V3.0.doc 7

14 4. Process Feasibility From the process evaluation website, the most suitable process for this project would be architected Agile. Importance Rating Scale: How importance is this criteria for this project? 1 (Low), 2 (Medium) and 3 (High) Criteria Rating Scale: How likely the given criteria fits the project? 0 (Very Low),1 (Low),2 (Medium),3 (High) and 4 (Very High) FED_FCP_F12a_T09_V3.0.doc 8

15 Table 7: Rationales for Selecting Architected Agile Model Criteria Rationales 30 % of NDI/NCS features Part of this project will be built by NDI to speed up the developing process. Single NDI/NCS The client asks for lots of interface design and functions for the website, using a single UDI doesn t match our need on this project. Unique/ inflexible business process Need control over upgrade / maintenance Rapid deployment Critical on compatibility Only few functions of the website are unique. It must be a website to have complete administrative interface, assuring our client is able to maintain it by herself in the future. The website and the information on it should be deployed rapidly, assuring its customers are able to receive latest information. It should be a cross template website, its customers may use different browser to surf the website. Internet connection independence Need high level of services / performance Need high security Asynchronous communication Be accessed from anywhere Critical on mass schedule constraints Lack of personnel capability Require little upfront costs Require low total cost of ownership Not-so-powerful local machines It should not be an independence internet. Its customers come from all over the world. It is not specified but better performance can gain better clients experience. Need electronic signature mechanism. It involves several security issue. It doesn t need a real time communication function. Its customers come from all over the world. It is not specified, but expected to be finished in two semesters. It s a small company with only several personnel. Its budget is very limited, so has to be built with minimal cost. It s better to be cheap but not necessary. Local machines are basic laptops/desktops. FED_FCP_F12a_T09_V3.0.doc 9

16 FED_FCP_F12a_T09_V3.0.doc 10

17 The architected agile process has only two non-conforming points, which is lower than any others. It would be better to follow architected agile process. FED_FCP_F12a_T09_V3.0.doc 11

18 5. Risk Assessment Table 8: Risk Assessment Risks The person who implements the website would not take 577b next semester. It would take extra time for others to take over it. The interface designer is not a member of our team. The designer may not be able to deliver her product in time, which may delay the whole project. Lack of knowledge of the host the client s system currently built on. Time spent on learning may delay the schedule. Risk Exposure Potential Magnitude Probability Loss Risk Exposure Risk Mitigations The people who would take 577b should be familiar with the code as well Develop the capability first. After the designer finishes it, we integrate it into our project Negotiate with the client and get this information as soon as possible so that team members can start early. FED_FCP_F12a_T09_V3.0.doc 12

19 6. NDI/NCS Interoperability Analysis 6.1 Introduction The website needs a managing interface for our client to be able to manage the website herself. It may take us too much to develop everything from the scratch. Therefore, we decide to adopt some NDIs to implement this website to speed up the whole developing process COTS / GOTS / ROTS / Open Source / NCS Table 9: NDI Products Listing NDI/NCS Products PHP MYSQL database CodeIgniter Framework Duel CMS Microsoft Internet Explorer 9.0 Mozilla Firefox 8.0 Google Chrome 15.0 Purposes The server-side programming language to build the website. The database used to store users information. A framework that is useful for us to develop the website. Duel is a framework that already implemented lots of manager interface for users to use. Show the contents of the website. Show the contents of the website. Show the contents of the website Connectors The system will be built with PHP and SQL Server. Therefore, the connector between these two is the ODBC Connector Legacy System The system does not have any legacy system. 6.2 Evaluation Summary The table 11 lists some the NDI and NCS that we are going to use, and it provides the positive and negative points of each NDI/NCS. FED_FCP_F12a_T09_V3.0.doc 13

20 PHP Table 12: NDI/NDS Evaluation NDI/NCS Usages Comments Programming language Positive Points: -Very widely used. -Fully compatible with SQL server. -Team members are familiar with. Negative Points: -No negative points. MYSQL database Developing tool Positive Points: - Easily to use. -Team members are familiar with.. Negative Points: -No negative points CodeIgniter Framework Framework Positive Points: -Very widely used. -Provide powerful libraries to use Negative Points: -Not all team members are familiar with it. Duel CMS Framework Positive Points: -Provide powerful CMS interface ready to use. Negative Points: -Lack of experience of using it. Microsoft Internet Explorer 9.0 Web Browser Positive Points: -Default browser of Windows OS. -Highly supported. Negative Points: - No negative points Mozilla Firefox 8.0 Web Browser Positive Points: -Fast and widely used. Negative Points: -No negative points Google Chrome 15.0 Web Browser Positive Points: -Fast and widely used. Negative Points: -No negative points FED_FCP_F12a_T09_V3.0.doc 14