Feasibility Evidence Description (FED)

Transcription

1 Feasibility Evidence Description (FED) Smart Locks Control Team 05 Team Member: Vaibhav Vishal Diego Brandao Zhe Wang Mohammadreza Barazesh Alejandro Monroy Hao-Yun Yang Katarzyna Ruszowska Project Manager, Life Cycle Planner, Trainer IV&V, Software Architect, Developer Feasibility Analyst, NDI/NCS Acquirer Software Architect, Developer Prototyper, Evaluator, Tester, Developer Requirements Engineer Quality Focal Point, UML Modeler, Developer 12/02/2017

2 Feasibility Evidence Description (FED) for Smart Locks Control System Version 1.0 Version History Date Author Version Changes made Rationale 10/16/17 ZW 1.0 First Version Initial draft for Smart Locks Control System 11/26/17 ZW 1.1 Section 6.1.1, 6.1.2, 6.2 Change NDI/NCS for the project 12/02/17 ZW 1.2 Document consistency Change wording to keep the consistency of the document. FED_TRR_F17a_T05_V1.2.doc ii Version Date: 12/02/17

3 Feasibility Evidence Description (FED) for Smart Locks Control System Version 1.0 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 FED_TRR_F17a_T05_V1.2.doc iii Version Date: 12/02/17

4 Feasibility Evidence Description (FED) for Smart Locks Control System Version 1.0 Table of Tables Table 1: Personnel Costs... 3 Table 2: Hardware and Software Costs... 3 Table 3: Benefits of Smart Locks Control 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... 9 Table 9: Risk Assessment Table 10: NDI Products Listing Table 11: NDI Evaluation FED_TRR_F17a_T05_V1.2.doc iv Version Date: 12/02/17

5 Feasibility Evidence Description (FED) for Smart Locks Control System Version 1.0 Table of Figures Figure 1: ROI Analysis Graph... 4

6 1. Introduction 1.1 Purpose of the FED Document The purpose of Feasibility Evidence Description (FED) is to provide evidence that Smart Locks Control system is feasible to implement and to show that other artifacts are consistent and compatible. The evidence provided in this document ensures the project is feasible to continue into the next phase. 1.2 Status of the FED Document - Updated to version 1.2. Change of NDI/NCS was updated in the document. New feasibility assessments were analyzed and reported correspondently in the document. FED_TRR_F17a_T05_V1.2.doc 1 Version Date: 12/02/17

7 2. Business Case Analysis Assumptions: Reliable connection of Device Handler to the hub and the locks. Schlage FE599 locks support the Z-wave protocol. Website is able to connect with the SmartThings API. Locks and hubs in use registered are on SmartThings and fully functional. Stakeholders Initiatives Value Propositions Beneficiaries Administrator House Manager House Staff Client Developer Maintainer Changing/maintaining slots and the overall service. Provide equipment, advertising and marketing strategy Develop the application Saves time, increases efficiency Control to Administrator Tracking user activity through log files Increases security through user hierarchy Client Administrator House Manager House Staff Guests Cost Personnel Costs Development Costs Schlage FE599 locks Samsung SmartThings hubs Rboy device handler Maintenance Costs Benefits Increase time efficiency for Administrator Increase management efficiency for house manager Decrease labor costs for house staff Decrease check-in time for guests 2.1 Cost Analysis - Training Costs - Personnel Costs - Hardware/Software Costs - Hardware/Software Maintenance Costs FED_TRR_F17a_T05_V1.2.doc 2 Version Date: 12/02/17

8 2.1.1 Personnel Costs Table 1: Personnel Costs Activities Time Spent (Hours) Development Period (12 weeks) Valuation and Foundations Phases: Time Invested (6 weeks) Client: Meeting via or in-person 14 Client: Win Win negotiation session 1 and 2 4 Client: Win Conditions discussion 2 Client: Prototype presentation 0.5 Client: ARB presentation 1.5 Development and Operation Phases: Time Invested (6 weeks) Client: Meeting via , phone or in-person [4 hrs/week * 6 24 weeks * 1 people] Client: CCD session 1.5 Client: ARB presentation 1.5 Deployment of System in operation phase and training 4 - Installation & Deployment [2 hrs * 1 time * 1 people] - Training & Support [2 hrs * 1 time * 1 people] Total 53 Maintenance Period (1 year) Maintenance [2 hr/week * 52 weeks] 104 Total Hardware and Software Costs Table 2: Hardware and Software Costs Type Cost Rationale Samsung Smartthings Platform Free Samsung offers free IDE for SmartThings hub MySQL Free Database used to store information RBoy device handler $30 Device handler lifetime license for using SmartApp Hardware - Lock $ 600 Estimated cost of 3 Schlage FE599 locks Hardware - Hub $ Samsung SmartThings hubs used to connect locks to internet service Hardware - Web hosting $30- $70/years for a small environment System requires web hosting and prices vary based on companies and services FED_TRR_F17a_T05_V1.2.doc 3 Version Date: 12/02/17

9 st 2nd 3rd 4th Qtr Qtr East West North 2.2 Benefit Analysis Table 3: Benefits of Smart Locks Control System Current activities & resources used % Reduce Time Saved (Hours/Year) Increase time efficiency for Administrator [5 hrs *52 weeks] 90% 260 Increase management efficiency for house manager [5 hrs * 52 weeks] 90% 260 Decrease labor costs for house staff [0.5 hrs * 52 weeks] 80% 26 Decrease check-in time for guests [2.5 hrs *52 weeks] 80% 130 Total ROI Analysis Table 4: ROI Analysis Year Cost Benefit (Effort Saved) Cumulative Cost Cumulative Benefit ROI Figure 1: ROI Analysis Graph FED_TRR_F17a_T05_V1.2.doc 4 Version Date: 12/02/17

10 FED_TRR_F17a_T05_V1.2.doc 5 Version Date: 12/02/17

11 3. Architecture Feasibility 3.1 Level of Service Feasibility Table 5: Level of Service Feasibility Level of Service Requirement LOS-1: System shall handle each API requests within 500ms. LOS-2: This system shall handle at least 50 different user accounts. LOS-3: System shall be easy to use. Product Satisfaction Product Strategies: Node.JS, Express.JS Process Strategies: Develop a backend server by using Node.JS and Express.JS. Analysis: By using Node.JS and Express.JS in the backend, the system is able to response each request within 500ms. Product Strategies: MySQL Process Strategies: Develop a database that store all users information Analysis: By using MySQL database, we are able to store 50 rows of user record into the system. Product Strategies: Error-reducing User Input/Output, UI consistency Process Strategies: Develop a prototype to provide clean UI for users to test. Then evaluate the UI design based on the feedbacks from users. Analysis: By using prototype, we can analyze the usability of the system, and improve the design for user have better user experience. 3.2 Capability Feasibility Table 6: Capability Requirements and Their Feasibility Evidence Capability Requirement CR-1: Remotely Lock/Unlock Locks Product Satisfaction Software/Technology used: Node.JS, Angular, Bootstrap, Samsung SmartThings hub, Rboy device handler, z-wave FED_TRR_F17a_T05_V1.2.doc 6 Version Date: 12/02/17

12 Feasibility Evidence: Develop a web application which sends requests to server. Then server can send requests to Samsung SmartThings hub by using Rboy device handler. Finally, the Samsung SmartThings hub will send signal to lock via Z-wave to lock/unlock locks. Referred use case diagram: 1. Use Case Diagram House manager 2. Use Case Diagram Administrator CR-2: Remotely Add/Delete Slot Software/Technology used: Node.JS, Angular, Bootstrap, MySQL, Samsung SmartThings hub, Rboy device handler, z-wave Feasibility Evidence: Use the same process as CR-1 to update slot to the locks. Meanwhile the server will send requests to update database. Referred use case diagram: 1. Use Case Diagram House manager 2. Use Case Diagram Administrator CR-3: Add/Delete Users Software/Technology used: Node.JS, Angular, Bootstrap, MySQL Feasibility Evidence: Develop web application which send requests to server to update user table in database. Referred use case diagram: 1. Use Case Diagram Administrator 3.3 Evolutionary Feasibility Table 7: Evolutionary Requirements and Their Feasibility Evidence Evolutionary Requirement ER-1: Remotely changing slot in a lock Product Satisfaction Software/Technology used: Postman, SmartThings API Feasibility Evidence: Using Postman to lock, unlock, change slot for specific lock Referred use case diagram: 1. Use Case Diagram House manager 2. Use Case Diagram Administrator ER-2: Create User Software/Technology used: MySQL Database, Node.JS, SQL query FED_TRR_F17a_T05_V1.2.doc 7 Version Date: 12/02/17

13 hierarchy Feasibility Evidence: Creating USER table and sore permission with ROLE table Referred use case diagram: 1. Use Case Diagram Administrator ER-3: View all lock activity records Software/Technology used: SmartThings API, MySQL Database, Node.JS, SQL query Feasibility Evidence: Create a LOG table in database to store lock activities from events created from handler, and query those data by sending a request from front-end website. Referred use case diagram: 1. Use Case Diagram Administrator FED_TRR_F17a_T05_V1.2.doc 8 Version Date: 12/02/17

14 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 NDI/NCS are used to build connections within the system. Most end-user functionality is not provided by NDI/NCS. Single NDI/NCS 1 0 Single NDI/NCS is not sufficient for the project. Unique/ inflexible business process 2 2 Business process may vary due to requirements. Need control over upgrade / maintenance 2 2 Normal maintenance of the system is required. Rapid deployment 3 3 System need to be deploy to the market quickly. Critical on compatibility 3 3 Require using standard communication protocol between components. Internet connection independence 1 0 Internet connection is required during deployment. Need high level of services / performance 2 2 Normal performance is acceptable. Need high security 3 4 Security is essential to the client. Asynchronous communication 3 3 Most request are using asynchronous communication. Be accessed from anywhere 3 3 System need to be built on web platform Critical on mass schedule 2 2 Normal mass schedule. constraints Lack of personnel capability 3 3 The users do not have technical knowledge to maintain the product. Require little upfront costs 3 3 Client need to provide hardware to development team. Require low total cost of 2 2 Client need to provide ownership Not-so-powerful local machines hardware support. 2 2 One powerful local machine is needed as server. FED_TRR_F17a_T05_V1.2.doc 9 Version Date: 12/02/17

15 5. Risk Assessment Table 9: Risk Assessment Risks Vulnerability to DDOS attacks Website vulnerability to brute force attack Maintainers of the system might require access to the Samsung account Current pre-defined roles might prove to be insufficient Potential Magnitude Risk Exposure Probability Loss Risk Exposure Risk Mitigations Risk Reduction - Define countermeasures against the attacks (such as CloudFlare) Risk Reduction - Limit the number of tries per IP address Buy Information - Do research on possible solutions to limit access to the Samsung account Buy Information - Discuss the issues with the client FED_TRR_F17a_T05_V1.2.doc 10 Version Date: 12/02/17

16 6. NDI/NCS Interoperability Analysis 6.1 Introduction This section will introduce all NDI/NCS that we are using or plan to use in our project and analyze their interoperability to find out best NDI/NCS solution for the project COTS / GOTS / ROTS / Open Source / NCS Table 10: NDI Products Listing NDI/NCS Products SQLite MySQL Rboy Device handler PHP NodeJS Angular AngularJS Purposes Relational database Relational database Device handler to connect our server to Samsung server Server-side script language Server-side framework Web application platform JavaScript Framework Connectors - In this project, we use NodeJS/MySQL Connector to enable NodeJS web application to retrieve data from the database. - In this project, we use Rboy Device handler/node.js Connector to handle sever-tosever requests from our server to Samsung server Legacy System - In this project, the systems we are using is all up to date. There is not any Legacy System in our project. 6.2 Evaluation Summary Table 11: NDI Evaluation NDI Usages Comments MySQL Database Positive Points: FED_TRR_F17a_T05_V1.2.doc 11 Version Date: 12/02/17

17 -Free -Secure -Easy to use -Scalable Negative Points: -Performance in large scale NodeJS BackEnd Positive Points: -Free -Easy to scale -Highly extensible Negative Points: -Inconsistency -Unsuitable for large web application Angular FrontEnd Positive Points: -Free -Previous development experience -Easy to handle JSON Negative Points: -Complicate FED_TRR_F17a_T05_V1.2.doc 12 Version Date: 12/02/17