WO2009113167A1 - User interface verification system, verification controller, and method of verification - Google Patents

Abstract

A UI verification system includes a verification controller having a plurality of connectors having communication lines for communicating with a plurality of detachably mounted UI units, buses for coupling the respective communication lines, a UI device having a communication control means for controlling the communication between the respective UI units and the verification controller, a unit table for storing an address of each UI unit and type information in a correspondence relationship, a scene setting table for storing the type information for triggering the change of a display state of a scene image in conjunction with the scene image, a receiving means for receiving operation information of the operated UI unit from the UI device, an acquisition means for acquiring the type information corresponding to the address of the UI unit included in the operation information from the unit table, and an image control means for controlling the scene image depending on set contents in the scene setting table when the acquired type information is set in the scene setting table as the trigger information for changing the display state of the scene image currently displayed.

Description

[Name of invention determined by ISA based on Rule 37.2] User interface verification system, verification control device, and verification method

The present invention relates to a technique for verifying a hardware user interface.

Currently, various electronic devices such as computers, mobile phones, and copiers are equipped with user interfaces (hereinafter simply referred to as UI). This UI is realized by operation units, input units such as trackballs, LED (Light Emitting Device), LCD (Liquid Crystal Display), output units such as speakers, and input / output units having input and output functions. The

Such a UI is an important factor that determines the usability of a product and affects user evaluation. Therefore, UI design is very important for product development, and its evaluation method has been reviewed. At the same time, securing developers with high UI design capabilities is an important issue for each company.

There is a prototyping method as a method for evaluating such UI design. In this method, a prototype incorporating the UI is produced, and usability is evaluated using the prototype.

Of the UIs, GUI (Graphical User Interface) is realized by software including various operation buttons and so on, so that it is relatively easy to change. Thereby, when the evaluation result of the UI design is bad, it is possible to relatively easily re-produce the prototype with the UI changed and perform further evaluation.

However, a UI realized by hardware such as a mobile phone or a remote controller (remote controller) of various electronic devices is not easy to re-produce a prototype with a modified UI even if it is a prototype. Absent.

A method for evaluating such a hardware UI is disclosed, for example, in Patent Document 1 below. Further, Patent Documents 2, 3 and 4 below disclose a method for making it possible to reconfigure a control panel component as a hardware UI.
JP 2005-275439 A Japanese Patent Laid-Open No. 5-216631 JP-A-2-307306 Japanese Patent Laid-Open No. 5-38010

However, in the above-described conventional technology, even though a UI can be evaluated for one electronic device, a UI designed for each electronic device for each electronic device cannot be verified. In addition, although a component (UI) to be arranged on the control panel can be reconfigurable, a component for another electronic device cannot be reconfigurable. Furthermore, it is not a technique for improving a user's UI design ability.

In view of such conventional problems, an object of the present invention is to provide a technique capable of verifying UI designs according to various electronic devices and improving user UI design capabilities.

Each aspect of the present invention employs the following configurations in order to solve the above-described problems. That is, according to the first aspect of the present invention, a UI device to which a plurality of UI units, each of which is a component of the UI and individually set with a unique address, and an operation of the UI unit attached to the UI device are operated. The present invention relates to a UI verification system having a verification control device that controls a scene screen according to the above. In the UI verification system according to the first aspect, the UI device removably supports each UI unit, and includes a plurality of connectors having communication lines for communicating with the mounted UI unit, and a plurality of connectors. And a communication control means for controlling communication with the plurality of UI units via the bus and communication with the verification control device, respectively, and the verification control device. Is a unit table that stores the address of each UI unit in association with the type information corresponding to the type of each UI unit, and the type information that triggers changing the display state of the scene screen. A scene setting table stored in association with the operation information including the address of the operated UI unit among the plurality of UI units. A receiving unit that receives from the UI device; an acquisition unit that acquires, from the unit table, type information corresponding to an address included in the operation information when the reception unit receives the operation information; and A screen for controlling the scene screen according to the setting contents of the scene setting table when the acquired type information is set in the scene setting table as trigger information for changing the display state of the currently displayed scene screen Control means.

Here, the UI unit is, for example, an input unit such as various operation buttons, an output unit such as an LCD, and an input / output unit.

In the first aspect, a UI to be verified is realized by mounting a plurality of UI units, each of which is a component of the UI and has a unique address set, on each connector of the UI device. . In the verification control apparatus, the addresses of a plurality of UI units constituting the UI to be verified are stored in the unit table in association with the type information corresponding to the type of each UI unit, and the display state is displayed according to the operation trigger of the UI unit. The type information corresponding to the UI unit regarding the scene screen to be changed is stored in the scene setting table as the trigger information of the scene screen.

In such a configuration, when the UI unit is operated, that is, when operation verification of the target UI is performed, operation information including the address of the operated UI unit is sequentially sent from the UI device to the verification control device. In the verification control device, when the operation information is received, the address included in the operation information is converted into the type information, and the scene screen is controlled according to the setting content of the scene setting table when the type information is acquired. .

Thus, according to the first aspect, the user can verify the operation of the UI realized on the UI device while referring to the scene screen along the setting information of the verification control device.

Furthermore, in the first aspect, each UI unit has a unique address, the communication lines of the respective connectors for mounting the UI unit are connected by buses, and the transmission source of the operation information is set as the transmission source. Since it can be specified by the address, even if the UI unit mounting position (connector position) is changed, there is no need to change the setting of the unit information and the scene setting table.

Therefore, according to the first aspect, it is possible to easily change the UI configuration, such as changing the arrangement of UI units.

Furthermore, in the first aspect, since the type information corresponding to the UI unit address is stored in the scene setting table in association with the scene screen, the UI unit address has to be changed or a new one has to be changed. Even if a UI unit is added, the scene screen is controlled as long as the setting of the unit table is changed.

Therefore, according to the first aspect, even if the UI configuration is significantly changed, the necessary setting action can be reduced. As described above, according to the UI verification system in the first aspect, the UI configuration can be changed freely and easily. Therefore, this system can be used for UI verification of various electronic devices. Furthermore, since it is easy to repeat the operation verification while changing the UI configuration, it can be used as an educational material for improving the design ability of the user, for example.

In the first aspect of the present invention, preferably, the communication control means of the UI device detects information on a connector in which each UI unit is mounted by detecting a connector in which the UI unit is mounted among a plurality of connectors. Each of which includes a collecting means for collecting, and the verification control apparatus obtains position information acquisition means for acquiring position information of a plurality of UI units based on connector information sent from the UI apparatus; A history recording unit that records operation histories of a plurality of UI units based on the received operation information, an operation history recorded by the history storage unit, and position information of each UI unit acquired by the position information acquisition unit Based on the calculation means for calculating the movement amount between each operation of the plurality of UI units, and the history recording means. Data generating means for generating evaluation data including the amount of movement between the calculated operation by by operation history and the calculating means, further configured to include.

According to such a configuration, the evaluation data including the operation history at the time of the operation verification and the movement amount between each operation is generated together with the execution of the operation verification, so that the operability evaluation of the UI can be performed together. It becomes possible. If this evaluation data can be provided to the user, the user's UI design ability can be improved.

Furthermore, according to this configuration, even if the UI configuration is changed, the connector information of the UI unit after the change can be automatically collected, and the connector information can be used for the operability evaluation after the change. it can.

As another aspect of the present invention, it may be a UI device, a verification control device, or a single unit of a UI unit constituting the UI verification system, or a method or program for causing each computer to realize any of the above functions. It may also be a storage medium in which such a program is recorded so as to be readable by a computer.

According to the aspect of the present invention, it is possible to verify UI designs corresponding to various electronic devices, and it is possible to provide a technique for improving a user's UI design ability.

FIG. 1 is a diagram illustrating a system configuration example of a UI verification system in the first embodiment. FIG. 2 is a block diagram showing a schematic hardware configuration of the UI unit and UI panel in the first embodiment. FIG. 3 is a diagram illustrating a format example of a data signal sent from the UI panel to the verification control apparatus. FIG. 4 is a diagram showing a format example of a data signal sent from the verification control apparatus to the UI panel. FIG. 5 is a diagram showing an outline of a functional configuration of the verification control apparatus in the first embodiment. FIG. 6 is a diagram showing a configuration example of the project setting file in the first embodiment. FIG. 7 is a diagram illustrating an example of the screen configuration of the operation verification application. FIG. 8 shows an example of the start screen. FIG. 9 is a diagram showing a project setting screen in the first embodiment. FIG. 10 is a diagram showing an example of the scene setting screen. FIG. 11 is a diagram showing an example of a link procedure screen. FIG. 12 is a diagram showing an example of a scene link preview screen. FIG. 13 is a diagram showing an example of the operation verification screen. FIG. 14 is a diagram showing a schematic device configuration of a UI panel in the second embodiment. FIG. 15 is a diagram showing a format example of position information data. FIG. 16 is a diagram illustrating an outline of a functional configuration of the verification control apparatus according to the second embodiment. FIG. 17 is a diagram showing a configuration example of a project setting file in the second embodiment. FIG. 18 is a diagram showing a configuration example of a project setting screen in the second embodiment. FIG. 19 is a diagram illustrating a configuration example of the operability evaluation screen (movement amount). FIG. 20 is a diagram illustrating a configuration example of the operability evaluation screen (time). FIG. 21 is a diagram illustrating a configuration example of the operability evaluation screen (speed). FIG. 22 is a diagram showing a configuration example of a project setting file in a modification of the second embodiment.

Explanation of symbols

1 interface 10 UI panel, 11 connector, 12 bus, 14 external interface, 15 CPU, 16 ROM, 17 RAM
20 Verification control device, 22 CPU, 23 External interface controller, 24 RAM, 25 HDD, 29 Display (display device)
30 UI unit, 31 address setting switch, 32 CPU, 33 connector 50 operation verification application, 51 project setting function unit, 52 operation verification function unit, 53 project setting file, 54 scene image file 62 project setting screen, 63 scene setting screen, 67 Operation Verification Screen 141 Transmission Selection Circuit, 142 Reception Selection Circuit, 145 Transmission Line, 146 Transmission Selection Information Line, 147 Reception Line, 148 Reception Selection Information Line 161 Location Information Collection Function Unit, 162 Operability Evaluation Function Unit, 163 Evaluation Results File 190 usability evaluation screen

Hereinafter, a UI verification system according to an embodiment of the present invention will be described with reference to the drawings. The configuration of each embodiment shown below is an example, and the present invention is not limited to the configuration of each embodiment shown below.

[First embodiment]
Hereinafter, a UI verification system as a first embodiment of the present invention will be described with reference to the drawings.

〔System configuration〕
First, the system configuration of the UI verification system in the first embodiment will be described with reference to FIG. FIG. 1 is a diagram illustrating a system configuration example of a UI verification system according to the first embodiment.

As shown in FIG. 1, the UI verification system in the first embodiment includes a verification control device 20, a UI panel 10 (corresponding to a UI device), a UI unit 30, and the like.

The UI unit 30 is a component of the UI realized by hardware. The UI unit 30 includes an output unit such as an LED, an LCD, and a speaker, an input unit such as an operation button and a trackball, and an input / output unit having an input function and an output function. In the example of FIG. 1, the UI unit 30 (# 1) is an LCD as an output unit, and the UI units 30 (# 2) to (# 9) are various operation buttons of the input unit.

Each UI unit 30 is detachably attached to a plurality of connectors 11 provided on the UI panel 10. The user prepares the required number of UI units 30 of a predetermined type of input unit, output unit, and input / output unit according to the UI to be verified. The user implements a UI to be verified on the UI panel 10 by attaching each UI unit 30 to the connector 11 at a predetermined position.

The UI panel 10 that realizes the UI to be verified in this way is connected to the verification control device 20 by the interface 1. The interface 1 is realized as a serial interface such as USB (Universal Serial Bus) and RS-232C (Recommended Standard 232 Version C). In addition, since this invention does not limit the realization method of this interface 1, this interface 1 may be implement | achieved by the radio | wireless communication using infrared rays, electromagnetic waves, etc.

The UI panel 10 sends the operation state of each UI unit 30 attached to the connector 11 to the verification control device 20 via the interface 1. Further, the UI panel 10 receives a data signal transmitted from the verification control device 20 via the interface 1.

The verification control device 20 is attached to the display 29 or the connector 11 on the UI panel 10 according to the operation state of the UI realized on the UI panel 10 by communicating with the UI panel 10 via the interface 1. The scene screen displayed on the UI unit 30 (# 1) of the LCD is controlled. The user verifies the UI realized on the UI panel while viewing the scene screen controlled by the verification control device 20. The UI verification used here includes not only that the user actually operates the UI, but also that the user sensuously confirms the usability of the UI, the degree of erroneous operation prevention, and the like.

〔Device configuration〕
Hereinafter, the configuration of each of the above-described devices constituting the UI verification system in the first embodiment will be described with reference to FIGS. FIG. 2 is a block diagram illustrating a schematic hardware configuration of the UI unit 30 and the UI panel 20 in the first embodiment.

<UI unit>
The UI unit 30 includes, as shown in FIG. 2, a CPU (Central Processing Unit) 32, an address setting switch 31, a connector 33, and the like, as well as a UI hardware configuration that is each component of the hardware UI. The UI hardware is, for example, a push button switch, a plurality of push button switches, a display lamp, an LED, an LCD display panel, or the like.

The address setting switch 31 sets a unique address for identifying each UI unit 30. The address setting switch 31 is realized by a dip switch, for example.

The connector 33 is mounted on the UI panel 20 by coupling with the connector 11 of the UI panel 10. The connector 33 has a communication terminal and a power supply terminal, and is combined with the connector 11 so that these contact the communication terminal and the power supply terminal of the connector 11 of the UI panel 10. Thereby, the connector 33 supplies the power supplied from the UI panel 10 to the UI unit 30 via the power supply terminal. Further, the connector 33 realizes communication between the UI panel 10 and the UI unit 30 via the communication terminal.

The CPU 32 reads out and executes a control program or the like stored in a ROM (Read Only Memory) and a RAM (Random Access Memory) (both not shown), thereby using its UI while using the address setting switch 31 and the connector 33. The following functions corresponding to the type of unit 30 are realized. Hereinafter, each function realized by the CPU 32 will be described as a function of the UI unit 30.

The UI unit 30 realizes a function as a hardware UI corresponding to the type of the UI unit 30. The function as the hardware UI is a function corresponding to the type of the UI unit 30. At this time, the CPU 32 reads the address information set in the address setting switch 31 and recognizes it as its own device number.

The UI unit 30 further has a communication function. When the own UI unit 30 is an input unit or an input / output unit, the UI unit 30 detects an operation state of the own UI unit 30 and detects the operation state of the own device. It is transmitted to the UI panel 10 together with the number.

The UI unit 30 receives a data signal sent from the UI panel 10 when the UI unit 30 is an output unit or an input / output unit. At this time, the UI unit 30 acquires only the data signal in which the device number included in the data signal sent from the UI panel 10 matches its own device number. The UI unit 30 controls UI hardware according to the received data signal. For example, when the UI unit 30 is a display unit such as an LCD, the UI unit 30 reads a predetermined scene screen stored in a ROM (not shown) or the like according to a data signal from the UI panel. Then, an image obtained by combining the data included in the data signal and the scene screen is displayed on the display unit.

<UI panel>
As shown in FIG. 2, the UI panel 10 includes a plurality of connectors 11 to which the above-described UI unit 30 is attached, an external interface 14, a CPU 15, a ROM 16, a RAM 17, and the like.

The connector 11 supports the UI unit 30 by being coupled with the connector 33 of the UI unit 30 as described above. The connector 11 supplies power supplied from the UI panel 10 to the UI unit 30 via the power supply terminal.

The connector 11 realizes communication with the UI unit 30 via the communication terminal. Each communication line connected to each communication terminal of the plurality of connectors 11 is connected to the bus 12. In other words, each UI unit 30 is connected by this bus 12.

The CPU 15 is connected to the bus 12, receives a data signal sent from each UI unit 30 via the bus 12, and sends a data signal to be sent to a predetermined UI unit 30. The CPU 15 is also connected to the external interface 14, receives a data signal sent from the verification control device 20 via the external interface 14, and sends a data signal to be sent to the verification control device 20.

The CPU 15 implements the following functions by reading out and executing control programs stored in the ROM 16 and RAM 17 while using the connector 11 and the external interface 14 as described above. Hereinafter, each function realized by the CPU 15 will be described as a function of the UI panel 10.

The UI panel 10 receives data signals sent from the UI units 30 in response to operations of the UI units 30 via the bus 12, and transmits the data signals to the verification control device 20 via the external interface 14, respectively. To do.

FIG. 3 is a diagram showing a format example of a data signal sent from the UI panel 10 to the verification control device 20. The data signal in the example of FIG. 3 includes a command field, a message length field, a device number field, a bit position field, and an operation field. An input command indicating that this signal (telegram) is a notification of an input operation of the UI unit 30 is set in the command field. In the message length field, the length (number of bytes) from the device number field to the operation field in this data signal is set. In the device number field, the device number of the UI unit 30 that is the transmission source of the data signal is set. In the bit position field, data indicating a bit position where an input change has occurred by the operation of the UI unit 30 is set. Data indicating the type of input operation of the UI unit 30 (for example, 1 = ON, 2 = OFF, 3 = long press ON, etc.) is set in the operation field. Hereinafter, the data signal transmitted from the UI panel 10 to the verification control device 20 shown in FIG. 3 is also referred to as operation data.

Conversely, the UI panel 10 receives the data signal sent from the verification control device 20 via the external interface 14 and sends this data signal to the bus 12. The data signal in this case is a signal to be sent to the UI unit 30 of the output unit.

FIG. 4 is a diagram showing a format example of a data signal sent from the verification control device 20 to the UI panel 10. The data signal in the example of FIG. 4 includes a display device number field, a message length field, a command field, and a parameter field (# 1 to #N). In the display device number field, the device number of the UI unit 30 to which the data signal is sent, that is, the UI unit 30 that performs output is set. In the message length field, the length (number of bytes) of the data signal from the command field to the final parameter field is set. In the command field, an output command for specifying an output operation in the UI unit 30 is set. This output command is data indicating, for example, lighting, extinguishing, screen clearing, text display, screen display, and the like. The parameter field is provided so as to satisfy the number of parameters determined according to the type of command set in the command field, and data determined according to the type of command is set. Examples of this data include a coordinate position, a color, display text, an identification number indicating a display image, and the like. Hereinafter, the data signal transmitted from the verification control device 20 to the UI panel 10 shown in FIG. 4 is also referred to as display data.

The UI panel 10 may relay the format of the data signal (operation data and display data) shown in FIGS. 3 and 4 as it is between the UI unit 30 and the verification control device 20, or the UI unit 30. A different format may be used for the format of the data signal sent to the network.

<Verification control device>
As shown in FIG. 1, the verification control apparatus 20 in the first embodiment includes a CPU 22, an external interface controller 23, a RAM 24, a hard disk drive (hereinafter referred to as HDD) 25, an operation input controller 27, a video, as shown in FIG. A main body 21 having a controller 28 and the like, an operation device (not shown) such as a keyboard and a mouse, a display device such as a display 29, and the like. In the main body 21, each of the above devices is connected by a bus 26. The verification control apparatus 20 may be realized by a general-purpose computer such as a personal computer having such a hardware configuration, or may be realized by a dedicated computer. The present invention does not limit the hardware configuration of the verification control device 20.

The external interface controller 23 is connected to the interface 1 and controls communication on the interface 1. Specifically, operation data sent from the UI panel 10 is received, and display data is sent to the UI panel 10. The video controller 28 is connected to a display device such as a display 29 and performs display control of the display 29. The operation input controller 27 is connected to an operation device (not shown) such as a mouse and controls input from these operation devices.

The CPU 22 implements a software function group as shown in FIG. 5 by reading and executing a program stored in the HDD 25, ROM, or the like. FIG. 5 is a block diagram showing an outline of a functional configuration of the verification control apparatus 20 in the first embodiment.

5 includes a general OS function for controlling hardware such as the external interface controller 23, the video controller 28, the operation input controller 27, and the HDD 25 described above. An operation verification application 50 is executed on the OS 59. The operation verification application 50 may be recorded on a recording medium such as a CD-ROM and installed in a general-purpose computer, or may be downloaded from another server computer to the computer and executed. Good.

The operation verification application 50 includes a project setting function unit 51, an operation verification function unit 52, a project setting file 53, a scene image file 54, and the like. A predetermined operation is performed according to the operation state of the UI unit 30 mounted on the UI panel 10. By controlling the scene screen, the user is allowed to verify the operation of the UI realized on the UI panel 10. Each component constituting the operation verification application 50 is realized as a software component (see [Others]).

The operation verification application 50 manages various settings for operation verification in units of projects. Accordingly, the user creates a project for each UI, and sets information for verifying each UI in each project. Thereafter, the user can select a predetermined project according to the UI to be verified and verify the operation.

The project setting function unit 51 manages setting information regarding a project, and stores setting data regarding a predetermined project input by the user in the project setting file 53. The project setting function unit 51 generates a project setting screen for allowing the user to set a project. Details of the project setting screen will be described later.

The project setting file 53 stores setting information related to the project in units of projects. FIG. 6 is a diagram showing a configuration example of the project setting file in the first embodiment. As shown in FIG. 6, the project setting file 53 stores the project name, memo, project ID, top page ID, display format, number of registered scenes, display unit setting, number of display lines, UI unit information, scene information, and the like. .

In the project ID field, an identification number for identifying the project is set. In the top page ID field, a scene ID that is first displayed on the display unit when the project is executed is displayed. In the display format field, whether a scene screen for operation verification is displayed on a display unit of the UI unit 30 or displayed on a display device (display 29 or the like) connected to the verification control device 20 is displayed. Information is set. When information for displaying on the display unit is set in the display format field, the device number of the display unit is set in the display unit setting field. In the display line number field, the number of display lines of the display device selected in the display format is set. The number of registered scene screens is set in the registered scene number field.

In the UI unit information field, information on each UI unit 30 used in the operation verification target UI is stored. In the example of FIG. 6, 22 UI unit information fields are provided, but the present invention is not limited to this number. In the UI unit information field, a device number and a logical ID related to each UI unit 30 are set. The device number is the address of the UI unit 30 set by the address setting switch 31 of the UI unit 30 as described above. The logical ID is information for identifying each UI unit 30 by the operation verification application 50, and may be a logical identification number or an identification character string indicating the type of the UI unit. .

In the scene information field, information about each scene screen controlled according to the operation of the UI unit 30 mounted on the UI panel 10 is stored. In the example of FIG. 6, 300 scene information fields are provided, but the present invention is not limited to this number. In the scene information field, for each scene screen, scene ID, scene name, text display, scene background, scene background color, scene image file name, text character color, number of linked list items, scroll type, linked list information, control information Etc. are stored.

The scene screen identification number is set in the scene ID field. Information about whether or not to display the scene screen as text is set in the text display field. Information on whether the background of the scene screen is a single color or an image is set in the scene background field. In the scene background color field, when information indicating a single color is set in the scene background field, background color information of the scene screen is set. In the scene image file name field, when information indicating an image is set in the scene background field, an image file name used for the background of the scene screen is set. In the text character color field, when information indicating text display is set in the text display field, the character color information of the text is set.

The number of links displayed on the scene screen is set in the link list item number field. This link is reference information that links the scene screen to another scene screen to be transitioned like a hyperlink in hypertext. The number of links registered in a link list information field described later is set in the link list item number field. In the scroll type field, a stop type or a ring type is set. The stop type is a scroll type that stops when the focus moves to the last line (bottom line) of the line displayed on the scene screen. The ring type is the highest level after the focus moves to the last line. This means a scrolling format that moves to the line again and moves the focus.

In the link list information field, information related to each link displayed on the scene screen is set. In the example of FIG. 6, 40 link list information fields are provided, but the present invention does not limit the number of link lists. The link list information field stores a link destination scene ID, a corresponding operation key number, a next scene display start position, a next scene cursor position, and the like. In the link destination scene ID field, the scene ID of the destination scene screen that is transitioned from the scene screen when the link is selected is set. In the corresponding operation key number field, the logical ID of the target UI unit 30 serving as an event for directly shifting to the linked scene screen without setting the link displayed on the scene screen is set. . In the next scene display start position field, data indicating a position at which display of the scene screen is started when the scene screen is moved to the scene screen indicated by the link destination scene ID is set. In the next scene cursor position field, a line number indicating a focus position at the time of display when set to the scene screen indicated by the link destination scene ID is set.

In the control information field, an up key number and a down key number in which the logical ID of the target UI unit 30 serving as an event for moving the focus line of the scene screen is set, and an event for selecting the focus line The key number at the time of determination in which the logical ID of the target UI unit 30 is set is stored.

The scene image file 54 stores a file group of scene images set in the scene image file name field of the project setting file 53.

The operation verification function unit 52 performs display control of the scene screen in order to cause the user to verify the operation of the UI actually implemented on the UI panel 10 based on the project information set as described above.

Specifically, the operation verification function unit 52 monitors operation data (see FIG. 3) received via the external interface controller 23. When this operation data is received, the operation verification function unit 52 extracts the logical ID corresponding to the device number of this operation data from the currently selected project information in the project setting file 53.

Furthermore, the operation verification function unit 52 recognizes the currently displayed scene screen (hereinafter also referred to as the current scene screen) and its display state (focus line, etc.). The operation verification function unit 52 extracts information on the current scene screen (information stored in the scene information field) from the project setting file 53 based on the scene ID. The operation verification function unit 52 determines whether or not the extracted scene screen information includes data having the operation of the logical ID as an event, and if included, the scene screen according to the data. Control the display of.

For example, when the received logical ID is set in the upward movement key number field of the control information field, the operation verification function unit 52 controls the focus line to move up one line from the current position. If the received logical ID is set in the key number field at the time of determination in the control information field, the operation verification function unit 52 controls to shift to the scene screen linked to the focus row. In addition, when the received logical ID is set in the corresponding operation key number field of the link list information field, the operation verification function unit 52 shifts to the scene screen indicated by the link destination scene ID of the link list information field. Control to do.

The operation verification function unit 52 displays the changed scene screen on the display 29 via the video controller 28 when the display format of the currently selected project information indicates the display 29 in the display control of the scene screen. To be controlled. If the display format of the currently selected project information indicates the display unit of the UI unit 30, the operation verification function unit 52 displays the display data in which the device number set in the display unit setting field is set (see FIG. 4) and transmits this display data to the UI panel 10 via the external interface controller 23. As a result, the scene screen displayed on the display unit mounted on the UI panel 10 changes.

When a scene screen is displayed on the display unit of the UI unit 30 and a scene image file is set as the scene screen, the set scene image file is stored in advance in the flash memory of the UI unit 30 or the like. Need to be. In this case, command data indicating image display is set in the command field of the display data in FIG. 4, and the scene image file name and the like are set in the parameter field. Thus, the display data is created based on the data stored in the project setting file 53.

[Operation example]
Hereinafter, the operation of the UI verification system in the first embodiment will be described.

In the UI verification system in the first embodiment, when starting operation verification, first, a target UI is realized on the UI panel 10. That is, a predetermined type of UI unit 30 is prepared, and each UI unit 30 is attached to each connector 11 at a desired position on the UI panel 10.

Next, the user operates the verification control device 20 by using a keyboard, a pointing device or the like while referring to the display 29. By this operation, the operation verification application 50 is executed as described below, and the UI on the UI panel 10 is verified.

When the operation verification application 50 is executed, a predetermined screen is generated, and each screen is displayed on a display device (display 29) connected to the verification control device 20. FIG. 7 is a diagram illustrating an example of a screen configuration of the operation verification application 50. The operation of the operation verification application 50 will be described below along the screen configuration example of FIG.

When the operation verification application 50 is started, a start screen 61 is first displayed. FIG. 8 shows an example of the start screen. On the start screen 61, a project in which settings for verifying the UI realized on the UI panel 10 are stored is selected. When using the settings of a project (existing project) already stored in the project setting file 53, the "Open" button 72 is selected, and when setting a new project, the "New project" button 71 is selected. . Note that when the “end” button 73 is selected, the operation verification application 50 ends.

When a new project or an existing project is selected on the start screen 61, a project setting screen 62 is displayed. FIG. 9 is a diagram showing a project setting screen in the first embodiment. The user performs various settings for operation verification by operating the project setting screen 62. The project setting screen 62 displays the data stored in the project setting file 53 for the project selected on the start screen 61 (hereinafter also referred to as the current project), and the data set on this screen is displayed in the project setting file 53. Store. In the project setting screen 62, the setting unit 80 corresponds to the display format field, the setting unit 81 corresponds to the display unit setting field, the setting unit 82 corresponds to the memo field, and the setting unit 83 corresponds to the display line number field. The setting unit 84 corresponds to the top page ID, and the setting unit 85 corresponds to the UI unit information field. Among these, the unit type displayed on the setting unit 85 corresponds to the logical ID of the UI unit information field.

When common information related to the current project is set on the project setting screen 62, the scene screen is then set. The setting of the scene screen is performed by the scene setting screen 63 displayed when the scene setting button 87 on the project setting screen 62 is selected. FIG. 10 is a diagram illustrating an example of a scene setting screen. The scene setting screen 63 is displayed by switching only the project setting section 89 of the project setting screen shown in FIG. On the scene setting screen 63, settings are made for each scene screen used in the current project, and the set data is stored in the project setting file 53.

In the setting unit 90 of the scene setting screen 63, a scene screen to be used in the current project is registered, and a scene screen to be changed is selected from the registered scene screens. Specifically, a list of scene screens registered for the current project is displayed in the list display section 92. The list display section 92 is linked to the scene information field of the project setting file 53. The user operates the new scene addition button 91, the copy button 93, and the deletion button 94 to add or delete a scene screen from the current project. When the user registers a plurality of scene screens, the user selects a scene screen to be set in detail on the list display unit 92.

The setting information about the scene screen selected in the list display section 92 is displayed in the scene property display section 95. The scene property display unit 95 corresponds to one scene information field of the project setting file 53. Of the scene property display section 95, the setting section 96 is linked to the scene name field, the setting section 97 is linked to the text display field, the setting section 98 is linked to the text character color field, and the setting section 99 is the scene background field. Linking with the scene background color field and the scene image file name field, the setting unit 100 links with the scroll type field.

In the link registration setting unit 101, link information displayed on the selected scene screen is registered. The link information is reference information that links the scene screen to another scene screen to be transitioned, like a hyperlink in hypertext. The user selects one of the scene screens displayed in the scene list list in the setting unit 101, and selects the button 106, thereby registering the selected scene screen as a link. The user can delete and move the registered link by operating the other buttons 102, 103 and 104. When the edit button 105 is selected, a link procedure screen 64 is displayed. The link procedure screen 64 will be described later.

The setting unit 110 is linked to the control information field of the project setting file 53, the combo box 111 is the up key key number field in the field, the combo box 112 is the down key number field in the field, and the combo box 113 is Links to the key number field when determined in that field. What is set in these combo boxes is a logical ID corresponding to the target UI unit 30.

The state of the scene screen set in this way is displayed on the image preview unit 115 when the preview button 116 is selected. The user can change the setting information on the scene screen while viewing this display. Finally, when the setting button 119 is selected, information on the scene screen set on the screen is stored in the project setting file 53.

FIG. 11 is a diagram showing an example of a link procedure screen. The link procedure screen 64 is a screen for setting information regarding the link selected in the link list in the link registration setting unit 101 of the scene setting screen 63, and is linked to one link list information field of the project setting file 53. The combo box 121 of the link procedure screen 64 is linked to the corresponding action key number field, the combo box 122 is linked to the next scene display start position field, and the combo box 123 is linked to the next scene cursor position.

FIG. 12 is a diagram showing an example of the scene link preview screen. The scene link preview screen 66 displays a scene screen registered for the current project in a tree view so that the link state is shown. The scene link preview screen 66 is always displayed, and the user may set the scene screen while viewing this screen.

As described above, the project setting is performed by operating each of the above screens, and this setting information is stored in the project setting file 53. When such setting is completed, the user selects the verification start button 88 on the project setting screen 62. If such a project setting has already been completed, the project may be selected on the start screen 61.

When the verification start button 88 is selected, an operation verification screen 67 as shown in FIG. 13 is displayed. FIG. 13 is a diagram showing an example of the operation verification screen. The operation verification screen 67 may be displayed as a new screen, or may be displayed so that the display of the project setting screen 62 is switched. When the operation verification screen 67 is displayed, the verification start button 88 is switched to a verification stop button.

In the operation verification screen 67, the scene screen set as described above is displayed in the display unit 130 while switching according to the scenario corresponding to the setting. That is, the operation verification screen 67 functions as a display unit for verifying the operation of the UI realized on the UI panel 10.

In the operation verification screen 67, first, the scene screen 131 set as the top scene in the above-described project setting screen 62 is displayed. Thereafter, the user performs the operation verification of the UI by operating the UI (UI unit 30) realized on the UI panel 10 while referring to the operation verification screen 67. In the example of FIG. 13, the top scene screen 131 is displayed, and the focus exists in the top row (Mr. Tokyo). The top scene screen 131 displays a list of names (Mr. Tokyo, Mrs. Osaka, Mr. Fukuoka) of the destination scene screens as links registered in the link list information field of the project setting file 53. ing.

Here, when the UI unit 30 having an address number corresponding to the logical ID set in the lower movement key number field in the control information field for this scene screen is operated, the focus line moves downward. As a result, Mrs. The Osaka line is focused. Further, when the UI unit 30 having an address number corresponding to the logical ID set in the key number field at the time of determination in the control information field is operated, the screen changes to the scene screen (Mrs. Osaka) indicated by the link. To do.

<Operation and effect of the first embodiment>
In the UI verification system in the first embodiment described above, a plurality of UI units 30 having at least one UI function of input and output and a unique address are attached to each connector 11 provided on the UI panel 10. Thus, the UI is realized as an operation verification target.

In the UI panel 10, each communication line connected to each UI unit 30 via the connector 11 and the connector 33 is connected by the bus 12, and is connected to the verification control device 20 via the external interface 14. In the UI panel 10, when each UI unit 30 constituting the UI is operated, operation data indicating the operation status is relayed to the verification control device 20.

In the verification control device 20, various settings for verifying the operation of the target UI are stored in the project setting file 53 in units called projects. The project setting file 53 stores a scenario (scene information) indicating a scene screen transition procedure corresponding to an operation of each UI unit 30 constituting the target UI. Further, the verification control device 20 stores a scene image file 54 that forms a scene screen used in the scenario.

In such a configuration, when the operation verification function is executed by the operation verification application 50 of the verification control device 20, the settings in the project setting file 50 described above are operated by operating each UI unit 30 configuring the target UI. The display of the scene screen is controlled in a scenario based on information.

Therefore, according to the UI verification system in the first embodiment, the user can verify the operation while referring to the scene screen in accordance with the scenario in which the UI realized on the UI panel 10 is set in the verification control device 20.

The project setting file 53 of the verification control device 20 stores, as UI unit information, the address of each UI unit 30 constituting the target UI in association with a logical ID, and as scene information from one scene screen to another The logical ID of the UI unit 30 that causes each event such as an event for shifting to the scene screen and an event for shifting the focus line of the scene screen is stored.

As a result, the operation information including the address of the operated UI unit 30 is sequentially sent from the UI panel 10 to the verification control device 20, and the verification control device 20 converts the address included in the operation information into a logical ID. The scene screen is controlled according to the setting contents of the project setting file 53 in response to the acquisition of the logical ID.

As described above, each UI unit 30 has a unique address, and the communication lines of the respective connectors 11 for mounting the UI unit 30 to the UI panel 10 are bus-connected, and the UI unit 30. Since the input information (operation information) and output information (display data) for each are specified by their addresses, the setting in the project setting file 53 is changed no matter what connector 11 the UI unit 30 is attached to. There is no need.

Therefore, according to the UI verification system in the first embodiment, the UI configuration can be easily changed, such as changing the arrangement of the UI unit 30.

Furthermore, since the scene information is associated with the logical ID corresponding to the address of the UI unit 30, there are cases where the address of the UI unit 30 must be changed or a new UI unit 30 is added. However, the scene screen is controlled as set as long as the relevant setting between the address of the UI unit information in the project setting file 53 and the logical ID is changed.

Thereby, according to the UI verification system in the first embodiment, it is possible to give a degree of freedom to change the UI configuration.

As described above, since the UI configuration can be easily changed, the UI verification system according to the first embodiment can be used for UI verification of various electronic devices. Furthermore, since it is easy to repeat the operation verification while changing the UI configuration, it can be used as an educational material for improving the design ability of the user.

Also, the verification control device 20 can designate a display device such as the display 29 connected to the device itself or a UI unit 30 having a display function on the UI panel 10 as a device for displaying a scene screen.

Therefore, when the electronic device subject to operation verification has a display unit such as an LDC, if the UI unit 30 is designated as the display device, the operation verification is performed in the same hardware environment as the actual electronic device. Can do.

Also, when the UI of a remote control device that does not itself have a display function is to be verified, the display device connected to the device itself may be selected as an electronic device operated by the remote control device.

Even with such a configuration, the UI verification system in the first embodiment can be used for UI verification of various electronic devices.

[Second Embodiment]
Hereinafter, a UI verification system as a second embodiment of the present invention will be described with reference to the drawings. In addition to the functions of the first embodiment described above, the UI verification system in the second embodiment collects position information of each UI unit 30 constituting the UI to be verified, and performs operability evaluation based on this position information. It further has a function to perform.

〔System configuration〕
Since the system configuration of the UI verification system in the second embodiment is the same as that in the first embodiment, description thereof is omitted here.

〔Device configuration〕
Hereinafter, only the parts different from the first embodiment will be described with respect to each device constituting the UI verification system in the second embodiment.

<UI panel>
The device configuration of the UI panel 10 in the second embodiment will be described below with reference to FIG. FIG. 14 is a diagram showing a schematic device configuration of the UI panel 10 in the second embodiment. The UI panel 10 according to the second embodiment further includes a transmission selection circuit 141 and a reception selection circuit 142 in addition to the configuration of the first embodiment. Although the UI panel 10 in the second embodiment includes all the configurations of the first embodiment, the ROM 16 and the RAM 17 are not shown in FIG.

In the UI panel 10 in the second embodiment, the bus 12 for connecting the communication lines of the connectors 11 is configured as shown in FIG. In other words, in the second embodiment, the bus 12 includes a transmission bus formed by connecting a plurality of branch transmission buses that respectively connect transmission lines of a predetermined number of connectors 11 to the transmission selection circuit 141, and a predetermined number of connectors 11. A plurality of branch reception buses connecting the respective reception lines are connected to the reception selection circuit 142, and the reception bus is formed. Further, each connector connected to one branch transmission bus via a transmission line is configured to be connected to a different branch reception bus via a reception line. In FIG. 14, the branch transmission bus is represented as “TX-SEL N”, and the branch reception bus is represented as “RX-SEL S”. FIG. 14 shows a configuration example having 459 connectors 11, 27 branch transmission buses, and 17 branch reception buses. The present invention does not limit the number of connectors and buses.

With this configuration, the CPU 15 is connected to the transmission selection circuit 141 via the transmission line 145 and the transmission selection information line 146, and is connected to the reception selection circuit 142 via the reception line 147 and the reception selection information line 148. The transmission line 145 and the reception line 147 flow the operation data shown in FIG. 3 and the display data shown in FIG. The transmission selection information line 146 and the reception selection information line 148 flow instruction signals for switching the connection state between the branch buses to the transmission selection circuit 141 and the reception selection circuit 142.

The transmission selection circuit 141 includes a switch mechanism for connecting each branch transmission bus (TX-SEL N) and the transmission line 145, respectively. The transmission selection circuit 141 switches the connection state between each branch transmission bus and the transmission line 145 in accordance with an instruction signal sent from the CPU 15 via the transmission selection information line 146.

Similarly to the transmission selection circuit 141, the reception selection circuit 142 includes a switch mechanism for connecting each branch reception bus (RX-SEL N) and the reception line 147, respectively. The reception selection circuit 142 switches the connection state between each branch reception bus and the reception line 147 in accordance with an instruction signal sent from the CPU 15 via the reception selection information line 148. Note that in the transmission selection circuit 141 and the reception selection circuit 142 during normal operation, all branch transmission buses are connected to the transmission line 145 and all branch reception buses are connected to the reception line 147.

As a function of the UI panel 10, the CPU 15 collects information related to the connector 11 to which the UI unit 30 is mounted among the plurality of connectors 11 in addition to the function of the first embodiment (hereinafter referred to as a connector information collecting function). To achieve). When the CPU 15 receives a collection instruction signal in which 0 is set in the display device number field in the data signal format shown in FIG. 4 via the external interface 14, the CPU 15 executes this connector information collection function. The CPU 15 holds information on the number of each connector 11 provided on the UI panel 10 and information on the branch transmission bus and branch reception bus to which the connector indicated by each connector number is connected in the ROM 16 or the like.

In this connector information collection function, the CPU 15 first selects any one of the plurality of connectors 11, and the transmission selection circuit 141 and the reception selection circuit 142 so that only the selected connector 11 can communicate with the CPU 15. To control. Specifically, the CPU 15 determines a branch transmission bus and a branch reception bus to which the communication line of the selected connector 11 is connected based on the information held as described above, and this determined branch transmission. A selection instruction signal indicating a bus is transmitted to the transmission selection circuit 141 via the transmission selection information line 146, and a selection instruction signal indicating the determined branch reception bus is transmitted to the reception selection circuit 142 via the reception selection information line 148. To do. The transmission selection circuit 141 and the reception selection circuit 142 that have received each selection instruction signal are connected to the transmission line 145 only for the branch transmission bus indicated by the signal, and are connected to the reception line 147 only for the branch reception bus indicated by the signal. Switch the switch mechanism so that

Subsequently, the CPU 15 transmits a predetermined position detection signal to the transmission selection circuit 141 via the transmission line 145. At this time, for example, if the selected connector is the connector 11 (# 3) shown in FIG. 14, the position detection signal is sent only to the branch transmission bus (TX-SEL1) according to the switch mechanism of the transmission selection circuit 141. Is done. As a result, the position detection signal is transmitted from the connector 11 (# 1) connected to the branch transmission bus (TX-SEL1) via the transmission line to (# 17).

For example, when the UI unit 30 is mounted on the connector 11 (# 2) and the connector 11 (# 3), each UI unit 30 transmits a confirmation signal as a response to the position detection signal. This confirms the branch reception bus (RX-SEL2) to which the reception line of the connector 11 (# 2) is connected and the branch reception bus (RX-SEL3) to which the reception line of the connector 11 (# 3) is connected. A signal is transmitted. At this time, since the reception selection circuit 142 is switched so that only the branch reception bus (RX-SEL3) is connected to the reception line 147, the confirmation signal transmitted through the branch reception bus (RX-SEL2) is the CPU 15 Only the confirmation signal transmitted through the branch reception bus (RX-SEL3) is delivered to the CPU 15. In this way, control is performed so that only information relating to the selected connector 11 (# 3) is received.

The CPU 15 waits for reception of this confirmation signal, and if it can be normally received, determines that the UI unit 30 is attached to the selected connector 11. When the CPU 15 cannot receive normally, the CPU 15 determines that the UI unit 30 is not attached to the connector 11.

When the CPU 15 determines that the UI unit 30 is attached to the selected connector 11, the data signal (shown in FIG. 15) including the number of the selected connector 11 and the device number included in the confirmation signal is displayed. Hereinafter, it is expressed as position information data). The CPU 15 transmits the generated position information data to the verification control device 20 via the external interface 14. The CPU 15 executes the connector information collection process as described above for all the connectors 11.

When the CPU 15 completes the connector information collection process for all the connectors 11, the CPU 15 uses the transmission selection information line 146 and the reception selection information line 148 so that the transmission selection circuit 141 and the reception selection circuit 142 are switched to the normal operation. Instruct. Accordingly, the transmission selection circuit 141 and the reception selection circuit 142 switch each switch mechanism so that all the branch transmission buses are connected to the transmission line 145 and all the branch reception buses are connected to the reception line 147.

FIG. 15 is a diagram showing a format example of position information data. In the command field, an identification number indicating position information data as a response to the collection instruction signal sent from the verification control device 20 is set. In the message length field, the length (number of bytes) from the subsequent connector number field to the connector field is set. In the connector number field, the number of the connector 11 to which the UI unit 30 is attached is set. In the device number field, the device number of the UI unit 30 attached to the connector indicated by the connector number is set. In the connector field, data indicating whether the position information data follows or is final is set.

As described above, when the UI panel 10 receives the collection instruction signal from the verification control device 20, the UI panel 10 displays the connector numbers related to all the connectors 11 to which the UI unit 30 is attached and the device numbers of the UI units 30 attached to them. The verification control device 20 is notified using the position information data shown in FIG.

<UI unit>
When the UI unit 30 of the second embodiment receives a predetermined position detection signal transmitted by the connector information collection function of the UI panel 10 in addition to the function of the first embodiment described above, its own device is returned as a response. It has a function of transmitting a confirmation signal including a number. Since other functions are the same as those of the first embodiment, description thereof is omitted here.

<Verification control device>
The hardware configuration of the verification control apparatus 20 in the second embodiment is the same as that in the first embodiment. In the second embodiment, a new function unit is added to the operation verification application 50 in the software function group realized by the CPU 22. As shown in FIG. 16, the operation verification application 50 in the second embodiment further includes a position information collection function unit 161, an operability evaluation function unit 162, and an evaluation result file 163 in addition to the configuration of the first embodiment. . FIG. 16 is a block diagram illustrating an outline of a functional configuration of the verification control device 20 according to the second embodiment. Only the configuration different from the first embodiment will be described below.

In the second embodiment, new information is added to the project setting file 53 in accordance with the addition of a new functional unit as described above. FIG. 17 is a diagram showing a configuration example of a project setting file in the second embodiment. In the project setting file 53 of the second embodiment, in addition to the device number and the logical ID, the connector number to which the UI unit is mounted is stored in the UI unit information field. Other information stored in the project setting file 53 is the same as in the first embodiment.

The position information collection function unit 161 collects position information of each UI unit 30 constituting the UI that is the target of operation verification at a predetermined timing such as when operation verification starts. As the position information of the UI unit 30, the number of the connector in the UI panel 10 to which the UI unit 30 is mounted is used. Specifically, the position information collection function unit 161 externally outputs a collection instruction signal whose display device number field is set to 0 in the data signal format shown in FIG. 4 at a predetermined timing such as when operation verification is started. The data is transmitted via the interface controller 23.

Thereby, in the UI panel 10, the connector information collecting function as described above is executed. As a result, the position information collection function unit 161 receives the position information data shown in FIG. 15 as a response to the collection instruction signal. The position information collection function unit 161 sets the device number and connector number included in the position information data in the device information field of the project setting file 53.

When the operation verification is started, the operability evaluation function unit 162 recognizes each operation of the UI, and calculates evaluation data for each recognized operation. Specifically, like the operation verification function unit 52, the operability evaluation function unit 162 monitors each operation of the UI by monitoring operation data (see FIG. 3) received via the external interface controller 23. recognize. The operability evaluation function unit 162 acquires the following data regarding each recognized operation.

The operability evaluation function unit 162 measures the time between operations. The operability evaluation function unit 162 generates evaluation data in a form in which this measured time is associated with identification information indicating the operation as an operation time related to the subsequent operation.

Furthermore, the operability evaluation function unit 162 calculates the movement amount between operations. When the operation data is received, the operability evaluation function unit 162 extracts a connector number corresponding to the device number of the operation data from the project setting file 53. The operability evaluation function unit 162 acquires the connector number at the time of the previous operation and the connector number extracted this time, and calculates the distance between the connector numbers. The distance between the connectors is preliminarily held in the arrangement information of the connector 11 on the UI panel 10, and is calculated based on the arrangement information.

For example, when the connectors 11 are arranged in a matrix as shown in FIG. 14, the position of each connector can be grasped as coordinate information, so that each connector is based on the vertical / horizontal distance between adjacent coordinate points. The distance between the position coordinates corresponding to the number can be calculated. In this case, the distance between the position coordinates is the amount of movement between the connector numbers. In addition, the distances between all connector numbers may be stored in advance, or may be calculated based on a predetermined rule.

The operability evaluation function unit 162 generates evaluation data in a form in which the calculated movement amount between operations is associated with identification information indicating the operation as a movement amount related to the subsequent operation.

Furthermore, the operability evaluation function unit 162 calculates the operation movement speed in the UI operation verification based on the time and the movement amount between each operation acquired as described above. The operability evaluation function unit 162 also generates evaluation data including the calculated operation moving speed.

The operability evaluation function unit 162 sequentially stores the evaluation data generated as described above in the evaluation result file 163. Thereby, in this evaluation result file 163, the operation time and movement amount for each operation, and the operation movement speed are set.

The operability evaluation function unit 162 generates an operability evaluation screen for displaying the contents of the evaluation result file 163 in a graph by a user operation, and displays the operability evaluation screen on the display 29.

Such processing of the operability evaluation function unit 162 may be performed each time an operation is detected in response to reception of operation data. When an operation is detected, the connector number and the operation time are detected. Only when the operability evaluation screen is displayed, the movement amount may be calculated based on the connector number, and the operation movement speed may be calculated based on the time and the movement amount between the operations.

[Operation example]
Hereinafter, the operation of the UI verification system in the second embodiment will be described mainly with respect to differences from the first embodiment.

As in the first embodiment, when a UI to be verified is realized on the UI panel 10 and various settings of the project are completed by the operation verification application 50 on the verification control device 20, a verification start button 88 on the project setting screen 62 is displayed. Operation verification is started by selecting.

In the second embodiment, when the operation verification is started, first, the operation verification application 50 collects the position information of each UI unit 30 constituting the UI to be verified (position information collection function unit 161). Specifically, a collection instruction signal is transmitted from the verification control device 20 to the UI panel 10, the connector information collection function is executed on the UI panel 10, and the connector numbers for all the connectors 11 to which the UI unit 30 is attached and their numbers The position information data including the device number of the UI unit 30 mounted on the UI panel 10 is transmitted from the UI panel 10 to the verification control device 20.

In the verification control device 20, the operation verification application 50 stores each connector number corresponding to the device number of each UI unit in the project setting file 53 based on the received position information data. Thereafter, operation verification is performed as in the first embodiment.

In the second embodiment, the same operation verification as in the first embodiment is realized, and the verification control device 20 recognizes each operation of the UI based on the operation data from the UI panel 10 and evaluates data about each operation. Are generated sequentially. This evaluation data is configured in such a manner that the time and amount of movement between each operation, and the operation moving speed are associated with the identification information indicating each operation. The verification control device 20 sequentially stores the evaluation data generated in this way in the evaluation result file 163.

The operation verification application 50 displays the operability evaluation screen 190 when an evaluation button 181 provided on the project setting screen 62, the operation verification screen 67, or the like is selected. FIG. 18 is a diagram illustrating a configuration example of the project setting screen 62 in the second embodiment. 19 to 21 are diagrams illustrating a configuration example of the operability evaluation screen.

The operability evaluation screen 190 is a screen for displaying the contents of the evaluation result file 163 in a graph. The operability evaluation screen 190 displays three types of graphs: movement amount, time, and speed. This display format is switched by the display format setting unit 191 in the operability evaluation screen 190.

When the display format of the movement amount is selected, as shown in FIG. 19, a graph 192 is displayed in which the operation is shown on the horizontal axis and the movement amount is shown on the vertical axis. Below the graph 192, an average movement amount, a maximum movement amount, and a minimum movement amount are further displayed.

When the time display format is selected, as shown in FIG. 20, a graph 201 is displayed in which operations are shown on the horizontal axis and time is shown on the vertical axis. Below the graph 201, an average operation time, a maximum operation time, and a minimum operation time are further displayed.

When the speed display format is selected, as shown in FIG. 21, a graph 211 is displayed in which time is shown on the horizontal axis and the amount of movement is shown on the vertical axis. Below the graph 211, an average operation speed, a maximum operation speed, and a minimum operation speed are further displayed.

<Operation and effect of the second embodiment>
In the UI verification system in the second embodiment, the UI panel 10 collects information about the connector 11 to which the UI unit 30 is attached in response to a request (collection instruction signal) from the verification control device 20, and collects this collected information ( The connector number of the connector 11) is sent to the verification control device 20.

In the verification control device 20, this connector number is stored in the project setting file 53 as UI unit information in association with the address and logical ID of the UI unit. The operation verification application 50 of the verification control apparatus 20 records the operation history at the time of operation verification by performing operation verification in the first embodiment and detecting operation data sent according to the operation of the UI unit 30. At this time, the verification control device 20 measures the time between each operation together with this operation history, calculates the movement amount between each operation according to the connector number on the UI panel 10 to which the UI unit is mounted, Based on these pieces of information, the speed of each operation is calculated. In the verification control device 20, as a result of the operation verification, evaluation data in which the time, movement amount, and operation speed related to each operation are associated is generated and output to the evaluation result file 163.

Therefore, according to the UI verification system in the second embodiment, the evaluation data including the operation history at the time of the operation verification and the movement amount between the operations is generated together with the execution of the operation verification. Can also be performed. This evaluation data is displayed in a graph on the operability evaluation screen generated by the operation verification application 50. Therefore, the user can recognize the UI operability evaluation designed by the user by referring to the operability evaluation screen. Thereby, according to the UI verification system in 2nd embodiment, a user's UI design capability can be improved.

Here, in the UI panel 10, the bus 12 is connected to the transmission selection circuit 141 to form a transmission bus, and the branch selection bus 142 is connected to the reception selection circuit 142 to form a reception bus. Each connector 11 is connected to any one of a plurality of branch transmission buses by the transmission line, and is different from other connectors 11 connected to the same branch transmission bus among the plurality of branch reception buses. Connect to the receive bus with the receive line. With such a configuration, the UI panel 10 is controlled so that the transmission selection circuit 141 and the reception selection circuit 142 can communicate with any one of the connectors 11, and becomes a response to the position detection signal sent to the branch transmission bus. The connector numbers to which the UI unit 30 is attached are collected depending on whether the confirmation signal is normally received.

With such a configuration, the UI verification system in the second embodiment can automatically detect the position of each UI unit 30 used for operability evaluation. In other words, even if the UI configuration is changed, the position of the UI unit 30 after the change can be automatically detected, so that complicated settings for performing operability evaluation are not required. Therefore, according to the UI verification system in the second embodiment, the UI configuration can be easily changed, and operability evaluation can be performed using the UI configuration after the change.

[Modification]
In the second embodiment described above, the verification control device 20 recognizes each operation of the UI based on the operation data from the UI panel 10, and sequentially generates evaluation data related to each operation. The identification information indicating the operation is configured in such a manner that the time and movement amount between the operations and the operation movement speed are associated with each other.

As a modification of the second embodiment, each UI block 30 constituting a UI is grouped according to the type (logical ID, etc.) of the UI block 30, and the time between operations within the same group and between operations across the groups. The movement amount and the operation speed may be acquired.

In this case, the verification control device 20 is configured such that the operation verification application 50 sets the group ID for identifying the group together with the connector number and the like in the device information field of the project setting file 53 in association with the device number. To do. FIG. 22 is a diagram illustrating a configuration example of a project setting file according to a modification of the second embodiment. This group ID may be set by the input setting unit 85 of the project setting screen 62 or the like.

The operation verification application 50 recognizes each operation of the UI based on the operation data from the UI panel 10 using this group ID, and recognizes each recognized operation as an operation of the group to which this UI belongs. As a result, the operation verification application 50 displays on the operability evaluation screen 190 a graph that indicates the time, movement amount, and operation speed between operations within the same group and between operations across the group.

[Others]
<About software components>
A software component is a component (fragment) that realizes the above function as software, and is not a concept that limits a language, a development environment, or the like that realizes the software. Examples of software components include tasks, processes, threads, drivers, firmware, databases, tables, functions, procedures, subroutines, predetermined portions of program code, data structures, arrays, variables, parameters, and the like. These software components are implemented on one or a plurality of memories (one or a plurality of processors (for example, a CPU (Central Processing Unit), a DSP (Digital Signal Processor), etc.)).

In addition, since each above-mentioned embodiment does not limit the implementation | achievement method of each said function part, each said function part is a method realizable by the normal engineer of this technical field as a component of the said software. What is necessary is just to be comprised by.

Claims (8)

1. A UI device on which a plurality of UI units, each of which is a component of a user interface (UI) and each having a unique address, and a scene screen are controlled according to the operation of the UI unit attached to the UI device. A UI verification system comprising: a verification control device that:
   The UI device is
   A plurality of connectors having communication lines for detachably supporting the UI units and communicating with the mounted UI units;
   A bus to which the communication lines of the plurality of connectors are respectively connected;
   Communication control means for controlling communication with the plurality of UI units via the bus and communication with the verification control device;
   With
   The verification control device includes:
   A unit table for storing the address of each UI unit in association with the type information corresponding to the type of each UI unit;
   A scene setting table for storing the type information that triggers changing the display state of the scene screen in association with the information of the scene screen;
   Receiving means for receiving, from the UI device, operation information including an address of the operated UI unit among the plurality of UI units;
   When the operation information is received by the reception unit, an acquisition unit that acquires type information corresponding to an address included in the operation information from the unit table;
   When the type information acquired by the acquisition unit is set in the scene setting table as trigger information for changing the display state of the currently displayed scene screen, the scene screen according to the setting content of the scene setting table Screen control means for controlling
   A UI verification system comprising:
2. The communication control means of the UI device is:
   Collecting means for collecting information on the connectors to which the UI units are mounted by detecting the connectors to which the UI units are mounted among the plurality of connectors,
   The verification control device includes:
   Position information acquisition means for acquiring position information of the plurality of UI units based on connector information sent from the UI device;
   History recording means for recording operation histories of the plurality of UI units based on the operation information received by the receiving means;
   Calculation means for calculating the movement amount between each operation of the plurality of UI units based on the operation history recorded by the history storage means and the position information of each UI unit acquired by the position information acquisition means;
   Data generation means for generating evaluation data including an operation history recorded by the history recording means and a movement amount between operations calculated by the calculation means;
   The UI verification system according to claim 1, further comprising:
3. Each communication line of each connector of the UI device includes a transmission line for sending a signal to the mounted UI unit and a reception line for receiving a signal from the UI unit,
   The bus of the UI device includes a plurality of branch transmission buses connected by a transmission selection circuit and a plurality of branch reception buses connected by a reception selection circuit, and each of the transmission lines of each connector is one Connected to the branch transmission bus, the receiving line of each connector is connected to any one of the branch receiving buses, and each connector connected to one branch transmitting bus by the transmitting line is connected to a different branch receiving bus by a receiving line. Configured to be connected,
   The collection means of the UI device includes:
   One of the plurality of branch transmission buses and one of the plurality of branch reception buses are selected, and only the selected branch transmission bus and branch reception bus are selected. Selection control means for controlling the transmission selection circuit and the reception selection circuit to be connected,
   The UI unit is mounted by checking whether or not a predetermined response signal to a predetermined signal transmitted to the branch transmission bus selected by the selection control means is received from the selected branch reception bus. Detect connector,
   The UI verification system according to claim 2.
4. The verification control device includes:
   Measuring means for measuring the time between each operation of the plurality of UI units based on the operation information received by the receiving means;
   Further comprising
   The data generation means further generates an operation speed based on the time between the operations measured by the measurement means as the verification data, and the movement amount between the operations and the time.
   The UI verification system according to claim 2 or 3.
5. The unit table of the verification control device stores the address of each UI unit in association with the type information corresponding to the type of each UI unit and the information of the group to which each UI unit belongs,
   The data generation means of the verification control device classifies the operation history recorded by the history recording means for each group, and as the verification data, in at least one between operations within the same group and between operations across groups. The UI verification system according to claim 4, further generating time, movement amount, and operation speed.
6. The verification control device includes:
   A display setting table for storing display unit setting information indicating whether a display unit of the plurality of UI units is used or a display unit other than that is used as the display unit for displaying the scene screen;
   Further comprising
   The screen control means determines whether to transmit control data for controlling the scene screen to the UI device according to display unit setting information stored in the display setting table;
   The UI verification system according to any one of claims 1 to 5.
7. A plurality of connectors each having a communication line for detachably supporting each UI unit, each of which is a component of a user interface (UI) and having a unique address set, and communicating with the mounted UI unit; A UI having a bus to which the communication lines of the plurality of connectors are respectively connected, and a communication control means for controlling communication with the plurality of UI units via the bus and communication with the verification control device. In a verification control device that is connected to a device and controls a scene screen in accordance with an operation of a UI unit mounted on the UI device.
   A unit table for storing the address of each UI unit in association with the type information corresponding to the type of each UI unit;
   A scene setting table for storing the type information that triggers changing the display state of the scene screen in association with the information of the scene screen;
   Receiving means for receiving, from the UI device, operation information including an address of the operated UI unit among the plurality of UI units;
   When the operation information is received by the reception unit, an acquisition unit that acquires type information corresponding to an address included in the operation information from the unit table;
   When the type information acquired by the acquisition unit is set in the scene setting table as trigger information for changing the display state of the currently displayed scene screen, the scene screen according to the setting content of the scene setting table Screen control means for controlling
   A verification control device comprising:
8. A plurality of connectors each having a communication line for detachably supporting each UI unit, each of which is a component of a user interface (UI) and having a unique address set, and communicating with the mounted UI unit; A UI having a bus to which the communication lines of the plurality of connectors are respectively connected, and a communication control means for controlling communication with the plurality of UI units via the bus and communication with the verification control device. In a UI verification method executed by a device and a verification control device that controls a scene screen according to an operation of a UI unit mounted on the UI device,
   The verification control device is
   Storing the address of each UI unit in the unit table in association with the type information corresponding to the type of each UI unit;
   Storing the type information that triggers changing the display state of the scene screen in the scene setting table in association with the information of the scene screen;
   Receiving operation information including the address of the operated UI unit among the plurality of UI units from the UI device;
   Obtaining the type information corresponding to the address contained in the operation information from the unit table when the operation information is received;
   When the acquired type information is set in the scene setting table as trigger information for changing the display state of the currently displayed scene screen, the scene screen is controlled according to the setting contents of the scene setting table Steps,
   UI verification method for executing
   

Images