Modeling system for graphic user interface
View Patent ↗A modeling system for universal specification of user interfaces. The system provides a means for defining user interfaces, including highly complex and dynamic user interfaces, in a manner that is independent of any implementation context. The modeling system leads from a user-friendly visual representation of the user interface, through progressively detailed specifications of structural and behavioral aspects of the user interface parts, until a rigorous definition of the user interface in all its contexts of use is achieved. Using the information captured in the model, tools that automatically generate the fully working user interface code can be built.
1. A method for generating a user interface in a distributed computer system, the method comprising:
displaying a first business function component selected by a first user on a first display area of a frontend system, the first business function component being associated with first application logic to access a first business application provided in a server system;
displaying a second business function component selected by the first user on the first display area of the client system, the second business function component being associated with second application logic to access a second business application provided in the server system;
forming a relationship between the first and second business function components, wherein a visual representation of the user interface is created based on the displaying steps and the forming step;
generating a canonic representation of the visual representation; and
generating an executable user interface code from the canonic representation, the user interface code being operable to access the first and second applications provided in the server system to retrieve desired data.
2. The method of claim 1 , further comprising:
storing the user interface code in a repository in the server system,
wherein the first and second business applications are different applications.
3. The method of claim 1 , wherein the visual representation includes a third business function component that specifies a presentation format, the method further comprising:
storing the user interface code in a repository associated with the server system; and
receiving a request to access the user interface code from a second user, wherein the user interface code is executed in response to the request, the code being used to access the first and second applications provided in the server system to retrieve data desired by the second user, wherein the data retrieved for the second user is displayed on a second display area of the client system according to presentation format specified by the third business function component, the first and second display areas being associated with different client systems.
4. The method of claim 1 , further comprising:
storing a first identifier for the first business function component in the client system in conjunction with the displaying-a-first-business-function-component step; and
storing a second identifier for the second business function component in the client system in conjunction with the displaying-a-second-business-function-component step,
wherein the first and second identifiers are used subsequently at a runtime to access the first and second application logics, respectively.
5. The method of claim 4 ,
wherein the first and second identifiers are inserted in the canonic representation.
6. The method of claim 5 , wherein the canonic representation is based on an XML-based language, wherein the first and second applications may be the same application or different applications.
7. The method of claim 5 , wherein the executable user interface code is a first executable user interface code, the method further comprising:
generating a second executable user interface code from the canonic representation, the second user interface code being operable to access the first and second applications provided in the server system to retrieve desired data,
wherein the first code is compatible with a first platform and the second code is compatible with a second platform that is different from the first platform.
8. The method of claim 1 , further comprising:
associating an operator to the second business function component; and
connecting an output port of the second business function component to an input port of the operator.
9. The method of claim 8 ,
wherein the generated code does not require verification.
10. The method of claim 9 , wherein the generated code does not require a performance tuning.
11. A non-transitory computer readable medium comprising a computer program, that when executed on a computer processor, causes the computer processor to:
display a first business function component selected by a first user on a first display area, the first business function component being associated with first application logic to access a first business application;
display a second business function component selected by the first user on the first display area, the second business function component being associated with second application logic to access a second business application;
form a relationship between the first and second business function components, wherein a visual representation of a user interface is created based on the display steps and the form step;
generate a canonic representation of the visual representation; and
generate an executable user interface code from the canonic representation, the user interface code being operable to access the first and second applications to retrieve desired data.
12. The non-transitory computer readable medium of claim 11 , wherein the computer program further causes the computer processor to:
store the user interface code in a repository; and
receive a request to access the user interface code from a second user, wherein the user interface code is executed in response to the request, the code being used to access the first and second applications to retrieve data desired by the second user, wherein the data retrieved for the second user is displayed on a second display area according to presentation format specified by the third business function component.
13. The non-transitory computer readable medium of claim 11 , wherein the computer program further causes the computer processor to:
store a first identifier for the first business function component; and
store a second identifier for the second business function component,
wherein the first and second identifiers are used subsequently at a runtime to access the first and second application logics, respectively.
14. The non-transitory computer readable medium of claim 13 ,
wherein the first and second identifiers are inserted in the canonic representation.
15. The non-transitory computer readable medium of claim 14 , wherein the executable user interface code is a first executable user interface code, wherein the computer program further causes the computer processor to:
generate a second executable user interface code from the canonic representation, the second user interface code being operable to access the first and second applications provided to retrieve desired data,
wherein the first code is compatible with a first platform and the second code is compatible with a second platform that is different from the first platform.
16. The non-transitory computer readable medium of claim 11 , wherein the computer program further causes the computer processor to:
associate an operator to the second business function component; and
connect an output port of the second business function component to an input port of the operator.
17. The non-transitory computer readable medium of claim 16 , wherein the computer program further causes the computer processor to:
wherein the generated code does not require verification.
18. A system comprising:
one or more computer processors; and
a non-transitory computer readable medium comprising a computer program, that when executed by the one or more computer processors, causes the one or more computer processors to:
display a first business function component selected by a first user on a first display area, the first business function component being associated with first application logic to access a first business application;
display a second business function component selected by the first user on the first display area, the second business function component being associated with second application logic to access a second business application;
form a relationship between the first and second business function components, wherein a visual representation of a user interface is created based on the display steps and the form step;
generate a canonic representation of the visual representation; and
generate an executable user interface code from the canonic representation, the user interface code being operable to access the first and second applications to retrieve desired data.