Feasibility Evidence Description (FED) COSMIC SYSTEM. Team 02. Sam Lehardi Project Manager/ Life Cycle Planner/ Trainer

Transcription

1 Feasibility Evidence Description (FED) COSMIC SYSTEM Team 02 Sam Lehardi Project Manager/ Life Cycle Planner/ Trainer Mishaal Aleem Prototyper/ Trainer / Implementer Rachel Inouye Operational Concept Engineer/ Implementer Terence Williams Software Architect/ Implementer Sitan Gao Feasibility Analyst/ Tester Sam Villarreal Requirements Engineer/ IIV & V/ Tester Nick Kwong Quality Focal Point/ IIV&V/ Tester 12/02/17

2 Version History Date Author Version Changes made Rationale 10/08/17 SG /15/17 SG /02/17 SG 1.2 Started working on the document; Finished Section 1, Section 5 and part of other section. Updated former work. Completed all sections. Fixed some error in title Updated Benefit Analysis, LOS Feasibility and Process Feasibility Initial draft for DC package. Final document for DC package. According to the feedback from ARB. According to the DC package feedback FED_T02_F17.doc ii Version Date: 12/02/17

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...11 FED_T02_F17.doc iii Version Date: 12/02/17

4 Table of Tables Table 1: Personnel Costs...3 Table 2: Hardware and Software Costs...3 Table 3: Benefits of COSMIC 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 Model...8 Table 8: Risk Assessment...10 Table 9: NDI Products Listing...11 Table 10: NDI Evaluation...11 FED_T02_F17.doc iv Version Date: 12/02/17

5 Table of Figures Figure 1: ROI Analysis Graph...4 FED_T02_F17.doc v Version Date: 12/02/17

6 1. Introduction 1.1 Purpose of the FED Document The Feasibility Evidence Description Document shows the analysis on feasibility evidence of COSMIC 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.1. Benefit analysis was recalculated and ROI analysis was added based on the feedback of ARB presentation. Other parts were also updated and finished. FED_T02_F17.doc 1 Version Date: 12/02/17

7 2. Business Case Analysis Assumptions Client and users will use the system once it s deployed Inventory Manager will keep the system up to date with current inventory Stakeholders Initiatives Value Propositions Beneficiaries Developers: Team Members Client: Darin Gray Maintainers: Inventory Manager Users: Volunteers Organizations Cost Development costs Maintenance costs Domain costs Developers: Develop the inventory management system Client: Provide Requirements Win Conditions Feedback / Input Hosting System Users Use the system Maintainers Test the system Use the system Provide Feedback Provide spreadsheet to import current inventory Increase time efficiency through inventory organization, tracking item location, and automated reorder s. Save costs by tracking inventory stock instead of over-ordering items due to disorganization. Easier lesson planning for volunteers & organizations through our searchable interface. USC STEM-EOP Director STEM Staff Inventory Manager Volunteers People that STEM- EOP affect Organizations Benefits Save time for people who want to borrow items Have a better management of items FED_T02_F17.doc 2 Version Date: 12/02/17

8 2.1 Cost Analysis Personnel Costs Table 1: Personnel Costs Activities Time Spent (Hours) Development Period Client Meeting: 1h/w * 12 w 12 Win-Win Sessions: 2 sessions * 1h 2 Training: 2h 2 Fill out inventory spreadsheet and organize it: 8h 8 ARB: 1 session * 1.5h 1.5 CCD: 1 session * 1h 1 TRR: 1 session * 1.5h 1.5 Total 28 Maintenance Period (per year) Maintenance: 5h/month * 12month * 1person = 60h 60 Total Hardware and Software Costs Table 2: Hardware and Software Costs Type Cost Rationale Development Cost $0 Only use PHP, AngularJS and MYSQL to develop Maintenance Cost $0 No foreseeable maintenance costs Hardware Cost $0 No foreseeable hardware costs GoDaddy Economy Cost $7.99/month Gain a hosting package 2.2 Benefit Analysis Table 3: Benefits of COSMIC System Current activities & resources used Find Item User: See if there are items available Reserve Item User: Send of reserve request Current Time Spent(Hrs/Yr) Proposed Time Spent(Hrs/Yr) % Reduce Time Saved (Hours/Year) % % 30 FED_T02_F17.doc 3 Version Date: 12/02/17

9 Manager: Set item reserved Manage Item Manager: Manage, update and track item % 210 Total ROI Analysis The total time spent by the clients for developing the COSMIC system is a total of 28 hours, which includes the total time the client spent attending meetings, negotiations, presentations, and completing and finalizing the database spreadsheet to import items into the system. The maintenance amount is 60 hours per year and will approximately increase 5% a year due to more users and traffic to the website. They will have to manage more s, registering accounts, and additional maintenance on phpmyadmin. Table 4: ROI Analysis Year Cost Benefit Cumulative Cumulative (Effort Saved) Cost Benefit ROI Figure 1: ROI Analysis Graph FED_T02_F17.doc 4 Version Date: 12/02/17

10 3. Architecture Feasibility 3.1 Level of Service Feasibility Table 5: Level of Service Feasibility Level of Service Requirement LOS-1: Have response time of less than 2 seconds in various browsers such as Safari 11, Firefox 56.0, Chrome 61 and Chrome 60 and different devices such as desktop, laptop and smartphone. LOS-2: Be able to handle 1000 different items in the system. Product Satisfaction Product Strategies: AngularJS, Bootstrap Process Strategies: Use different browsers and mobiles to search the website to see whether it can meet the requirement. Utilize AngularJS and Bootstrap to improve responsiveness. Analysis: Different users may use different browsers and different mobiles, so it is important to support many browsers and various mobiles and offer a responsive system. Product Strategies: PHP, MySQL Process Strategies: Create prototypes; import items currently in the inventory into MySQL database. Analysis: It is important to be able to handle all items in the case the system grows. This allows scalability for the future and allows items to be added to the database with no problems. 3.2 Capability Feasibility Table 6: Capability Requirements and Their Feasibility Evidence Capability Requirement CR-1: Create account CR-2: Reserve an item Product Satisfaction Feasibility Evidence: When receiving account request, admin can use the system to generate an account and create password for the account so that user can login. AngularJS provides interface to create account, which is stored in MySQL. Referred use case diagram: UC-1, UC-2, UC-10, UC-11 Feasibility Evidence: When receiving reserve request, manager can click the item to check it and set the reservation time and amount by filling out a form. AngularJS provides the interface where the item can be reserved as a string in MySQL which is connected through PHP. Referred use case diagram: UC-9 FED_T02_F17.doc 5 Version Date: 12/02/17

11 CR-3: Add new item CR-4: Import a spreadsheet CR-5: Generate item logs CR-6: Check item availability and its location CR-7: Various status of item CR-8: Show check-out items CR-9: Set items checked in CR-10: The status of items changes with the quantity Feasibility Evidence: Manager can add an item to the system and set quantity and tags and also upload a picture. AngularJS provides functionality to add a.jpeg image stored on the server and item details will be stored in MySQL. Referred use case diagram: UC-12, UC-13 Software/Technology used: MYSQL Feasibility Evidence: When the system is delivered, developer can import all the items in the spreadsheet into the database. Spreadsheet will be filled by maintainer and imported to system as a CSV format into the database. Referred use case diagram: N/A Feasibility Evidence: The system can generate logs about the checkin and check-out record for manager to read. PHP will use serverside scripting to generate code to save into database as timestamps and data queries. Referred use case diagram: UC-15, BootStrap Feasibility Evidence: Volunteer can login to the system and click the item to see the page of the availability and location. AngularJS framework and BootStrap allows for items to be visually displayed. Referred use case diagram: UC-3, UC-4 Feasibility Evidence: Manager can click the item and set the status. This can be adjusted easily through an interface developed using front-end framework. Referred use case diagram: UC-14 Feasibility Evidence: Users can login to the system to view the items on their dashboard. Front-end frameworks show items from checked-out database table on MySQL. Referred use case diagram: UC-5, UC-6 Feasibility Evidence: A user can return the items to the locations and choose items check-in. From the user dashboard there is interface to check-in the item to transfer from checked-out table in MySQL to item inventory list. Referred use case diagram: UC-6 Feasibility Evidence: The system will automatically change the status of items according to the quantity. This is automatically changed with server-side scripting and front-end framework to change values in MySQL. Referred use case diagram: UC-5 FED_T02_F17.doc 6 Version Date: 12/02/17

12 CR-11: Generate notification and send to admin CR-12: Show item details CR-13: Meet multiple platforms requirement CR-14: Search function on item CR-15: Show all the inventory CR-16: Show item images CR-17: Have Darin function CR-18: Show reservations for volunteer Software/Technology used: PHP, MYSQL Feasibility Evidence: When an item is out of stock, the system will generate an and send it automatically to admin. This will be done with php to automatically determine to notify admin when threshold is breached. Referred use case diagram: N/A Feasibility Evidence: User can view the details of an item by clicking it and the system will show the page of the item in detail. This can be done by using AngularJS to create a view for users. Referred use case diagram: UC-3, UC-4 Software/Technology used: AngularJS, Bootstrap Feasibility Evidence: The website is cross-platform. Bootstrap allows for responsive wed design. Referred use case diagram: N/A Feasibility Evidence: Users can type name or tags to search for an item and the website will return the search result. AngularJS allows for search to view certain items. Referred use case diagram: UC-4 Feasibility Evidence: Users can see all items through the website. This can just be done by viewing through framework the items in MySQL. Referred use case diagram: UC-3 Software/Technology used: AngularJS Feasibility Evidence: The browser is able to show an image from the server related to an item. AngularJS allows for viewing of items located in the images folder. Referred use case diagram: UC-3, UC-4 Software/Technology used: AngularJS, PHP Feasibility Evidence: Manager can click a button to Darin to reorder an item. A server-side function can be developed to send to client. Referred use case diagram: N/A Feasibility Evidence: Volunteer can see their reservations through the dashboard and also cancel or check it out. This is allowable through viewing from front-end framework of reservations found in the database. Scripting allows users to cancel reservations too. Referred use case diagram: UC-7, UC Evolutionary Feasibility No evolutionary requirements are negotiated at this time. FED_T02_F17.doc 7 Version Date: 12/02/17

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 7: Rationales for Selecting Architected Agile Model Criteria Importance Project Status Rationales 30 % of NDI/NCS features 3 4 Use AngularJS and PHP for development. Use MYSQL to store data. Use GoDaddy for hosting. Single NDI/NCS 1 0 There is no single NDI/NCS product that allows for the required functionalities. Unique/ inflexible business 1 1 Business process is not unique. process Need control over upgrade / maintenance 2 1 Maintenance is needed, but no major upgrades, just upkeep of system. Rapid deployment 3 0 Used multiple NDI services to finish the project in the length of a semester to deliver product to client. Critical on compatibility 3 3 Run on various kinds of browsers and devices. Internet connection independence 2 3 It is a web system functioning only if internet is available. Need high level of services / performance 2 2 The system needs to support multiple users and multiple browsers/devices. Need high security 1 1 User information is securely Asynchronous communication Be accessed from anywhere stored through MySQL. 2 3 Asynchronous communication is required in the system. 2 2 The system needs web service and can be accessed on portable devices. Critical on mass schedule constraints 3 4 Only one semester for the project. Lack of personnel capability 2 2 User manuals and forums provide enough information for team members to have enough technical knowledge. Require little upfront costs 3 1 There is little upfront cost as FED_T02_F17.doc 8 Version Date: 12/02/17

14 Require low total cost of ownership Not-so-powerful local machines most the NDIs used are free, but there is low cost to host website and utilize these tools with the service provider chosen. 3 3 The system will not generate profit, but have no relatively large costs outside hosting package monthly fee. 2 2 No processes are being run on the local machine as the website is being hosted on the GoDaddy web hosting. FED_T02_F17.doc 9 Version Date: 12/02/17

15 5. Risk Assessment Table 8: Risk Assessment Risks Personnel shortfalls: Skill deficiencies in aspects of web technologies and lack of cohesion between members as new team just formed. Communication problems between members of diverse backgrounds. Midterms and recruiting season outside of class cause time conflicts. Inventory management system crashing and loss of information: Bugs, malfunctions, malware, etc. may cause database to not function and crash, potentially losing months of information. Gold Plating /Requirements mismatch: Taking too much time to develop features that add little value to the overall user experience of the product. Inability to handle multiple users: Various schools/organizations/students will have access which may cause real-time issues for reserving items. Requirements change: Client introduced modifications to preexisting features to improve overall quality and flow of system. Risk Exposure Potential Probability Risk Risk Mitigations Magnitude Loss Exposure Researching and learning several technologies and better understanding of server-side programming languages and databases. Plan more team meetings and participate in team-building activities. Delegate tasks efficiently to members with more time Developing extra features to create save points and restore points for the system Performing case-analysis and holding win-win negotiations with client. Taking surveys from stakeholders to determine most important features Prototyping system to determine how many users can actively use system with no performance loss. Discuss with client expected number of users Incremental development of highest priority features and functions first. Schedule hardest features and discuss with client FED_T02_F17.doc 10 Version Date: 12/02/17

16 6. NDI/NCS Interoperability Analysis 6.1 Introduction COTS / GOTS / ROTS / Open Source / NCS Table 9: NDI Products Listing NDI/NCS Products AngularJS PHP MYSQL GoDaddy Purposes JavaScript Framework Programming Language Store data (eg. user, item, check-in/check-out record) Hosting Connectors In the COSMIC system, we use PHP/MySQL Connector to enable the PHP web application to manage the item and user and also update the check-in and check-out record Legacy System The COSMIC system is the new system for Viterbi STEM-EOP. There is no web system that is currently used. So, there is no incorporation of legacy system or use of any legacy systems. 6.2 Evaluation Summary Table 10: NDI Evaluation NDI Usages Comments AngularJS Front-end framework -Overcome the shortcomings of HTML in the construction of applications PHP Back-end development -Strong cross platform -Consume very little system resources MYSQL Data storage -Constitute a good development GoDaddy Hosting package environment with php -Flexible management -Fast speed FED_T02_F17.doc 11 Version Date: 12/02/17