Fandom

Scratchpad

QA Billable Leads

216,170pages on
this wiki
Add New Page
Discuss this page0 Share

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.



Title page


Active Billable Page Types

and

Pay For Performances



Table of Contents

Table of Figures

Billable Page Types:

Use Cases

Software requirements were captured and modeled using Use Cases. Each use case description contains the following information:

  • Actors involved in use case – may be users, external systems or events;
  • Goals to be achieved by use case ;
  • Pre-conditions that apply to execute the use case successfully;
  • Outcome achieved after use case is completed successfully;
  • Basic flow of use case, i.e., sequence of interactions between actors and system required to achieve goals;
  • Alternative flows of events which may occur, including failure situations
  • List of requirements that are derived directly from use case. May include non-functional requirements that the use case must meet;
  • Frequency of occurrence of the use case when system is operational;
  • Additional notes, comments, and issues that remain to be solved.

We expect that the use cases will serve the following purposes in the software development process:

  • To model the systems requirements;
  • To provide specifications to guide implementation of the system;
  • To validate whether prototypes and the final deployed system meet the initial requirements;
  • Provide test cases for Usability Testing;
  • Provide the basis for a task based help system (i.e., "how to…" and "how do I…" help systems).

The use cases for Citysearch Website and collaborative environment are presented next. Each use case starts at the top of a new page.

Use Case: api_xml_maps_search_popup

Actors

General Public Users

Goals

To search for a business type or a keyword near a certain location.

Pre-conditions

User is looking for the location of a certain business or business type near a certain location or area.

Outcome

User is able to locate the business centered on the map with a popup window containing details about the business such as name, phone number, and links that enable directions and profile view.

Basic Flow

1. User is at the home page, looking for a certain business or type of business.

2. User selects the "Maps" section page.

3. User selects "Map Location" of "Local Business Search" link.

4. User enters keyword and selects "Search".

5. User clicks on any one of the results entries marked A through Z in the list on the right of the Map.

6. The Map is centered at the selected business and a popup window appears with details about the business.

Use Case: apixmlsend2phone_success

Actors

General Public Users

Goals

The User wants to send details about a certain profile in the form of text message to a mobile phone.

Pre-conditions

User is viewing the profile of a customer that has enabled the service of sending profile details as an SMS.

Outcome

User is able to send the profile information in the form of SMS and a success message is displayed.

Basic Flow

1. User is at the profile page of a customer that had enabled the SMS/text service.

2. User selects the SMS/text link.

3. User enters a valid mobile number with area code.

4. User indicates agreement to terms and conditions by selecting the corresponding check box.

5. User selects the "Send to Phone" button.

6. Message is displayed indicating that SMS was sent successfully.

Use Case: customer_website

Actors

General Public Users

Goals

The User wants to view more details about a certain client and wants to visit the client’s personal website.

Pre-conditions

User is viewing the profile of a client that has enabled the service of providing the user the ability to view the client’s personal website.

Outcome

User is redirected to client’s personal homepage in a new window or tab.

Basic Flow

1. User is at the profile page of a customer that has enabled the redirect to customer website service.

2. User selects the "Website" link.

3. User is redirected to customer website.

.

Use Case: email

Actors

General Public Users

Goals

The User wants to email a certain business he has located on the website.

Pre-conditions

1. User is viewing the profile of a client that has enabled the service of providing the user the ability to email the client.

2. Or, user is viewing the search results of a certain search where one or more clients listed in the search results have enabled the option of emailing the business form the search results.

Outcome

User is redirected to a perl page where he is required to enter the usual email specifications such as from, subject, cc, and the body of the email.

Basic Flow

1. Scenario 1, email from search results.

  • User is at the home page or at any other section page except maps and has entered text in the search text box.
  • User selects the "Search" button.
  • Search results appear that contain clients that have enabled the option of emailing the business from search results.
  • User clicks on the "Email the Business" link below the designated clients.
  • User is redirected to an email perl page where User can email the client.

2. Scenario 2, email from profile

  • User is viewing the profile of a client that has enable the option of emailing the client from within the profile.
  • User selects the "Email the Business" link.
  • User is redirected to an email perl page where User email the client.

Use Case: maps_directions

Actors

General Public Users

Goals

The User wishes to search for directions from a start location to an end location.

Pre-conditions
  • User is at the home page or at one of the section pages and is able to access the maps section page.
  • User is in "Maps and Directions" tab of a particular profile.
Outcome

User is able to get detailed directions with a visual route on a map pertaining to his desired search for directions.

Basic Flow
  • User is at the home page, looking for a certain business or type of business.
  • User selects the "Maps" section page.
  • User selects "Driving Directions" link.
  • User enters the "Starting Location" and the "Ending Location" in a valid form.
  • User clicks on the "Get Directions" button.
  • The Map is centered at the selected business and a popup window appears with details about the business.
  • User is in a profile page looking for directions to that particular business.
  • User selects the "Maps and Directions" tab.
  • User enters address and selects "To" or "From"
  • User clicks on "Get Directions" to obtain the path on the map and written directions below the map.

Use Case: maps_nearby_customer_windoid

Actors

General Public Users

Goals

The User wants to view other businesses nearby the location of the business he is currently viewing.

Pre-conditions

User is viewing the profile of a non-customer and has selected the Maps and Directions tab.

Outcome

User is displayed the location and detailed information of customers nearby the profile he is currently viewing.

Basic Flow

1. User is at the profile page of a Non-Customer client type and has selected the Maps and Directions tab.

2. User is displayed the list of customers nearby the client he is currently viewing.

3. User clicks on one of the entries and a popup is displayed on the map, centering the map at the chosen customer, displaying details about the customer including reviews.

Use Case: menu

Actors

General Public Users

Goals

The User wants to view the menu of the client of type restaurant.

Pre-conditions

User is viewing the profile of a client that has enabled the service of providing the user the ability to view the client’s menu.

Outcome

User is redirected to client’s menu in a new window or tab.

Basic Flow

1. User is at the profile page of a customer that has enabled the view menu service.

2. User selects the "Menu" link.

3. User is redirected to customer’s menu.

Use Case: offerprintout

Actors

General Public Users

Goals

The User wants to view the offer or coupon of the client.

Pre-conditions

User is viewing the profile of a client that has enabled the service of providing the user the ability to view the client’s offer or coupon and print it.

Outcome

User is redirected to client’s offer or coupon page in a new window or tab, and the link to the local printer is displayed enabling the user to easily print.

Basic Flow

4. User is at the profile page of a customer that has enabled the offer or coupon printout.

5. User selects the "Offer" or "Coupon" link in the blue list box or the link towards the bottom of the profile..

6. User is redirected to offer or coupon page and is given the ability to print.

Use Case: profile

Actors

General Public Users

Goals

The User wants to view the profile of a certain business he has located on the website.

Pre-conditions

1. User has conducted a search where a list of clients is presented pertaining to his search.

2. Or, user is viewing a map where a collection of clients are displayed on the map.

Outcome

User is redirected to the profile page of the client where he has access to more details about that specific service.

Basic Flow

1. Scenario 1, access profile from search results.

  • User is at the home page or at any other section page except maps and has entered text in the search text box.
  • User selects the "Search" button.
  • Search results appear that contain a list of clients of type customer or non-customer.
  • User clicks on the name of the listed business.
  • User is redirected to the profile page of the client.

2. Scenario 2, access profile from map.

  • User is viewing a map of a certain location where has searched for a certain type of business.
  • A collection of users are displayed on the map, pertaining to his search.
  • User selects one of the displayed businesses which then displays a popup.
  • User clicks on the name of business displayed in the popup that has appeared.

Use Case: profile_print

Actors

General Public Users

Goals

The User wants to print out the information displayed on the profile page of one of the businesses.

Pre-conditions

User is viewing the profile of a client that has enabled the service of providing the user the ability to print out the information displayed on the profile page.

Outcome

User is redirected to a print preview page associated with the printer functionality and printing options window.

Basic Flow

1. User is at the profile page of a customer that has enabled the print profile option.

2. User selects the "Print" link in the blue list box.

3. User is redirected to print preview page and is given the ability to print.

Use Case: profile_map

Actors

General Public Users

Goals

The User wants to view the location of the business on a map.

Pre-conditions

User is viewing the profile of a client.

Outcome

User is redirected to a map that displays the client’s location on the map with the option of getting direction or selecting nearby businesses if client is non-customer.

Basic Flow

1. User is at the profile page of a business and clicks on the map tab.

2. Another scenario is that the user is viewing the profile page of a client and selects the "Map" link from the blue list.

Use Case: profile_print_map

Actors

General Public Users

Goals

The User wants to print out the location of the business on the map.

Pre-conditions

User has selected the maps tab from the profile page of a certain business.

Outcome

User is able to printout a small map indicating the location of the desired business.

Basic Flow

1. User is at the profile page of a business.

2. User selects the "Map" link in the blue list box or Maps and Directions tab of the profile.

3. User is redirected to a map page and is given the ability to print.

4. User can either print location or get directions and then print location on map with directions and graphed route on the map.

Use Case: reviews_all

Actors

General Public Users

Goals

The User wants to view business reviews or write their own review.

Pre-conditions

User is viewing the profile of a business with at least one review.

Outcome

User is redirected to client’s reviews page where he is able to read other user’s reviews or write a new one.

Basic Flow

1. User is at the profile page of a customer that has at least one review.

2. User selects the "Reviews" tab or the reviews link below the blue list or the reviews link from the search results page.

3. User is redirected to reviews page and is given the read other reviews and write his own review.

Billable Page Type Visualization:

File:QA Billable Leads 02.png

Figure 1.1: api_xml_maps_search_popup


File:QA Billable Leads 03.png

Figure 1.2: apixmlsend2phone_success


File:QA Billable Leads 04.png

Figure 1.3: customer_website


File:QA Billable Leads 05.png

'Figure 1.4: 'email


File:QA Billable Leads 06.png

'Figure 1.5: 'external_profile

File:QA Billable Leads 07.png

Figure 1.6.1: maps_directions

File:QA Billable Leads 08.png

Figure 1.6.2: maps_directions

File:QA Billable Leads 09.png

Figure 1.7: maps_nearby_customer_windoid


File:QA Billable Leads 10.png

'Figure 1.8: 'menu

File:QA Billable Leads 11.png

Figure 1.9: offerprintout

File:QA Billable Leads 12.png

'Figure 1.10: 'profile


File:QA Billable Leads 13.png

Figure 1.11: profile_print


File:QA Billable Leads 14.png

Figure 1.12: profile_map


File:QA Billable Leads 15.png

Figure 1.13: profile_print_map

File:QA Billable Leads 16.png

Figure 1.14: reviews_all

Pay For Performance

Pages Containing PFPs:

Search Results

Profile Page (Bottom, NonCustomer)

Section Pages

Roundups (things to do etc.)

Maps Tab (3 businesses on right side)

Landing (this page is currently turned off)

Search Grid PFPs

Types:

-Priority Listing //sg_priority_location

//image + name + tagline + website_link

//Handled by ads department in terms of tagging and content.

//No rating or address

-Regular   //sg_pfpads_top_X_location
    //name + tagline + website_link + rating
      //Iincludes Address that is not linkable or tagged.
      //have entity id


-Virtual   //sg_pfpads_top_virtual_X_location

//name + tagline + website_link

//No Rating or Address

//no entity id

       
-Overture Backfill // sg_pfpads_top_overture_X_location
  //name + tagline + website_link

//No Rating or Address but allowed up to 190 chars hence usually //have more text imbedded.

//no entity id

      //ad_id=overture


- Verizon Backfill // sg_pfpads_top_verizon_X_location
    //name + tagline + website_link
      //Similar to Overture Backfill
      //no entity id
      //ad_id=verizon_backfill

- Non Tagged Interstitial PFPs located in the middle of the page.

Categorization and Identification:


----
Search Grid TOP
PFP Type Location ad_type ad_id EID Name
Regular</$$DeleteCell$$font$$DeleteCell$$> Name 201 Ad Specific Y sg_pfpads_top_X_name
align = "center" align = "center"|Tagline 201 Ad Specific Y sg_pfpads_top_X_tagline
align = "center" align = "center"|Website Link 201 Ad Specific Y sg_pfpads_top_X_website_link
align = "center" align = "center"|Rating 201 Ad Specific Y sg_pfpads_top_X_rating
align = "center" rowspan = "3"|<f$$DeleteCell$$ont$$DeleteCell$$ col$$DeleteCell$$or=$$DeleteCell$$"#F$$DeleteCell$$F00$$DeleteCell$$00"$$DeleteCell$$><f$$DeleteCell$$on$$DeleteCell$$t size = "4">Virtual</font> Name 201 Ad Specific N sg_pfpads_top_virtual_X_name
align = "center" align = "center"|Tagline 201 Ad Specific N sg_pfpads_top_virtual_X_tagline
align = "center" align = "center"|Website Link 201 Ad Specific N sg_pfpads_top_virtual_X_website_link
align = "center" align = "center" rowspan = "3"|Overture
Backfill
Name 201 "overture" N sg_pfpads_top_overture_X_name
align = "center" align = "center"|Tagline 201 "overture" N sg_pfpads_top_overture_X_tagline
align = "center" align = "center"|Website Link 201 "overture" N sg_pfpads_top_overture_X_website_link
align = "center" align = "center" rowspan = "3"|Verizon Backfill Name 201 "verizon_backfill" N sg_pfpads_top_verizon_X_name
align = "center" align = "center"|Tagline 201 "verizon_backfill" N sg_pfpads_top_verizon_X_tagline
align = "center" align = "center"|Website Link 201 "verizon_backfill" N sg_pfpads_top_verizon_X_website_link
Search Grid BOTTOM Regular</f$$DeleteCell$$ont$$DeleteCell$$>$$DeleteCell$$$$DeleteCell$$ Name 238 Ad Specific Y sg_pfpads_bottom_X_name
Tagline 238 Ad Specific Y sg_pfpads_bottom_X_tagline
align = "center" align = "center"|Website Link 238 Ad Specific Y sg_pfpads_bottom_X_website_link
align = "center" align = "center"|Rating 238 Ad Specific Y sg_pfpads_bottom_X_rating
align = "center" rowspan = "3"|<fo$$DeleteCell$$nt co$$DeleteCell$$lor=$$DeleteCell$$"#F$$DeleteCell$$F00$$DeleteCell$$00"$$DeleteCell$$><f$$DeleteCell$$ont size = "4">Virtual</font> Name 238   N  
align = "center" align = "center"|Tagline 238   N  
align = "center" align = "center"|Website Link 238   N  
align = "center" align = "center" rowspan = "3"|Overture
Backfill
Name 238 "overture" N sg_pfpads_bottom_overture_X_name
align = "center" align = "center"|Tagline 238 "overture" N sg_pfpads_bottom_overture_X_tagline
align = "center" align = "center"|Website Link 238 "overture" N sg_pfpads_bottom_overture_X_website_link
align = "center" align = "center" rowspan = "3"|Verizon Backfill Name 238 "verizon_backfill" N  
align = "center" align = "center"|Tagline 238 "verizon_backfill" N  
align = "center" align = "center"|Website Link 238 "verizon_backfill" N  

Figure 2.1.1: Table: Search Grid tagged PFP types and properties excluding priority listing.


 MediaWiki2WordPlus Converter found a non convertable object. Please send example to developer.
 http://meta.wikimedia.org/wiki/Word2MediaWikiPlus

FormType = 21

File:QA Billable Leads 01.gif

Figure 2.1.2: Procedure for identifying the four types of tagged search grid PFP types.

Visualization:

Tagged PFPs:
File:QA Billable Leads 17.png

Figure 2.1.3: Tagged search grid PFP of business name with sample access log entry.


File:QA Billable Leads 18.png

Figure 2.1.4: Tagged search grid PFP of business tagline with sample access log entry.


File:QA Billable Leads 19.png

Figure 2.1.5: Tagged search grid PFP of business web link with sample access log entry.


File:QA Billable Leads 20.png

Figure 2.1.6: Tagged search grid PFP of business rating with sample access log entry.


File:QA Billable Leads 21.png

Figure 2.1.7: Tagging criteria for tagged search grid PFP type "Priority Listing".


File:QA Billable Leads 22.png

Figure 2.1.8: Tagging criteria for tagged search grid PFP type "Regular".


File:QA Billable Leads 23.png

Figure 2.1.9: Tagging criteria for tagged search grid PFP type "Virtual".


File:QA Billable Leads 24.png

Figure 2.1.10: Tagging criteria for tagged search grid PFP type "Overture Backfill".


File:QA Billable Leads 25.png

Figure 2.1.11: Tagging criteria for tagged search grid PFP type "Verizon Backfill".

==

File:QA Billable Leads 26.png

Figure 2.1.12: Interstitial PFPs.

Ad Type IDs

File:QA Billable Leads 27.png

Figure 2.1.13: PFP Ad types based on location on search grid.

Profile PFPs:

File:QA Billable Leads 28.png

Figure 2.2.1: Profile PFPad "Featured Sponsor" name, rating and image.

Also on Fandom

Random wikia