System arrangement and method for automated application development with user guidance

• US 20060206858A1
• Filed: 03/06/2006
• Published: 09/14/2006
• Est. Priority Date: 03/07/2005
• Status: Active Grant

• Current Assignee: Siemens Healthineers AG (Siemens AG)
• Original Assignee: Siemens AG
• Inventors: Ukis, Vladyslav, Dorn, Karlheinz, Becker, Detlef, Scharf, Christian, Von Stockhausen, Hans-Martin
• Granted Patent: US 8,438,537 B2
• Time in Patent Office: Days
• US Class Current: 717/104
• CPC Class Codes: G06F 8/20 Software design

Abstract

A system arrangement is disclosed for automated application development with user guidance, including at least one view component (front-end) with a plurality of presentation forms, from which, at a particular time, a respective one is intended for data viewing and for input by a user, at least one model component (back-end) for storing and retrieving data, and a controller component for forwarding user inputs and/or requests for data to the model component and for forwarding requested data to a view component. The controller component is also intended for changeover between the presentation forms. Finally, a process flow component is provided for stipulating a sequence for the changeover between the presentation forms.

Claims

1. A system arrangement for application development with user guidance, comprising:

at least one view component with a plurality of presentation forms, from which, at a particular time, a respective one is intended for data viewing and for input by a user;

at least one model component for at least one of storing, processing and retrieving data;

a controller component for forwarding at least one of user inputs and data processing to the model component and for forwarding at least one of requested and processed data to a presentation form, the controller component also being intended for changeover between the views;

a process flow component, which provides at least one configurable sequence for the changeover between the views; and

a state manager component for storing states for the other parts of the system arrangement when it is suspended and for restoring the states when the system arrangement resumes.

2. The system arrangement as claimed in claim 1, wherein the model component includes a plurality of business forms, each logically connected to at least one presentation form, the changeover between presentation forms being coupled to a corresponding changeover between business forms.

3. The system arrangement as claimed in claim 1, wherein the presentation forms and, if appropriate, the business forms are in a hierarchical arrangement, so that the sequence of the changeover within one hierarchical level takes place when the sequence of the changeover in the next lowest hierarchical level has been performed.

4. The system arrangement as claimed in claim 1, wherein the process flow component is capable of taking prescribed events during the user input in a presentation form as a basis for instructing the controller component to use the stipulated sequence to change over between two presentation forms and, if appropriate, between two business forms.

5. The system arrangement as claimed in claim 1, wherein the sequence of presentation forms is determined by at least one configuration file for the process flow component.

6. The system arrangement as claimed in claim 1, wherein the changeover can be triggered by at least one preconfigurable event.

7. The system arrangement as claimed in claim 1, further comprising a view manager for producing generic front-end program components for at least one view component.

8. The system arrangement as claimed in claim 1, further comprising a model manager for producing generic back-end program components for at least one model component.

9. The system arrangement as claimed in claim 1, wherein the controller component has apparatuses for forwarding events from and to the model components and view components.

10. The system arrangement as claimed in claim 1, wherein the controller component at least one of contains and is capable of processing program code for producing the presentation forms of at least one view component.

11. The system arrangement as claimed in claim 2, wherein the controller component at least one of contains and is capable of processing program code for producing the business forms of the model component.

12. The system arrangement as claimed in claim 10, wherein the program code is based on a script.

13. The system arrangement as claimed in claim 1, wherein the system arrangement has at least one view component for local use at operating system level and at least one further view component for network use using network protocols.

14. The system arrangement as claimed in claim 1, further comprising means for data buffer-storage when the views are changed over.

15. The system arrangement as claimed in claim 14, wherein the data buffer-storage is performed by the process flow component and is performed in a memory area of the controller component.

16. The system arrangement as claimed in claim 1, wherein the program code for producing and configuring the components of the system is code written in a script language.

23. The system arrangement as claimed in claim 2, wherein the presentation forms and, if appropriate, the business forms are in a hierarchical arrangement, so that the sequence of the changeover within one hierarchical level takes place when the sequence of the changeover in the next lowest hierarchical level has been performed.

17. A method for application development with automated user guidance, comprising:

providing a view component with a plurality of presentation forms, from which, at a particular time, a respective one is intended for data viewing and for input by a user;

providing at least one model component for at least one of storing, processing and retrieving data;

forwarding at least one of user inputs and data processing to the model component, and forwarding at least one of requested and processed data to a presentation form, by a controller component;

changing a presentation form over to another, prescribed presentation form via the controller component, after prescribed user inputs have been stipulated;

stipulating a sequence for the changeover between the views, inter alia, via a process flow component; and

storing states for the other parts of the system arrangement when it is suspended and for restoring the states when the system arrangement resumes, via a state manager component.

18. The method as claimed in claim 17, wherein the model component includes a plurality of business forms which are each logically connected to at least one presentation form, the method further comprising:

coupling the changeover between presentation forms to the changeover between business forms.

19. The method as claimed in claim 17, performed using a system arrangement.

20. A computer program, adapted to, when executed on a computer, cause the computer to carry out the method as claimed in claim 17.

21. A computer program product, including the computer program of claim 20.

22. A computer readable medium including program segments for, when executed on a computer, causing the computer to implement the method of claim 17.