Methods and tools for data-driven application engineering

• US 8,271,935 B2
• Filed: 07/09/2008
• Issued: 09/18/2012
• Est. Priority Date: 07/09/2008
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Lewis, William J.
• Primary Examiner(s): Tecklu, Isaac
• Assistant Examiner(s): KABIR, MOHAMMAD H
• Application Number:
  US12/170,113
• Publication Number:
  US 20100011338A1
• Time in Patent Office: 1,532 Days
• Field of Search: 717/104, 717/105, 717/106, 717/107, 717/108
• US Class Current: 717/104
• CPC Class Codes: G06F 8/00 Arrangements for software engineering testing or debugging G06F11/36; administrative, planning or organisation aspects of software project management G06Q10/06
• CPC Class Codes: G06F 8/10 Requirements analysis; Specification techniques
• CPC Class Codes: G06F 8/20 Software design
• CPC Class Codes: G06F 8/35 model driven

Abstract

The invention generally relates to enterprise computer applications, and more particularly to methods and tools for data-driven engineering of computer applications. A method of generating a business application includes: inputting requirement data into a requirement model; inputting platform data into a platform model; generating a design model based on the requirement model and the platform model; generating source code of the business application from the design model; and outputting the source code.

Claims

1. A method of generating a business application embodied in a machine readable medium, comprising:

receiving requirement data into a requirement model;

receiving platform data into a platform model, the requirement data and the platform data comprising data and dependencies between the data, defined in a relational database;

generating a design model based on the requirement model and the platform model;

generating source code of the business application from the design model; and

outputting the source code, wherein;

the platform model is based on a platform metamodel having a platform base entity which includes data pertaining to a plurality of platforms and provides a list of potential implementation platforms.

2. The method of claim 1, wherein the requirement model is an instantiation of a requirement metamodel implemented in a database.

3. The method of claim 2, wherein the requirement metamodel comprises a plurality of entities and dependencies that define relationships between at least a portion of the plurality of entities.

4. The method of claim 2, wherein the design model includes a transformation of the requirement model, based upon the platform model.

5. The method of claim 4, wherein the design model includes a design unit entity, a design linkage entity, and a design property entity.

6. The method of claim 1, wherein the outputting comprises storing or writing the source code to a tangible medium that is compilable on a target platform of the business application.

7. The method of claim 1, wherein a service provider at least one of creates, maintains, deploys and supports a computer infrastructure that performs at least one of the steps of claim 1.

8. The method of claim 1, wherein at least one of the steps of claim 1 is provided by a service provider under a subscription and/or fee agreement and/or based on advertising content to one or more third parties.

19. The method of claim 5, wherein:

the design unit entity comprises a set of one or more objects from a requirements base entity targeted for a specific platform defined by a platform base entity, the one or more objects being a result of a transformation of a business requirement defined in the requirement model into a specific platform; and

lines of the design unit entity are structured rows derived from the requirements model that provide details required for generation of compilable code by syntax formatters.

9. A method of generating a business application embodied in a machine readable medium, comprising:

defining a requirement model;

defining a platform model, the requirement model and the platform model comprising data and dependencies between the data, defined in a relational database;

instantiating the requirement model into a requirement metamodel;

transforming the requirement model into a design model based upon the platform model, the design model comprising a design unit linkage entity which instantiates each dependency of the design model and a plurality of design units;

altering a portion of the design model to create a modified design model, the altering comprising converting a subset of the plurality of design units into a single design unit;

generating a source code of the business application based on the modified design model;

outputting the source code, wherein;

the platform model is based on a platform metamodel having a platform base entity which includes data pertaining to a plurality of platforms and provides a list of potential implementation platforms.

10. The method of claim 9, wherein the requirement metamodel is implemented in a database and comprises entities and dependencies that define relationships between the entities.

11. The method of claim 9, wherein the plurality of design units are defined in the database.

12. The method of claim 9, wherein the altering comprises manually selecting the subset of the plurality of design units.

13. The method of claim 9, further comprising providing a computer infrastructure arranged to perform at least one of the instantiating, the transforming, and the generating.

20. The method of claim 9, wherein the requirement metamodel comprises data entities, operation entities, and condition entities.

21. The method of claim 20, wherein:

the data entities include at least one of a domain, a domain value, a constant, a data element, a relationship, an entity, an universe, and an expression node;

the operation entities include at least one of a variable operation and a set operation; and

the condition entities include at least one of a condition, a necessary precondition, a sufficient precondition, and a set operation qualifier.

22. The method of claim 20, wherein:

the data entities include data which define values utilized for implementing the business application;

the operation entities include data which define aspects of business rules for implementing the business application; and

the condition entities include data which define conditions that that must be satisfied for one of the operation entities to act on at least one of the data entities.

14. A method of iteratively engineering a business application, comprising:

providing a computer infrastructure that operates to;

store input data associated with a requirement model and a platform model, the input data comprising data and dependencies between the data, defined in a relational database;

transform the input data into a design model;

generate a first source code of the business application by transforming the design model;

store revised input data based on altering the input data;

transform the revised input data into a second design model; and

generate a second source code of the business application by transforming the second design model

output the first source code and the second source code, wherein;

the first source code is executable on a first platform,

the second source code is executable on a second platform different from the first platform, and

the platform model is based on a platform metamodel having a platform base entity which includes data pertaining to a plurality of platforms and provides a list of potential implementation platforms.

15. The method of claim 14, wherein the requirement model is an instantiation of a requirement metamodel which is implemented in a relational database and comprises entities and dependencies that define relationships between the entities.

16. The method of claim 14, wherein the altering the input data is based upon feedback from at least one user executing the first source code.

17. A computer program product comprising a computer usable medium having a computer readable program embodied in the medium, wherein the computer readable program when executed on a computing device is operable to cause the computing device to:

receive requirement data into a requirement model;

receive platform data into a platform model;

instantiate the requirement model based on a requirement metamodel;

based on the platform model, transform the requirement model into a design model;

generate source code of a business application from the design model; and

output the source code, wherein;

the requirement metamodel is implemented in a relational database and comprises entities and dependencies that define relationships between the entities,

the entities and dependencies define business rules of the business application, and

the platform model is based on a platform metamodel having a platform base entity which includes data pertaining to a plurality of platforms and provides a list of potential imlementation platforms.

18. The computer program product of claim 17, wherein the transforming is accomplished using predefined database queries.

23. The computer program product of claim 17, wherein the platform metamodel further includes a platform dependency entity and a platform property entity.

24. The computer program product of claim 23, wherein:

the platform base entity includes data that defines a computer implementation technology that the business application will execute on;

the platform dependency entity contains data that specifies dependencies between the data of the platform base entity particular to one or more platforms to be implemented; and

the platform property entity includes data which specifies properties of the data of the platform base entity.