Browse Prior Art Database

[IM] 3D representation of screen-transition diagram

IP.com Disclosure Number: IPCOM000035561D
Original Publication Date: 2005-Jan-25
Included in the Prior Art Database: 2005-Jan-25
Document File: 2 page(s) / 28K

Publishing Venue

IBM

Abstract

Disclosed is a system for assisting creation of screen-transition-diagrams. We tried to develop "3D screen-transition-diagram" method for complicated screen-transition-diagrams of GUI. This method separates button-triggered-transitions (button-transitions), and state-transitions, such as the car run/stop. Button-transitions are expressed as horizontal connections on a diagram. On the other hand, state-transitions are expressed as vertical connections between diagrams.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 55% of the total text.

Page 1 of 2

[IM] 3D representation of screen -transition diagram

In developing GUI of a car-navigation-system, and a mobile-phone, and so on, there are several problems. It is because these systems have many types of transition-triggers, which are hardware-buttons, GUI-buttons, state-changes, and so on.

Transitions by hardware-buttons and GUI buttons (button-transitions) are led by user's UI operation; for example, pushing, clicking, and so on.

On the other hand, transitions by state-changes (state-transitions) are not led by user's UI operation, but mechanical state-changes; for example, the state change between run/stop has an influence on screen-transitions and screen-appearances.

If these two types of transitions are drawn in the same diagram, the number of screen-transitions is increased, and the diagram becomes complicated. (Figure 1)

If button-transitions and state-transitions are completely separated, it is difficult to understand whole transitions and their structures.

A complicated screen-transition-diagram. (Both run and stop state are displayed in one screen-transition-diagram)

2.[S]

3.[S]

5.[S]

8.[S]

[R]: screen of run state

[S]: screen of stop state

[RS]: screen of both states.

2.[R]

3.[R]

5.[R]

7.[R]

8.[R]

6.[S]

9.[S]

4.[RS]

10.[S]

6.[R]

9.[R]

15.[S]

1.[RS]

12.[S]

16.[S]

Transitions only for run state and only for stop state are existing.

10.[R]

12.[R]

16.[R]

11.[S]

18.[RS]

17.[S]

13.[RS]

14.[RS]

11.[R]

17.[R]

These connections are hard to be understood.

Confusing connections are existing.

(Figure 1)

To solve these problems, we tried to develop "3D screen-transition-diagram" method.

Screens are displayed as squares. Transitions are displayed as connections between


1.


2.

screen-squares.

Button-transitions by GUI buttons, widgets, and external buttons (for...