US 8024703 B2
View templates for use in generating application content are created by analyzing and categorizing existing application examples to derive reusable abstractions of application artifacts. Example application artifacts or source modules are categorized by role and function. Based on the categorized artifacts, a generalized, abstract view for the role and function is defined. View templates are created for each abstract view and contain static content and dynamic content that varies for each instance of the template. The view templates are stored in a template library for use in a model driven application generator.
1. A method, comprising:
analyzing application content to identify a plurality of content artifacts;
categorizing each content artifact of the plurality of content artifacts according to purpose and function;
identifying portions of each content artifact as dynamic content;
grouping the categorized content artifacts according to the categorization and identification to create abstract artifact roles;
generating, based upon the abstract artifact roles, a view template for each of said abstract artifact roles, said view templates comprising static and dynamic content.
2. The method of
3. The method of
4. The method according to
5. The method of
6. The method of
indicating sections of the content artifacts as potential dynamic content sections; and
replacing selected indicated sections with a dynamic attribute indicator upon selection by a user.
7. A system for developing view templates, comprising:
storage, coupled to the processor, for storing example code artifacts;
logic, stored on the storage for execution on the processor, for categorizing each of said example code artifacts according to purpose and function;
logic, stored on the storage for execution on the processor, for grouping said example code artifacts based on the categorization to produce corresponding artifact roles;
logic, stored on the storage for execution on the processor, for generating a view template, based upon the artifact roles, having static content portions and zero, one or more dynamic content portions; and
logic, stored on the storage for execution on the processor, for storing view templates for reuse.
8. A computer program product comprising:
a storage medium for storing program code containing logic for generating view templates from example code, the logic including program logic for analyzing an example of application content by:
categorizing each content artifact of said example according to purpose and function;
identifying portions of each content artifact as dynamic content;
grouping the categorized artifacts according to the categorization and identification to create abstract artifact descriptions;
generating, based upon the artifact roles, a view template for each of said abstract artifact descriptions, said view templates comprising static and dynamic content.
9. A computer program product according to
10. The computer program product of
11. The system of
12. The system of
13. The system according to
14. The system of
15. The system of
logic, stored on the storage for execution on the processor, for indicating sections of the example code as potential dynamic content sections; and
logic, stored on the storage for execution on the processor, for replacing selected indicated sections with a dynamic attribute indicator upon selection by a user.
1. Field of the Invention
The present invention relates to data processing systems. In particular, it relates to software development tools for code generation. Still more particularly, the present invention relates to processes for creating code generation patterns.
2. Background of the Invention
The development of software application code and related application content has long been the province of experts. A systems development expert must analyze the business problem, select the appropriate software tools to solve the business problem and then develop the software code necessary to implement the selected solution.
The field of software engineering developed in an attempt to standardize and simplify the creation of software. Software engineering defines standard processes and procedures that are applied to develop software code. Standardization is intended to promote use of effective solutions and to promote the reuse of previously developed solution components.
Process standardization still leaves the significant task of preparing the software code to implement a solution. Software code may be source code written in one of a number of programming languages such as JAVA®, C++, C#, Pascal or others. In addition, software code may include web pages coded in HTML, database access code in SQL, and written documentation in text form or portable document format (PDF.) Although many of the object oriented languages have stressed code reuse, this has often proved difficult in practice.
Code generation has been attempted using a number of code generators. These code generators use as input a description of the business problem to be solved expressed in some form of modeling language. This language is then interpreted and source code in a selected programming language generated. Many code generators implement what is known as a Model Driven Architecture. A Model Driven Architecture is a structure in which a business model, expressed in a modeling language drives the generation of the resulting software content. One example of a Model Driven Architecture is the Object Management Group (OMG) Model Driven Architecture.
One problem with existing code generators is the inflexibility of the modeling language or the code generation capability. For example, the OMG Model Driven Architecture requires that models be expressed in a well defined notation such as Unified Modeling Language (UML.) UML is a structured language that requires specific content and keywords to describe the business problem. The structure allows code generation to be accomplished by recognizing structural components, and generating software content based on those components. Unfortunately, many business problems are not readily expressed in UML compliant models, eliminating the ability to use generators relying on UML as the model.
Other model architectures provide fixed output generators. That is, the developer has no control over the form or format of the outputs generated base on a model input.
A problem therefore exists in providing a Model Driven approach to software content generation that is flexible in the expression of the business model as well as the content generation options. In addition, a problem exists in capturing the knowledge of systems development experts so that generated code can represent the best of breed solutions to business problems.
The present invention is therefore directed at providing a process for capturing expert software design solutions as patterns for use in a model driven software content generation system.
The present invention provides method for analyzing application examples to create view templates for use in building an application or software content using an open model driven architecture. The method includes: analyzing an example of application content; categorizing each content artifact of the example; identifying portions of each artifact as dynamic content; grouping the categorized artifacts and creating abstract artifact descriptions; and generating a view template for each of the abstract artifact descriptions, the view templates having static and dynamic content.
The preferred embodiment of the present invention implements a model driven architecture that maintains flexibility of expression in each of the descriptive components. The preferred embodiment enables construction of view templates capturing application content and structure from existing application examples that can be used to generate new applications. This process allows capturing of good quality techniques for reuse by other developers.
Allowing flexibility in expressing the application model reduces the barriers to development for the application developer. The flexible expression structure enables use of the presently claimed invention to develop a large variety of application content. Model descriptions are not limited to a set of problems that can be expressed in a rigid model language.
View templates or content patterns 20 are developed according to the preferred embodiment of the present invention as described in greater detail below. The view templates are accessed by the content developer from template libraries that collect view templates that implement a variety of application solutions. In an on-going development organization, libraries of view templates will be assembled as a result of development projects. A template may have the form shown in the table below.
Flow control actions include conditional actions that apply a particular pattern only if certain conditions exist or repetitive actions such as applying a pattern multiple times. Pattern application actions include generating content output based on variable data specified in the application definition and content output data specified in a pattern. The controller specifies which pattern is to be selected and which variable data is applied to that pattern. The controller specifies how many different output files are to be generated and specifies the structure for the names of those file. An example of a controller element or controller description is shown below.
The content generation process is managed by a transformation engine 40. Transformation engine 40 accesses the controller description 30, application definition 10 and templates or patterns 20. The application definition 10 is read by the transformation engine 40 and parsed to locate keywords and variable data. This parsing occurs using well known techniques of XML analysis or other lexical analysis of a textual file. Keywords are used to locate actions specified in the controller description 30. When a match is found, the matched action is applied. This causes a pattern 20 to be accessed and content to be generated. Content generation involves writing out specified static information and replacing dynamic information with application instance specific information passed to the transformation engine. The result is application content that solves the business problem modeled in the application definition.
The preferred embodiment of the present invention employs an open model driven architecture. The architecture is “open” because of the ability to flexibly specify the application definition (model), the controller, and the view templates. The modeling and generation process is not restricted to a certain class of models or models expressed in a fixed format or language.
The present invention implements a Model-View-Controller (MVC) model of a system. MVC models were originally developed to reduce the complexity of software systems that provide graphical user output using a graphical user interface (GUI.) In such a system the user view of data is kept separate from the rules for accessing the data to be displayed. The application logic for accessing and processing the data is specified in the model. Finally, the controller specifies how data acquired by the model is mapped to the GUI display (the view.)
A system designed using MVC modeling principles provides independence between the model and the view. This reduces implementation complexity because the view designer can concentrate solely on user interface issues while the model designer can concentrate on application logic and data access issues. This independence permits independent design changes to the user interface or the application logic. The user interface could be changed from a web browser display to a workstation client display or a portable device display without modifying the model specification.
In the present invention, the component independence of the MVC model is used to give the designer flexibility in application definition and content creation. For example, a particular application definition can be used to generate content output in different programming languages through the use of different views for each of the languages. Thus, an application definition may specify certain business requirements. The controller will map these to certain patterns. If matched to C language patterns, C program source code can be generated to implement the business solution. Use of a different controller that maps to JAVA° language patterns will result in a JAVA® solution.
The preferred embodiment generates content output. Content output can be any of a plurality of textual data or binary data. This output may be programming code for a particular programming language such as C, JAVA®, or C++. Output also can include descriptive materials such as solution documentation or descriptions. The output may also include web pages or other web components. Binary data may include bitmapped images, graphics or sound output.
The present invention is preferably employed in conjunction with a computer system such as that shown generally in
Random access memory 204 manages the program instructions and data for the computer system. In a typical computer system, an operating system 232 will manage the processing of tasks on the computer and the interface between particular programs and the hardware subsystems. Application programs 236 execute on the system to perform particular tasks. The number of application programs running at one time is limited only by the resources of the system including the operating system limitations. Finally, a variety of middleware 234 may be provided for certain tasks. Middleware 234 are programs that provide generally used facilities used by application programs or directly by users. Middleware can include software such as database management systems such as IBM DB2, MICROSOFT SQLSERVER®, MYSQL®. It may also include web servers and web application servers such as IBM WEBSPHERE® Application Server or MICROSOFT® IIS. Middleware provides generalized services that link together programs and systems to achieve the desired business goals.
Examples of computer systems that can be used in the preferred embodiment include the IBM THINKCENTER® series of personal computers, IBM THINKPAD® notebook computers, IBM XSERIES® workstations, and other machines based on INTEL® or AMD® central processing units (CPUs). These computer systems may operate under an operating system such as MICROSOFT WINDOWS XP®, Linux, or AIX®. The present invention is not limited to a particular hardware or software structure except as claimed.
The invention also may be embodied in a computer program product, such as a diskette, optical ROM, or other recording medium, for use with a data processing system. Embodiments of a computer program product may be implemented by use of any recording medium for machine-readable information, including magnetic media, optical media, or other suitable media. Persons skilled in the art will immediately recognize that any computer system having suitable programming means will be capable of executing the steps of the method of the invention as embodied in a program product. Persons skilled in the art will recognize immediately that, although most of the exemplary embodiments described in this specification are oriented to software installed and executing on computer hardware, nevertheless, alternative embodiments implemented as firmware or as hardware are well within the scope of the present invention.
The preferred embodiment of the present invention is preferably used in conjunction with an integrated development environment (IDE.) An IDE provides a number of facilities to assist the software developer. The IDE may include project, library and file management features, editors for editing and validating program source code, and compilers for creating compiled executable versions of the desired programs. An example of a IDE is the IBM WEBSPHERE® Application Studio Developer (WASD). Another example is the Eclipse development system managed by the Eclipse Foundation.
A system according to the present invention is preferably embodied as an addition to the IDE system. In WASD and Eclipse IDEs such an addition is termed a “plug-in.” As shown in
The IDE also provides editors that can be used to construct application definition files and controller definitions. Editor features such as find or find and replace can also be used by the application developer and the transformation engine. The use of an IDE, however, is not required to practice the present invention because the functions performed by the IDE can be performed directly by the preferred embodiment.
A view template includes static and dynamic content. For example, if programming language code is being generated, the template may include static program language keywords. Particular program variables will be represented as dynamic code. The template is used to generate code by replacing the dynamic code with information extracted from the application definition as specified by the controller definition. The controller definition provides the mapping between information provided in the application definition 416 and the dynamic portions of the output. Dynamic portions may represent “variables” in a programming language, but may also represent other changeable information. Thus, the chapter titles in a document could be represented as having static and dynamic parts. Program code may include dynamic names for classes and methods as well. A standardized naming convention is used in one embodiment to control the types and formats of names used throughout the resulting system.
The analysis of the business problem 410 results in an application definition 416. The term “business problem” is used to describe the problem scope the content is desired to solve. It need not be “business” related and can include analysis of games, non-profit organization issues, entertainment or recreational problems. In each case the problem is analyzed and the results expressed as an application definition. The analytical results are also used to specify the controller 412. The controller definition is developed based on the application analysis and the available patterns 408. The controller definition is stored as a controller definition 414.
Finally, content is generated 418 using a transformation engine. Content generation is performed by accessing the application definition 416 under the control of controller 414. The generator applies the application definition variables to the patterns 408 to create generated content 420.
The process of developing a view template from an examplar according to the present invention will be described with reference to
The first phase of view template creation according to the present invention requires identification and categorization of source artifacts 504. Artifacts according to the present invention are any content required by the application. Typically these will take the form of a source file. A source file is content that is either used directly or is used as input to a compiler or other transformation engine to create an executable or interpreted application component.
Source artifacts according the present invention include Java source files, HTML files, XML files, C language files, and documentation files. These source artifacts are classified to provide high level metamodel types. Thus, a “Java source file” is one metamodel type.
Next, the designer determines the metamodel types represented by the artifacts 506. Metamodel types can be states, transitions and data objects present in the application. These metamodel types determine the object types of the view pattern and are represented as separate patterns. For example, in a web based applications based on J2EE or web portal architectures, the metamodel types are transitions, states and data objects and determine and define the Java servlets, portlets, enterprise Java beans (EJBs), Java server pages (JSPs), HTML files and related content. Similarly, the database bean source files are specified based on the schemas, tables and columns of databases being accessed.
In analyzing the source artifacts identified in step 504, the designer begins by listing each artifact and categorizing it according to purpose and function. Each artifact is then classified according to metamodel type 508. The metamodel types are based on the states, transitions and data objects from step 506. The designer uses the metamodel type and purpose to begin to condense the existing artifacts into a set of models that represent the metamodel type that is an abstraction of the related artifacts. The metamodel types also indicate the roles of the artifacts.
The designer also begins to determine metamodel attributes 510. The attributes of a metamodel type provide the specific details that transform a metamodel object into a particular object instance. For example, a data object metamodel type has a table attribute that, when specified, allows creation of a data object for accessing a particular table. The preferred embodiment of the present invention analyzes the example code and presents the designer with view templates that contain sections of example code highlighted as candidates to become dynamic content. The tool permits the developer to select individual candidates and replace all occurrences in the model with a dynamic attribute reference. The designer can specify other dynamic content sections or add static content to create the final view template.
Metamodel attributes typically comprise on of three attribute types. Core attributes are those that comprise basic application requirements. For example, the names of application states are core attributes. Naming attributes are derived from other attributes according to specific naming conventions. For example, a data access object name for an object used to an Employee database table may be named “EmployeeAccess”. Derived attributes are those derived in a fixed manner from other attributes. For example, the source code for a Java class names “a.b.c.MyClass” is stored in a file structure named “a/b/c/MyClass.java.”
Once metamodel types and attributes are captured, the developer must analyze the model to determine whether view templates are needed for artificial roles 511. Artificial roles are metamodel types not directly required by the application definition but necessary to complete the application code. After the additional views are defined, the developer can generate view templates 512. The generated view templates 514 are stored in a file system or view template library (not shown.)
The view template or pattern 514 has both static and dynamic content portions. The static portions represent content that is generated as specified into the content output. Dynamic content varies based on the output instance. Object attributes generally are expressed as dynamic content in a view template. For example, the data access object name would be a dynamic attribute of a data access object. When the view template is applied, the dynamic variable for data object access name is replaced by the actual data object name provided by the content generator.
It will be understood from the foregoing description that modifications and changes may be made in various embodiments of the present invention without departing from its true spirit. The descriptions in this specification are for purposes of illustration only and are not to be construed in a limiting sense. The scope of the present invention is limited only by the language of the following claims.