Sample Prd Sections

SAMPLE PRD SECTIONS

1.1  World Clock

The World Clock is an application that enabled the user to view the time in a variety of cities all throughout the world. The consistent portion of the implementation of this application (through-out all OEMs) is that a world map is provided that the user can scroll through to select a city. As they select cities, the time and date change accordingly.

This application was almost unheard of 3 years ago but today, it was a mandatory application for several tiers of handsets on dozens of networks including VZW and Sprint.

For COMPANY XYZ, this will be one of our showcase applications with the entire application being implemented using FL 2.0. The COMPANY XYZ world clock will be used to illustrate a phone application implementation success. As with the other applications we create, it will also be used as a launch point for customer service.

1.1.1  Access To World Clock

Access to and from the world clock is influenced by the fact that it is a very simple application that is generally considered an end point on the phone. Most users accessing the world clock are generally not doing it to enhance a data experience but to perform a specific function.

ID / Requirement Name / Description / Supported
A, B, C / Implement
In Phase:
1, 2, 3
WCACCESS1 / World Clock Access Point / The World Clock MUST be accessible through the following:
·  Main menu (through an icon)
·  Tools Menu (through and icon)
·  Tools Menu (through a text menu item)
·  Set as a hot key to access from idle screen
·  Set as a favorite applications list / A / 1
WCACCESS2 / World Clock Exit / The World Clock MUST be exited via:
·  User Depresses End Key to return to idle screen (data is saved)
·  User Depresses “C” key to incrementally exit from application to the next hierarchical level on the handset. / A / 1
WCACCESS4 / Link to Clock Settings / The World Clock SHOULD provide a link to the date and time settings area of the handset. / B / 2
WCACCESS5 / Return To World Clock / When the user is exiting the date and time settings area of the handset, they MAY return to the World Clock via a direct link or back out using the “C” key. NOTE: It is important to note that COMPANY XYZ might not be implementing the clock settings portion of the handset so enacting this functionality will be dependant upon that application. / C / 3

1.1.2  World Clock Functionality

ID / Requirement Name / Description / Supported
A, B, C / Implement
In Phase:
1, 2, 3
WORLD3 / Carrier Provisioned Images / The carrier MAY have the ability to replace specific images of the world clock so that they can have the application reflect seasonal changes via the OTA capabilities on the handset. / C / 3
WORLD4 / World database / The world clock MUST contain a database of cities, coordinates (which correspond to the map), time differentials and relative distances. / A / 1
WORLD5 / OEM Default City / The OEM MUST have the ability to select the default city (starting point) within the World Clock. This accounts for the city the first time you use the application. / A / 1
WORLD6 / Carrier Default City / The carrier SHOULD have the ability to set the default city (starting point) within the World Clock via OTA provisioning. / B / 2
WORLD7 / User Default City / The user MUST have the ability to select the default city (starting point) within the World Clock / A / 1
WORLD8 / Date Line / The World Clock MUST have the ability to overlay a secondary semi-transparent image over the map to signify the date line. This must follow the same provisioning standards as are implemented for the map images. / A / 1
WORLD9 / Date Line Motion Path / The World Clock MUST have the ability to set the secondary semi-transparent image on a motion path. This must be supported to accurately illustrate the movement of the date line. / A / 1
WORLD10 / Disable Date Line / The user SHOULD have the ability to disable the secondary semi-transparent image (Dateline) if they so choose. / B / 2
WORLD11 / City Display / The World Clock MUST always display one city along with the time and date. / A / 1
WORLD12 / Current Time Display / The World Clock SHOULD have a user controlled option to display the current time and date in the local that the phone is in. Note: Most handsets are provisioned with the current time and date off of the network. However, if this data is not present, this feature must be automatically disabled. / B / 2
WORLD13 / Current City Highlight / The World Clock MUST show the primary world map (the one displayed) and the secondary semi-transparent image (Dateline – if enabled) with a cursor, crosshair, or icon pointed at the currently selected city. COMPANY XYZ will provide a default set of icons (preferably animated). / A / 1
WORLD14 / City Highlight Icons By OEM / The OEM MUST have the ability to replace the COMPANY XYZ provided icon set with their own. / A / 1
WORLD15 / City Highlight Icons By Carrier / The Carrier MAY have the ability to replace the COMPANY XYZ or OEM provided icon set with their own via OTA. / C / 3
WORLD16 / Starting Point / The default starting position MUST always be a local city within the current time zone. NOTE: If this is a available from the network. Otherwise, it will be regionally determined. / A / 1
WORLD17 / Cursor Options / The World Clock SHOULD provide a visual cue to indicate that it is possible to move the cursor or crosshair to select a new city. This could be as simple as providing a right arrow icon on the right side of the screen and a left arrow icon on the left side of the screen. / B / 2
WORLD20 / Navigation / The World Clock MUST support the use of the handsets navigation keys to move the cursor across the map in order to select a different city. NOTE: This application must support both left right arrows as well as four way rockers with an OK key. / A / 1
WORLD21 / City List / The user SHOULD have the ability to display the list of available cities as a text based list (with city name, time and date). / B / 2
WORLD22 / City List Sort / The text based city list MUST be sorted in alphabetical order. / A / 1
WORLD23 / City List Behavior / The text based city list MUST behave the same as current menu scrolling. / A / 1
WORLD24 / City List Search / The user SHOULD have the ability to enter a city name into a text field and have the city name auto complete within the field. NOTE: This feature will be tied to FL 2.1. / B / 2
WORLD25 / City Selection / Selecting a city from the list MUST return the user to the map portion of the application with the city highlighted and the proper data presented. / A / 1
WORLD26 / Persistent City / The last selected city MUST be displayed when the user returns to the application after leaving. NOTE: Marketing and sales should highlight that this feature has been practically implemented in an application. This feature is new to FL 2.0 / A / 1
WORLD27 / Daylight Savings Time / The World Clock SHOULD provide an option to toggle Daylight Saving Time (DST) for the currently selected city. A clear visual indication of whether DST is active should be shown on screen next to the display of the currently selected city’s time and date. / B / 2
WORLD28 / Database / The World Clock Database MUST maintain the following information:
·  City Name
·  Map Coordinates
·  Longitude and Latitude
·  Country
·  Relative distance information
·  Local dialing codes (country code and local city)
·  Picture Information (Optional)
Audio Clip (Optional) / A / 1