Feasibility Evidence Description (FED)

Transcription

1 Feasibility Evidence Description (FED) Mental Math Team - 7 Chang Yu Prototyper, Implementer, Requirements Engineer Isha Agarwal Prototyper, Life Cycle Planner, Implementer JingXing Cheng Implementer Kajal Taneja Operational Concept Engineer, UML Modeler, Implementer Kiranmai Ponakala Implementer, Life Cycle Planner, IIV & V Sushant Ramesh Software Architect, Operational Concept Engineer Sunmeet Nagpal Program Manager, Quality Focal Point Yuanxiu Yang Feasibility Analyst, Tester 10/10/2018

2 Version History Date Author Version Changes made Rationale 08/20/05 PP 1.0 Original template for use with LeanMBASE v1.0 08/30/06 SK, RT 1.6 Add template table Remove Section 3. Requirement Traceability 10/06/06 SK 1.61 Removed Section 1.6 Initial draft for use with LeanMBASE v1.0 Consistent format Move to Supporting Information Document Section 1.6 was duplicated with section 1.7 due to Format error 09/14/07 SK 1.9 Updated Section 2 Consistent with LeanMBASE1.9 08/25/08 IC /14/09 SK 2.1 Moved Section 1.1 to 1.2 Add Section 1.2 Updated Section 3 and add Updated Section 6, 6.3 Embedded description in each Table Removed Section Definition Consistent with IICM-Sw To be consistent with ICM EPG template set standard V2.1 To leanify the artifact 08/17/12 TK 2.2 Updated Section 2, 3, and 6 To be consistent with IICSM-Sw IICSMSw_FED_Architected Agile_Template.doc ii Version Date: 08/17/12

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 Introduction Evaluation Summary... Error! Bookmark not defined. IICSMSw_FED_Architected Agile_Template.doc iii Version Date: 08/17/12

4 Table of Tables Table 1: Personnel Costs... 3 Table 2: Hardware and Software Costs... 3 Table 3: Benefits of Mental Math 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 Table 10: NDI Products Listing Table 11: NDI Evaluation... Error! Bookmark not defined. IICSMSw_FED_Architected Agile_Template.doc iv Version Date: 08/17/12

5 Table of Figures Figure 1: ROI Analysis Graph... 5

6 1. Introduction 1.1 Purpose of the FED Document The Feasibility Evidence Description Document shows the analysis on feasibility evidence of Metal Math system. It contains several aspects such as business case analysis, architecture feasibility, process feasibility, risks analysis and interoperability NDI/NCS analysis. 1.2 Status of the FED Document This is FED document version 1.0. Benefit analysis was recalculated, and ROI analysis was added based on the feedback of ARB presentation. Other parts were also updated and finished. IICSMSw_FED_Architected Agile_Template.doc 1 Version Date: 08/17/12

7 2. Business Case Analysis Assumptions 1. Users are willing to practice math on the app. 2. Users have Android smartphones or tablets with mobile connections. 3. Competitive nature of users on a global level. Stakeholders Initiatives Value Propositions Beneficiaries (Who is accountable for the initiatives) (What to do to realize benefits) (Benefits i.e Why) (Who derives value) Owner (Client) Maintainer (Client) Users (People who wish to practice math) Developers (Students of CSCI 577A) Developers must develop the system according to all the requirements and win-conditions Client must maintain the system properly based on documentation provided by the developers Use app and rate it on the Play store Refers friends to increase user base Users can improve their basic mathematical skills and track their progress. Users can gain patience and perseverance. Users can analyze their progress. The application can generate an interest in Math for students at a young age. Monetary benefits from free and paid version to client. Customers and Users Client Costs Personal Cost - Client time in meetings, win conditions evaluation, code review. Maintainer Cost - Effort required for expansion of the application, Future Goals, Maintaining Code Benefits Increase skills of user to analyze problems and critical thinking. Reduce the amount of time/effort to open calculator or any other source of solving mathematical problems. 2.1 Cost Analysis This section identifies all possible cost either in monetary term or non-monetary term, such as hours spent, qualitative benefits for the project. We do not include the effort cost spent by development team, we include only cost spent by clients. IICSMSw_FED_Architected Agile_Template.doc 2 Version Date: 08/17/12

8 2.1.1 Personnel Costs All personnel-related cost from exploration phase to operation phase. Table 1: Personnel Costs Activities Time Spent (Hours) Exploration, Valuation and Foundation Phases: Time Invested(CS577a, 6 24 weeks) Group: 1st WinWin session [2 hr * 1 person] 2 Group: 2st WinWin session [2 hr * 1 person] 2 Client: Meeting via , phone, and other channels [ 2hr/week * 6 weeks * 1 12 person] Group: Conceptual Review Boards[4 hr * 2 times * 1 people] 8 Development Phase: Time Invested (CS577a, 6 weeks) 26 Client: Meeting via , phone, and other channels [2hr/week * 6 weeks * 1 12 person] Installation & deployment [5 hr * 2 times * 1 person] 10 Support [ 4 hr * 1 time * 1 person] 4 Total Time: 50 Total Cost [$0 / hours] $0 Maintenance: 4h/month * 12month * 1person Hardware and Software Costs All hardware and software-related cost from exploration phase to operation phase. Table 2: Hardware and Software Costs Type Android device Google Sign In Google Leaderboard Google Firebase Cost Free Free Free Free IICSMSw_FED_Architected Agile_Template.doc 3 Version Date: 08/17/12

9 2.2 Benefit Analysis Table 3: Benefits of Mental Math System Current activities & % Reduce Time Saved (Hours/Year) resources used Users can improve 90% 104 their math skills(2 hours * 52 weeks) Kids who use this App 85% 156 will get better grades in math(3 hours * 52 weeks) Total 260 Current activities Monetary Value Profit (per Year) Users will buy $4.99 $5988 premium Ad-free Application [100 users * 12 months] Total(for 1 st year) $ ROI Analysis Calculated Return on Investment by using your cost and benefit analysis results and identified the breakeven point. Given the cost/benefit analysis above, a return on investment analysis shows the project breaking even in april-may Table 4: ROI Analysis Year Cost Benefit Cumulative Cumulative (Effort Saved) Cost Benefit ROI IICSMSw_FED_Architected Agile_Template.doc 4 Version Date: 08/17/12

10 Figure 1: ROI Analysis Graph IICSMSw_FED_Architected Agile_Template.doc 5 Version Date: 08/17/12

11 3. Architecture Feasibility 3.1 Level of Service Feasibility Table 5: Level of Service Feasibility Level of Service Requirement LOS 1 Multiple Device Support LOS 2 Sharing my Scores/Application LOS 3 More and Different Content Product Satisfaction Product Strategies : Google Play Console/Constraint Layout Process Strategies: Constraint Layout allows you to specify the position and size for each view according to spatial relationships with other views in the layout. Analysis: Using constraint Layout, showed application adjust to different screen sizes. Product Strategies: ActionProvider API Process Strategies: ActionProvider can generate action views for use in the action bar, dynamically populate submenus of a MenuItem. Analysis: Application is able to interact with other application and is able to share its content. Product Strategies: Strings.xml/Shared Preferences Process Strategies: Developer can add more levels to string xml file and can increase content of application. Moreover, can support different languages and retain them for any session of application. Analysis: Adding more description in strings xml generated new levels in the game dynamically. IICSMSw_FED_Architected Agile_Template.doc 6 Version Date: 08/17/12

12 3.2 Capability Feasibility Table 6: Capability Requirements and Their Feasibility Evidence Capability Requirement CR 1 Google Login CR 2 Progress Tracker CR 3 Link to Premium App Product Satisfaction Software Technology Used: Firebase Feasibility Evidence: Sign in yet to be debug, since its working for some members. Referred Use Case : As a user I should be able to sign-in to google to save my progress Software Technology Used: Shared Preferences Feasibility Evidence: Created prototype of progress view page to mitigate risk and show evidence. Referred Use Case : As a user I am able to track my progress. Software Technology Used: Google Play Feasibility Evidence: Implemented a dependent use case which will eventually lead to this capability. Yet to publish app and test. Referred Use Case : As a user, I can buy premium version to remove ads. 3.3 Evolutionary Feasibility Table 7: Evolutionary Requirements and Their Feasibility Evidence Capability Requirement ER-1: Scalability of the system Product Satisfaction Software Technology Used: AWS Feasibility Evidence: This application can be deployed on AWS which is a scalable and highly available server, to create DB, server management, app integration etc. Referred Use Case Diagram: N/A IICSMSw_FED_Architected Agile_Template.doc 7 Version Date: 08/17/12

13 4. Process Feasibility Table 8: Rationales for Selecting Architected Agile Model Criteria Importance Project Status Rationales 30 % of NDI/NCS features 4 Already Implement Google leaderboard and achievement is very important feature of user account Single NDI/NCS 5 Already Preference Shared is used to Unique/ inflexible business process Need control over upgrade / maintenance Implement 4 Already Implement 3 App is developed for future developed Rapid deployment 3 We have finished the first version of our App Critical on compatibility 3 It is already in progress Internet connection independence Need high level of services / performance 3 Our App can play offline 0 We are using a google account and no services Need high security 4 We have applied a encryption algorithm in this APP Asynchronous communication Be accessed from anywhere Critical on mass schedule constraints 3 All the data transmit is Asynchronous communication 3 The App can played both online and offline 2 We do not have many store data. A inflexible business process is important to reduce time cost and money cost The App should integrate with ios version in the future The App should be finished at early time so we can do some test and improvement in future The App should be compatible in different screen and in different android version User may do not have a internet connection and still want to use it This program do not need service since we are using a google account As a game APP, we should avoid someone manipulate the data and make it more fare We do not have function which need synchronous communication Customer do not necessary need internet to play it The schedule is flexible and shouldn t have many IICSMSw_FED_Architected Agile_Template.doc 8 Version Date: 08/17/12

14 constraints Lack of personnel 3 Encryption capability Algorithm is challenge Require little upfront costs 4 We don t costs a lot in early time Require low total cost of ownership Not-so-powerful local machines 3 The app is designed to reduce the dependencies on us in the future 1 Our App is designed in low time cost. constraints Many team members are not familiar with android and Git We have a good prototype The app will be maintained by client in future Powerful machine is not needed to run our program. IICSMSw_FED_Architected Agile_Template.doc 9 Version Date: 08/17/12

15 5. Risk Assessment Table 9: Risk Assessment Risks Risk Exposure Risk Mitigations Personnel Shortfalls with respect to documentation and developmental abilities Potential Magnitude Probability Loss Risk Exposure Attending meetings and communicating such shortfalls to the other members UI Risk in terms of usability Prototyping and getting feedback from all success-critical stakeholders for an easily operable UI Not consulting end users Should gather feedback and interact with eventual endusers to establish initial requirements. Collaboration may be difficult, and siloing may occur within the team. Programmatic testing might go unexplored. Scheduled time for project completion Lack of security measures leading to leakage of data Requirement changes in the application Performance issues in the application Establish a plan for collaboration, so that very large deliverables are not assigned to only an individual Consider the risks of not including code-based testing practices. Research available options and possibly implement tests, depending on risk factors Proper time management to be able to complete the project within one semester Data can be encrypted by running a file-level encryption to prevent data leakage Spending time learning about the client s requirements and negotiating mutually agreeable requirements at an early stage The team should optimize the code completely and clear any memory caches. Furthermore, the client can upgrade the application from time to IICSMSw_FED_Architected Agile_Template.doc 10 Version Date: 08/17/12

16 time. Fire Base Integration Currently, Firebase is being explored to interface with Android. However, user can enter the values as long as the feature is yet to be implemented. IICSMSw_FED_Architected Agile_Template.doc 11 Version Date: 08/17/12

17 6. NDI/NCS Interoperability Analysis 6.1 Introduction COTS / GOTS / ROTS / Open Source / NCS Table 10: NDI Products Listing NDI/NCS Products AdMob/Interstitial Ads GoogleAPIClient FireBaseAnalytics Shared Preferences Android Developer Libraries(API 28) Support Library Package Purpose AdMob is one of the world's largest mobile advertising platforms and claims to serve more than 40 billion mobile banner and text ads per month across mobile Web sites and handset applications Firebase is the Google-wide solution for building applications on mobile devices. It offers an SDK with client code that lets you access mobile-relevant Cloud APIs directly and signing-in. Analytics reports help you understand clearly how your users behave, which enables you to make informed decisions regarding app marketing and performance optimizations. To store user data into caches and retrieve settings across multiple Screens. To support basic android development libraries, for example, View, OnCLick, Buttons, TextView etc. To support legacy software and help build project for earlier versions of android Connectors No connectors used in this project Legacy System There is no incorporation of legacy system or use of any legacy systems as this is a new system. IICSMSw_FED_Architected Agile_Template.doc 12 Version Date: 08/17/12