DSDP/MTJ/Add New Device Feature

Back to main DSDP-MTJ Use Cases

Short description:

A Java developer adds into the device database information about a new device feature which is not available in the database.

Priority:

Owner:

Status: Proposed, Outlined

Proposed:|Accepted: date_here

Identified|Described|Outlined|Detailed

Community Review: review_date_here

---

Use Case Specification: Add new device feature into device database

1. Brief Description

A Java developer adds into the device database information about a new device feature which is not available in the database. Java developer opens up the database editing tools and adds a new device defining feature into the database. Java developer gives the feature a name, description and a value category.

E.g. in which phones can several players be processed at the same using Java. E.g. real full screen parameters overriding the parameters phones give

2. Flow of events

Basic Flow

B1: The user opens up device database editing tools.

B2: The user chooses to add a new defining feature into the database.

B3: The system asks for a name, description and value category for the new feature.

B4: The user types in the name, the description and chooses the value category for the feature.

B5: The system creates the new feature with the given name, description and value category.

B6: The system marks that the new feature has been created by the user and remembers when it has been created.

3. Alternative flows

Alternative flow 1: Override device feature with another feature.

Alternative flow 2: Delete device feature.

Alternative flow 3: Edit device feature.

4. Preconditions

4.1 Device database exists
There exists a device database into which new defining features can be added.

New information is available

The user needs to have some new information to be added into the device database. The information can be acquired during current or previously done development project.

5. Post Conditions

5.1 New feature has been created
The system has included a new feature into the device database.

5.2 Feature is distinguished from previous features
The system remembers when the feature has been created and by whom. When updates to the public device database are released, the new public information can be compared with the user generated information. Based on the comparison the database can adjusted to its fullest and most up-to-date form.

5.3 Feature can be used in compilation and when running the solution
The new feature can be used in compilation, in compilation preprocessing for creating different builds from the same source code and when running the solution.

5.4 Database gives better support for sales process
The device database with the new feature gives better support for the sales process. The people negotiating with the clients can give more up-to-date information about the possibilities and options in creating a solution.

6. Extension Points

---

Comments:

Back to main DSDP-MTJ Use Cases