Classifications

• • 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 methods and apparatuses for generating a user interface model, and more particularly, to methods and apparatuses for generating a user interface model which develop a user interface model to be simultaneously applicable to various platforms and thus are efficient in terms of the length of a development period and human resources and can effectively perform a test.
• Background Art
• GUI Graphic User Interface
• Typical GUI technology is What You See Is What You Get (WYSIWYG), whereby an output result the same as the content that a user is currently viewing on a screen can be obtained. Since a user works while watching an object to be actually printed, he/she can know ahead of time what will be printed. In other words, it is possible to work while checking editing or a format of a document on a screen using a document editor.
• the WYSIWYG function is absolutely necessary for editing systems using a computer as well as document editors.
• the composition of a document has to be appropriately defined. For example, when a user writes a document using a common document editor, he/she may insert a space between lines and in the head of paragraphs to distinguish one paragraph from another, enlarge the character size of a sentence at the beginning of a new chapter or paragraph, and appropriately position a picture or diagram.
• These composition works are for estimating a print result before objects seen from a screen are printed.
• the present invention is directed to methods of generating a user interface model which is applicable to various platforms and can reduce a development time and test time taken for developing a user interface according to the various platforms.
• the present invention is also directed to apparatuses for generating a user interface model which is applicable to various platforms and can reduce a development time and test time taken for developing a user interface according to the various platforms.
• One aspect of the present invention provides a method of generating a user interface model applicable to various platforms, the method including editing an organization formed by defining at least one user interface screen constituting a user interface and at least one resource constituting the user interface screen in a tree shape; editing a flow including a transition condition between the at least one user interface screen constituting the user interface and a relationship between the at least one resource constituting the user interface screen; and editing a platform-specific layout defining a position of a resource in the at least one user interface screen constituting the user interface according to at least one platform.
• the editing the platform-specific layout may include selecting at least one user interface screen constituting the user interface; selecting at least one platform to which the user interface will be applied; selecting a standard platform to be a direct editing object from the at least one platform; positioning resources constituting the editing- object user interface screen according to the standard platform; and synchronously positioning resources constituting a user interface screen corresponding to a platform other than the standard platform among the at least one platform according to positions of the resources positioned in positioning the resources constituting the editing-object user interface screen and constituting the editing-object user interface screen, and supporting simultaneous editing.
• the editing the platform-specific layout may include performing desynchronization to select one platform to which the user interface will be applied, selecting one user interface screen constituting the user interface to be applied only to the selected platform, and positioning resources constituting the user interface screen.
• the method may further include testing the generated user interface model.
• the testing the generated user interface model may include generating a test case using a flowchart and a statechart corresponding to a user interface model generated using the method of generating a user interface model; verifying the test case and generating the verified test case; receiving information on a platform corresponding to the generated user interface model and generating platform profiling information; converting the verified test case into a program code for simulation with reference to the platform profiling information; and performing a simulation using the program code for simulation in an actual or virtual test environment.
• an organization editor configured to edit an organization formed by defining at least one user interface screen constituting a user interface and at least one resource constituting the user interface screen in tree shape
• a flow editor configured to edit a flow including a transition condition between the at least one user interface screen constituting the user interface and a relationship between the at least one resource constituting the user interface screen
• a layout editor configured to edit a platform-
• the layout editor may include an editing-object screen selector configured to select at least one user interface screen constituting the user interface, an editing-object platform selector configured to select at least one platform to which the user interface will be applied, a standard platform selector configured to select a standard platform to be a direct editing- object from the at least one platform, a position editor configured to position resources constituting the editing-object user interface screen according to the standard platform, and a synchronizer configured to synchronously position resources constituting a user interface screen corresponding to a platform other than the standard platform among the at least one platform according to positions of the resources positioned by the position editor and constituting the editing-object user interface screen, and thereby support simultaneous editing.
• an editing-object screen selector configured to select at least one user interface screen constituting the user interface
• an editing-object platform selector configured to select at least one platform to which the user interface will be applied
• a standard platform selector configured to select a standard platform to be a direct editing- object from the at least one platform
• a position editor configured to position resources
• the layout editor may include a desynchronizer configured to perform desynchro- nization to select one platform to which the user interface will be applied, select one user interface screen constituting the user interface to be applied only to the selected platform, and position resources constituting the user interface screen.
• the apparatus may further include a simulator configured to test the generated user interface model.
• the simulator may include a test case generator configured to generate a test case using a flowchart and a statechart corresponding to a user interface model generated by the apparatus for generating a user interface model, a test case verifier configured to verify the test case and generate a verified test case, a platform profiler configured to receive information on a platform corresponding to the generated user interface model and generate platform profiling information, a mapper configured to convert the verified test case into a program code for simulation with reference to the platform profiling information, and a simulation executor configured to perform a simulation using the program code for simulation in an actual or virtual test environment.
• a test case generator configured to generate a test case using a flowchart and a statechart corresponding to a user interface model generated by the apparatus for generating a user interface model
• a test case verifier configured to verify the test case and generate a verified test case
• a platform profiler configured to receive information on a platform corresponding to the generated user interface model and generate platform profiling information
• a mapper configured to
• the user interface model generation methods and apparatuses supporting multiple platforms according to example embodiments of the present invention can perform modeling using a high-productivity method according to the preference of a developer. For example, resources can be easily allocated using a tree-shaped organization editing step and editor, and a transition condition between screens can be defined using a graphic-based flow editing step and editor.
• the user interface model generation method and apparatus can easily generate a model capable of operating on various platforms. For example, even when a screen is edited according to one platform layout in/by a layout editing step and editor, an appropriate screen for another platform is automatically generated. If a slightly different layout has to be set for another platform, it is possible to disable a synchronization setting and edit a specialized setting.
• the user interface model generation method and apparatus provide an efficient test method in the development step. It is possible to immediately perform a test through, for example, a simulation step and executor in an actual or virtual test environment.
• FIG. 1 is a flowchart illustrating a method of generating a user interface model applicable to various platforms according to an example embodiment of the present invention.
• FIGs. 2 to 6 illustrate examples of user interface screens edited in an organization editing step and a flow editing step constituting the method of generating a user interface model applicable to various platforms.
• Fig. 7 illustrates an example of an organization defined in the shape of a tree according to the method of generating a user interface model applicable to various platforms.
• FIGs. 8 and 9 are conceptual diagrams illustrating a flow editing step constituting the method of generating a user interface model applicable to various platforms.
• FIG. 10 is a flowchart illustrating a layout editing step constituting the method of generating a user interface model applicable to various platforms.
• FIG. 11 to 13 illustrate examples of a user interface screen edited in a position editing step of a layout editing step.
• FIG. 14 is a flowchart illustrating a simulation step constituting the method of generating a user interface model applicable to various platforms.
• Figs. 15 to 17 illustrate examples of a flow chart, a statechart and a platform profile used in the simulation step.
• FIG. 18 is a block diagram of an apparatus for generating a user interface model applicable to various platforms according to an example embodiment of the present invention.
• Fig. 19 is a block diagram of a layout editor constituting the apparatus for generating a user interface model applicable to various platforms.
• FIG. 20 is a block diagram of a simulator constituting the apparatus for generating a user interface model applicable to various platforms.
• FIG. 1 is a flowchart illustrating a method of generating a user interface model applicable to various platforms according to an example embodiment of the present invention.
• the method of generating a user interface model applicable to various platforms may include an organization editing step (Sl 10), a flow editing step (S 120), a layout editing step (S 130) and a simulation step (S 140).
• the organization editing step (Sl 10) may be a step of editing an organization formed by defining at least one user interface screen constituting a user interface and at least one resource constituting the user interface screen in a tree shape.
• the flow editing step (S 120) may be a step of editing a flow including a transition condition between the at least one user interface screen constituting the user interface and a relationship between the at least one resource constituting the user interface screen.
• the layout editing step (S 130) may be a step of editing a layout defining a position of the resource in the at least one user interface screen constituting the user interface according to at least one platform.
• the simulation step (S 140) may be a step of testing a user interface model generated through the organization editing step, the flow editing step and the layout editing step.
• FIGs. 2 to 6 illustrate examples of user interface screens edited in the organization editing step and the flow editing step constituting the method of generating a user interface model applicable to various platforms.
• the method of generating a user interface model applicable to various platforms will be described below with reference to Figs. 2 to 6.
• Fig. 2 illustrates an example of a main screen according to the method of generating a user interface model, and shows a main screen of a mobile communication terminal that is one of user interface screens constituting a user interface model according to an example embodiment of the present invention.
• the main screen may have four resources that can lead to sub-screens, and also may display a resource configuring a background, a resource displaying a charge level of a battery, a resource displaying a message receiving state, and so on.
• Fig. 3 illustrates an example of a sound screen to be shown after screen transition when "Sound" is selected from among the four resources that can lead to sub-screens in the main screen.
• the sound screen may also have three resources that can lead to three sub-screens and display resources such as a background, as in the main screen.
• Fig. 4 illustrates an example of a sub-screen to be shown after screen transition when
• “Screen” is selected from among the four resources that can lead to sub-screens in the main screen.
• the sub-screen may also have two resources that can lead to two sub- screens and display resources such as a background, as in the main screen.
• Fig. 5 illustrates an example of a message screen to be shown after screen transition when "Message" is selected from among the four resources that can lead to sub- screens in the main screen.
• the message screen may also have two resources that can lead to two sub-screens, and display resources such as a background, as in the main screen.
• Fig. 6 illustrates an example of a moving picture screen to be shown after screen transition when "Moving picture" is selected from among the four resources that can lead to sub-screens in the main screen.
• the moving picture screen may have a resource of a background, and also have resources of a moving picture display screen, a play button, a pause button and a stop button.
• a moving picture may be displayed according to a selection from the resources.
• Fig. 7 illustrates an example of an organization defined in the shape of a tree according to the method of generating a user interface model applicable to various platforms.
• the organization editing step (Sl 10) may be a step of editing an organization formed by defining at least one user interface screen constituting a user interface and at least one resource constituting the user interface screen in a tree shape. Respective resources may be an icon, text, sound, dialog box, event, etc., constituting a screen.
• a main screen may lead to a "Sound” screen, a "Sub-screen” screen, a “Message” screen and a “Moving picture” screen according to a selection of the resource constituting the main screen.
• the "Sound” screen may lead to a "Ring tone” setting screen, a “Ring/Vibration” setting screen and a “Volume” setting screen according to a selection of the resource constituting the "Sound” screen.
• the "Sub-screen” screen may lead to a “Standby screen” setting screen and a “Background” setting screen according to a selection of the resource constituting the "Sub-screen” screen.
• the "Message” screen may lead to a “Message box” screen and a “Message writing” screen according to a selection of the resource constituting the "Message” screen.
• the "Moving picture” screen may have resources of a moving picture display screen, a moving picture play button, a pause button and a stop button.
• FIGs. 8 and 9 are conceptual diagrams illustrating the flow editing step (S 120) constituting the method of generating a user interface model applicable to various platforms.
• the flow editing step (S 120) may be a step of editing a flow including a transition condition between at least one user interface screen constituting a user interface and a relationship between at least one resource constituting the user interface screen.
• the transition condition of resources may include anything that may cause a transition from one screen to another screen, such as a selection of an icon indicating the corresponding resource.
• Relationships between user interface screens and resources constituting the user interface screens may include a relationship in which when an icon corresponding to the resource is selected, another resource is changed, and so on.
• Fig. 8 illustrates an example of a transition condition between screens in the flow editing step.
• Fig. 8 shows a transition condition whereby the main screen is changed into the "Sound” screen when "Sound” is selected from among four resources having transition conditions.
• Fig. 9 illustrates an example of a relationship between screens and resources defined in the flow editing step.
• the "Play” button is selected from among the four resources having transition conditions in the "Moving picture” screen
• a moving picture is played in the moving picture display screen according to a relationship between resources.
• the "Pause” button is selected while a moving picture is being played, the moving picture display screen pauses.
• the "Stop” button is selected while a moving picture is being played, play of the moving picture is stopped, and a blank is shown in the moving picture display screen.
• Fig. 10 is a flowchart illustrating the layout editing S 130 constituting the method of generating a user interface model applicable to various platforms.
• the layout editing step (S 130) may be a step of editing a layout defining a position of a resource in the at least one user interface screen constituting a user interface according to at least one platform.
• the layout editing step (S 130) may include an editing-object screen selection step (S 131), an editing-object platform selection step (S 132), a standard platform selection step (S 133), a position editing step (S 134) and a synchronization step (S 135).
• a desynchronization step (S 136) may be included in the layout editing step only when independent screen configuration is needed according to a selection of a user.
• the editing-object screen selection step (S 131) may be a step of selecting at least one user interface screen constituting the user interface.
• the editing-object platform selection step (S132) may be a step of selecting all platforms, to which the user interface selected in the editing-object screen selection step (S 131) will be applied, and determining the platform in which a layout editing result is reflected in the synchronization step.
• the standard platform selection step (S 133) may be a step of selecting a standard platform to be a direct editing object from the at least one platform, and determining one platform in which layout editing will be reflected.
• the position editing step (S 134) may be a step of positioning resources constituting the editing-object user interface screen according to the selected standard platform.
• the synchronization step (S 135) may be a step of synchronously positioning resources constituting a user interface screen corresponding to a platform other than the standard platform among all the selected platforms according to positions of the resources which are positioned in the position editing step (S 134) and constitute the editing-object user interface screen.
• the desynchronization step (S 136) may be a step of performing desynchronization to select one platform to which the user interface will be applied, selecting one user interface screen constituting the user interface, and positioning resources constituting a user interface screen applied only to the selected screen that will be applied to the selected platform.
• an additional user interface screen to be applied only to a selected platform is configured, and thus it is possible to configure a creative screen to be applied only to the selected platform.
• FIG. 11 to 13 illustrate examples of the position editing step of the layout editing step.
• Fig. 11 illustrates a screen in which a play screen is positioned on the upper side
• Fig. 12 illustrates a screen in which a play screen is positioned on the lower side
• Fig. 13 illustrates a screen in which a play screen is positioned on the right side.
• it may be determined whether or not a user interface screen can interest a user, and also resources may be favorably positioned in the user interface screen.
• Fig. 14 is a flowchart illustrating the simulation tep (S 140) constituting the method of generating a user interface model applicable to various platforms.
• the simulation step (S 140) may be a step of testing a user interface model generated through the organization editing step (Sl 10), the flow editing step (S 120) and the layout editing step (S 130).
• Fig step (S140) may include a test case generation step (S141), a test case verification step (S 142), a platform profiling step (S 143), a mapping step (S 144) and a simulation step (S 145).
• the test case generation step (S 141) is a step of generating a test case using a flowchart and a statechart corresponding to a user interface model generated using the method of generating a user interface model.
• the test case generation step (S 141) may include an input step (S 141-1) of receiving a flowchart and a statechart of test-object software, an analysis step (S 141-2) of analyzing flows that can be derived from the flowchart and state transition cases that can be derived from the statechart, and a generation step (S 141-3) of generating a test case corresponding to the numbers of the flows and state transition cases. Additionally, an editing step (S 141-4) of separately editing the generated test case using an editor may be included.
• Fig. 15 illustrates an example of a flowchart input in the test case generation step of the simulation step.
• FIG. 15 a process of analyzing all flows from a flowchart of a test-object program from which a test case is generated in the test case generation step (S 141) is illustrated.
• Fig. 15 is a flowchart of the program showing branches from a main screen to other screens, which shows possible paths from the main screen to a sound screen, a message screen or a moving picture screen.
• the number of all flows derived from the flowchart of Fig. 15 is 3.
• test-object software shown as an example in Fig. 15, a statechart of the test-object software may be used for generating a test case in the test case generation step (S 141).
• Fig. 16 illustrates an example of a statechart input in the test case generation step
• Fig. 16 illustrates a state and changed states of respective resources of a test-object program.
• Fig. 16 may be "Main screen ⁇ Sound screen”, “Main screen ⁇ Message screen” and “Main screen ⁇ Moving picture screen”.
• testcase generation step (S 141) a test case may be generated in consideration of the numbers of all flows and state transition cases derived from the flowchart and statechart shown as examples in Figs. 15 and 16.
• the test case verification step (S 142) may be a step of verifying the generated test case and generating the verified test case.
• the test case verification step (S 142) may include a repetition removal step (S 142-1) of removing a repeated subtest case from at least one subtest case constituting the test case, and an impossible achievement removal step (S 142-2) of removing a subtest case resulting in a state that cannot be achieved from at least one subtest case constituting the test case.
• FIG. 17 illustrates an example of platform profiling information required for the platform profiling step (S 143) in the simulation step.
• the platform profiling step (S 143) may be a step of receiving information on a platform corresponding to a generated user interface model and generating platform profiling information.
• the platform profiling information may be all information, such as a screen size, a screen color, a memory capacity, a data file format, etc., expressing the corresponding platform.
• the platform profiling information generated in the platform profiling step (S 143) is used for converting the test case into a program code for simulation in the mapping step (S 144).
• the mapping step (S 144) may be a step of converting the verified test case into a program code for simulation with reference to the platform profiling information corresponding to the platform.
• the simulation step (S 145) may be a step of performing a simulation using the program code for simulation in an actual or virtual test environment to perform a test.
• the step (S 145) may include a step (S 145-2) of storing, in a snapshot database, a snapshot of a user interface screen of the test-object software as a state of the test- object software changed according to performance of the simulation, and a step (S145-1) of outputting and storing a test result after performing the simulation.
• FIG. 18 is a block diagram of an apparatus 500 for generating a user interface model applicable to various platforms according to an example embodiment of the present invention.
• the apparatus for generating a user interface model may include an organization editor 510, a flow editor 520, a layout editor 530 and a simulator 540.
• the organization editor 510 may edit an organization formed by defining at least one user interface screen constituting a user interface and at least one resource constituting the user interface screen in a tree shape.
• the flow editor 520 may edit a flow including a transition condition between the at least one user interface screen constituting the user interface and a relationship between the at least one resource constituting the user interface screen.
• the layout editor 530 may edit a platform- specific layout defining a position of the resource in the at least one user interface screen constituting the user interface according to at least one platform.
• the simulator 540 may be a component that is additionally provided to the apparatus
• the apparatus 500 for generating a user interface model to test the generated user interface model may be configured to include the component.
• the user interface and a storage device existing out of the apparatus 500 for generating a user interface model applicable to various platforms are external devices not included in an example embodiment of the present invention.
• FIG. 19 is a block diagram of the layout editor 530 constituting the apparatus for generating a user interface model applicable to various platforms.
• the layout editor 530 may include an editing-object screen selector 531, an editing- object platform selector 532, a standard platform selector 533, a position editor 534 and a synchronizer 535.
• the layout editor 530 may further include a desyn- chronizer 536 for a user interface screen to be applied only to a specific platform.
• the editing-object screen 531 may select at least one user interface screen constituting a user interface.
• the editing-object platform selector 532 may select at least one platform to which the user interface will be applied.
• the standard platform selector 533 may select a standard platform to be a direct editing object from the at least one platform.
• the position editor 534 may position resources constituting the editing-object user interface screen according to the standard platform.
• the synchronizer 535 may synchronously position resources constituting a user interface screen corresponding to a platform other than the standard platform among the at least one platform according to positions of the resources constituting the editing-object user interface screen and positioned in the position editing step.
• the desynchronizer 536 may perform desynchronization to select one platform to which the user interface will be applied, select one user interface screen constituting the user interface to be applied only to the selected platform, and position resources constituting the user interface screen.
• Fig. 20 is a block diagram of the simulator 540 constituting the apparatus for generating a user interface model applicable to various platforms.
• the simulator 540 may include a test case generator 541, a test case verifier 542, a platform profiler 543, a mapper 544 and a simulation executor 545.
• the test case generator 541 may generate a test case using a flowchart and a statechart corresponding to a user interface model generated using a method of generating a user interface model.
• the test case verifier 542 may verify the test case and generate the verified test case.
• the platform profiler 543 may receive information on a platform corresponding to the generated user interface model and generate platform profiling information.
• the mapper 544 may convert the verified test case into a program code for simulation.
• the simulation executor 545 may perform a simulation using the program code for simulation in an actual or virtual test environment.
• a user interface and a storage device existing out of the simulator 540 are external devices not included in an example embodiment of the present invention.

Landscapes

• Engineering & Computer Science (AREA)
• Software Systems (AREA)
• General Engineering & Computer Science (AREA)
• Theoretical Computer Science (AREA)
• Human Computer Interaction (AREA)
• Physics & Mathematics (AREA)
• General Physics & Mathematics (AREA)
• User Interface Of Digital Computer (AREA)

Priority Applications (2)

Applications Claiming Priority (1)

Publications (1)

Family

ID=40885461

Family Applications (1)

Country Status (2)

Cited By (2)

Families Citing this family (1)

Citations (5)

Family Cites Families (6)

• 2008
  • 2008-01-15 JP JP2010543035A patent/JP5199393B2/ja not_active Expired - Fee Related
  • 2008-01-15 WO PCT/KR2008/000258 patent/WO2009091088A1/en active Application Filing

Patent Citations (5)

Also Published As

Similar Documents

Legal Events