Abstract: A computer-implemented method of representing a software application to be coded in a procedural language is provided. An initial UML class diagram modelizing the software application is received. Data definition classes within the initial UML class diagram are identified. Class operations within the initial UML class diagram are identified. The initial UML class diagram is modified by a processor to generate an extended UML class diagram by applying a data object stereotype to the identified data definition classes, and applying a program stereotype to the identified class operations. The data definition classes represent logical data, and the class operations represents programs.

Abstract: Locating program code units stored on digital data storage includes defining a software module fragment by assigning a software module fragment label to selected program code units, creating a module fragment list defining a software module, said list comprising a set of said software module fragments, receiving a request to retrieve the program code units of a specified software module from the digital data storage, and converting, using a processor, the module fragment list of the specified module into a list of physical locations for resolving the locations of the corresponding program code units on the digital data storage using said labels.

Abstract: Locating program code units stored on digital data storage includes defining a software module fragment by assigning a software module fragment label to selected program code units, creating a module fragment list defining a software module, said list comprising a set of said software module fragments, receiving a request to retrieve the program code units of a specified software module from the digital data storage, and converting, using a processor, the module fragment list of the specified module into a list of physical locations for resolving the locations of the corresponding program code units on the digital data storage using said labels.

Abstract: A computing device can store a class diagram of an application in a storage medium. A new model element type is applied to class operations in the class diagram and to a resource new model element type to data classes by defining properties, which include at least a resource name property, for each new model element. Flow diagrams of the application are applied to as many new model element types as different types of actions exist in the flow diagrams. The actions represent the operations on resources.

Abstract: Locating program code units stored on digital data storage includes defining a software module fragment by assigning a software module fragment label to selected program code units, creating a module fragment list defining a software module, said list comprising a set of said software module fragments, receiving a request to retrieve the program code units of a specified software module from the digital data storage, and converting, using a processor, the module fragment list of the specified module into a list of physical locations for resolving the locations of the corresponding program code units on the digital data storage using said labels.

Abstract: An activity diagram can be converted into code, by traversing the activity diagram to identify the cycles in the activity diagram. Each identified cycle can be stored in a list of cycles. Intermixed cycles among the list of cycles can be resolved. When resolving, the identified cycles can be compared one to another to determine if they have common nodes. If so one of the cycles can be removed from the list of cycles. The other cycle can be labeled as a GOTO loop. The activity diagram can be traversed. For each traversed node, code statements can be generated based on the node type and the labels associated with the node.

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.

Abstract: A class diagram can be created for an application. The application can use a modeling language. The application can be configured for creation of the class diagram. The class diagram can comprise classes and relationships. The application can also be configured for creating flow diagrams comprising actions, relationships, and definitions of model element types. The application can also be configured to create new model elements in the class diagram and flow diagrams. A program new model element type can be applied to relevant class operations in the class diagram and a resource new model element type to relevant data classes of the class diagram. A flow diagram can be created per program of the application. The flow diagrams can be applied as many new model element types as different types of actions exist in the flow diagrams. These actions can represent the operations on resources.

Abstract: A computer-implemented method of representing a software application to be coded in a procedural language is provided. An initial UML class diagram modelizing the software application is received. Data definition classes within the initial UML class diagram are identified. Class operations within the initial UML class diagram are identified. The initial UML class diagram is modified by a processor to generate an extended UML class diagram by applying a data object stereotype to the identified data definition classes, and applying a program stereotype to the identified class operations. The data definition classes represent logical data, and the class operations represents programs.

Abstract: A method and system to represent in UML the resources and external data manipulated by a program to be coded in a procedural language is disclosed. The usual UML class diagram is enhanced with two new stereotypes “Program” and “Data Object”. The program stereotypes applied to an operation and its parameters describe the data manipulated, through the logical definition provided by the Data Object. This model will be enhanced in order to introduce classes on which the Resource stereotype is applied. These classes will be connected to the appropriate logical data definition (the Data Object) and used as parameter types of the operation instead of the Data Object. A second set of stereotypes will be applied to the Resource classes to indicate the physical type of the resource (a file, table etc. . . . ) and its characteristics. Parameters that point to a DataObject or a primitive type will be considered as external data.

Abstract: An activity diagram can be converted into code, by traversing the activity diagram to identify the cycles in the activity diagram. Each identified cycle can be stored in a list of cycles. Intermixed cycles among the list of cycles can be resolved. When resolving, the identified cycles can be compared one to another to determine if they have common nodes. If so one of the cycles can be removed from the list of cycles. The other cycle can be labeled as a GOTO loop. The activity diagram can be traversed. For each traversed node, code statements can be generated based on the node type and the labels associated with the node.

Abstract: A method and system to represent in UML the resources and external data manipulated by a program to be coded in a procedural language is disclosed. The usual UML class diagram is enhanced with two new stereotypes “Program” and “Data Object”. The program stereotypes applied to an operation and its parameters describe the data manipulated, through the logical definition provided by the Data Object. This model will be enhanced in order to introduce classes on which the Resource stereotype is applied. These classes will be connected to the appropriate logical data definition (the Data Object) and used as parameter types of the operation instead of the Data Object. A second set of stereotypes will be applied to the Resource classes to indicate the physical type of the resource (a file, table etc. . . . ) and its characteristics. Parameters that point to a DataObject or a primitive type will be considered as external data.

Abstract: A class diagram can be created for an application. The application can use a modeling language. The application can be configured for creation of the class diagram. The class diagram can comprise classes and relationships. The application can also be configured for creating flow diagrams comprising actions, relationships, and definitions of model element types. The application can also be configured to create new model elements in the class diagram and flow diagrams. A program new model element type can be applied to relevant class operations in the class diagram and a resource new model element type to relevant data classes of the class diagram. A flow diagram can be created per program of the application. The flow diagrams can be applied as many new model element types as different types of actions exist in the flow diagrams. These actions can represent the operations on resources.

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.