Feasibility Evidence Description (FED) Fuppy Team No-7 Krupa Patel (Product Manager) Adil Assouab (Requirement Engineer) Yiyuan Chen (Software Architecture) Praveen Chander (Designer/Prototyper) Zhouyun Feng (Developer) Fereshteh Khorzani (Quality Focal Point)
11/27/2016 Version History Date Author Version Changes made Rationale 10/06/2016 FK 1.0 Original template for use with Fuppy v1.0 Initial draft for use with Fuppy v1.0 10/16/2016 FK 1.1 Cost Analysis and ROI Based on the feedback changes Have been made to Cost Analysis 11/27/2016 FK 1.2 LOS, ER, CR, Process feasibility, Risk Assessment, NDI/NCS Based on improvement in project.
Purpose of the FED Document The purpose in fuppy program is built the system in android mobile, it will - User can register in fuppy program and log in to fuppy. Allow the users to find their favorite pet. Get appointment and feedback notification from shelter. “find a match and take a pet home” is the value proposition of fuppy. Build the system with low budget and in 12 weeks’ semester. Satisfactory for all stakeholder: decrease kill animals, user have easy app to find favorite pet in local shelter, shelter gets more users to adopt pets, and have market in Android. fuppy gets the Shelter data from Pet Finder. Also all risks to use App in Android will be resolved by risk management plan. Status of the FED Document In the Previous version: fuppy web application used by user/shelter for pet adoption were shown, and a working prototype model for mobile application has been designed. Requested: Plan Delivery Date: End of Semester An Android App which allows the users search pets from various adaption agencies is requested. Artifact Description Requested/ Shown/ Received Planned Delivery Date Web Application The fuppy web app used by the users/shelter for pet adoption Shown Prototype A working prototype model for the mobile application has already been designed Shown and Received Feasibility Study A test was conducted to validate the value proposition of fuppy Shown and Received Android App A mobile application which allows the users to search and find pets from various shelter Requested End of semester
User can be secure and usable. LOS-2: Search System Usability Product Strategies: As a user I want to apply type/locations/price etc. filters on search results sorted so that I can have more accurate results. Error-reducing User Input/output, UI Consistency, UI Flexibility Process Strategies: Prototyping, Usage Monitoring & Analysis, User Engineering, User Interface Tools, User Involvement Analysis: Search system is feasible and usable. LOS-3: Show pet information Interoperability Product Strategies: As a User, I should be able to see pet's information, so that I can decide whether I should go and see the pet or not. Generality, Integrity Functions, Interface Specification, Layering, Modularity, Self-containedness Process Strategies: Interface Change Control, Interface Definition Tools, Interoperator Involvement, Specification Verification Analysis: Develop pet information system with interface change control and verification. LOS-4: Appointment system Schedule Product Strategies: As a user, I want to see the appointments I made, so that I don't forget to visit the shelters. Descoping, Domain Architecture-driven, Modularity, Reuse Process Strategies: Design schedule, Early Error Elimination Tools and Techniques, Personnel/Management, Process Automation, Reuse-oriented Processes, User & Customer Involvement
communication Get access from anywhere Medium Access by App. The first version just Los Angeles, and then will develop Critical on mass schedule constraints Lack of personnel capability High Android Information about Android programming is important. Require little upfront costs Medium Fuppy own database, API cost Cost for own database in future, and cost for API after implementation. Require low total cost of ownership Medium AWS cost Fuppy need own database in AWS in future. Not-so-powerful local machines Table 9: Risk Assessment Risks Risk Exposure Risk Mitigations Potential Magnitude Probability Loss Risk Exposure Team Collaboration 8 6 48 We stopped using Slack and setup Group Chat. We plan on meeting twice a week instead of one. Include the Den Student in the Group Chat. Add Den Student in team meeting remotely instead of sending her meeting summaries. Google Map API Integration 2 4 8 Create a different design for the versions on which Google Map API does not work Timely Validation of the Application from the Client 2 3 6 Send a bi-weekly update report to the client and also set up bi-weekly meeting with him either in person or remotely Interoperability Analysis