التفاصيل البيبلوغرافية
| العنوان: |
INTEGRATED ENVIRONMENT FOR SOFTWARE DESIGN AND IMPLEMENTATION |
| Document Number: |
20120060141 |
| تاريخ النشر: |
March 8, 2012 |
| Appl. No: |
12/876114 |
| Application Filed: |
September 04, 2010 |
| مستخلص: |
Systems and methods for providing an integrated computer environment for software design and implementation are described. A number of UI components are connected in several sequences in the integrated computer environment. Each sequence describes a screenflow corresponding to a particular task in a software application. The screenflows are combined in a normalized interaction diagram representing the sequences of screens for every task that could be performed in the software application. The interaction diagram aggregates the similar UI components in different screenflows to avoid redundant duplicates. The UI components are bound to at least one business object (BO) as defined in a backend computer system. The software application is implemented and ready to be executed after the binding. |
| Inventors: |
DEMANT, HILMAR (Karlsdorf, DE); Aziz, Abdul (Bangalore, IN); Bose, Debobrata (Kolkata, IN); Dutt, Indranil (Bangalore, IN); Gopalan, Mahesh (Bangalore, IN); Hebling, Niels (Schriesheim, DE); R, Jayakanth (Edayar Pakkam, IN); Nair, Vinod S. (Palakkad, IN); Sivakumar, Aaby (Kollam, IN) |
| Claim: |
1. An article of manufacture including a non-transitory computer readable storage medium to tangibly store instructions, which when executed by a computer, cause the computer to: group a plurality of base floorplans, wherein each floorplan of the plurality of floorplans includes at least one general user interface (UI) component; generate at least one primary screenflow corresponding to a first use case, wherein the at least one primary screenflow includes a first set of floorplans of the plurality of floorplans configured to represent at least one primary sequence of UI controls for executing at least one task of first use case; generate at least one secondary screenflow corresponding to a second use case, wherein the at least one secondary screenflow includes a second set of floorplans of the plurality of floorplans configured to represent at least one secondary sequence of UI components for executing at least one task of the second use case; combine the at least one primary screenflow with the at least one secondary screenflow into a normalized interaction diagram representing the at least one primary sequence of UI controls and the at least one secondary sequence of UI components; and bind at least one floorplan from the plurality of floorplans to a data structure corresponding to at least one business object (BO) in a backend system, wherein the at least one floorplan is included in the normalized interaction diagram. |
| Claim: |
2. The article of manufacture of claim 1, wherein the non-transitory computer readable storage medium tangibly stores further instructions, which when executed by a computer cause the computer to: assign a first type of user profiles to initiate the generation of the at least one primary screenflow; assign a second type of user profiles to initiate the combination of the at least one primary screenflow with the at least one secondary screenflow into the normalized interaction diagram; and assigning a third type of user profiles to initiate the binding of the at least one floorplan from the plurality of floorplans to the data structure corresponding to the at least one BO. |
| Claim: |
3. The article of manufacture of claim 1, wherein the non-transitory computer readable storage medium tangibly stores further instructions, which when executed by a computer cause the computer to: receive BO metadata from the backend computer system, wherein the BO metadata includes one or more of a description of the fields structure of the at least one BO, at least one relationship to another BO, and at least one method definition of the BO; and send UI metadata to the backend computer system to allow a third party execution of the at least one task of the first use case or the at least one task of the second use case over the at least one BO, wherein the UI metadata includes description of the first set and the second set of floorplans and the binding of the at least one floorplan included in the normalized interaction diagram to the data structure corresponding to the at least one BO. |
| Claim: |
4. The article of manufacture of claim 3, wherein the non-transitory computer readable storage medium tangibly stores further instructions, which when executed by a computer cause the computer to: generate a second version of the interaction diagram reflecting a change in a floorplan of the first set of floorplans corresponding to a change in the first use case; and send a second version of the UI metadata corresponding to the second version of the interaction diagram to allow the third party execution of at least one task of the changed first use case. |
| Claim: |
5. The article of manufacture of claim 1, wherein generating the at least one primary screenflow comprises: defining a source floorplan of the first set of floorplans; defining a target floorplan from the first set of floorplans; and defining a condition to navigate from a base UI component of the source floorplan to a base UI component of the target floorplan during runtime. |
| Claim: |
6. The article of manufacture of claim 1, wherein generating the at least one primary screenflow comprises: generating a detailed specification of an instance of a floorplan of the first set of floorplans, wherein the detailed specification includes one or more categories of components selected from a group consisting of a view defining at least one customized UI component deriving from a general UI component, a data model describing at least one data structure component corresponding to the at least one customized UI control component, and a controller defining at least one event handler component to initiate an action corresponding to one or more of a system event, user action and a context. |
| Claim: |
7. The article of manufacture of claim 1, wherein generating the at least one primary screenflow comprises: relating a general UI component of a first floorplan of the first set of floorplans to a general UI component of a second floorplan of the first set of floorplans; and relating a customized UI component deriving from the general UI component of the first floorplan of the first set of floorplans with the general UI component of the second floorplan of the first set of floorplans, or with a customized UI component deriving from the general UI component of the second floorplan of the first set of floorplans. |
| Claim: |
8. A computer implemented method for a business application development and implementation within an integrated environment, the method comprising: connecting a first floorplan to a second floorplan with a first connection to form a first screenflow corresponding to a first business scenario; connecting the first floorplan to a second floorplan with a second connection to form a second screenflow corresponding to a second business scenario; combining the first screenflow with the second screenflow into an interaction diagram corresponding to the first business scenario and to the second business scenario, wherein the first floorplan is aggregated; and assigning the floorplans and the connections between floorplans in the interaction diagram to at least one business object (BO) based on BO metadata stored in a backend computer system; and storing user interface (UI) metadata in the backend computer system to allow a third party execution of the business scenarios over the at least one BO, wherein the UI metadata includes a description of the floorplans and the connections in the interaction diagram. |
| Claim: |
9. The method of claim 8 further comprising: assigning to a first role system rights to initiate the connection of the first floorplan with the second floorplan into the first screenflow; assigning to a second role system rights to initiate the combination of the first screenflow and the second screenflow into the interaction diagram; assigning to a third role system rights to initiate the assignment of the floorplans and the connections between floorplans to the at least one BO; and assigning a user profile to one or more roles selected from a group consisting of the first role, the second role and the third role. |
| Claim: |
10. The method of claim 8 further comprising: maintaining a general specification of the first floorplan containing a base UI control. |
| Claim: |
11. The method of claim 8, wherein connecting the first plan to the second floorplan with the first connection comprises: defining a source UI control of the first floorplan and a target UI control of the second floorplan to navigate between the floorplans during runtime when a predefined condition is met. |
| Claim: |
12. The method of claim 8, wherein assigning the floorplans and the connections between floorplans in the interaction diagram to the at least one BO comprises: receiving a detailed specification of an instance of the first floorplan, wherein the detailed specification includes a plurality of components of one or more categories selected from a group consisting of a view category defining at least one customized UI control component corresponding to the base UI control, a data model category describing at least one data structure component corresponding to at least one component of the floorplan, and a controller category defining at least one event handler to be associated with an component of the floorplan to initiate an action corresponding to one or more of a system event, user action and a context. |
| Claim: |
13. The method of claim 12, wherein receiving the detailed specification of the instance of the first floorplan comprises: generating the detailed specification of the instance of the first floorplan based on one or more of a user input and BO metadata import from the backend computer system. |
| Claim: |
14. The method of claim 12 further comprising: assigning a user profile to an component of the plurality components included in the detailed specification of the instance of the first floorplan, wherein the user profile is responsible for the detailed specification of the component |
| Claim: |
15. The method of claim 8, wherein assigning the floorplans and the connections between floorplans in the interaction diagram to the at least one BO comprises: receiving a detailed specification of a relationship between a customized UI component of an instance of the first floorplan and a customized UI component of an instance of the second floorplan. |
| Claim: |
16. A computer system for application development and implementation within an integrated environment, the system comprising: a memory to store computer instructions, wherein the memory is connected to a backend computer system via network; and a processor coupled to the memory to execute the computer instructions to maintain at least one project container including items of one or more integrated categories selected from a group consisting of use cases, documents, user profiles, roles, floorplans and cross project items, display at least one floorplan from a plurality of floorplans of an interaction diagram for the at least one project, generate a list of at least one screenflow aggregated into the interaction diagram, wherein the at least one screenflow includes the at least one floorplan, and maintain a correspondence between the at least one floorplan and at least one business object (BO) defined in the backend computer system. |
| Claim: |
17. The computer system of claim 16, wherein displaying the at least one floorplan comprises: rendering a graphical user interface (GUI) including a first area showing a schematic view of the at least one floorplan and at least one relationship modeled to connect the at least one floorplan with at least one other floorplan, and a second area showing the list of the at least one screenflow. |
| Claim: |
18. The computer system of claim 16, wherein displaying the at least one floorplan comprises: rendering a GUI showing a detailed view of the at least one floorplan, wherein the detailed view includes at least one screen selected from a group consisting of a data model screen showing a data structure underlying at least one component of the at least one floorplan, a controller screen showing at least one definition of an event handler associated with an component of the at least one floorplan, and a user interface (UI) view screen showing a representation of a customized UI component of the at least one floorplan. |
| Claim: |
19. The computer system of claim 16, wherein displaying the at least one floorplan comprises: rendering a GUI to switch between a schematic view and detailed view of the at least one floorplan enabling drill-down design or analysis of the components of the at least one floorplan, wherein the GUI switching between views is in response to a user action or to a system event. |
| Claim: |
20. The computer system of claim 16, wherein generating the list of the at least one screenflow comprises: generating a statistical data related to the at least one screenflow in order to provide monitoring information regarding the execution of a task of a use case corresponding to the at least one screenflow. |
| Current U.S. Class: |
717/101 |
| Current International Class: |
06 |
| رقم الانضمام: |
edspap.20120060141 |
| قاعدة البيانات: |
USPTO Patent Applications |