Revision as of 04:04, 2 August 2011 (view source) Texrat (Talk | contribs) (→Structure) ← Older edit		Revision as of 04:12, 2 August 2011 (view source) Texrat (Talk | contribs) (→Structure) Newer edit →
Line 16:		Line 16:
	=== Platforms ===		=== Platforms ===
		+
		+	This table lists the platforms supported by MeeGo.  The values are editable only by program coordinators.
	Definitions:		Definitions:
Line 41:		Line 43:
	=== Devices ===		=== Devices ===
		+
		+	This table lists Devices made available by Providers.  Platform values are linked in and associated to specific devices by the data entrant.
	Definitions:		Definitions:
Line 55:		Line 59:
	=== Providers ===		=== Providers ===
		+
		+	List of Device Providers participating in the program.
	Definitions:		Definitions:
Line 65:		Line 71:
	:: PrimaryContactEmail		:: PrimaryContactEmail
	:: PrimaryContactPhone		:: PrimaryContactPhone
-	:: CustomForm	+	:: CustomForm (Binary Y/N), ''Does the Provider require their own form for requests?''
-	:: CustomFormLink	+	:: CustomFormLink (Hyperlink), ''Link to Provider's custom form''
	=== Device-Provider Matrix ===		=== Device-Provider Matrix ===
		+
		+	This table establishes a matrix between Devices and Providers, since Devices can be offered by more than one Provider.  When applicants request a device, they will be presented with at least one Provider and multiple Provider choices if they are available.
	Definitions:		Definitions:
Line 84:		Line 92:
	=== Requestors ===		=== Requestors ===
		+
		+	Device applicants.
	Definitions:		Definitions:
Line 93:		Line 103:
	=== Requests ===		=== Requests ===
		+
		+	Applicant requests for devices.
	Definitions:		Definitions:
Line 114:		Line 126:
	=== Approvers ===		=== Approvers ===
		+
		+	Not yet defined
	Definitions:		Definitions:
Line 123:		Line 137:
	=== Allocations ===		=== Allocations ===
		+
		+	Devices that have been approved and allocated.
	Definitions:		Definitions:

---

Revision as of 04:12, 2 August 2011

This page will cover the design and documentation of the device program's setup, workflows, data model, forms and other aspects *in process*

Contents 1 Requirements 1.1 Setup 1.2 Workflow 1.3 Structure 1.3.1 Platforms 1.3.2 Devices 1.3.3 Providers 1.3.4 Device-Provider Matrix 1.3.5 Requestors 1.3.6 Requests 1.3.7 Approvers 1.3.8 Allocations 1.4 Forms

Requirements

Setup

Preliminary configuration. See Structure for pre-populated data.

Workflow

Typical process

Structure

The following tables describe suggested data structures. Where ever Values are shown, they are meant to be pre-populated.

Platforms

This table lists the platforms supported by MeeGo. The values are editable only by program coordinators.

Definitions:

Fields

ID (autonumber, Primary Key, required)

Name (Varchar, required), Platform name

Description (Text), Description of platform

Values:

Name

Netbook

Entry-level Desktop

Nettop

Tablet Computer

Mobile Computers/Handset

In-Vehicle Infotainment (IVI) System

Smart TV/Connected TV

IP TV Box

Development Device

Other Embedded System

Devices

This table lists Devices made available by Providers. Platform values are linked in and associated to specific devices by the data entrant.

Definitions:

Fields

ID (autonumber, Primary Key, required)

Creator_ID

Platform_ID (Foreign Key) Links to Platforms.ID

Name (Varchar, required), Device name

Model (Varchar)

Description (Text), Description of device

DateAdded (DateTime, required), automatic DateTime stamp

Providers

List of Device Providers participating in the program.

Definitions:

Fields

ID (autonumber, Primary Key, required)

CompanyName

PrimaryContactName

PrimaryContactEmail

PrimaryContactPhone

CustomForm (Binary Y/N), Does the Provider require their own form for requests?

CustomFormLink (Hyperlink), Link to Provider's custom form

Device-Provider Matrix

This table establishes a matrix between Devices and Providers, since Devices can be offered by more than one Provider. When applicants request a device, they will be presented with at least one Provider and multiple Provider choices if they are available.

Definitions:

Fields

ID (autonumber, Primary Key, required)

Device_ID

Nature

DiscountPercentage

AllowedDuration

InventoryQuantity

Terms

DateAdded

Requestors

Device applicants.

Definitions:

Fields

ID (autonumber, Primary Key, required)

Requests

Applicant requests for devices.

Definitions:

Fields

ID (autonumber, Primary Key, required)

Requestor_ID

DeviceProviderMatrix_ID

DateOpened

DesiredQuantity

TeamName

ProjectName

ProjectURL

PrimaryUse

DevicePlans

ProviderSpecificNotes

RequestStatus

Remarks

DateUpdatedPlatforms

Approvers

Not yet defined

Definitions:

Fields

ID (autonumber, Primary Key, required)

Allocations

Devices that have been approved and allocated.

Definitions:

Fields

ID (autonumber, Primary Key, required)

Request_ID

DeviceSN

DateAssigned

AllocatedQuantity

DateDue

Notes

DateClosed

Forms

(this needs updating)

• (drop down) Select device provider
• (drop down) Select device (add any available devices to drop down)
• (drop down) Select primary use (fields: platform / project development, app development, design, localization, peripherals, other)
• (text box) Project Name (if applicable)
• (text box) Project URL (this is a requirement for TI; can be link to a forum thread, et al)
• (text box) Describe in more detail your plans for the device.
• (text box) Describe your past (if any) contributions to the MeeGo, Maemo and/or Moblin project(s).
• (drop down) MeeGo member name [] meego.com [] forum.meego.com
• (text field) Full Name
• (text field) Shipping Location (organization name or use 'home' if shipping to a residential address)
• (text field) Shipping Address
• (text field) Phone Number
• (text field) Email Address
• [] I confirm that I asked my employer for a device (if applicable) and have been turned down.
• [] I agree to use the device for the purpose stated above.
• [] I agree to blog/tweet/present about my experience with the device.
• [] I confirm that I have met all other requirements to receive this device.