Graphical modelization of user interfaces for data intensive applications

• US 8,458,648 B2
• Filed: 12/02/2008
• Issued: 06/04/2013
• Est. Priority Date: 12/10/2007
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Dangeville, Nicolas, Matusiak, Thierry
• Primary Examiner(s): Zhen, Wei
• Assistant Examiner(s): Wu, Junchun
• Application Number:
  US12/326,614
• Publication Number:
  US 20090235229A1
• Time in Patent Office: 1,645 Days
• Field of Search: 717/105
• US Class Current: 717/105
• CPC Class Codes: G06F 8/10 Requirements analysis; Specification techniques
• CPC Class Codes: G06F 8/38 for implementing user interfaces

Abstract

A method, computer program product and system for creating class diagrams of user interfaces of applications. A modeling language such as UML V2.0 may be used to create class diagrams through a graphical editor, create new model elements derived from existing ones such as stereotypes for creating a comprehensive class diagram for the user interface. The class diagram for the user interface is based on a limited number of stereotyped classes for pages, views in the pages of the user interface, operations in the view classes and class for services triggered by the operations. The user interface class diagram is attached to the application class through the classes of the application for data manipulated by the user interface. A sequence diagram reflecting the correlation between view operation and services is also created to complete the description of the user interface.

Claims

1. A method comprising:

a computer selecting graphical user interface elements for insertion into a model, the model defined using Unified Modeling Language, wherein the graphical user interface elements comprise;

a DataObject class type, describing a structure of data manipulated through a user interface;

three view class types depending from a first class type, SearchView describing data to be searched, ListView describing data to be listed and DetailView describing data content to be detailed through the user interface;

a Page class type depending on the view class types describing a page of the user interface;

an ActionTrigger operation type describing an action triggered from a view class type;

a Service class type describing operations where at least one operation is triggered by an ActionTrigger operation type;

the computer applying the DataObject class type to data already described in an existing class diagram, said data being manipulated through a user interface; and

the computer creating a class diagram of the user interface using new types of model elements, wherein the Unified Modeling Language includes the new types of model elements to provide a graphical object model of the user interface in the Unified Modeling Language.

2. The method of claim 1 further comprising, after the step of the computer creating new types of model elements:

the computer applying the Service class type to the classes already described in the existing class diagram containing one operation to be triggered through the user interface.

3. The method of claim 1 further comprising:

the computer graphically representing as a flow diagram;

each operation of the ActionTrigger type of the view classes;

at least one operation of a class of Service type which is triggered by an operation of ActionTrigger type; and

view classes which are opened depending on a result of an execution of the at least one operation of a class of Service.

4. The method of claim 1, wherein the steps of creating the class diagram of the user interface using the new types of model elements is automatically performed by the computer, the user providing input pattern parameters.

5. The method of claim 1 wherein the existing class diagram uses the Unified Modeling Language, and wherein the steps performed for creation of the new types of model elements use stereotyping of elements in the Unified Modeling Language.

6. The method of claim 5 wherein the flow diagram is a sequence diagram using the Unified Modeling Language.

7. The method of any one of claim 3 wherein the step of creating the class diagram of the user interface is automatically performed by the computer executing IBM Rational Software Architect version 6 or 7, the user providing a pattern for each Page class and each ActionTrigger operation.

8. A non-transitory computer program product comprising:

one or more computer readable storage mediums;

computer program instructions stored in at least one computer readable storage medium for selecting graphical user interface elements for insertion into a model, the model defined using Unified Modeling Language, wherein the graphical user interface elements comprise;

a DataObject class type, describing a structure of data manipulated through the user interface;

three view class types depending from a first class type, SearchView describing data to be searched, ListView describing data to be listed and DetailView describing data content to be detailed through the user interface;

a Page class type depending on the view class types describing a page of the user interface;

an ActionTrigger operation type describing an action triggered from a view class type;

a Service class type describing operations where at least one operation is triggered by an ActionTrigger operation type;

the user computer program instructions stored in at least one computer readable storage medium for applying the DataObject class type to data already described in an existing class diagram, said data being manipulated through a user interface; and

computer program instructions stored in at least one computer readable storage medium for creating a class diagram of the user interface using the new created types of model elements, said class diagram of the user interface, wherein the Unified Modeling Language includes the new types of model elements to provide a graphical object model of the user interface in the Unified Modeling Language.

9. A system comprising means

one or more processors, one or more computer readable memories, and one or more computer readable storage mediums;

computer program instructions stored in at least one computer readable storage medium for execution by at least one processor via at least one computer readable memory for selecting graphical user interface elements for insertion into a model, the model defined using Unified Modeling Language, wherein the graphical user interface elements comprise;

a DataObject class type, describing a structure of data manipulated through the user interface;

three view class types depending from a first class type, SearchView describing data to be searched, ListView describing data to be listed and DetailView describing data content to be detailed through the user interface;

a Page class type depending on the view class types describing a page of the user interface;

an ActionTrigger operation type describing an action triggered from a view class type;

a Service class type describing operations where at least one operation is triggered by an ActionTrigger operation type;

computer program instructions stored in at least one computer readable storage medium for execution by at least one processor via at least one computer readable memory for applying the DataObject class type to data already described in the existing class diagram, said data being manipulated through a user interface; and

computer program instructions stored in at least one computer readable storage medium for execution by at least one processor via at least one computer readable memory for creating a class diagram of the user interface using new created types of model elements, said class diagram of the user interface, wherein the Unified Modeling Language includes the new types of model elements to provide a graphical object model of the user interface in the Unified Modeling Language.