WO2014147924A1 - ユーザインタフェース一貫性チェック方法、装置およびプログラム - Google Patents
ユーザインタフェース一貫性チェック方法、装置およびプログラム Download PDFInfo
- Publication number
- WO2014147924A1 WO2014147924A1 PCT/JP2014/000085 JP2014000085W WO2014147924A1 WO 2014147924 A1 WO2014147924 A1 WO 2014147924A1 JP 2014000085 W JP2014000085 W JP 2014000085W WO 2014147924 A1 WO2014147924 A1 WO 2014147924A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- user interface
- screen
- consistency
- check
- inspection
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/957—Browsing optimisation, e.g. caching or content distillation
- G06F16/9577—Optimising the visualization of content, e.g. distillation of HTML documents
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/103—Formatting, i.e. changing of presentation of documents
- G06F40/106—Display of layout of documents; Previewing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/103—Formatting, i.e. changing of presentation of documents
- G06F40/109—Font handling; Temporal or kinetic typography
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/166—Editing, e.g. inserting or deleting
- G06F40/177—Editing, e.g. inserting or deleting of tables; using ruled lines
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/20—Natural language analysis
- G06F40/205—Parsing
- G06F40/226—Validation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/77—Software metrics
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/38—Creation or generation of source code for implementing user interfaces
Definitions
- the present invention relates to a user interface consistency check method, a user interface consistency check device, and a user interface consistency check program for checking consistency of a screen user interface.
- Non-Patent Document 1 discloses a tool that automatically evaluates usability such as readability on a WEB page screen and easy-to-understand contents and extracts problems to be improved.
- Non-Patent Document 2 discloses selenium, which is an application software test automation tool.
- Non-Patent Document 1 the inspection in the tool described in Non-Patent Document 1 is only an inspection for individual items, and there is a problem that the usability of the entire user interface including a plurality of items cannot be inspected.
- an object of the present invention is to provide a usability check result output method, a user interface consistency check device, and a usability check result output program capable of inspecting the usability of the entire user interface including a plurality of items.
- the user interface consistency check method obtains screen information of a screen to be inspected, performs an inspection on the consistency of the screen user interface based on a predetermined check rule, and does not conform to the check rule. Is displayed.
- the user interface consistency check device includes an input unit that acquires screen information of a screen to be inspected, an inspection unit that performs an inspection on the consistency of the user interface of the screen based on a predetermined check rule, And a display processing unit that displays items that do not conform to the check rule.
- the user interface consistency check program is a computer program for performing inspection related to consistency of a screen user interface based on an input process for acquiring screen information of a screen to be inspected and a predetermined check rule. It is characterized by executing a process and a display process for displaying an item that does not conform to the check rule.
- the present invention can inspect the usability of the entire user interface including a plurality of items.
- FIG. 1 is a block diagram showing the configuration of the user interface consistency check device of this embodiment.
- the user interface consistency check device includes an input unit 1, an inspection unit 2, a check rule storage unit 3, and a display processing unit 4.
- the input unit 1, the inspection unit 2, and the display processing unit 4 are realized by, for example, hardware designed to perform specific arithmetic processing or the like or an information processing device such as a CPU (Central Processing Unit) that operates according to a program.
- the check rule storage unit 3 is realized by a storage device such as a general HDD (Hard Disk Drive), for example.
- HDD Hard Disk Drive
- the input unit 1 acquires screen information that defines the user interface of the screen to be inspected. For example, when the screen is a WEB page displayed on a general browser, the input unit 1 acquires an HTML (HyperText Markup Language) source as screen information.
- the input unit 1 may acquire screen information such as coordinate information, color information, and text information in the displayed screen from the browser.
- the screen to be inspected is not limited to a WEB page, but may be a screen that displays a user interface.
- the inspection unit 2 acquires a check rule regarding the consistency of the user interface from the check rule storage unit 3 and checks whether the screen information acquired from the input unit 1 conforms to the check rule. Specifically, when there are different expression methods for a plurality of related items, the inspection unit 2 determines an inconsistent item as an error based on the most expression methods.
- the check rule storage unit 3 stores check rules for checking the consistency of the user interface on the screen.
- the check rule is a rule from the viewpoint of consistency regarding display and operation in a plurality of related items, and is stored in advance by a designer or the like.
- the check rule storage unit 3 may store an error message, a supplement message, a response method, and the like associated with each check rule.
- the check rule may be described in a program for causing the CPU to execute the operation of the inspection unit 2, and in that case, the check rule storage unit 3 is unnecessary.
- the display processing unit 4 displays a list of items that did not conform to the check rule in the inspection.
- the inspection result is, for example, the URL and title of the screen including the corresponding item, an error number, an error message, and a handling method.
- FIG. 2 is a flowchart showing the operation of the user interface consistency check device of this embodiment.
- the user sends an instruction for causing the user interface consistency check device to start an inspection.
- the display processing unit 4 may display a setting screen on which the user can make detailed settings for inspection.
- FIG. 3 is an explanatory diagram illustrating an example of a setting screen. Specifically, for example, the user selects a category to be inspected on the setting screen as shown in FIG. 3 and presses a check start button.
- the setting screen is configured so that the user can select the contents to be checked according to the importance. In the example shown in FIG. 3, the user can select from three types of “important”, “recommended”, and “hint”.
- the setting screen may be configured such that the user can select the type of rule that the user wants to check. Also, as shown in FIG. 3, the number of problems (the number of items that do not conform to the check rule) may be displayed when an inspection to be described later is completed.
- the setting screen is configured so that the user can switch the display method of the check result. In the example illustrated in FIG. 3, the user can select a display method from three types of “comment display”, “number display”, and “non-display”.
- the input unit 1 acquires screen information that defines the user interface of the screen to be inspected (step S1).
- the input unit 1 acquires an HTML source.
- the input unit 1 may acquire coordinate information, color information, and text information in the screen from a browser, for example. Both a method of acquiring screen information from an HTML source and a method of acquiring from a browser may be used, or only one of them may be used.
- the input unit 1 uses a function of a general script language such as javascript (registered trademark) in order to acquire screen information such as coordinate information, color information, and text information in the screen from the browser. By acquiring screen information from the browser, the input unit 1 can also acquire information that cannot be acquired from HTML sources, such as the distance between text and buttons, the size of radio buttons, and the like.
- javascript registered trademark
- the inspection unit 2 acquires a check rule regarding the consistency of the user interface from the check rule storage unit 3, and checks whether the screen information acquired from the input unit 1 conforms to the check rule (step S2). Specifically, when there are different expression methods or input methods for a plurality of related items, the inspection unit 2 determines that an inconsistent item is an error based on the most common expression methods or input methods. To do.
- FIG. 4 is an explanatory diagram showing an example of a check rule.
- the inspection unit 2 inspects consistency regarding a plurality of related items.
- the check rule described in FIG. 4 will be described.
- the check rule shown in FIG. 4 describes the consistency check regarding the layout. Specifically, as a check item in rule number 1, a check rule indicating whether or not the basic operation button arrangement positions are consistent is described. For example, when “left alignment”, “center alignment”, and “right alignment” are mixed in the button arrangement, the inspection unit 2 determines that an error has occurred.
- check item in rule number 2 when the same information is displayed in a table or a list, a check rule indicating whether the arrangement order of elements is consistent is described. For example, when the item names in the table are not arranged in the predetermined item name order, the inspection unit 2 determines that an error has occurred.
- a check rule is described as to whether the arrangement order of buttons and menus providing the same function is consistent. For example, when the buttons “OK” and “Cancel” are arranged on a plurality of pages and the arrangement order is not consistent, the inspection unit 2 determines that there is an error.
- the check rule shown in FIG. 4 describes a consistency check regarding navigation.
- a check item in rule number 4 a check rule indicating whether the display method of the current position in the application is consistent is described. For example, when the display method of the current position on the search result list page is not consistent, the inspection unit 2 determines that an error has occurred. For example, in the case of the display method of “displaying 20 to 40 cases out of 123 cases”, “20 to 40 cases” indicates the current position.
- a breadcrumb list is used as a display method of the current position.
- the check rule shown in FIG. 4 describes a consistency check for data display components. These items are check rules relating to a method for expressing static parts such as labels and text. Specifically, as a check item in rule number 5, a check content indicating whether the expression method of the item name is consistent is described.
- the inspection unit 2 checks, for example, the background color, font color, arrangement, and symbols at the beginning and end of the character string for table or input / output component item names. The inspection unit 2 considers an error to have a style different from the most common style.
- a check rule is described as to whether the expression method indicating the required and optional input is consistent.
- the inspecting unit 2 checks, for example, whether the text box that is an essential item and the expression of the item name that indicates the text box (background color, font color, symbol indicating the essentiality (asterisk, etc.)) are consistent.
- the check rule shown in FIG. 4 describes the check contents as to whether the expression method regarding the control component is consistent.
- the control component is a component used for the interaction between the user and the computer, such as a radio button or a text box.
- the inspection unit 2 determines that an error has occurred, for example, when the sizes of the same type of control parts or the labels attached to the same type of control parts are not consistent.
- the check rule shown in FIG. 4 describes the consistency check regarding the basic input operation of the user. Specifically, as a check item in rule number 8, a check content indicating whether there is consistency regarding an operation method (including an input method) is described.
- the inspection unit 2 checks whether the input method is the same when, for example, input parts for inputting “year / month / day” and “time” are arranged and two or more input parts of the same type exist. To do. For example, when “YYYY / MM / DD” and “YYYYMMDD” are mixed as the input method of date, the inspection unit 2 determines that an error has occurred. In addition, the inspection unit 2 determines that an error has occurred when functions or the like realized by the same kind of operation method such as mouse double click, single click, and touch operation are not consistent.
- the check rule shown in FIG. 4 describes a consistency check regarding feedback. Specifically, as a check item in rule number 9, a check rule is described as to whether the information presentation method for the user operation is consistent.
- the information presenting method is, for example, a method for displaying a tooltip after mouse over or a method for displaying a message for an input error.
- check rule shown in FIG. 4 describes a consistency check regarding fonts, terms, and visual expressions. Specifically, as a check item in rule number 10, a check rule is described as to whether the display method of fonts, terms, and visual expressions is consistent.
- the inspection unit 2 inspects not only the consistency of the user interface in one screen but also the consistency of the user interface in a plurality of screens. For example, when the same type of user interface is included in each screen in a plurality of screens, the inspection unit 2 inspects whether or not the user interface is consistent. For example, when a WEB site includes a plurality of screens, developers may be different for each screen. Even in such a case, the user can create a high-quality user interface by checking the consistency of each screen in a plurality of screens.
- FIG. 5 is an explanatory diagram showing an example of a screen on which two types of buttons are arranged.
- FIG. 6 is an explanatory diagram showing an example of another screen on which two types of buttons are arranged.
- a “cancel” button is arranged below the “OK” button.
- a “cancel” button is arranged on the “OK” button. In this case, the inspection unit 2 does not correspond to the check item of rule number 3 in FIG.
- the display processing unit 4 displays items that do not conform to the check rules in the inspection (step S3).
- FIG. 7 is an explanatory diagram illustrating an example of a screen on which a list of inspection results is displayed.
- the display processing unit 4 may add a link to the corresponding screen in the list.
- the display processing unit 4 may display a message box on the screen indicating an item that does not conform to the check rule in the inspection, and display the inspection result in the message box.
- FIG. 8 is an explanatory diagram illustrating an example of a screen displaying a message box indicating an item that does not conform to the check rule.
- the inspection result is, for example, an error message stored in the check rule storage unit 3 in association with the check rule.
- the display processing unit 4 uses the coordinate information of the screen acquired by the input unit 1 in order to determine the display position of the message box. In this way, an error message is displayed to point to an item in the immediate vicinity of the problem item, so that the user can easily check the problematic item.
- the user interface consistency check device of the present embodiment can check the usability of the entire user interface including a plurality of items in order to check the consistency regarding display and operation of a plurality of items.
- FIG. 9 is a block diagram illustrating a configuration of the user interface consistency check device according to the second embodiment.
- the functions of the input unit 1, the check rule storage unit 3, and the display processing unit 4 are the same as those in the first embodiment, and thus description thereof is omitted.
- the option setting unit 5 sets the inspection standard based on the user's selection. For example, the option setting unit 5 sets the reference screen based on the user's selection. In this case, the inspection unit 2 performs inspection by comparing another screen with the reference screen.
- the option setting unit 5 may set detailed inspection criteria based on user input.
- the inspection unit 2 acquires a check rule from the check rule storage unit 3 and acquires setting contents from the option setting unit 5. The inspection unit 2 inspects whether the screen information acquired from the input unit 1 meets the inspection rule set by the check rule and option setting unit 5.
- FIG. 10 is a flowchart illustrating the operation of the user interface consistency check device according to the second embodiment.
- the option setting unit 5 displays an option setting screen for accepting option settings related to inspection, and sets inspection criteria based on user input (step S11).
- the option setting unit 5 sets a reference screen based on the user's selection, for example. In this case, the inspection unit 2 performs the inspection by comparing another screen with the reference screen.
- the option setting unit 5 may set detailed inspection criteria based on user input.
- FIG. 11 is an explanatory diagram showing an example of an option setting screen.
- the user decides a reference screen and wants to inspect by comparing another screen with the reference screen, the user presses the automatic setting button 51 while displaying the reference screen. Further, when the user wants to set the contents to be inspected, the user presses the setting button 52 for the desired item.
- FIG. 12 is an explanatory diagram showing an example of a check criteria setting screen.
- FIG. 12 is a screen displayed when the button arrangement order setting button 52 in FIG. 11 is pressed. For example, when there are three types of buttons having the button names “OK”, “Cancel”, and “Apply”, the user inputs the button names in the text boxes in the order in which they are to be arranged.
- the input unit 1 acquires screen information that defines the user interface of the screen to be inspected (step S12).
- the process of step S12 is the same as the process of step S1 in FIG.
- the inspection unit 2 acquires a check rule regarding consistency of the user interface from the check rule storage unit 3 and acquires setting contents from the option setting unit 5.
- the inspection unit 2 inspects whether the screen information acquired from the input unit 1 meets the inspection rule set by the check rule and option setting unit 5 (step S13).
- the inspection unit 2 performs an inspection by comparing another screen with a reference screen, the reference screen and the inspection target screen regarding the inspection items such as the button position, the text content, and the background or character color And compare.
- the inspection unit 2 inspects the screen based on the criteria.
- the display processing unit 4 displays items that do not conform to the check rule in the inspection (step S14).
- the process of step S14 is the same as the process of step S3 in FIG.
- the user interface consistency check device can inspect the screen according to the user's request because the user can freely customize the inspection method.
- FIG. FIG. 13 is a block diagram illustrating a configuration of a user interface consistency check device according to the third embodiment.
- the user interface consistency check device according to the present embodiment includes a batch execution unit 6 and a user interface consistency check unit 10. Since the configuration in the user interface consistency check unit 10 is the same as the configuration shown in the first embodiment, description thereof is omitted.
- the batch execution unit 6 causes the user interface consistency check unit 10 to execute processing on a file in which a program that realizes a screen to be inspected is described when a predetermined condition is satisfied.
- the batch execution unit 6 causes the user interface consistency check unit 10 to execute processing on screen information described in a source file such as HTML.
- the batch execution unit 6 automatically displays a screen to be inspected, automatically performs operations such as login and text input, and executes processing by the user interface consistency check unit 10 on the screen. Also good.
- FIG. 14 is a flowchart showing the operation of the user interface consistency check device of this embodiment. Note that the processing from step S23 to step S25 is the same as the processing from step S1 to step S3 of the first embodiment, and a detailed description thereof will be omitted.
- the user performs settings related to batch processing (step S21). Specifically, the user sets a storage destination of a program file (for example, HTML) that realizes a screen to be inspected. Further, the user sets a time for executing the batch processing.
- a program file for example, HTML
- the batch execution unit 6 When the preset execution time is reached (YES in step S22), the batch execution unit 6 causes the user interface consistency check unit 10 to execute processing on the program file that realizes the screen to be inspected (step S23 to step S22). S25).
- the batch execution unit 6 is not limited to the set time.
- the batch execution unit 6 may cause the user interface consistency check unit 10 to execute processing when a new update is made to the program file or a user operation. .
- FIG. 15 is an explanatory diagram illustrating an example of batch processing.
- a user saves a source file such as HTML from a client-side PC (Personal computer) to a server repository.
- the batch execution unit 6 causes the user interface consistency check unit 10 to execute processing on the program file that realizes the screen to be inspected.
- the inspection unit 2 performs inspection using only the source file without actually displaying the screen, and thus executable program files are limited.
- the inspection of the inspection unit 2 can be executed for HTML, but cannot be executed for jsp, php, cgi, and the like.
- FIG. 16 is an explanatory diagram showing another example of batch processing.
- the user saves a source file such as HTML from the client PC to the server repository.
- the batch execution unit 6 causes the simulation processing unit 20 of the server to deploy the screen to be inspected at a preset time.
- an automatic test tool disclosed in Non-Patent Document 2 is used.
- the simulation processing unit 20 of the server automatically displays a screen to be inspected, and automatically performs operations such as login and text input.
- the batch execution unit 6 causes the user interface consistency check unit 10 to execute processing using the program file that realizes the screen to be inspected and the screen information acquired from the displayed screen.
- the inspection unit 2 can inspect all the screens as in the case where the user manually performs the inspection.
- the user interface consistency check unit 10 of the present embodiment may include the option setting unit 5 described in the second embodiment. In that case, the user needs to set options before the batch is executed.
- the user interface consistency check device of the present embodiment for example, by setting the user to execute batch processing every night at night, it is possible to easily know problems in the development stage screen that is changed daily. be able to. Moreover, according to the user interface consistency check device of the present embodiment, it is possible to save the user from performing the inspection.
- FIG. 17 is a block diagram showing a configuration of a main part of the user interface consistency check device according to the present invention.
- An input unit 1 for acquiring screen information of a screen to be inspected, an inspection unit 2 for inspecting consistency of a screen user interface based on a predetermined check rule, and items that do not conform to the check rule are displayed.
- the user interface consistency check device described in the following (1) to (9) is also disclosed.
- a user interface consistency check device that inspects whether or not the user interface is consistent when the inspection unit (for example, the inspection unit 2) includes the same type of user interface in each screen of a plurality of screens.
- the user interface consistency check device may be configured such that the inspection unit inspects consistency regarding the layout.
- the user interface consistency check device may be configured such that the inspection unit inspects consistency regarding the display method of the current position in the application.
- the user interface consistency check device may be configured such that the inspection unit inspects consistency regarding a method of expressing a static part.
- the user interface consistency check device may be configured such that the inspection unit inspects consistency regarding the control component used for the interaction between the user and the computer.
- the user interface consistency check device may be configured such that the inspection unit inspects consistency regarding the user input operation method.
- the user interface consistency check device may be configured such that the inspection unit inspects consistency regarding an information presentation method with respect to a user operation.
- the user interface consistency check device includes an option setting unit (for example, option setting unit 5) for setting an inspection standard based on a user's selection, and the inspection unit is based on the check rule and the inspection standard.
- the screen information may be inspected. According to such an interface consistency check device, since the user can freely customize the inspection method, the screen can be inspected according to the user's wishes.
- the user interface consistency check device when a predetermined condition is satisfied, performs processing by the input unit (for example, the input unit 1), processing by the inspection unit (for example, the inspection unit 2), and display unit (for example, display processing). It may be configured to include a batch execution unit (for example, batch execution unit 6) for executing the processing by the unit 4). According to such an interface consistency check device, it is possible to save the user from performing the inspection.
- the present invention is used for checking the usability of the user interface of the WEB site.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computational Linguistics (AREA)
- General Health & Medical Sciences (AREA)
- Health & Medical Sciences (AREA)
- Audiology, Speech & Language Pathology (AREA)
- Artificial Intelligence (AREA)
- Software Systems (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Human Computer Interaction (AREA)
- User Interface Of Digital Computer (AREA)
- Debugging And Monitoring (AREA)
Abstract
Description
図9は、第2の実施形態のユーザインタフェース一貫性チェック装置の構成を示すブロック図である。図9において、入力部1、チェックルール記憶部3および表示処理部4の機能は、第1の実施形態と同じであるため、説明を省略する。
図13は、第3の実施形態のユーザインタフェース一貫性チェック装置の構成を示すブロック図である。図13に示すように、本実施形態のユーザインタフェース一貫性チェック装置は、バッチ実行部6とユーザインタフェース一貫性チェック部10とを備える。ユーザインタフェース一貫性チェック部10内の構成は、第1の実施形態に示した構成と同じであるため、説明を省略する。
図15は、バッチ処理の例を示す説明図である。利用者は、クライアント側のPC(Personal computer)からサーバのリポジトリにHTML等のソースファイルを保存する。そして、バッチ実行部6は、予め設定された時刻になると、検査対象となる画面を実現するプログラムファイルに対し、ユーザインタフェース一貫性チェック部10による処理を実行させる。図15に示す例では、検査部2は、実際に画面を表示させずにソースファイルのみを用いて検査を行うため、実行可能なプログラムファイルが限られる。例えば、検査部2の検査は、HTMLに関しては実行可能であるがjsp、php、cgi等には一部実行できない。
2 検査部
3 チェックルール記憶部
4 表示処理部
5 オプション設定部
6 バッチ実行部
Claims (14)
- 検査対象の画面の画面情報を取得し、
予め定められたチェックルールに基づいて、前記画面のユーザインタフェースの一貫性に関する検査を行い、
前記チェックルールに適合しない項目を表示する
ことを特徴とするユーザインタフェース一貫性チェック方法。 - 複数画面における各画面に同種のユーザインタフェースを含む場合に、当該ユーザインタフェースに一貫性があるかどうかを検査する
請求項1記載のユーザインタフェース一貫性チェック方法。 - レイアウトに関する一貫性を検査する
請求項1または請求項2記載のユーザインタフェース一貫性チェック方法。 - アプリケーションにおける現在位置に関する一貫性を検査する
請求項1から請求項3のうちのいずれか1項に記載のユーザインタフェース一貫性チェック方法。 - 静的な部品の表現方法に関する一貫性を検査する
請求項1から請求項4のうちのいずれか1項に記載のユーザインタフェース一貫性チェック方法。 - ユーザとコンピュータとのインタラクションに用いられるコントロール部品に関する一貫性を検査する
請求項1から請求項5のうちのいずれか1項に記載のユーザインタフェース一貫性チェック方法。 - ユーザの入力操作方法に関する一貫性を検査する
請求項1から請求項6のうちのいずれか1項に記載のユーザインタフェース一貫性チェック方法。 - ユーザの操作に対する情報提示の方法に関する一貫性を検査する
請求項1から請求項7のうちのいずれか1項に記載のユーザインタフェース一貫性チェック方法。 - 利用者の選択に基づいて、検査基準の設定を行い、
チェックルールおよび前記検査基準に基づいて画面情報の検査を行う
請求項1から請求項8のうちのいずれか1項に記載のユーザインタフェース一貫性チェック方法。 - 所定の条件が成立した場合、画面情報の取得処理、画面の検査処理および検査結果の表示処理を実行させる
請求項1から請求項9のうちのいずれか1項に記載のユーザインタフェース一貫性チェック方法。 - 検査対象の画面の画面情報を取得する入力部と、
予め定められたチェックルールに基づいて、前記画面のユーザインタフェースの一貫性に関する検査を行う検査部と、
前記チェックルールに適合しない項目を表示する表示処理部とを備えた
ことを特徴とするユーザインタフェース一貫性チェック装置。 - 検査部は、複数画面における各画面に同種のユーザインタフェースを含む場合、当該ユーザインタフェースに一貫性があるかどうかを検査する
請求項11記載のユーザインタフェース一貫性チェック装置。 - コンピュータに、
検査対象の画面の画面情報を取得する入力処理と、
予め定められたチェックルールに基づいて、前記画面のユーザインタフェースの一貫性に関する検査を行う検査処理と、
前記チェックルールに適合しない項目を表示する表示処理とを
実行させるためのユーザインタフェース一貫性チェックプログラム。 - コンピュータに、
検査処理で、複数画面における各画面に同種のユーザインタフェースを含む場合、当該ユーザインタフェースに一貫性があるかどうかを検査させる
請求項13記載のユーザインタフェース一貫性チェックプログラム。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2015506567A JP6045050B2 (ja) | 2013-03-19 | 2014-01-10 | ユーザインタフェース一貫性チェック方法、装置およびプログラム |
US14/778,304 US20160283072A1 (en) | 2013-03-19 | 2014-01-10 | User-interface consistency-checking method, device and program |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2013056651 | 2013-03-19 | ||
JP2013-056651 | 2013-03-19 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2014147924A1 true WO2014147924A1 (ja) | 2014-09-25 |
Family
ID=51579633
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2014/000085 WO2014147924A1 (ja) | 2013-03-19 | 2014-01-10 | ユーザインタフェース一貫性チェック方法、装置およびプログラム |
Country Status (3)
Country | Link |
---|---|
US (1) | US20160283072A1 (ja) |
JP (1) | JP6045050B2 (ja) |
WO (1) | WO2014147924A1 (ja) |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE102017004348A1 (de) * | 2017-05-08 | 2018-11-08 | Gerhard Schilling | Verfahren zur Computer gestützten, automatisierten Überprüfung von Software-Anforderungen |
CN108614775A (zh) * | 2018-05-03 | 2018-10-02 | 深圳Tcl新技术有限公司 | 自动化测试方法、装置、终端设备及计算机可读存储介质 |
KR102489118B1 (ko) * | 2022-05-12 | 2023-01-18 | 주식회사 미코명진 | 금형 리프터 |
KR102491453B1 (ko) * | 2022-05-13 | 2023-01-26 | 주식회사 미코명진 | 금형 리프터 |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH08241191A (ja) * | 1995-03-02 | 1996-09-17 | Matsushita Electric Ind Co Ltd | Gui自動評価装置 |
Family Cites Families (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2998652B2 (ja) * | 1996-09-20 | 2000-01-11 | 日本電気株式会社 | Gui画面レイアウト設計方式 |
US7231606B2 (en) * | 2000-10-31 | 2007-06-12 | Software Research, Inc. | Method and system for testing websites |
US8392890B2 (en) * | 2007-10-15 | 2013-03-05 | Software Research, Inc. | Method and system for testing websites |
US8429601B2 (en) * | 2007-11-29 | 2013-04-23 | Red Hat, Inc. | Code completion for object relational mapping query language (OQL) queries |
US20100058185A1 (en) * | 2008-08-28 | 2010-03-04 | International Business Machines Corporation | Dynamic hints for gui control modes contingent upon context-defined conditions |
WO2010035388A1 (ja) * | 2008-09-29 | 2010-04-01 | 日本電気株式会社 | Gui評価システム、gui評価方法およびgui評価用プログラム |
US8402319B2 (en) * | 2010-09-30 | 2013-03-19 | Fujitsu Limited | Method and system to extract a navigation model for analysis of a web application |
US9841956B2 (en) * | 2011-01-31 | 2017-12-12 | Sap Se | User interface style guide compliance reporting |
US9323418B2 (en) * | 2011-04-29 | 2016-04-26 | The United States Of America As Represented By Secretary Of The Navy | Method for analyzing GUI design affordances |
US9134969B2 (en) * | 2011-12-13 | 2015-09-15 | Ipar, Llc | Computer-implemented systems and methods for providing consistent application generation |
JP5629722B2 (ja) * | 2012-04-11 | 2014-11-26 | 京セラドキュメントソリューションズ株式会社 | 表示入力装置及びこれを備えた画像形成装置 |
US20140160049A1 (en) * | 2012-12-10 | 2014-06-12 | Samsung Electronics Co., Ltd. | Clipboard function control method and apparatus of electronic device |
US9547422B2 (en) * | 2014-03-07 | 2017-01-17 | Blackberry Limited | System and method for capturing notes on electronic devices |
-
2014
- 2014-01-10 WO PCT/JP2014/000085 patent/WO2014147924A1/ja active Application Filing
- 2014-01-10 JP JP2015506567A patent/JP6045050B2/ja active Active
- 2014-01-10 US US14/778,304 patent/US20160283072A1/en not_active Abandoned
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH08241191A (ja) * | 1995-03-02 | 1996-09-17 | Matsushita Electric Ind Co Ltd | Gui自動評価装置 |
Non-Patent Citations (1)
Title |
---|
TERUYA IKEGAMI: "Development of Quantitative Usability Evaluation Method", PAPER OF HUMAN INTERFACE SOCIETY, vol. 14, no. 1, 27 February 2012 (2012-02-27), pages 101 - 110 * |
Also Published As
Publication number | Publication date |
---|---|
US20160283072A1 (en) | 2016-09-29 |
JPWO2014147924A1 (ja) | 2017-02-16 |
JP6045050B2 (ja) | 2016-12-14 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9772978B2 (en) | Touch input visualizations based on user interface context | |
US20140115459A1 (en) | Help system | |
JP6045050B2 (ja) | ユーザインタフェース一貫性チェック方法、装置およびプログラム | |
Varaksin | PrimeFaces Cookbook | |
Xu et al. | A pilot study of an inspection framework for automated usability guideline reviews of mobile health applications | |
KR20110060419A (ko) | 자바스크립트를 이용한 웹 기반 소프트웨어 생성 장치 및 방법 | |
US10095528B2 (en) | Interfacing systems and methods | |
JP6774862B2 (ja) | プログラム、制御装置、および情報記憶媒体 | |
US11704126B2 (en) | Non-transitory recording medium having computer-readable program recorded thereon, server apparatus, function graph display control apparatus, and function graph display control method | |
US20130174013A1 (en) | Wiki monitoring and updating | |
WO2014147923A1 (ja) | ユーザビリティチェック結果出力方法、装置およびプログラム | |
JP2020197997A (ja) | 情報処理装置、方法及びプログラム | |
JP6068639B2 (ja) | ユーザインタフェース検査方法、装置およびプログラム | |
JP2019204357A (ja) | 設定装置、設定方法及び設定プログラム | |
Çalışkan et al. | PrimeFaces cookbook | |
WO2016092626A1 (ja) | 開発支援システム | |
Czerniak et al. | The Influence of task-oriented human-machine interface design on usability objectives | |
US11113359B1 (en) | Method and system for navigation control | |
JP2016162385A (ja) | 手順情報表示装置、手順情報表示方法およびプログラム | |
Freeman et al. | Overview of MVC Projects | |
Wesley et al. | Browser Tools | |
Bowden | Visualforce Development Cookbook | |
JP2022051276A (ja) | コンピュータプログラム、仕様出力装置、及びプログラムの製造方法 | |
JP2013206263A (ja) | 試験手順作成装置及びプログラム | |
JP2016001382A (ja) | ウェブページ提供システム、ウェブページ提供方法、プログラム及び通信装置 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 14767959 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2015506567 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 14778304 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 14767959 Country of ref document: EP Kind code of ref document: A1 |