Prototype Report. Fuppy. Team No.7

Transcription

1 Prototype Report Fuppy Team No.7 Krupa Patel (Product Manager) Adil Assouab (Requiremnt Engineer) Yiyuan Chen (Software Architecture) Praveen Chander (Designer/Prototyper) Zhouyun Feng (Developer) Fereshteh Khorzani (Quality Focal Point) 10/13/2016

2 Version History Date Author Version Changes made Rationale 10/13/201 6 PC,KP 1.0 Original for CSCI477; Tailored from ICSM OCD Template To fit CS477 course content 2

3 Table of Contents Prototype Report Version History Table of Contents Table of Tables Table of Figures 1. Introduction 1.1 Purpose of the prototype report 1.2 Status of the prototype 2. Navigation Flow 3. Prototype 3

4 Table of Tables Table 1: User Login Table 2: Registration Table 3: User Profile Table 4: Search Table 5: Display Search Data Table 6:Information Center Table 7: Appointment Center Table 8: Appointment Confirmation 4

5 Table of Figures Figure 1: Navigation Flow of Fuppy User Mobile Application Figure 2: Login Page Figure 3: User Registration Figure 4: User Profile Figure 5: Search Pets Figure 6: Filter Based Search Figure 7: Information Center Figure 8: Appointment Center Figure 9: Appointment Confirmation 5

6 41. Introduction This prototype report refers to the final product that will be delivered to the clients during our transition period. The prototype is entirely deployed in Wordpress using different plugins for the core functionalities and further customization using child themes and short code creation to accommodate specific requests by the clients. The main difference from the previous report is that all the primary assessed risks are handled. the mobile application integration with the external petfinder API and google map integration for location based information are streamlined and displayed. The end product is kept minimalistic for we are engaged in this project only for one semester and have come to a common ground to develope further if all the mmfs are completed in advance 42. Navigation Flow Figure 1: Navigation Flow of Fuppy User Mobile Application 6

7 43. Prototype Description Table 1: User Login Guest user Login page for users intending to use the application OC-1 - only registered user can access the pet information Guest users are familiar with Fuppy and have already registered Users redirected to search page Figure 2: Login Page 7

8 Table 2: Registration Description When a user is new to the system and is looking forward to adopt a pet he/she must first register in order to search and access the shelter information OC-1 - only registered user can access the pet information User decides to adopt a pet. Redirected to profile completion and forwarded to search menu Figure 3: User Registration 8

9 Table 3: User profile Description Users can edit and modify their profile & preferences to the pets and type of animal he/she wishes to adopt Win Condition (WC_4045): profile As a user, I should be able to modify my personal information so that it stays up to date. User finishes registration Redirects to search Pets Figure 4 : User Profile 9

10 Table 4: Search Description Registered users are provided with the options to search for what they are looking for in the application OC-1 - only registered user can access the pet information User decides to adopt a pet. Forwarded to the Information center Figure 5: Search Pets 10

11 Table 5: Display Search Data Description Once the user selects to view pets he can view all the data fetched from the external API and displayed through the Mobile application. Filter options are also provided for advance search OC-3 : Filter Based Search User decides to adopt a pet. Redirected to Information Center Figure 6: Filter Based Search 11

12 Table 6: Information Center Description If the user finds a pet of interest then complete data of the Animal from the shelter is displayed OC-2 : Information Center Finds a pet of their interest Proceed to booking appointments 12

13 Figure 7: Information Center 13

14 Table 7: Appointment Center Description User gets the shelter details and proceeds to book an appointment to meet with the concerned personnel OC-2: Information Center OC-4 : Data Integrity User decides to meet with the Shelter Waits to receive appointment confirmation. Figure 8: Appointment Center 14

15 Description Table 8: Appointment Confirmation Once an appointment is made the system sends a confirmation message to both the user and shelter OC-4 : Data Integrity User makes Appointment Waits to receive appointment confirmation. Figure 9: Appointment Confirmation 15