Feasibility Evidence Description (FED)

Transcription

1 Feasibility Evidence Description (FED) NICE E-Commerce Team 7 Lawrence Stratton Project Manager (PM), Prototyper, UML Modeler Deborah Baker Assistant PM, QFP (Team & Web Req), IIV & V, Team Website Admin Antonis Papantoniou Prototyper, Software Architect, Feasibility Analyst Runxuan Wei Prototyper, Life Cycle Planner Weijiang Dang Developer, Operational Concept Engineer King Lun Au Developer, Life Cycle Planner Dhananjay Nakrani Prototyper, Operational Concept Engineer, Team Website Admin October 15, 2015

2 Feasibility Evidence Description (FED) for Architected Agile Template Version x.x 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 Feasibility Evidence Description (FED) for Architected Agile Template Version x.x 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 IICSMSw_FED_Architected Agile_Template.doc iii Version Date: 08/17/12

4 Feasibility Evidence Description (FED) for Architected Agile Template Version x.x Table of Tables Table 1: Personnel Costs... 3 Table 2: Hardware and Software Costs... 3 Table 3: Benefits of NICE E-Commerce System... 4 Table 4: ROI Analysis... 4 Table 5: Level of Service Feasibility... 6 Table 6: Capability Requirements and Their Feasibility Evidence... 6 Table 7: Evolutionary Requirements and Their Feasibility Evidence... 7 Table 8: Rationales for Selecting Architected Agile Model... 8 Table 9: Risk Assessment... 9 Table 10: NDI Products Listing Table 11: NDI Evaluation IICSMSw_FED_Architected Agile_Template.doc iv Version Date: 08/17/12

5 Feasibility Evidence Description (FED) for Architected Agile Template Version x.x Table of Figures Figure 1: ROI Analysis Graph... 5

6 1. Introduction 1.1 Purpose of the FED Document The purpose of Feasibility Analysis is to objectively and rationally uncover: The strengths and weaknesses of an existing business or proposed venture Opportunities and threats as presented by the environment The resources required to carry through And ultimately the prospects for success Several methods of performing this analysis include: Cost vs benefits analysis Technology feasibility Economic feasibility Legal feasibility Operational feasibility Schedule feasibility 1.2 Status of the FED Document This is the first release of this document, and is the most current version. This document has been updated after presentation to the FCR. IICSMSw_FED_Architected Agile_Template.doc 1 Version Date: 08/17/12

7 2. Business Case Analysis Assumptions People are interested in buying the clients products online There is a market for these products people desire health-related products Vendors are interested in selling Stakeholders Initiatives Value Propositions Beneficiaries Developers Clients Maintainers Customers/Consumers Vendors/Suppliers Design & develop the new system Maintain the system Training, documentation and tutorials Marketing Host a blog with information to educate consumers Cost (Cost factors) Development costs Maintenance costs Web server hosting, domain name Connect suppliers with consumers Educate consumers Provide economic development Empower entrepreneurs Provide a platform to purchase herbal & health related products Consumers Vendors/Suppliers Benefits (Key performance indicators KPIs) Increase in net income generated from suppliers sales Increase in the number of suppliers, customers and subscribers 2.1 Cost Analysis Costs include personnel costs, specific to the client s hours, and costs for hardware and software related to the system operations. We have estimated ROI based on a two-semester project, since there is a possibility we may have to develop components of the system that we cannot purchase due to budget constraints. Specifically, the multi-vendor module will need to be developed if we can t acquire it from the various COTS frameworks available. IICSMSw_FED_Architected Agile_Template.doc 2 Version Date: 08/17/12

8 2.1.1 Personnel Costs Table 1: Personnel Costs Activities Development Period (24 weeks) Valuation and Foundations Phases: Time Invested (C577a, 12 weeks) Client: Meeting via , phone and other channels [2 hrs/week * 12 weeks * 3 people] Time Spent (Hours) Architecture Review Boards [1.5 hours * 2 times * 3 people] 9 Development and Operation Phases: Time Invested (C577b, 12 weeks) Client: Meeting via , phone and other channels [3 hrs/week * weeks * 3 people] Architecture Review Boards and Core Capability Drive-through session 13.5 [1.5 hrs * 3 times * 3 people] Deployment of system in operation phase and training 60 - Installation & Deployment [5 hrs * 3 times * 2 people] - Training & Support [5 hrs * 2 times * 3 people] Total Maintenance Period (1 year) Maintenance [4 hr/month * 12 weeks] 48 Total Hardware and Software Costs Table 2: Hardware and Software Costs Type Cost Rationale Web Hosting and Domain $4.99/month GoDaddy provides Economy web hosting services including domain name to deliver the minimum capabilities needed and can scale as necessary to meet growth Payment processing fees 2.9% +.30 Stripe fees for payment processing per transaction Web Hosting Maintenance $25-$100/hr For website changes and fixes Software Licenses (potential) Unknown May need capabilities above and beyond free e-commerce tools 2.2 Benefit Analysis Benefits for this project are very subjective, as there is no current business model or existing process that can be improved on. The overall objective of the system is: 72 IICSMSw_FED_Architected Agile_Template.doc 3 Version Date: 08/17/12

9 Increase supplier sales Create NICE income as a percentage of supplier sales Increase in NICE reputation and outreach to the alternative health community There are no existing numbers to base growth on. Table 3: Benefits of NICE E-Commerce System Current activities & resources used % Increase Time Saved (Hours/Year) No direct connection between local healthcare suppliers and customers Increase customer base for suppliers 25% Not quantifiable Increase sales for suppliers 25% Not quantifiable Increase health awareness for customers 25% Not quantifiable Create income for NICE business 100% No income exists today Total 2.3 ROI Analysis As there is no current system or business model, calculating an ROI is extremely hard. The bottom line is that if the website does not generate enough income to cover the cost of web hosting, domain fees and web hosting maintenance, then it is not feasible to continue. The numbers below are a general assumption of when the amount of client hours and income will impact cost. For our purposes, we converted personnel costs to currency to better understand costs and benefits. We will use $100/hour as the basis for labor cost estimation. For maintenance costs, we used 48 hours annually at an average of $50/hour. For Cost calculations, we plan to increase annual costs by 10% to accommodate for maintenance and growth. For Benefit calculations, we calculated based on net income alone without consideration of the soft benefits such as increasing health awareness for customers. We used an estimation of $10K in net sales the first year in business, and 15% sales growth year over year after that. Table 4: ROI Analysis Year Cost (10%) Benefit (15%) Cumulative Cumulative Cost Benefit ROI 2015 $26,250 + $60 0 $26, $66 + $2400 $10,000 $28,776 $10, $73 + $2400 $11,500 $31,249 $21, $80 + $2400 $13,225 $36,529 $34, $88 + $2400 $15,209 $39,017 $49, IICSMSw_FED_Architected Agile_Template.doc 4 Version Date: 08/17/12

10 Figure 1: ROI Analysis Graph ROI 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: Website load size (mb) LOS-2: Search Module Filters (number of filters) Product Satisfaction Product Strategies: Usability, response time Process Strategies: Prototyping, speed tests when loading site Analysis: Determine total load size when accessing web site Product Strategies: Advanced search Process Strategies: Incorporate search capability for multiple fields Analysis: Measure search against multiple fields 3.2 Capability Feasibility Table 6: Capability Requirements and Their Feasibility Evidence Capability Requirement CR-1: Multi-Vendor Capability CR-2: Vendor Product Listings and Management CR-3: Customer search, combined shopping cart and purchase CR-4: Website owner/moderator Product Satisfaction Software/Technology used: xcart provides multi-vendor module, but it is not free Feasibility Evidence: research on multi-vendor capabilities within xcart Referred use case diagram: Vendor use case Software/Technology used: e-commerce software provides the underlying capability. Free xcart software delivers core capabilities. Feasibility Evidence: the xcart package provides everything needed to setup an e-commerce website, including product listing management Referred use case diagram: Vendor use case Software/Technology used: e-commerce software provides the underlying capability. Free xcart software delivers core capabilities. Feasibility Evidence: the xcart package provides everything needed to setup an e-commerce website, including payment methods. Referred use case diagram: Buyer use case Software/Technology used: e-commerce software provides the underlying capability. Free xcart software delivers core capabilities. Feasibility Evidence: the xcart package provides everything needed to setup an e-commerce website, including administrative functions IICSMSw_FED_Architected Agile_Template.doc 6 Version Date: 08/17/12

12 CR-5: Blog posting and management Referred use case diagram: Administrator use case Software/Technology used: wordpress was determined to provide the capabilities needed. Feasibility Evidence: wordpress was evaluated to determine capability and integration and met all requirements Referred use case diagram: Vendor and Admin use case 3.3 Evolutionary Feasibility Table 7: Evolutionary Requirements and Their Feasibility Evidence Evolutionary Requirement ER-1: Add additional capability for user forums Product Satisfaction Software/Technology used: identified two tools that could be integrated into the system Feasibility Evidence: conducted research to determine compatibility with current e-commerce platforms Referred use case diagram: User Forums IICSMSw_FED_Architected Agile_Template.doc 7 Version Date: 08/17/12

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 3 4 Multiple NDIs Used Single NDI/NCS 2 2 Using one NDI as a platform and integrating the rest Unique/ inflexible business Very flexible, and non unique. 1 1 process Ecommerce is common Need control over upgrade A lot of upgrades will be done 2 1 / maintenance directly by NDI owners Rapid deployment 3 3 Website must be running ASAP Critical on compatibility 1 2 Critical for different NDIs to be compatible Internet connection Ecommerce is internet 1 1 independence dependent Need high level of services Professional look and payment 2 3 / performance process required Need high security 2 3 Secure payments and accounts are essential Asynchronous No requirement on 2 1 communication asynchronous communications Be accessed from Website must be accessible 3 3 anywhere from internet Critical on mass schedule constraints 1 1 No important constraints Lack of personnel capability 2 2 Require little upfront costs 2 3 Require low total cost of ownership Not-so-powerful local machines Company doesn t have maintainers/developers employed Startup non profit company has limited budget Running costs must be kept low since there is no profit involved Client doesn t have any hardware infrastructure IICSMSw_FED_Architected Agile_Template.doc 8 Version Date: 08/17/12

14 5. Risk Assessment Table 9: Risk Assessment Risks Customer-developer-user team cohesion Risk Exposure Potential Probability Magnitude Loss Risk Exposure Budget and schedule constraints Architecture complexity, quality tradeoffs COTS and other independently evolving systems Risk Mitigations Designate tasks, divide and conquer, break tasks into reasonable parts. Hold people accountable for their responsibilities in JIRA. Still working with client to tie down specifics related to budget and hardware. Will be assuming for ongoing development that budget is zero and if the client has any funds then we can improve substantially beyond current plans. Customizing xcart will require teammates to learn xcart Working on next prototype for payments IICSMSw_FED_Architected Agile_Template.doc 9 Version Date: 08/17/12

15 6. NDI/NCS Interoperability Analysis 6.1 Introduction Several e-commerce platforms were evaluated at the beginning of the project. At that time, xcart was chosen as the base platform for the product listing component. Other products can be integrated or plugged into the xcart platform. Xcart runs on either Windows or LAMP COTS / GOTS / ROTS / Open Source / NCS Table 10: NDI Products Listing NDI/NCS Products Apache MySQL Xcart Wordpress Stripe Paypal phpbb bbpress Solr Google AJAX search Oauth Purposes Web Server Database Product listing, payment blogging Additional blogging functionality Payment processing Payment processing Forum tool Forum tool Search tool Search tool Authentication tool Connectors In this project, we use PHP/MySQL Connector to enable the PHP web application to retrieve and query data from the database. This is provided in the base xcart functionality Legacy System No legacy systems exists. 6.2 Evaluation Summary Table 11: NDI Evaluation NDI Usages Comments Apache Web Server + freeware IICSMSw_FED_Architected Agile_Template.doc 10 Version Date: 08/17/12

16 + documentation available MySQL Database + freeware + suitable for large/small scale systems - No maintenance support Xcart e-commerce platform + base system is free + documentation available + can be extensible via large library of modules + contains most of the capabilities we are looking for - Advanced modules are not free, including multi-vendor module Wordpress Blog platform + free + documentation available Stripe Paypal Payment processing Payment processing + integrates easily with other tools + free to integrate + provides security + free to integrate + provides security phpbb Forum tool + free bbpress Forum tool + free Solr Search tool + free Google AJAX search Search tool + free Oauth Authentication tool + free + integrates easily IICSMSw_FED_Architected Agile_Template.doc 11 Version Date: 08/17/12