Feasibility Evidence Description (FED)

Transcription

1 Feasibility Evidence Description (FED) LINGGGO Team 3 Chicheng Ren Software Architect Dahai Li Quality Focal Point Dashun Wen Life Cycle Planner Kraingkrai Bumroungruksa Feasibility Analyst Siming Ye Operational Concept Engineer Shiqi Wei Prototyper Yiting Xiao Project Manager 11/22/15 FED_FCP_F15a_T03_V2.0.doc i Version Date: 11/22/15

2 Version History Date Author Version Changes made Rationale 10/17/15 KB 1.0 Documented sections /22/15 KB 2.0 Documented sections 2-5 Documented from initial template Updated ROI Analysis Updated Level of Service Feasibility Updated Risk Assessment FED_FCP_F15a_T03_V2.0.doc ii Version Date: 11/22/15

3 Table of Contents Feasibility Evidence Description (FED)... i Version History... ii Table of Contents... iii Table of Tables... iv Table of Figures... v 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 FED_FCP_F15a_T03_V2.0.doc iii Version Date: 11/22/15

4 Table of Tables Table 1: Personnel Costs... 2 Table 2: Hardware and Software Costs... 2 Table 3: Benefits of LINGGGO System... 4 Table 4: ROI Analysis... 4 Table 5: Level of Service Feasibility... 6 Table 6: Capability Requirements and Their Feasibility Evidence... 7 Table 7: Evolutionary Requirements and Their Feasibility Evidence... 7 Table 8: Rationales for Selecting Architected Agile Model... 8 Table 9: Risk Assessment... 9 FED_FCP_F15a_T03_V2.0.doc iv Version Date: 11/22/15

5 Table of Figures Figure 1: ROI Analysis Graph... 5 FED_FCP_F15a_T03_V2.0.doc v Version Date: 11/22/15

6 1. Introduction 1.1 Purpose of the FED Document The purpose of this FED document is to determine all possible strengths, weaknesses, opportunities, risks, resources, cost, and benefits of the project. 1.2 Status of the FED Document Business case analysis has been added. Architecture feasibility has been added. Process feasibility has been added. Risk assessment has been added. FED_FCP_F15a_T03_V2.0.doc 1 Version Date: 11/22/15

7 2. Business Case Analysis Assumptions 1. People desire to learn language 2. People desire to learn from a native people 3. People like to teach 4. People are going to go online to match language exchangers Stakeholders Initiatives Value Propositions Beneficiaries Language Learners Build the new system Language Learners find Language Learners Developers Training plan each other to (LINGGGO User manual practice team members) Marketing language Maintainers Advertising Increasing (Wesley plays learning the role now, and clients will hire others when our team is not in charge of the project) opportunities Increase chances for Language Learners to meet native Cost Clients (Zsuzsa Londe, Ajay Rai) Testers (LINGGGO team members) Meeting Costs Development Costs Maintenance Costs Web Hosting Costs Domain Name Costs Marketing Costs Benefits speakers Increase awareness of other culture through individual meetings and conversations Save time looking for Language Learners Help solve homework problems Increase income from advertisement as the number of Language Learners grow o Metric: Track the number of Language Learners signing up per month FED_FCP_F15a_T03_V2.0.doc 2 Version Date: 11/22/15

8 2.1 Cost Analysis Personnel Costs Table 1: Personnel Costs Activities Time Spent (Hours) Valuation and Foundations Phases: Time Invested (CS577a, 6 weeks) Client: Meeting via and on campus [3 hrs/week * 6 weeks * 36 2 people] Architecture Review Boards [1.5 hrs * 2 times * 2 people] 6 Development and Operation Phase: Time Invested(CS577a, 6 weeks) Client: Meeting via and on campus [3 hrs/week * 6 weeks * 2 36 people] Architecture Review Boards [1.5 hrs * 2 times * 2 people] 6 Implement, test, and deploy the system [ 4 hours/week * 6 weeks * 96 4 people] Total 180 Maintenance Period (1 year) Maintenance [3 hrs/week * 52 weeks] 156 Total Hardware and Software Costs Table 2: Hardware and Software Costs Development Type Cost Rationale Hardware - Web Hosting $0 Free Amazon AWS for students account Service Private Version Control System $0 Free private Github for students account Operation Type Cost/year Rationale Domain Name Service $20 LINGGGO.com - Domain name Hardware Web Hosting $150 Web hosting and server that will be used in production (cost increased as the number of the language learners grow) FED_FCP_F15a_T03_V2.0.doc 3 Version Date: 11/22/15

9 2.2 Benefit Analysis Table 3: Benefits of LINGGGO System Number of Language Learners Income/month from Advertisement 0 1,000 $0 - $100 1,001-10,000 $200 - $500 10, ,000 $1,000 - $2, ,001-1,000,000 $5,000 - $10, ROI Analysis Table 4: ROI Analysis As the number of users of the site has increased, it will affect cost & benefit in the following way. Cost will be increased since the website has to handle more load from users, which affects hardware cost. For example, the hosting server of the first 2 years can be a shared hosting server as the number of users is not too much. Once the site has got more significant amount of users, it may need to upgrade to a dedicated server, which costs more money. Benefit of the website is from the advertisement, so it will be increased according to the number of users of the website. In the first year, the website probably will have a low amount of users, so it will not make any income from advertisement. However, once the website has got more reputation and traffics in the following years, it will have a lot more users. This will make other companies interested in buying advertisement from the website. Also, the price rate of the advertisement will be higher once the amount of users getting increased. Year Cost (Money spent on server) Benefit (Money earned from advertisement) Cumulative Cost Cumulative Benefit ROI , , , ,500 1,550 5, FED_FCP_F15a_T03_V2.0.doc 4 Version Date: 11/22/15

10 Figure 1: ROI Analysis Graph FED_FCP_F15a_T03_V2.0.doc 5 Version Date: 11/22/15

11 3. Architecture Feasibility 3.1 Level of Service Feasibility Table 5: Level of Service Feasibility Level of Service Requirement LOS-1: The language learner can receive the Match result in 3 seconds LOS-2: The language learner can Register accounts in 2 seconds after filling all the fields correctly and update of profile management in 3 seconds LOS-3: The language learner can Send/Receive messages within 3 seconds Product Satisfaction Product Strategies: PHP, MySQL, HTML Process Strategies: Prototyping, Development Analysis: The matching system will use paging when query for users who have similar language interested so that it fetches part of matching users not the whole which will help us achieve this performance objective. Product Strategies: PHP, MySQL, HTML Process Strategies: Prototyping, Development Analysis: The profile registration system will use asynchronous way when upload user s profile photo and insert data into the database, so data insertion does not have to wait for the upload to be completed. Also, the profile management system separates data fields into tabs (user information, user skilled/desired languages), so users can update only part of data that they want to change which will take less time in updating data in database. Product Strategies: PHP, MySQL, HTML Process Strategies: Prototyping, Development Analysis: The message system will insert only one record per one message, so the sending process will take short time. Also, the receiving message system will show only part of latest messages not the whole messages history, so this reduces the load time. FED_FCP_F15a_T03_V2.0.doc 6 Version Date: 11/22/15

12 3.2 Capability Feasibility Table 6: Capability Requirements and Their Feasibility Evidence Capability Requirement CR-1: Matching System CR-2: Profile Management CR-3: Message System Product Satisfaction Software/Technology used: PHP, MySQL, AngularJS, HTML Feasibility Evidence: Develop functional prototype showing language learners the native speakers of the language they want to learn Referred use case diagram: Process Diagram in SSAD document Software/Technology used: PHP, MySQL, AngularJS, HTML Feasibility Evidence: Develop functional prototype which allows language learners to create their profile including name and desired to learn language info Referred use case diagram: Process Diagram in SSAD document Software/Technology used: PHP, MYSQL, AngularJS, HTML Feasibility Evidence: Develop functional prototype which allows language learners to send and receive message from other language learners in the system Referred use case diagram: Process Diagram in SSAD document 3.3 Evolutionary Feasibility Table 7: Evolutionary Requirements and Their Feasibility Evidence Evolutionary Requirement ER-1: Real-Time Chat Product Satisfaction Software/Technology used: PHP, MySQL, HTML, JavaScript Feasibility Evidence: Use of online chat tool as NDI to prototype the feature Referred use case diagram: Process Diagram in SSAD document FED_FCP_F15a_T03_V2.0.doc 7 Version Date: 11/22/15

13 4. Process Feasibility Decision Criteria Rating Scale; 0:Very Low; 1:Low; 2: Medium; 3:High; 4:Very High Importance Rating Scale: 1:Low; 2: Medium; 3:High Table 8: Rationales for Selecting Architected Agile Model Criteria Importance Project Status Rationales 30 % of NDI/NCS features 1 1 We built almost everything from scratch. Single NDI/NCS 1 1 We integrated Facebook login system. Unique/ inflexible business 1 1 The business model and process Need control over upgrade / maintenance requirements are very flexible. 1 1 The upgrade and maintenance can be done seamlessly without external concerns. Rapid deployment 2 2 There is no specific deadline in the deployment. Critical on compatibility 1 1 The system is web-based which has low compatibility issues. Internet connection independence 3 3 This is an online system, so the internet connection is mandatory. Need high level of services / performance 3 3 The system needs to be able to handle large user load. Need high security 3 3 The system contains Language Learner's personal information which must be secured. Asynchronous communication 2 2 The system uses asynchronous calls to the server. Be accessed from anywhere 3 3 The system must be able to access from any country. Critical on mass schedule 1 1 There is no such constraints. constraints Lack of personnel capability 1 1 Our team is capable of implementing the system. Require little upfront costs 1 1 We are using free services for students. Require low total cost of ownership 2 2 The system has no need to buy any tool. Not-so-powerful local machines 2 2 We are using free development environment. FED_FCP_F15a_T03_V2.0.doc 8 Version Date: 11/22/15

14 5. Risk Assessment Table 9: Risk Assessment Risk Exposure Risks Potential Probability Risk Risk Mitigations Magnitude Loss Exposure Requirements Change Use incremental development to let clients see the working product early and also discuss with clients in advance about the cost and consequences when changing requirements. Requirements Mismatch Discuss with clients frequently to make sure that we clearly and correctly understood the requirements. Also, delivering working product frequently so that clients can test the system early to discover requirements mismatch faster. Some functions may be not possible to implement because the limitation of the technology The real server environment may be different to the development environment in a way that causes some malfunctions to the website Project may not finish in time because some team members do not have web development experience Explain to clients about the limitation of the technology to avoid any un-implementable functions Define the support environment of the server in terms of PHP minimum version, required modules and also the database Provide web development training to team members and let them practice using the framework to get familiar with it. FED_FCP_F15a_T03_V2.0.doc 9 Version Date: 11/22/15

15 6. NDI/NCS Interoperability Analysis NOT REQUIRED/NOT APPLICABLE FED_FCP_F15a_T03_V2.0.doc 10 Version Date: 11/22/15