DSDP/MTJ/Override Device Feature

Back to main DSDP-MTJ Use Cases

Short description:
A Java developer overrides an existing device feature in the database with another feature.

Priority:

Owner:

Status: Proposed, Outlined

Proposed:|Accepted: date_here

Identified|Described|Outlined|Detailed

Community Review: review_date_here

---

Use Case Specification: Override phone feature with another feature in device database

1. Brief Description

A Java developer overrides an existing device feature in the database with another feature. Java developer opens up the database editing tools. Java developer chooses the feature to be overridden. Java developer chooses the feature which overrides the other feature in compilation and compilation preprocessing.

E.g. real full screen parameters overriding the parameters devices give out themselves

2. Flow of events

2.1 Basic Flow

B1: The user opens up device database editing tools.

B2: The user chooses to override a feature.

B3: The system presents options to choose the feature to be :overridden.

B4: The user chooses the feature.

B5: The system presents options to choose the feature which overrides the other feature.

B6: The user chooses the overriding feature.

B7: The system marks the overridden feature.

2.2 Alternative flows

3. Special Requirements

4. Preconditions

4.1 Device database exists
There exists a device database in which overriding with features can be made.

4.2 Information for justifying overriding is available
The user has some new information which justifies that a feature is overridden with another feature. The information can be acquired e.g. during current or previously done development project.

4.3 The features are of the same value category
The features are of the same value category – they can have similar values. This is needed in order to avoid errors in compilation or during the use of the solution.

5. Post Conditions

5.1 A feature has been overridden with another feature
The system overrides a device feature with another feature in development use. The system replaces the value of the feature with the value of the overriding feature if there is an overriding value available for a certain device. If there is not overriding value available for a certain device the system uses the normal value of the feature.

5.2 Overridden feature is distinguished
The system marks the overridden feature. The user sees the state of the feature immediately. By seeing the state of the feature the user can make assumptions about the needed number of software and graphic variations.

5.3 Overriding can be used in compilation and when running the solution
The overriding of the feature can be used in compilation, in compilation preprocessing and when running the solution. The value of the overriding feature is used instead of the value of the overridden feature.

5.4 Database gives better support for sales process
The device database with the distinguished overriding gives better support for the sales process. The user can make assumptions about the number of software and e.g. graphics variations and the amount of work.

6. Extension Points

---

Comments:

Back to main DSDP-MTJ Use Cases