1 / 69

Perfecto Coffee

Explore the operational concept and team analysis for Perfecto Coffee, a multi-platform application that streamlines coffee ordering, customization, and sharing. Discover how the team addresses challenges and works towards win-win agreements.

zumwalt
Download Presentation

Perfecto Coffee

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Perfecto Coffee DCR-ARB - Team 5

  2. Agenda • Team Analysis (Remote Team Member) • Operational Concept Design (OCD) • Win-Win Agreements • Prototype/Product Demo • Architecture • Life Cycle Plan • Feasibility Evidence • Quality Focal Point (QFP) • Definition of Done • Metrics

  3. Team Analysis

  4. Team Analysis - Strengths & Weaknesses

  5. Technical Concerns & Solutions • Not all team members have experience in mobile development • Solution: Select a straightforward, intuitive and accessible mobile development language/framework that allows the team to jump in and start building quickly- based on existing skill, industry consensus of difficulty, etc. • Different team members have different development platforms which may cause slowdowns if incompatibilities are encountered • Solution: Ensure that all tools chosen for development have cross-client compatibility. If not possible, make sure that all team members have access (whether borrowed laptop or VM) to an operating system that can run the tool they need. • Solution: Ensure that items that might be system-specific such as file pathnames are coded in a way that is agnostic across various systems.

  6. Operational Risks & Mitigations • Two DEN students means that not all members may be present during team meetings • Mitigation: Ensure that key takeaways from meetings are summarized in Slack or communicated through email to ensure that DEN students don’t miss information. • Mitigation: Work with DEN students to select a time that works with their work schedule for meetings that require attendance. • Balancing priorities for other classes may mean there are delays in work completion that doesn’t leave adequate time for testing and verification • Mitigation: Accept the risk and plan for it in advance. When estimating how long something will take to complete, encourage the team member to consider their other commitments alongside the task at hand instead of the task alone to project when something will be finished. • Mitigation:Communicate frequently to let teammates know of any obstacles or difficulties. The earlier, the better so perhaps others can step in and help.

  7. Sources of Observations

  8. Sources of Observations, Con’t.

  9. Sources of Observations, Con’t.

  10. Operational Concept Description

  11. System Purpose The purpose of Perfecto Coffee is to expedit the coffee ordering process to save time for its customers while also giving customers the ability to craft their own unique coffee blend. By connecting its customers, Perfecto Coffee aims to foster a community through users sharing recipes via app and social media networks. With Perfecto Coffee, coffee drinkers can order high quality coffee at a lower cost, faster speed, and from more conveniently placed locations than other companies. Proposed System Multi-Platform application that allows users to quickly and easily order, customize, and share their coffee from their phone. Supporting this system is a server/database backend that aims to organize user, coffee, and transaction data to allow scalability for future business expansion.

  12. Shared Vision

  13. Benefit Chain Diagram

  14. System Boundary Diagram

  15. Core Capabilities

  16. Constraints • CO-1: React Native as the App coding framework: The code will be developed using React, allowing the code to be used for iOS and Android. • CO-2: Close to Zero Budget: COTS API and system are to be free at least in the developing and testing phase. • CO-3: Commercial Off The Shelf Dependency: We are using Google Maps API and various social media API. • CO-4: Amazon Web Services as Database: AWS hosts our database.

  17. Organizational goals • OG-1: Increase sales and profits via a more efficient customizable coffee order process • OG-2: Expand service locations nationwide and globally • OG-3: Increase user-base and foster a strong, growing, and positive community

  18. Win-Win Agreements

  19. Win-Win Agreements • Recipe Customization • WC_4820: As a user, I can browse from a list of existing recipes. • WC_4846: As a user, I can select a coffee type (e.g. Cappuccino, Latte, Expresso, etc) and then adjust ingredients as I want from its standard recipe. • WC_4918: As a user, I can customise my coffee. • WC_4846: As a user, I can customize an existing base recipe and save it as my own recipe. • WC_4920: As a user I will be able to check if my recipe contains specific allergens

  20. Win-Win Agreements • Convenience is Key • WC_4913: As a user, I can easily replace my last order. • WC_4919: As a user I can view the recipe from my saved coffee selections and choose to vend it • WC_4916: As a user, I can change which kiosk I send my order to. • WC_4917: As a user, I can use apple pay or paypal to purchase coffee. • WC_4845: As a user, I can save and set a default payment method for my orders.

  21. Win-Win Agreements • User Interaction • Win Condition (WC_4915): As a user, I can view my order history. • Win Condition (WC_4914): As a user, I can send someone else a cup of coffee I've purchased for them. • Win Condition (WC_4899): As a user, I can earn rewards for using my coffee app • Win Condition (WC_4910): As a User, I should be able track rewards and cash in for appropriate rewards • Social Media Integration • WC_4909: As a User, I should be able to share the recipe via social media.

  22. Win-Win Agreements • Other main stakeholders • Win Condition (WC_4922): As a maintainer I will be able to update the location of any new kiosks • Win Condition (WC_4921): As a maintainer I will be able to track any faulty kiosks • Win Condition (WC_4912): As a supplier, I should be able to receive updates from the admin via a page on the portal • Win Condition (WC_4911): As an admin, I should have a unique portal to track inventory, view kiosk usage and track demographic information

  23. Prototype/Product Demo

  24. High Priority Capabilities Demo • Customization Process • Being able to customize a recipe in 3 to 4 steps. • Slider for ingredient amount adjusting. • Milk, syrup preference options. • Recipe Inventory • Show all the customized recipes. • Dependencies • Base flavor research and investigation. • Data flow and storage. • User-friendly

  25. Backup Slides - Customization Steps

  26. Backup Slides - Customization Steps After going through 4 steps of customization, a review page is shown for finalizing the process. If it is all good, by clicking “Save” button, the customized recipe is saved to users’ inventory.

  27. Backup Slides - Recipe Inventory In the recipe inventory view, users can browse all the customized recipes they have made. By clicking each tab, the detail information of a chosen recipe is shown, users can either modify or share the recipe in this view.

  28. Backup Slides - Order View In the order view, users can either choose to vend a existed base recipe or a customized flavor from their recipe inventory. By clicking the tab at the bottom, a map view is shown letting users to pick a preferred kiosk for vending the order.

  29. Backup Slides- Kiosk Search View In the kiosk search view, users can see their location information and information of kiosk. By searching the address on the top, mapview and marker can show to users’ current location or other address.

  30. Architecture

  31. System Context Diagram Use AWS as server to save data.

  32. Artifacts & Information Diagram Focus on Recipe Customization Recipe have a list of data to customize.

  33. Use Case Diagram Most important use case: Recipe Customization After login successfully, it will get the recipe list for users to customize.

  34. Hardware Component Class Diagram Customer: Mobile Devices Supplier: Kiosk Database: Json Back-end Server: AWS

  35. Software Component Class Diagram Mobile app: 6 main pages Database: 4 Json files Third party libraries: 2

  36. Life Cycle Plan

  37. Life Cycle Plan Purpose: • To plan and document the life-cycle through all phases of the Perfecto Coffee App Strategy: • NDI/NCS team Assumptions • Project will be carried out over 12 weeks with the team of 6 on campus and 2 off campus students up to app completion

  38. Life Cycle Plan - Strategy • Identify activities and project deliverables through all phases • Define key stakeholder responsibilities by phase • Outline project tools • Mechanisms for monitoring, feedback and coordination • Ensure the project remains on schedule using cost estimation

  39. Life Cycle Plan - Foundations Phase 09/28/18- 10/22/18 • Activities: • Risk mitigation strategies developed and documented • Further develop prototype for highest risk use cases • Cost estimates formulated • Deliverables • Front end UI using React Native • Customisation UI • Social media API integration • Google Maps API integration • Back end database • DC package and DCR-ARB • Technical debt report

  40. Life Cycle Plan - Development Phase 10/22/18- 11/30/18 • Activities: • Increase functionality by implementing new use cases: • Save recipe • Payment • Order history • Consult client with each development increment to realign goals based on progress • Test code after implementation • Review documentation changes alongside implementations e.g. update cost estimation

  41. Life Cycle Plan - Development Phase 10/22/18- 11/30/18 • Deliverables • Core capability drive through report • Transition readiness review • Project archive

  42. Life Cycle Plan - Operation Phase Undetermined/ Dependent on Hardware Development • Activities: • Product service • Maintainer duties • Track problems (App and kiosk related) • Utilise admin portal to track ingredients stock and supply • Expand service (more kiosks) • Deliverables • Maintainer reports

  43. Life Cycle Plan - Key Stakeholder Responsibilities Bruce Long - Client Jaimin Patel - Project Manager/ Life Cycle Planner Edward Hays - Requirements Engineer Yucheng Hsieh - Software Architect Atreya Lahiri - Feasibility Analyst Yun Shen (Flora) - Prototyper Andrew Tran - Operational Concept Engineer Chloe Good - IV & V/ Quality Focal Point Yekaterina Glazko (Kate) - IV & V

  44. Life Cycle Plan - COCOMO II Scale Drivers

  45. Life Cycle Plan - COCOMO II Cost Drivers Database Module UI Module Sharing Module

  46. Life Cycle Plan - COCOMO II

  47. Life Cycle Plan - COCOMO II Resource Estimation • Total SLOC: 2250 • Effort: • Over semester: 18hrs/week x 8 members x 12 weeks = 1728 hrs • Monthly: 18hrs/week x 8 members x 4 weeks = 576 hrs • Estimate effort (Most Likely) = 8.2 person months • Required time • Time required: 8.2 person month x 152 hrs/person month / 576 hrs/month = 2.17 months • Conclusion • The project can be completed within the allocated time of 12 weeks

  48. Feasibility Evidence

  49. NDI/NCS Integration

  50. Business Case Costs • Initial Setup Cost • Supplier fees • Server fees • Scaling costs Benefits • Cheaper, high quality coffee • Location friendly • Flexible ordering process

More Related