API derivation and XML schema derivation for developing applications

• US 8,255,888 B2
• Filed: 09/30/2003
• Issued: 08/28/2012
• Est. Priority Date: 09/30/2003
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Jesse, Stefan, Lauterbach, Johannes
• Primary Examiner(s): VU, TUAN A
• Application Number:
  US10/676,373
• Publication Number:
  US 20050071801A1
• Time in Patent Office: 3,255 Days
• Field of Search: 717/104, 717/106, 717107-118, 717/143, 715/513.517, 715/500, 715/763, 715/513, 715/517, 709/223, 709/202, 709/315, 719/310, 719/313, 719/315, 719/319, 719/328, 705/1, 705/37, 707/10, 707/103.R
• US Class Current: 717/143
• CPC Class Codes: G06F 8/34 Graphical or visual programming

Abstract

Methods and apparatus, including computer program products, for developing an application. The development includes the use of a data model (e.g., a metamodel represented using UML) from which an API is derived. The API can include features derived from customizable extensions within the data model.

Claims

1. A computer-readable storage device storing a computer program product operable to cause a data processing apparatus to:

receive a metamodel in a first language, the first language comprising a customizable extension and the metamodel describing a diagram of classes that define one or more development objects, the development objects representing building blocks for developing an application;

convert the metamodel to a model description that describes the metamodel in a second language according to an interchange format;

generate a set of intermediate objects to represent the classes of the metamodel by parsing the model description, the generating including generating an Extensible Markup Language (XML) schema that enables implementation of the development objects by implementing at least one feature using the customizable extension, the at least one feature comprising at least one of an indication of a file border, a copy operation, or a paste operation; and

generate code using the set of intermediate objects as inputs to derive a metadata Application Program Interface (API), the metadata API enabling development tools to access the development objects to develop the application.

2. The computer-readable storage device of claim 1, wherein the second language comprises Extensible Markup Language (XML).

3. The computer-readable storage device of claim 1, wherein the first language comprises unified modeling language (UML).

4. The computer-readable storage device of claim 1, wherein the metamodel is stored on one of a storage module, a server, and a portable storage device.

5. The computer-readable storage device of claim 1, wherein the set of intermediate objects comprises Java objects.

6. A non-transitory computer-readable storage device storing a computer program product, the computer program product being operable to cause a data processing apparatus to:

receive a metamodel in a first language, the metamodel describing a diagram of classes that define one or more development objects, the development objects representing building blocks for developing the application, wherein the first language comprises a customizable extension and a unified modeling language;

convert the metamodel to a model description that describes the metamodel in a second language according to an interchange format, wherein the second language comprises Extensible Markup Language (XML);

generate a set of intermediate objects to represent the classes of the metamodel by parsing the model description, the generating including generating an XML schema that enables implementation of the development objects by implementing at least one feature using the customizable extension, the at least one feature comprising at least one of an indication of a file border, a copy operation, or a paste operation; and

generate code using the set of intermediate objects as inputs to derive a metadata Application Program Interface (API), and further wherein the metadata API enables development tools to access the development objects to develop the application.

7. The computer-readable storage device of claim 6, wherein the set of intermediate objects comprises Java objects.

8. The computer-readable storage device of claim 6, wherein the XML schema includes a tree based on aggregation relationships in the metamodel.

9. The computer-readable storage device of claim 6, wherein the XML schema includes a reference based on an association relationship in the metamodel first model.

10. The computer-readable storage device of claim 6, wherein the XML schema includes a complex type extension based on an inheritance relationship in the metamodel.

11. A non-transitory computer-readable storage device storing a computer program product being operable to cause a data processing apparatus to:

receive a metamodel describing a diagram of classes that define one or more development objects, the received metamodel being in a language comprising a customizable extension and the development objects representing building blocks for developing the application;

generate an Extensible Markup Language Metadata Interchange (XMI) model that is a representation of the metamodel according to an interchange format;

generate a set of intermediate objects to represent the classes of the metamodel by parsing the XMI model using an XML parser, the generating including generating an XML schema that enables implementation of the development objects by implementing at least one feature using the customizable extension, the at least one feature comprising at least one of an indication of a file border, a copy operation, or a paste operation; and

generate code using the set of intermediate objects as inputs to derive a metadata API enabling development tools to access the development objects to develop the application.

12. The computer-readable storage device of claim 11, wherein the computer program product is further operable to cause the data processing apparatus to:

create a new development object as a transient object without an existing corresponding file; and

modify the transient object until the transient object is committed to a persistent file.

13. The computer-readable storage device of claim 12, wherein the computer program product is further operable to cause the data processing apparatus to destroy the transient object if a delete command is requested before the transient object is committed to a persistent file.

14. The computer-readable storage device of claim 12, wherein the computer program product is further operable to cause the data processing apparatus to mark the persistent file as deleted if a delete command is requested after the transient object is committed to a persistent file.

15. The computer-readable storage device of claim 11, wherein the metamodel is stored on one of a storage module, a server, and a portable storage device.

16. The computer-readable storage device of claim 11, wherein the set of intermediate objects comprises Java objects.