US20050246681A1 - System and method for computing code generation - Google Patents

System and method for computing code generation Download PDF

Info

Publication number
US20050246681A1
US20050246681A1 US11/176,925 US17692505A US2005246681A1 US 20050246681 A1 US20050246681 A1 US 20050246681A1 US 17692505 A US17692505 A US 17692505A US 2005246681 A1 US2005246681 A1 US 2005246681A1
Authority
US
United States
Prior art keywords
code
source data
rules
data
template
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US11/176,925
Inventor
Todd Little
Loren Konkus
Gilles Lavalou
Timo Metsaportti
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
BEA Systems Inc
Original Assignee
BEA Systems Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by BEA Systems Inc filed Critical BEA Systems Inc
Priority to US11/176,925 priority Critical patent/US20050246681A1/en
Publication of US20050246681A1 publication Critical patent/US20050246681A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/10Requirements analysis; Specification techniques

Definitions

  • the invention relates generally to computer software development and specifically to a system and a method for generating computer code for software applications.
  • UML Unified Modeling Language
  • OMT Object Modeling Technique
  • OOSE Object Oriented Software Engineering
  • UML UML
  • OA&D object analysis and design
  • IDL Interface Definition Language
  • Some tools have attempted to combine the design aspects of a UML-based design system, with code generation functionality, to better assist the software developer in code design and generation.
  • An example of this type of tool is the Builder range of products from BEA Systems, Inc, San Jose, Calif., that can be used to build applications, primarily in C or C++, and primarily for the Tuxedo server product, although other types of application can be built, and in other languages.
  • a problem with most of these types of product are that they tend to proprietary in nature, or geared specifically toward code generation for a particular species of code type or server. If the developer or architect must work across platforms on a particular project they often need to learn the specific code generation techniques for those platforms. This in turn consumes development time, and adds to both the learning and maintenance time required to manage the various platform tools. The overall situation ends up being not much more useful than if no tools were used.
  • the invention tackles the demand for a software development and code generation environment that combines the ability to act generically across a wide variety of platforms, yet can be customized for each individual product as required.
  • the invention provides a framework, that supports a system and a method for computer code generation, which can in turn be used to generate code and configuration files from any data source.
  • a Builder Generator Framework (or simply a Generator Framework) provides a common set of standards and application programming interfaces (APIs) through which designs may be input.
  • the purpose of the Generator Framework is to unify the code generation techniques implemented in products such as the Builder products from BEA Systems, Inc., by introducing sufficient abstraction levels.
  • a data navigation layer or interface isolates the generator framework from the data sources (and the underlying software products, applications, development suites or servers) used. Filters can be added to the framework to transform data, while notifiers are used by the generator framework to notify external components about the generation process.
  • FIG. 1 shows a Generator Framework in accordance with an embodiment of the invention.
  • FIG. 2 illustrates how the Generator Framework flexibly maps an abstraction data representation to the source data.
  • FIG. 3 shows an example of a template file in accordance with an embodiment of the invention.
  • FIG. 4 is a UML diagram of the components of the Generator Framework in accordance with an embodiment of the invention.
  • FIG. 5 is a flowchart of a code generation process in accordance with an embodiment of the invention.
  • the invention provides a system and method for computer code generation that can be used to generate code and configuration files from any data source.
  • a Generator Framework is used to unify the code generation techniques implemented in products such as the Builder products from BEA Systems, Inc., by introducing sufficient abstraction levels.
  • the framework may be referred to as the Builder Generator Framework, although it will be evident to one skilled in the art that the systems and techniques described herein have application beyond the products described, which are listed for illustrative purposes and to show the operation of the invention in an everyday setting.
  • Design Pattern A Design Pattern names and identifies a common object oriented design structure.
  • Interface Repository An interface repository (or simple repository) contains the definitions of the interfaces that determine client/server contracts.
  • the Generator Framework provides a common set of standards and application programming interfaces (APIs) to generate code and configuration files from any data source.
  • APIs application programming interfaces
  • a primary goal in developing the Generator Framework is to unify the code generation techniques implemented in the Builder family of products, by introducing sufficient abstraction levels.
  • Built-in (or generic) rules are introduced in the generator framework.
  • a data navigation layer isolates the generator framework from the data sources used. Filters can be added to the framework to transform data. Notifiers are used by the generator framework to notify external components about the generation process.
  • the Generator Framework is intended to be used in development products such as those produced by BEA Systems, Inc. which includes their Builder family of products.
  • BEA Builder is designed to enable companies to leverage the development skills of their existing programming staff, while substantially reducing the time and costs associated with implementing new applications, such applications being then used primarily for the BEA Tuxedo platform.
  • BEA Builder is a suite of five products which address the key aspects of client-side and server-side application development. These include:
  • BEA Active Expert A tool that allows the use of popular Windows development tools to create BEA TUXEDO client applications.
  • BEA C++ Expert—A tool that assists the programmer in writing BEA TUXEDO servers and clients using C++.
  • BEA Contract Repository A central repository for the storage of interface information for server-side BEA TUXEDO application components.
  • BEA Rose Expert 2.0 A plug-in to the Rational Rose development tool that allows the application designer to leverage the Rose object design environment to build BEA TUXEDO servers and clients using C++.
  • BEA Configuration Expert 2.0 A tool to quickly and simply generate BEA TUXEDO configuration files without having to know the specific configuration file formats.
  • the Generation Framework architecture is also intended to be flexible enough to be reused in other BEA products, such as BEA Repository, but it will be evident to one skilled in the art that the architecture has applications beyond theses examples.
  • the Generator Framework architecture does not decide upon or define the implementation language used, code examples given herein are in JAVA. These examples can easily be transposed to C or C++.
  • the Generator Framework architecture may be used and customized in several Builder products, such as the Active Expert, C++ Expert, Rose Expert, Configuration Expert and Ice Crystal products.
  • This document describes the architecture of a common Generator Framework, in which the abstraction levels are raised to integrate different tools and types of generation (C++, UBBconfig files, etc.); and different data sources (Contract Repository, Configuration Repository, etc.)
  • FIG. 1 shows the Generator Framework architecture
  • FIG. 5 shows a flowchart of a code generation process in accordance with an embodiment of the invention.
  • the arrows describe the data flow and the lines ending with dots describe a plug-in relationship.
  • Rules, Filters, Conditions and Notifiers are internal or external pieces of code that plug into the framework.
  • the Generator Framework architecture is composed of the following elements (although not all elements may be present in each embodiment):
  • the Data Source 100 is the place where the data used for the generation comes from. It is usually considered as a repository (e.g. Builder Contract Repository, CORBA Interface Repository, etc. . . . ).
  • the data source may be stored on any temporary, permanent or semipermanent storage device, hereinafter referred to simply as a storage device. Such storage devices may include memory devices, magnetic devices, hard (fixed) disks, and equivalent storage mechanisms.
  • the Output Files 102 are the result of the generation.
  • the output files may be output, written to, or stored on any temporary, permanent or semipermanent storage device, hereinafter referred to simply as a storage device, such as described above.
  • a storage device such as described above.
  • the output files When the output files are intended to be sent directly to another software application they may be sent directly or in real-time to that application and not e stored as any discrete file or record.
  • Templates 104 are text files containing both instructions to drive the generation process and pieces of static code that need to be generated.
  • Rules can be internal ( 106 ) or external ( 108 ) to the framework, and are pieces of logic that implement template instructions. Rules are used to generate output dynamically when static template code is not appropriate.
  • Filters can be internal ( 110 ) or external ( 112 ) pieces of logic invoked from rules and used to transform data.
  • Conditions 114 are external pieces of logic invoked from rules used to evaluate conditions. Conditions are used to generate code depending on some specific conditions.
  • Notifiers 116 are external pieces of logic used when a rule is invoked. This allows external components to be notified of the progress of the generation process.
  • the Generator Framework is composed of a set of classes providing generation abstractions, using a data source as input, template files and external specific rules to drive the generation process against the data sources, and producing one or many output files.
  • the Generator Framework itself is composed of the following elements:
  • a Parser 130 parses template files and invokes appropriate rules (built-in or specific). The Parser is also the place where all the plug-ins are registered: Rules, Filters, Conditions and Notifiers.
  • a Data Navigation Layer 132 acts as an abstraction to the data source, by providing navigational capabilities inside the data source. This layer implements the Facade design pattern, and exposes only the navigation primitives, not the details of the data source. This and other design patterns are described in Design Patterns, Gamma et al. Addison Wesley, hereby incorporated by reference.
  • Built-in Rules 106 provide basic functions to query symbol values from the data source, navigate through the data source, and open and close files.
  • Built-in Filters 110 provide generic transformation capabilities, such as lowercase/uppercase conversion.
  • FIG. 2 illustrates how the data navigation layer is used to provide access to the data source 140 .
  • the model used for the data source is independent of specific data source implementations.
  • the resultant abstraction 142 provides access to simple type data elements, and navigation inside the data source. Because the model is based on navigation inside the data source, a context must be maintained. This context is referred to herein as a scope 144 .
  • the scope provides access to the data sources as a pointer to the current data.
  • the model used in generation is assumed to be a hierarchical assembly 146 , so that the scopes are stacked by the parser as abstract tree structures are traversed. The combined scopes act as a “facade”, isolating the parser from the data source implementation.
  • the Parser 130 provides functions to manipulate the scope stack, such as pushing a new scope on the stack, popping the scope stack, and getting the current scope.
  • the model for the data navigation layer is based on an object-oriented model for data. Scope represents objects from the data source, which have string attributes, accessed through attribute related functions; and references (relationships or pointers to other objects), accessed through reference related functions.
  • a symbol name is a name for an attribute (simple data) or a reference (related scope), and can be absolute or relative.
  • An absolute symbol name is composed of the scope name and the relative symbol name, for example Interface::name.
  • a relative symbol name can be simple or composed.
  • a simple symbol name is just an identifier, such as “srvList”.
  • a composed symbol name contains several reference names separated by dots and a simple symbol name used to access a related scope symbols. For instance, getting the module name from the operation scope in the Contract Repository would be done using the following symbol:
  • Attributes and references can be single or multi-valued. This impacts the usage of the Scope API, because it is not semantically possible to query individually an attribute or a reference which is multi-valued.
  • the Scope API defines functions to both query single and multi-valued attributes and references. Single valued attributes and references are queried by functions that return directly the requested value (character string or scope). Multi-valued attributes and references are queried by functions that return an iterator of character strings or scopes.
  • the Scope API provides an isMultiple( ) function that checks if a symbol name corresponds to a single or multi-valued attribute or reference.
  • the Scope interface implements a getValue( ) method to get the value of a single-valued attribute. This method accepts a relative symbol name only. If the attribute is multi-valued, this function throws an exception.
  • the scope method getvalue( ) is used to return the type of a parameter (for example “in”, “out” or “inout”) in IDL generation:
  • Scope Navigation is performed by means of pointers or pointer-like references.
  • a reference provides access to a list of (sub-)scopes related to the current scope.
  • reference names are either relative or absolute.
  • a Module scope gives access to an “interface list” reference, which provides access to the interfaces of the module.
  • the relation between the scope navigation and the data source navigation is shown in FIG. 2 .
  • the scope method getScope( ) takes a reference name as input and returns the related scope. If the reference is multi-valued, this functions throws an exception. The following shows an example:
  • a rule is represented by a string delimited by separators, containing a rule name and zero or more arguments.
  • a rule name is an identifier containing uppercase characters.
  • a rule argument contains text (which may also contain nested rules).
  • a rule has the following syntax:
  • Built-in rules provide a generic set of rule implementation for data access, data navigation and boolean conditions. These rules are part of the Generator Framework. The (non-exhaustive) list and syntax of these rules is described below in the section titled Built-in
  • FIG. 3 shows an example of a template 150 as it may used to generate code 154 .
  • Templates are text files that drive the generation process. Template files contain lines of text in which rules are parsed by the generator parser. Template lines also contain static text which is sent directly to the generator output. Some rules (ITERATE, COND) define the notion of a block of template code which is parsed zero or several times depending on some conditions. These blocks of template code are put between the ‘@ ⁇ ’ and ‘@ ⁇ ’ markers. The following is a yacc-like syntax description of the template files. The terminal symbols are in uppercase.
  • TemplateFile TemplateLines ; TemplateLines:
  • Filters are used to transform data during the generation.
  • a filter is a piece of logic that takes a string and a scope as input, and outputs the transformed string. Transformations include:
  • Filters are initially registered with the Parser in the framework. Each filter has a name, and may allow several transformations to take place. For example, the “Case” filter (built-in filter) has the two “U” and “L” transformations, for uppercase and lowercase conversion respectively.
  • the Parser provides functions to add and remove filters, and to get a filter by its name.
  • Text Filters are used to transform any kind of data during the generation process. Text Filters are used by the FILTER rule (see also the FILTER Rule below), and can be used by external rules.
  • the TextFilter interface defines the following abstract method: abstract public String transform(Scope scope, String input, String transformationName); A filter is invoked from a rule, either built-in (such as the FILTER rule) or specific.
  • the filter name and transformation name are typically arguments to a rule, as shown in the example below:
  • the SymbolFilter interface is used to transform the value of a symbol.
  • the difference with Text Filters is that a symbol bears more information than simple text from the scope point of view.
  • the type of the symbol that can be used to transform data includes adding double quotes if the symbol is a string, or generating Y or N if the symbol is boolean.
  • Symbol Filters are used by the VAL rule (see also the VAL Rule below), and can be used by external rules.
  • the SymbolFilter interface defines the following abstract method: abstract public String transform(Scope scope, String symbolName, String input, String transformationName); Using Filters
  • Conditions are used to generate code conditionally. Conditions are pieces of code that are plugged into the Generator Framework.
  • the Parser provides functions to add and remove conditions, and to get a condition by its name.
  • COND rule This rule accepts complex conditions as input, expressed by symbol values, constants and logical operators.
  • the condition text is parsed by the COND rule code.
  • UnaryExpression Expression Identifier Constant ( ConditionalExpression ) Identifier: Literal Identifier . Literal Identifier . $# Constant: NumberConstant StringConstant NumberConstant: [ ⁇ ]?[0-9]+ StringConstant: “ StringChars ” Conditional Lists and Iterations
  • the list of input parameters may be needed: if the model only provides a list of parameters (in, out, and inout), a conditional list may be useful to do this.
  • Notifiers are used to send messages to external components that use the Generator Framework. Notifiers are typically used to inform external components (such as progress bars, output text widgets) about the status of the generation. A component wanting to be notified about the generation progress must simply implement the Notifier interface (see below). Notifications are sent in rules using the parser notify( ) method. Notifiers are registered in the parser for a specific rule (e.g. OPEN, CLOSE). Two conditions must be met for receiving notification messages from a rule:
  • the Notifier interface defines the following abstract method: abstract public void ruleInvoked(String ruleName, Parser P, String message); Protected Code Sections
  • Protected code sections allow users of the Generator Framework to define parts of the output file (or files) being untouched by the generation process. This is a powerful mechanism used to preserve user code while still being able to apply the generator to produce updated versions of the output files. For instance, defining a protected code section in a function implementation allows to keep the user code in the output file.
  • Protected code sections are identified by a particular rule in the templates (see also the PCS Rule below). Unicity of a protected code section depends on a tag—which is defined by the person writing the template. The tag generated in the output file is parsed by the PCS rule to ensure uniqueness.
  • the UML diagram in FIG. 4 shows the class architecture of the framework.
  • the meaning of the UML representation 160 in FIG. 4 will be evident to one skill in the art.
  • the parser is the central point of the Generator Framework. It's functions include invoking the parsing of a template file, and executing rules which in turn change the scope of the parser. Scopes are organized in a stack inside the parser.
  • the following class and interface specifications are given as examples, although it will be evident to one skilled in the art that the specific classes given are
  • the Scope class is an abstract class providing access to a data source (Contract Repository, Configuration Repository, UREP, . . . ). package com.beasys.generator; public abstract class Scope ⁇ // // General purpose functions // public String getName( ); public String getType(String symbolName); public boolean isMultiple(String symbolName); // // Attribute-related functions // public abstract boolean hasAttribute(String symbolName); public abstract int getAttributeCount(String symbolName); public abstract String getValue(String symbolName) throws CardinalityException; public abstract Enumeration values(String symbolName); // // Reference related functions // public abstract boolean hasReference(String symbolName); public abstract int getReferenceCount(String symbolName); public abstract Scope getScope(String symbolName) throws CardinalityException; public abstract Enumeration values(String symbol Name); ⁇ Rule Class
  • the Rule class defines the function that implements a rule.
  • a rule is invoked by the parser when a rule invocation is recognized in the templates.
  • package com.beasys.generator public abstract class Rule ⁇ public String execute(String[ ] args, Parser p) throws GenException; ⁇ Parser Class
  • the Parser class contains the core of the Generator Framework, parsing template files and invoking rules.
  • the Filter class is the common superclass of the SymbolFilter and TextFilter classes: abstract public class Filter ⁇ protected Filter(String name); public String getName( ); public abstract boolean hasTransformation(String name); ⁇ SymbolFilter Class
  • the SymbolFilter class is used by the VAL rule to transform a symbol value.
  • abstract public class SymbolFilter extends Filter ⁇ protected SymbolFilter(String); abstract public String transform(Scope s, String symbolValue, String input, String transfName); ⁇ TextFilter Class
  • TextFilter is used by the FILTER and VAL rules to transform a text value.
  • abstract public class TextFilter extends Filter ⁇ protected TextFilter(String); abstract public String transform(Scope s, String input, String transfName); ⁇ Condition Interface
  • the Condition interface defines a isApplicable( ) method used to
  • the Notifier interface defines a method used to notify external components about the status of the generation. External components are notified from rules when the rule invokes the notify( ) method of the Parser class.
  • public interface Notifier ⁇ public abstract void ruleInvoked(String ruleName, Parser p, String message); ⁇ 4. Built-in Rules Syntax
  • the OPEN rule opens the file ⁇ fileName> for output.
  • the generation output is written to the file ⁇ fileName>.
  • the name of ⁇ fileName> can contain static values such as “test.idl”, or symbols for substitution, such as “$[VAL: moduleName].idl”.
  • the CLOSE rule closes the current output file.
  • the generator output is restored to the previous opened output file, if any. If there is no more output file, any rule other than $[OPEN] causes the generator to fail.
  • the SCOPE rule ensures that the current scope name is the same as the scope name passed in the rule.
  • the generator fails if the current scope name is not ⁇ scopeName>. This rule has no other effect.
  • the VAL rule is used to return the value of symbols.
  • a symbol value pertains to the current scope stack. Symbol values are retrieved against scopes from the scope stack, using the getValue( ) method of the Scope class.
  • the VAL rule can only be used on single-valued attributes. An exception is thrown if this rule is used on a multiple-valued attribute.
  • the VAL rule can be used with a symbol representing a multi-valued attribute only if it is invoked from an iterated code block in the LIST, ITERATE, CONDLIST and CONDITERATE rules.
  • the second form allows the framework to apply a symbol or a text filter to the symbol value.
  • the ⁇ filterName> parameter is the name of the filter to be used.
  • the ⁇ transformationName> parameter is the name of a valid transformation in this filter.
  • the FILTER rule is used to apply a text filter to some text block.
  • the ⁇ text> argument is parsed by the parser (it may contain rules).
  • the ⁇ filterName> parameter is the name of the text filter to be used.
  • the ⁇ transformationName> parameter is the name of a valid transformation in this text filter.
  • the COND rule has two forms: the first forms allows to conditionally generate a (one line) piece of code depending on a named or generic condition.
  • the second form allows to generate a block of code (on multiple lines) depending on a named or generic condition.
  • the code block is delimited by the ‘@ ⁇ ’ and ‘@ ⁇ ’ markers.
  • the ITERATE rule repeats the same block of code for a given symbol name.
  • the iteration symbol name is a static name corresponding to a multi-valued reference related to the current scope.
  • the iterated code block (between the ‘@ ⁇ ’ and ‘@ ⁇ ’ markers) is a piece of template code that is iterated for all the objects returned by the iteration at the scope level. Rules may be invoked inside this block, with a scope corresponding to the iterated objects.
  • the iteration symbol name can also be a multi-valued attribute. In that case, the iterated code block is invoked with the same scope, and the VAL rule can be used to retrieve the sequenced values of the multi-valued attribute.
  • the LIST rule is similar to the ITERATE rule. Instead of iterating several lines of code, it outputs a list of ⁇ codeBlock> elements, separated by a separator string (the default separator is “,”)
  • the CONDITERATE rule repeats the same block of code for a given symbol name, depending on a named or generic condition.
  • the iteration symbol name is a static name corresponding to a multi-valued reference related to the current scope.
  • the iterated code block (between the ‘@ ⁇ ’ and ‘@ ⁇ ’ markers) is a piece of template code that is iterated for all the objects returned by the iteration at the scope level which satisfy the named or generic condition. Rules may be invoked inside this block, with a scope corresponding to the iterated objects.
  • the CONDLIST rule is the result of the composition of a LIST rule and a COND rule. Each element generated in the list and used as the current scope in the code block must satisfy the named or generic condition.
  • the INCLUDE rule is used to include a template inside the current template.
  • the PCS rule defines the location of a protected code section in a template.
  • the argument to the PCS rule is a tag which is parsed by the parser.
  • the protected code section will be delimited by the two lines shown below. Any comments put in the template on the $[PCS: . . . ] line will be preserved in the output file for both begin and end markers.
  • the “name” symbol is used several times to get the names of modules, interfaces, operations and parameters, respectively.
  • the ITERATE and LIST rules manage the data navigation so that the “name” symbol is each time the name of the element in the corresponding scope.

Abstract

A system and method for computer code generation that can be used to generate code and configuration files from any data source. In accordance with one embodiment a Generator Framework provides a common set of standards and APIs through which designs may be input. The purpose of the Generator Framework is to unify the code generation techniques implemented in products such as the Builder products from BEA Systems, Inc., by introducing sufficient abstraction levels. Built-in rules are introduced in the Generator Framework, and a data navigation layer isolates the Generator Framework from the data sources used. Filters can be added to the framework to transform data. Notifiers are used by the Generator Framework to notify external components about the generation process.

Description

    CLAIM OF PRIORITY
  • This application is a continuation of “SYSTEM AND METHOD FOR COMPUTER CODE GENERATION”, application Ser. No. 09/970,741,filed Oct. 4, 2001 which claims priority from provisional applications “SYSTEM AND METHOD FOR COMPUTER CODE GENERATION”, application Ser. No.60/238,559, filed Oct. 4, 2000, and “SYSTEM FOR SOFTWARE APPLICATION DEVELOPMENT AND MODELING,” application Ser. No. 60/238,561, filed Oct. 4, 2000, all of which are incorporated herein by reference. This application is also related to “SYSTEM FOR SOFTWARE APPLICATION DEVELOPMENT AND MODELING,” application Ser. No. 09/970,917, filed Oct. 4, 2001, also incorporated herein by reference.
  • COPYRIGHT NOTICE
  • A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.
  • FIELD OF THE INVENTION
  • The invention relates generally to computer software development and specifically to a system and a method for generating computer code for software applications.
  • BACKGROUND
  • The increasingly important field of software development brings with it the ever more common question—who can we get to actually do the software coding? Software developers or coders are in high demand, and their skills demand premium salaries. As such the software generation or development process is a major factor to consider for any company that relies on or uses software for it's day-to-day business needs. This issue is even more relevant to those companies who support the software development process—companies such as BEA Systems, Inc, IBM Corporation, and Microsoft Corporation who develop software development products, suites and tools. In order to maximize the benefits of their products to their end customers, these companies must develop tools that allow a software developer to minimize the amount of time necessary to finish a particular software project, while at the same time maximizing the options available to the developer to create a quality product. Some tools are also particularly geared to helping junior or beginning developers, who may not be as experienced, to successfully compete against more established and skilled software architects.
  • Given the importance of software development to the global industry, and the demands that it should be relatively painless, easy to work with, and that it make optimal use of time and resources, it seems natural to want to develop a software generation tool or system, that automatically generates software code in accordance with some preset or preordained wishes of a developer. This allows the software architect or developer to concentrate on the “big picture”, and to envisage the functioning of the software application as a whole, without undue regard to the intricacies of code development.
  • To this end, many tools allow the architect to develop a model or plan of the desired software application and to use this plan as a blueprint for subsequent software development. Similar to the way in which an architect designs blueprints for a building, software designers also design blueprints for their complex software applications. And just as a building architect likes to be able to test those blueprints for structural soundness, using for example a modeling or analysis system to test each aspect of the design, software architects also like to test their software blueprints for reliability, scalability, optimal use of resources, and good software design. As the complexity of a particular project increases, so too does the need for a reliable, accurate model. The software industry has developed several modeling techniques to address this need, one of which is the Unified Modeling Language (UML), a nonproprietary language defined in the Object Management Group Unified Modeling Language Specification, hereby incorporated by reference. UML provides software architects with a standardized language for specifying, constructing, visualizing and documenting the artifacts of a complex software system. The UML specification is a successor to three earlier object-oriented methods, Booch, Object Modeling Technique (OMT), and Object Oriented Software Engineering (OOSE), and includes additional expressiveness to handle more complex modeling problems, not readily handled by prior techniques.
  • Some of the features inherent in UML are: Formal definition of a common object analysis and design (OA&D) metamodel to represent the semantic of OA&D models, including static, behavioral, usage and architectural models, Interface Definition Language (IDL) Specifications for mechanisms for model interchange between OA&D tools, which includes a set of IDL interfaces that support dynamic construction and traversal of a user model; and, easily readable notation for representing OA&D models, most commonly a graphic syntax for consistently expressing UML semantics. As such the UML is more correctly considered a visual modeling language rather than a visual programming language. Because of its open standard and widespread industry use it serves to lower the cost of training and retooling when changing between projects or organizations, and provides opportunity for new integration between tools, processes and domains.
  • Some tools have attempted to combine the design aspects of a UML-based design system, with code generation functionality, to better assist the software developer in code design and generation. An example of this type of tool is the Builder range of products from BEA Systems, Inc, San Jose, Calif., that can be used to build applications, primarily in C or C++, and primarily for the Tuxedo server product, although other types of application can be built, and in other languages. A problem with most of these types of product are that they tend to proprietary in nature, or geared specifically toward code generation for a particular species of code type or server. If the developer or architect must work across platforms on a particular project they often need to learn the specific code generation techniques for those platforms. This in turn consumes development time, and adds to both the learning and maintenance time required to manage the various platform tools. The overall situation ends up being not much more useful than if no tools were used.
  • It would be more useful if there existed a uniform code development or generation system, that was generic enough to be used with a wide variety of platforms and technologies, yet could be made specific enough in those cases in which a detailed integration with the product was needed.
  • SUMMARY
  • The invention tackles the demand for a software development and code generation environment that combines the ability to act generically across a wide variety of platforms, yet can be customized for each individual product as required. Roughly described, the invention provides a framework, that supports a system and a method for computer code generation, which can in turn be used to generate code and configuration files from any data source. I n accordance with one embodiment of the invention a Builder Generator Framework (or simply a Generator Framework) provides a common set of standards and application programming interfaces (APIs) through which designs may be input. The purpose of the Generator Framework is to unify the code generation techniques implemented in products such as the Builder products from BEA Systems, Inc., by introducing sufficient abstraction levels. Built-in rules are introduced or plugged-in into the generator framework, and a data navigation layer or interface isolates the generator framework from the data sources (and the underlying software products, applications, development suites or servers) used. Filters can be added to the framework to transform data, while notifiers are used by the generator framework to notify external components about the generation process.
  • BRIEF DESCRIPTION OF THE FIGURES
  • FIG. 1 shows a Generator Framework in accordance with an embodiment of the invention.
  • FIG. 2 illustrates how the Generator Framework flexibly maps an abstraction data representation to the source data.
  • FIG. 3 shows an example of a template file in accordance with an embodiment of the invention.
  • FIG. 4 is a UML diagram of the components of the Generator Framework in accordance with an embodiment of the invention.
  • FIG. 5 is a flowchart of a code generation process in accordance with an embodiment of the invention.
  • DETAILED DESCRIPTION
  • Roughly described, the invention provides a system and method for computer code generation that can be used to generate code and configuration files from any data source. As referred to herein, a Generator Framework is used to unify the code generation techniques implemented in products such as the Builder products from BEA Systems, Inc., by introducing sufficient abstraction levels. When used in the context of the Builder products, the framework may be referred to as the Builder Generator Framework, although it will be evident to one skilled in the art that the systems and techniques described herein have application beyond the products described, which are listed for illustrative purposes and to show the operation of the invention in an everyday setting.
  • Introduction
  • The following terms are used herein, and have the appropriate meanings and equivalents known to one skilled in the art:
  • Design Pattern—A Design Pattern names and identifies a common object oriented design structure.
  • IDL—Interface Definition Language, as defined by the Common Object Request
  • Broker Architecture and Specification.
  • Interface Repository—An interface repository (or simple repository) contains the definitions of the interfaces that determine client/server contracts.
  • The Generator Framework provides a common set of standards and application programming interfaces (APIs) to generate code and configuration files from any data source. A primary goal in developing the Generator Framework is to unify the code generation techniques implemented in the Builder family of products, by introducing sufficient abstraction levels. Built-in (or generic) rules are introduced in the generator framework. A data navigation layer isolates the generator framework from the data sources used. Filters can be added to the framework to transform data. Notifiers are used by the generator framework to notify external components about the generation process.
  • The Generator Framework is intended to be used in development products such as those produced by BEA Systems, Inc. which includes their Builder family of products. BEA Builder is designed to enable companies to leverage the development skills of their existing programming staff, while substantially reducing the time and costs associated with implementing new applications, such applications being then used primarily for the BEA Tuxedo platform. BEA Builder is a suite of five products which address the key aspects of client-side and server-side application development. These include:
  • BEA Active Expert—A tool that allows the use of popular Windows development tools to create BEA TUXEDO client applications.
  • BEA C++]Expert—A tool that assists the programmer in writing BEA TUXEDO servers and clients using C++.
  • BEA Contract Repository—A central repository for the storage of interface information for server-side BEA TUXEDO application components.
  • BEA Rose Expert 2.0—A plug-in to the Rational Rose development tool that allows the application designer to leverage the Rose object design environment to build BEA TUXEDO servers and clients using C++.
  • BEA Configuration Expert 2.0—A tool to quickly and simply generate BEA TUXEDO configuration files without having to know the specific configuration file formats.
  • This robust suite of products helps enable rapid development of BEA TUXEDO applications and encompasses the full set of development tasks, allowing the developer to continue to use their tool of choice, while filling in the gaps, augmenting standard development tools to provide the essential capabilities needed to do both client and server side business application development. The Generation Framework architecture is also intended to be flexible enough to be reused in other BEA products, such as BEA Repository, but it will be evident to one skilled in the art that the architecture has applications beyond theses examples. Although the Generator Framework architecture does not decide upon or define the implementation language used, code examples given herein are in JAVA. These examples can easily be transposed to C or C++.
  • Within this document, the following conventions are used within this document when displaying UML diagrams:
      • Interfaces are in Italic
      • Abstract classes are in Bold Italic
      • Concrete classes are in Bold.
        Generator Architecture
  • The Generator Framework architecture may be used and customized in several Builder products, such as the Active Expert, C++ Expert, Rose Expert, Configuration Expert and Ice Crystal products. This document describes the architecture of a common Generator Framework, in which the abstraction levels are raised to integrate different tools and types of generation (C++, UBBconfig files, etc.); and different data sources (Contract Repository, Configuration Repository, etc.)
  • FIG. 1 shows the Generator Framework architecture, while FIG. 5 shows a flowchart of a code generation process in accordance with an embodiment of the invention. As shown in FIG. 1, the arrows describe the data flow and the lines ending with dots describe a plug-in relationship. Rules, Filters, Conditions and Notifiers are internal or external pieces of code that plug into the framework. In accordance with one embodiment The Generator Framework architecture is composed of the following elements (although not all elements may be present in each embodiment):
  • The Data Source 100 is the place where the data used for the generation comes from. It is usually considered as a repository (e.g. Builder Contract Repository, CORBA Interface Repository, etc. . . . ). The data source may be stored on any temporary, permanent or semipermanent storage device, hereinafter referred to simply as a storage device. Such storage devices may include memory devices, magnetic devices, hard (fixed) disks, and equivalent storage mechanisms. When the data source is taken directly from a software product or application it may be read directly or in real-time from that application and not e stored as any discrete file or record.
  • The Output Files 102 are the result of the generation. The output files may be output, written to, or stored on any temporary, permanent or semipermanent storage device, hereinafter referred to simply as a storage device, such as described above. When the output files are intended to be sent directly to another software application they may be sent directly or in real-time to that application and not e stored as any discrete file or record.
  • Templates 104 are text files containing both instructions to drive the generation process and pieces of static code that need to be generated.
  • Rules can be internal (106) or external (108) to the framework, and are pieces of logic that implement template instructions. Rules are used to generate output dynamically when static template code is not appropriate.
  • Filters can be internal (110) or external (112) pieces of logic invoked from rules and used to transform data.
  • Conditions 114 are external pieces of logic invoked from rules used to evaluate conditions. Conditions are used to generate code depending on some specific conditions.
  • Notifiers 116 are external pieces of logic used when a rule is invoked. This allows external components to be notified of the progress of the generation process.
  • The Generator Framework is composed of a set of classes providing generation abstractions, using a data source as input, template files and external specific rules to drive the generation process against the data sources, and producing one or many output files. The Generator Framework itself is composed of the following elements:
  • A Parser 130 parses template files and invokes appropriate rules (built-in or specific). The Parser is also the place where all the plug-ins are registered: Rules, Filters, Conditions and Notifiers.
  • A Data Navigation Layer 132 acts as an abstraction to the data source, by providing navigational capabilities inside the data source. This layer implements the Facade design pattern, and exposes only the navigation primitives, not the details of the data source. This and other design patterns are described in Design Patterns, Gamma et al. Addison Wesley, hereby incorporated by reference.
  • Built-in Rules 106 provide basic functions to query symbol values from the data source, navigate through the data source, and open and close files.
  • Built-in Filters 110 provide generic transformation capabilities, such as lowercase/uppercase conversion.
  • Data Navigation Layer 132
  • FIG. 2 illustrates how the data navigation layer is used to provide access to the data source 140. The model used for the data source is independent of specific data source implementations. The resultant abstraction 142 provides access to simple type data elements, and navigation inside the data source. Because the model is based on navigation inside the data source, a context must be maintained. This context is referred to herein as a scope 144. The scope provides access to the data sources as a pointer to the current data. Furthermore, the model used in generation is assumed to be a hierarchical assembly 146, so that the scopes are stacked by the parser as abstract tree structures are traversed. The combined scopes act as a “facade”, isolating the parser from the data source implementation.
  • The Parser 130 provides functions to manipulate the scope stack, such as pushing a new scope on the stack, popping the scope stack, and getting the current scope. The model for the data navigation layer is based on an object-oriented model for data. Scope represents objects from the data source, which have string attributes, accessed through attribute related functions; and references (relationships or pointers to other objects), accessed through reference related functions.
  • Symbol Naming
  • A symbol name is a name for an attribute (simple data) or a reference (related scope), and can be absolute or relative. An absolute symbol name is composed of the scope name and the relative symbol name, for example Interface::name. A relative symbol name can be simple or composed. A simple symbol name is just an identifier, such as “srvList”. A composed symbol name contains several reference names separated by dots and a simple symbol name used to access a related scope symbols. For instance, getting the module name from the operation scope in the Contract Repository would be done using the following symbol:
      • interface.module.name
        If a module and an interface scopes have been pushed on the scope stack when parsing, the same name can be written:
      • Module::name
        The General form of a symbol name is:
      • [<ScopeName>::][<ReferenceName>.]*<Name>
        Element Cardinality
  • Attributes and references can be single or multi-valued. This impacts the usage of the Scope API, because it is not semantically possible to query individually an attribute or a reference which is multi-valued. The Scope API defines functions to both query single and multi-valued attributes and references. Single valued attributes and references are queried by functions that return directly the requested value (character string or scope). Multi-valued attributes and references are queried by functions that return an iterator of character strings or scopes. The Scope API provides an isMultiple( ) function that checks if a symbol name corresponds to a single or multi-valued attribute or reference.
  • Accessing Data Elements
  • The Scope interface implements a getValue( ) method to get the value of a single-valued attribute. This method accepts a relative symbol name only. If the attribute is multi-valued, this function throws an exception. In the following example, the scope method getvalue( ) is used to return the type of a parameter (for example “in”, “out” or “inout”) in IDL generation:
      • String parameterType=currentScope.getValue(“paramType”);
        The Scope interface implements a value so method that returns an iterator of the values for a multi-valued attribute:
      • Iterator i=currentScope.values(“portNumbers”);
        Because the scopes are stacked by the parser, the value of a symbol can also be queried to the parser itself, asking the value of the symbol to the top scope on the stack, then to the previous scope, and so on. When querying symbol values from the parser, both absolute and relative symbol names can be used. The parser itself implements a getValue( ) and a value so methods, which retrieve directly the corresponding attribute value(s) if the symbol name is absolute; and retrieve the value(s) of the attribute of the current scope (i.e. the scope at the top of the scope stack) if the symbol name is relative.
        Scope Navigation
  • Scope Navigation is performed by means of pointers or pointer-like references. A reference provides access to a list of (sub-)scopes related to the current scope. Similarly to the attribute names, reference names are either relative or absolute. For instance, in IDL generation, a Module scope gives access to an “interface list” reference, which provides access to the interfaces of the module. The relation between the scope navigation and the data source navigation is shown in FIG. 2. The scope method getScope( ) takes a reference name as input and returns the related scope. If the reference is multi-valued, this functions throws an exception. The following shows an example:
      • Scope moduleScope=interfaceScope.getScope(“module”);
        The scope method scopes( ) takes a reference name as input and returns an iterator of the corresponding scopes, as shown in the example below:
      • Iterator i=moduleScope.scopes(“interfaces”);
        Similarly, the parser allows access to references through the scope stack by providing a getScope( ) and scopes( ) methods, accepting both absolute and relative reference names. For instance, this allows access to the module interface list at the operation scope level, by calling:
      • parser.scopes(“Module::interfaceList”);
        Rules
  • In the template files, a rule is represented by a string delimited by separators, containing a rule name and zero or more arguments. A rule name is an identifier containing uppercase characters. A rule argument contains text (which may also contain nested rules). In terms of regular expressions, a rule has the following syntax:
      • $[ruleName[:ruleArgument]*]
        The rule delimiter symbols “$[“, ”]” and “:” may be changed if appropriate. They may even be changeable programmatically. Examples of these are shown below:
      • $[OPEN:$[APPNAME].cpp]
      • $[VAL:date:U]
        Rule Interface
  • For each rule, there is a piece of code implementing the rule logic. This piece of code is implemented by an execute( ) method which is invoked by the parser. The parser's built-in rules are implemented in the Generator Framework itself. Specific rules are implemented out of the Generator Framework. The Rule interface defines the following abstract method:
      • public abstract String execute(String[]args, Parser p) throws GenException;
        where args are the arguments passed to the rule (arg[0] is the rule name itself). The returned value contains the result of the rule execution, and can then be either printed to the output file or used as an argument to an upper-level rule (see also the OPEN rule example above). If a rule does not generate any output, its return value is null. Rule arguments may contain other rules. It is up to the rule implementation to decide if the arguments should be parsed again. In order to do this, the rule calls the parsed method from the parser:
      • String parse(String str) throws GenException;
        Built-in Rules
  • Built-in rules provide a generic set of rule implementation for data access, data navigation and boolean conditions. These rules are part of the Generator Framework. The (non-exhaustive) list and syntax of these rules is described below in the section titled Built-in
  • Rules Syntax.
  • Templates
  • FIG. 3 shows an example of a template 150 as it may used to generate code 154. Templates are text files that drive the generation process. Template files contain lines of text in which rules are parsed by the generator parser. Template lines also contain static text which is sent directly to the generator output. Some rules (ITERATE, COND) define the notion of a block of template code which is parsed zero or several times depending on some conditions. These blocks of template code are put between the ‘@{’ and ‘@}’ markers. The following is a yacc-like syntax description of the template files. The terminal symbols are in uppercase.
    TemplateFile: TemplateLines ;
    TemplateLines:| TemplateLines TemplateLine ;
    TemplateLine: BlockDelimiter RET | TemplateElements
    RET ;
    TemplateElements:| TemplateElements TemplateElement;
    TemplateElement: Rule | Text;
    Rule: ‘$[’ RuleName RuleArgs ‘]’ ;
    RuleName: RULE_IDENT;
    RuleArgs: | ‘:’ TemplateElements;
    Text: TEXT ;
    BlockDelimiter: ‘@{’| ‘@}’ ;

    Filters
  • Filters are used to transform data during the generation. A filter is a piece of logic that takes a string and a scope as input, and outputs the transformed string. Transformations include:
      • Mapping a name to another name.
      • Prepending/appending characters.
      • Changing character case.
  • Filters are initially registered with the Parser in the framework. Each filter has a name, and may allow several transformations to take place. For example, the “Case” filter (built-in filter) has the two “U” and “L” transformations, for uppercase and lowercase conversion respectively. The Parser provides functions to add and remove filters, and to get a filter by its name.
  • TextFilter Interface
  • Text Filters are used to transform any kind of data during the generation process. Text Filters are used by the FILTER rule (see also the FILTER Rule below), and can be used by external rules. The TextFilter interface defines the following abstract method:
    abstract public String transform(Scope scope,
                String input,
                String transformationName);

    A filter is invoked from a rule, either built-in (such as the FILTER rule) or specific. The filter name and transformation name are typically arguments to a rule, as shown in the example below:
      • $[FILTER:$[VAL:moduleName]:Case:U]
        SymbolFilter Interface
  • The SymbolFilter interface is used to transform the value of a symbol. The difference with Text Filters is that a symbol bears more information than simple text from the scope point of view. For instance, the type of the symbol that can be used to transform data includes adding double quotes if the symbol is a string, or generating Y or N if the symbol is boolean. Symbol Filters are used by the VAL rule (see also the VAL Rule below), and can be used by external rules. The SymbolFilter interface defines the following abstract method:
    abstract public String transform(Scope scope,
                String symbolName,
                String input,
                String transformationName);

    Using Filters
  • When implementing Filters, there is the alternative between using:
      • $[FILTER:$[VAL:symbolName]:filterName:transformationName]
        or
      • $[VAL:symbolName:filterName:transformationName]
        These two forms are equivalent, unless the symbol name is meaningful to perform the transformation, like the formatting depending on the symbol type above.
        Conditions
  • Conditions are used to generate code conditionally. Conditions are pieces of code that are plugged into the Generator Framework. The Parser provides functions to add and remove conditions, and to get a condition by its name.
  • Condition Interface
  • The Condition interface implements the following abstract method:
      • abstract public boolean isApplicable(Scope scope);
        Conditions are used by the COND rule (see COND Rule below), and can be used by external rules.
        Generic Conditions
  • Generic Conditions are implemented by the COND rule. This rule accepts complex conditions as input, expressed by symbol values, constants and logical operators. The condition text is parsed by the COND rule code. The syntax of generic conditions is still an open issue. Below is an example of a generic condition:
    $[COND:domain.machines.$# > 1]
    @{
    *NETWORK
    $[ITERATE:domain.machines]
    @{
    $[VAL:lmid] NADDR=$[VAL:naddr] NLSADDR=$[VAL:nlsaddr]
    @}
    @}
  • In this example, domain. machines is a composed symbol name representing a reference. The $# notation is the number of elements of this reference. Below is a possible syntax for generic conditions, the notation and syntax are borrowed from “The JAVA Language Specification” by the JAVA Team, Addison Wesley, 1996, hereby incorporated by reference.
    ConditionalExpression:
    ConditionalAndExpression
    ConditionalExpression || ConditionalAndExpression
    ConditionalAndExpression:
    EqualityExpression
    ConditionalAndExpression && EqualityExpression
    EqualityExpression:
    UnaryExpression
    EqualityExpression RelationalOperator UnaryExpression
    RelationalOperator: one of
    == != > < >= <=
    UnaryExpression:
    Expression
    ! UnaryExpression
    Expression:
    Identifier
    Constant
    ( ConditionalExpression )
    Identifier:
    Literal
    Identifier . Literal
    Identifier . $#
    Constant:
    NumberConstant
    StringConstant
    NumberConstant:
    [−]?[0-9]+
    StringConstant:
    “ StringChars ”

    Conditional Lists and Iterations
  • When navigating the data source with the scopes, it is often desirable to select related data elements depending on some condition. For instance, when generating code from IDL, the list of input parameters may be needed: if the model only provides a list of parameters (in, out, and inout), a conditional list may be useful to do this. This is the purpose of the CONDLIST and CONDITERATE rules, which apply a condition (named orgeneric) to each scope element of the list or the iteration, and then process their block of template code.
  • Notifications
  • Notifiers are used to send messages to external components that use the Generator Framework. Notifiers are typically used to inform external components (such as progress bars, output text widgets) about the status of the generation. A component wanting to be notified about the generation progress must simply implement the Notifier interface (see below). Notifications are sent in rules using the parser notify( ) method. Notifiers are registered in the parser for a specific rule (e.g. OPEN, CLOSE). Two conditions must be met for receiving notification messages from a rule:
      • The rule must call notify( ) in its execute( ) method.
      • The notifier must be registered in the parser for that rule.
        Notifier Interface
  • The Notifier interface defines the following abstract method:
    abstract public void ruleInvoked(String ruleName,
                Parser P,
                String message);

    Protected Code Sections
  • Protected code sections allow users of the Generator Framework to define parts of the output file (or files) being untouched by the generation process. This is a powerful mechanism used to preserve user code while still being able to apply the generator to produce updated versions of the output files. For instance, defining a protected code section in a function implementation allows to keep the user code in the output file. Protected code sections are identified by a particular rule in the templates (see also the PCS Rule below). Unicity of a protected code section depends on a tag—which is defined by the person writing the template. The tag generated in the output file is parsed by the PCS rule to ensure uniqueness.
  • 3. Generator Framework
  • The UML diagram in FIG. 4 shows the class architecture of the framework. The meaning of the UML representation 160 in FIG. 4 will be evident to one skill in the art. As shown therein, the parser is the central point of the Generator Framework. It's functions include invoking the parsing of a template file, and executing rules which in turn change the scope of the parser. Scopes are organized in a stack inside the parser. The following class and interface specifications are given as examples, although it will be evident to one skilled in the art that the specific classes given are
  • Scope Class
  • The Scope class is an abstract class providing access to a data source (Contract Repository, Configuration Repository, UREP, . . . ).
    package com.beasys.generator;
    public abstract class Scope {
       //
       // General purpose functions
       //
    public String getName( );
    public String getType(String symbolName);
    public boolean isMultiple(String symbolName);
       //
       // Attribute-related functions
       //
    public abstract boolean hasAttribute(String symbolName);
    public abstract int getAttributeCount(String symbolName);
    public abstract String getValue(String symbolName)
          throws CardinalityException;
    public abstract Enumeration values(String symbolName);
       //
       // Reference related functions
       //
    public abstract boolean hasReference(String symbolName);
    public abstract int getReferenceCount(String symbolName);
    public abstract Scope getScope(String symbolName)
          throws CardinalityException;
    public abstract Enumeration values(String symbol Name);
    }

    Rule Class
  • The Rule class defines the function that implements a rule. A rule is invoked by the parser when a rule invocation is recognized in the templates.
    package com.beasys.generator;
    public abstract class Rule {
    public String execute(String[ ] args, Parser p) throws GenException;
    }

    Parser Class
  • The Parser class contains the core of the Generator Framework, parsing template files and invoking rules.
    package com.beasys.generator;
    public class Parser {
    public Parser( );
    //
    // Scope Management
    //
    public Scope getCurrentScope( );
    public String getValue(String symbolName)
    throws CardinalityException;
    public Enumeration values(String symbolName);
    public Scope getScope(String symbolName) throws CardinalityException;
    public Enumeration scopes(String symbolName);
    public void popScope( );
    public void pushScope(Scope s);
    //
    // Rule Management
    //
    public void addRule(Rule r);
    public void removeRule(String ruleName);
    //
    // Condition Management
    //
    public void addCondition(String name, Condition c);
    public void removeCondition(String name);
    public Condition getCondition(String name);
    public boolean hasCondition(String name);
    //
    // Filter Management
    //
    public void addFilter(Filter f);
    public void removeFilter(String);
    public Filter getFilter(String name);
    //
    // Notifier Management
    //
    public void addNotifier(String ruleName, Notifier n);
    public void removeNotifier(String ruleName, Notifier);
    public void notify(Rule r, String message);
    //
    // Template Management
    //
    public void loadTemplates(String)
    throws ParserException;
    //
    // Parsing Functions
    //
    public String parse(String s)
    throws GenException;
    public void parseTemplate(String templateName)
    throws GenException;
    //
    // Parser Properties
    //
    public String getOutputDir( );
    public void setOutputDir(String dirName);
    public String getRootDir( );
    public void setRootDir(String dirName);
    public void setTemplateDir(String dirName);
    }

    Filter Class
  • The Filter class is the common superclass of the SymbolFilter and TextFilter classes:
    abstract public class Filter
    {
    protected Filter(String name);
    public String getName( );
    public abstract boolean hasTransformation(String name);
    }

    SymbolFilter Class
  • The SymbolFilter class is used by the VAL rule to transform a symbol value.
    abstract public class SymbolFilter
    extends Filter
    {
    protected SymbolFilter(String);
    abstract public String transform(Scope s,
              String symbolValue,
              String input,
              String transfName);
    }

    TextFilter Class
  • The TextFilter class is used by the FILTER and VAL rules to transform a text value.
    abstract public class TextFilter
    extends Filter
    {
    protected TextFilter(String);
    abstract public String transform(Scope s,
              String input,
              String transfName);
    }

    Condition Interface
  • The Condition interface defines a isApplicable( ) method used to
  • conditionally generate code. Conditions are used by the COND rule.
    public interface Condition
    {
    public abstract boolean isApplicable(Scope scope);
    }

    Notifier Interface
  • The Notifier interface defines a method used to notify external components about the status of the generation. External components are notified from rules when the rule invokes the notify( ) method of the Parser class.
    public interface Notifier
    {
    public abstract void ruleInvoked(String ruleName,
              Parser p,
              String message);
    }

    4. Built-in Rules Syntax
  • The following rules are given as examples of the type of rules that can be used with the invention. It will be evident to one skilled in the art that other rules can be used.
  • OPEN Rule
  • Synopsis
      • $[OPEN:<fileName>]
        Description
  • The OPEN rule opens the file <fileName> for output. The generation output is written to the file <fileName>. The name of <fileName> can contain static values such as “test.idl”, or symbols for substitution, such as “$[VAL: moduleName].idl”.
  • EXAMPLE
      • $[OPEN:$[VAL:moduleName].idl]
        CLOSE Rule
        Synopsis
      • $[CLOSE]
        Description
  • The CLOSE rule closes the current output file. The generator output is restored to the previous opened output file, if any. If there is no more output file, any rule other than $[OPEN] causes the generator to fail.
  • SCOPE Rule
  • Synopsis
      • $[SCOPE:<scopeName>]
        Description
  • The SCOPE rule ensures that the current scope name is the same as the scope name passed in the rule. The generator fails if the current scope name is not <scopeName>. This rule has no other effect.
  • VAL Rule
  • Synopsis
      • $[VAL:<symbolName>]
      • $[VAL:<symbolName>:<filterName>:<transformationName>]
        Description
  • The VAL rule is used to return the value of symbols. A symbol value pertains to the current scope stack. Symbol values are retrieved against scopes from the scope stack, using the getValue( ) method of the Scope class. Usually, the VAL rule can only be used on single-valued attributes. An exception is thrown if this rule is used on a multiple-valued attribute. However, the VAL rule can be used with a symbol representing a multi-valued attribute only if it is invoked from an iterated code block in the LIST, ITERATE, CONDLIST and CONDITERATE rules. The second form allows the framework to apply a symbol or a text filter to the symbol value. The <filterName> parameter is the name of the filter to be used. The <transformationName> parameter is the name of a valid transformation in this filter.
  • EXAMPLE
      • $(VAL:passingMode]$[VAL:type]$[VAL:parameterName:Case:U]
        FILTER Rule
        Synopsis
      • $[FILTER:<text>:<filterName>:<transformationName>]
        Description
  • The FILTER rule is used to apply a text filter to some text block. The <text> argument is parsed by the parser (it may contain rules). The <filterName> parameter is the name of the text filter to be used. The <transformationName> parameter is the name of a valid transformation in this text filter.
  • EXAMPLE
      • $[FILTER:$[VAL:parameterType]:FML:outDecl]
        COND Rule
  • Synopsis
    $[COND:<condition>:<codeBlock>]
    $[COND:<condition>]
    @{
      <conditionalCodeBlock>
    @}

    Description
  • The COND rule has two forms: the first forms allows to conditionally generate a (one line) piece of code depending on a named or generic condition. The second form allows to generate a block of code (on multiple lines) depending on a named or generic condition. The code block is delimited by the ‘@{’ and ‘@}’ markers.
  • ITERATE Rule
  • Synopsis
    $[ITERATE:<symbolName>]
    @{
      <iteratedCodeBlock>
    @}

    Description
  • The ITERATE rule repeats the same block of code for a given symbol name. The iteration symbol name is a static name corresponding to a multi-valued reference related to the current scope. The iterated code block (between the ‘@{’ and ‘@}’ markers) is a piece of template code that is iterated for all the objects returned by the iteration at the scope level. Rules may be invoked inside this block, with a scope corresponding to the iterated objects. The iteration symbol name can also be a multi-valued attribute. In that case, the iterated code block is invoked with the same scope, and the VAL rule can be used to retrieve the sequenced values of the multi-valued attribute.
  • LIST Rule
  • Synopsis
    $[LIST:<listName>:<codeBlock>]
    $[LIST:<listName>:<codeBlock>:<separator>]

    Description
  • The LIST rule is similar to the ITERATE rule. Instead of iterating several lines of code, it outputs a list of <codeBlock> elements, separated by a separator string (the default separator is “,”)
  • EXAMPLE
      • $[VAL:operationName]($[LIST:parameterList:$[VAL:parameterName]])
        CONDITERATE Rule
  • Synopsis
    $[CONDITERATE:<symbolName>]
    @{
      <iteratedCodeBlock>
    @}

    Description
  • The CONDITERATE rule repeats the same block of code for a given symbol name, depending on a named or generic condition. The iteration symbol name is a static name corresponding to a multi-valued reference related to the current scope. The iterated code block (between the ‘@{’ and ‘@}’ markers) is a piece of template code that is iterated for all the objects returned by the iteration at the scope level which satisfy the named or generic condition. Rules may be invoked inside this block, with a scope corresponding to the iterated objects.
  • CONDLIST Rule
  • Synopsis
    $[CONDLIST:<listName>:<condition>:<codeBlock>]
    $[CONDLIST:<listName>:<condition>:<codeBlock>:<separator>]

    Description
  • The CONDLIST rule is the result of the composition of a LIST rule and a COND rule. Each element generated in the list and used as the current scope in the code block must satisfy the named or generic condition.
  • EXAMPLE
      • $[CONDLIST:parameterList:passingMode==“in”:$[VAL:parameterName]]
        INCLUDE Rule
        Synopsis
      • $[INCLUDE:<templateName>]
        Description
  • The INCLUDE rule is used to include a template inside the current template.
  • EXAMPLE
      • $[INCLUDE:t_funcDecl]
        PCS Rule
        Synopsis
      • $[PCS:<pcs_tag>]
        Description
  • The PCS rule defines the location of a protected code section in a template. The argument to the PCS rule is a tag which is parsed by the parser. In the output file, the protected code section will be delimited by the two lines shown below. Any comments put in the template on the $[PCS: . . . ] line will be preserved in the output file for both begin and end markers.
    $ [BEGIN_PCS:<parsed_tag>]
    $ [END_PCS]
  • 5. TEMPLATE EXAMPLE
  • The following example was developed as a prototype for validating the Generator Framework architecture. This particular template example is used to generate IDL files:
    $[SCOPE:Module]
    $[OPEN:$[VAL:name].idl]
    #
    # File: $[VAL:name].idl
    #
    module $[VAL:name] {
     $[ITERATE:interfaceList]
     @{
      interface $[VAL:name] {
       $[ITERATE:operationList]
       @{
        $[VAL:retType]
         $[VAL:name]($[LIST:paramList:$[VAL:passMode]
    $[VAL:type] $[VAL:name]]);
       @}
      }
     @}
    }
    $[CLOSE]
  • In this example, the “name” symbol is used several times to get the names of modules, interfaces, operations and parameters, respectively. The ITERATE and LIST rules manage the data navigation so that the “name” symbol is each time the name of the element in the corresponding scope.
  • The foregoing description has been provided for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Obviously, many modifications and variations will be apparent to the practitioner skilled in the art. The embodiments were chosen and described in order to best explain the principles of the invention and its practical application, thereby enabling others skilled in the art to understand the invention for various embodiments and with various modifications that are suited to the particular use contemplated. It is intended that the scope of the invention be defined by the following claims and their equivalence.

Claims (18)

1. A system for code generation, comprising:
a data navigation layer that provides navigational access to a software application source data, via pointers to the source data;
a template that specifies instructions to drive a code generation process that is applied to the source data;
a parser that parses the template in accordance with rules, and accesses the source data via the pointers of the data navigation layer, to generate code; and
a code output logic that outputs the generated code.
2. The system of claim 1 wherein the navigation layer allows mapping of an abstracted data representation to the source data.
3. The system of claim 1, further comprising rules that implement template instructions and dynamically generate output.
4. The system of claim 1, wherein the system further comprises filters.
5. The system of claim 4, wherein the rules implement the template instructions, and wherein the filters are used to transform the source data.
6. The system according to claim 4, wherein the rules and filters are registered as plug-ins to the parser.
7. The system of claim 1, wherein the code output logic outputs the generated code to a storage device.
8. The system of claim 1, wherein the parser comprises a set of classes providing generation abstractions.
9. The system of claim 1, wherein the source data includes protected code sections that allow users to define parts of the output file to remain untouched by the code generation process.
10. A method of generating computer code, comprising the steps of:
accessing a data navigation layer that provides navigational access to a software application source data, via pointers to the source data;
accessing a template that specifies instructions to drive a code generation process that is applied to the source data;
parsing the template in accordance with rules, and accessing the source data via the pointers of the data navigation layer, to generate code; and
outputting the generated code.
11. The method of claim 10 wherein the navigation layer allows mapping of an abstracted data representation to the source data.
12. The method of claim 10, further comprising accessing rules that implement template instructions and dynamically generate output.
13. The method of claim 10, further comprising accessing filters, wherein the rules implement the template instructions, and wherein the filters are used to transform the source data.
14. The method according to claim 13, wherein the rules and filters are registered as plug-ins.
15. The method of claim 10, wherein the step of outputting includes outputting the generated code to a storage device.
16. The method of claim 10, wherein the step of parsing includes accessing a set of classes that provide generation abstractions.
17. The method of claim 10, further comprising defining in the source data a protected code section that allow users to define parts of the output file to remain untouched by the code generation process.
18. A computer readable medium including instructions stored thereon which when executed cause the computer to perform the steps of:
accessing a data navigation layer that provides navigational access to a software application design product source data, via pointers to the source data;
accessing a template that specifies instructions to drive a code generation process that is applied to the source data;
parsing the template in accordance with rules, and accessing the source data via the pointers of the data navigation layer, to generate code; and
outputting the generated code.
US11/176,925 2000-10-04 2005-07-07 System and method for computing code generation Abandoned US20050246681A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US11/176,925 US20050246681A1 (en) 2000-10-04 2005-07-07 System and method for computing code generation

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US23855900P 2000-10-04 2000-10-04
US23856100P 2000-10-04 2000-10-04
US09/970,741 US6973640B2 (en) 2000-10-04 2001-10-04 System and method for computer code generation
US11/176,925 US20050246681A1 (en) 2000-10-04 2005-07-07 System and method for computing code generation

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US09/970,741 Continuation US6973640B2 (en) 2000-10-04 2001-10-04 System and method for computer code generation

Publications (1)

Publication Number Publication Date
US20050246681A1 true US20050246681A1 (en) 2005-11-03

Family

ID=27399113

Family Applications (3)

Application Number Title Priority Date Filing Date
US09/970,917 Expired - Lifetime US7047518B2 (en) 2000-10-04 2001-10-04 System for software application development and modeling
US09/970,741 Expired - Lifetime US6973640B2 (en) 2000-10-04 2001-10-04 System and method for computer code generation
US11/176,925 Abandoned US20050246681A1 (en) 2000-10-04 2005-07-07 System and method for computing code generation

Family Applications Before (2)

Application Number Title Priority Date Filing Date
US09/970,917 Expired - Lifetime US7047518B2 (en) 2000-10-04 2001-10-04 System for software application development and modeling
US09/970,741 Expired - Lifetime US6973640B2 (en) 2000-10-04 2001-10-04 System and method for computer code generation

Country Status (1)

Country Link
US (3) US7047518B2 (en)

Cited By (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040216085A1 (en) * 2003-04-22 2004-10-28 Computer Associates Think, Inc. System and method for integrating object-oriented model profiles and object-oriented programming languages
US20080134152A1 (en) * 2006-12-01 2008-06-05 Elias Edde Producer graph oriented programming framework with scenario support
US20080134161A1 (en) * 2006-12-01 2008-06-05 Fady Chamieh Producer graph oriented programming framework with undo, redo, and abort execution support
US20080134138A1 (en) * 2006-12-01 2008-06-05 Fady Chamieh Producer graph oriented programming and execution
CN102063324A (en) * 2010-12-31 2011-05-18 杭州依赛通信有限公司 Method and system for implementing automatic programming
US20110302553A1 (en) * 2010-06-04 2011-12-08 Microsoft Corporation Generating text manipulation programs using input-output examples
US8307337B2 (en) 2006-12-01 2012-11-06 Murex S.A.S. Parallelization and instrumentation in a producer graph oriented programming framework
US20140123103A1 (en) * 2009-06-05 2014-05-01 Maxymiser Ltd. Method of website optimisation
US20150007128A1 (en) * 2013-06-28 2015-01-01 Successfactors, Inc. Model Framework for Applications
US9552335B2 (en) 2012-06-04 2017-01-24 Microsoft Technology Licensing, Llc Expedited techniques for generating string manipulation programs
US9613115B2 (en) 2010-07-12 2017-04-04 Microsoft Technology Licensing, Llc Generating programs based on input-output examples using converter modules
US10671353B2 (en) 2018-01-31 2020-06-02 Microsoft Technology Licensing, Llc Programming-by-example using disjunctive programs
US10831451B2 (en) * 2017-12-01 2020-11-10 Microsoft Technology Licensing, Llc Synthesized programming-by-example programs
US10846298B2 (en) 2016-10-28 2020-11-24 Microsoft Technology Licensing, Llc Record profiling for dataset sampling
US11256710B2 (en) 2016-10-20 2022-02-22 Microsoft Technology Licensing, Llc String transformation sub-program suggestion
US11620304B2 (en) 2016-10-20 2023-04-04 Microsoft Technology Licensing, Llc Example management for string transformation

Families Citing this family (334)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7334216B2 (en) * 2000-04-04 2008-02-19 Sosy, Inc. Method and apparatus for automatic generation of information system user interfaces
US7885820B1 (en) 2000-07-19 2011-02-08 Convergys Cmg Utah, Inc. Expert system supported interactive product selection and recommendation
US6886038B1 (en) * 2000-10-24 2005-04-26 Microsoft Corporation System and method for restricting data transfers and managing software components of distributed computers
EP1205841A1 (en) * 2000-10-26 2002-05-15 Ebeon Research &amp; Development Limited Software development processes
US7290243B1 (en) * 2001-02-28 2007-10-30 Apple Inc. Method and apparatus for application building using build styles
US20030023539A1 (en) * 2001-07-27 2003-01-30 Wilce Scot D. Systems and methods for facilitating agreement definition via an agreement modeling system
WO2003014927A2 (en) * 2001-08-08 2003-02-20 Trivium Systems Inc. Scalable messaging platform for the integration of business software components
US8739112B1 (en) * 2001-08-27 2014-05-27 Goldman, Sachs & Co. Developers' resource portal
US7685562B2 (en) * 2001-09-28 2010-03-23 Siebel Systems, Inc. Method and code generator for integrating different enterprise business applications
US7069546B2 (en) * 2001-12-03 2006-06-27 Corrigent Systems Ltd. Generic framework for embedded software development
US8244702B2 (en) * 2002-02-26 2012-08-14 International Business Machines Corporation Modification of a data repository based on an abstract data representation
US6996558B2 (en) * 2002-02-26 2006-02-07 International Business Machines Corporation Application portability and extensibility through database schema and query abstraction
US7533026B2 (en) * 2002-04-12 2009-05-12 International Business Machines Corporation Facilitating management of service elements usable in providing information technology service offerings
US7562022B2 (en) * 2002-04-12 2009-07-14 International Business Machines Corporation Packaging and distributing service elements
US7302400B2 (en) * 2002-04-12 2007-11-27 International Business Machines Corporation System and method for the development and deployment of service elements
US7440902B2 (en) * 2002-04-12 2008-10-21 International Business Machines Corporation Service development tool and capabilities for facilitating management of service elements
FR2840089B1 (en) * 2002-05-23 2004-08-27 Cit Alcatel SOFTWARE DEVELOPMENT TOOL FOR ENSURING LINKS BETWEEN ULM MODELS AND THEIR IMPLEMENTATION IN THE CORBA ENVIRONMENT
US20040059802A1 (en) * 2002-06-24 2004-03-25 Christian Jacquemot Modeling states and/or transitions in a computer system
US8639542B2 (en) * 2002-06-27 2014-01-28 Siebel Systems, Inc. Method and apparatus to facilitate development of a customer-specific business process model
US7424702B1 (en) 2002-08-19 2008-09-09 Sprint Communications Company L.P. Data integration techniques for use in enterprise architecture modeling
AU2003279115A1 (en) * 2002-10-03 2004-04-23 Whisperwire, Inc. System and method for bundling resources
US8015541B1 (en) * 2002-10-24 2011-09-06 Rage Frameworks, Inc. Business process technology for the enterprise
US7367018B2 (en) * 2002-10-25 2008-04-29 Aspen Technology, Inc. System and method for organizing and sharing of process plant design and operations data
US7711670B2 (en) * 2002-11-13 2010-05-04 Sap Ag Agent engine
US7412658B2 (en) * 2002-11-14 2008-08-12 Sap Ag Modeling system for graphic user interface
TWI262383B (en) * 2003-01-10 2006-09-21 Univ Nat Cheng Kung A generic software testing system and method
US7140003B2 (en) * 2003-02-14 2006-11-21 International Business Machines Corporation Method and system for specifying sets of instructions for selection by an instruction generator
US8122106B2 (en) 2003-03-06 2012-02-21 Microsoft Corporation Integrating design, deployment, and management phases for systems
US7054877B2 (en) * 2003-03-31 2006-05-30 International Business Machines Corporation Dealing with composite data through data model entities
US7302677B2 (en) * 2003-05-08 2007-11-27 Microsoft Corporation Event driven graph explorer for model-based testing of software
US7546575B1 (en) * 2003-06-09 2009-06-09 Dillman Frederick J System and method for using blueprints to provide a software solution for an enterprise
US7051279B2 (en) * 2003-07-08 2006-05-23 Intentional Software Corporation Method and system for providing multiple levels of help information for a computer program
US20050010893A1 (en) * 2003-07-11 2005-01-13 Schmidt John G.E. Process for creating middleware adapters
US8219968B2 (en) * 2003-07-17 2012-07-10 Raytheon Company Designing computer programs
US7899843B2 (en) * 2003-09-19 2011-03-01 International Business Machines Corporation Expanding the scope of an annotation to an entity level
US20070055747A1 (en) * 2003-09-23 2007-03-08 Loh Tien W Method for accessing and displaying dynamic data in web application
US7293252B2 (en) * 2003-09-30 2007-11-06 Oracle International Corporation Case modelling
US7296256B2 (en) * 2003-10-20 2007-11-13 International Business Machines Corporation Method and apparatus for automatic modeling building using inference for IT systems
US20050114832A1 (en) * 2003-11-24 2005-05-26 Microsoft Corporation Automatically generating program code from a functional model of software
US20050154742A1 (en) * 2003-11-26 2005-07-14 Aviv Roth Business software application generation system and method
US7752559B1 (en) 2003-12-05 2010-07-06 The Mathworks, Inc. Graphical model preparation for embedded deployment
US7900133B2 (en) 2003-12-09 2011-03-01 International Business Machines Corporation Annotation structure type determination
US7434200B2 (en) * 2003-12-11 2008-10-07 Sap Ag Using incremental generation to develop software applications
US7543274B2 (en) * 2003-12-22 2009-06-02 The United States Of America As Represented By The Administrator Of The National Aeronautics And Space Administration System and method for deriving a process-based specification
US7650590B2 (en) * 2004-01-13 2010-01-19 Sap Ag Flexible code generation
US7685576B2 (en) * 2004-01-26 2010-03-23 Siemens Corporation System and method for model based system testing of interactive applications
US20050177814A1 (en) * 2004-01-26 2005-08-11 Martlage Aaron E. System for providing a graphical representation of user interface and executable application operation
US20050165720A1 (en) * 2004-01-27 2005-07-28 Mckeown Thomas Modular assembly of software and method of configuring same
US7533365B1 (en) 2004-02-03 2009-05-12 Borland Software Corporation Development system with methodology for run-time restoration of UML model from program code
US20050198610A1 (en) * 2004-03-03 2005-09-08 Ulf Fildebrandt Providing and using design time support
US7665085B2 (en) * 2004-03-15 2010-02-16 Ramco Systems Limited Flexible deployment of software applications
US7426713B2 (en) * 2004-03-31 2008-09-16 International Business Machines Corporation Controlling a GUI display for a plug-in
US7647579B2 (en) * 2004-03-31 2010-01-12 International Business Machines Corporation Method, system and program product for detecting deviation from software development best practice resource in a code sharing system
US20050246529A1 (en) * 2004-04-30 2005-11-03 Microsoft Corporation Isolated persistent identity storage for authentication of computing devies
DE102004023634B4 (en) * 2004-05-10 2007-09-27 Siemens Ag Method for checking the completeness and consistency of an information library
JP4100630B2 (en) * 2004-05-14 2008-06-11 インターナショナル・ビジネス・マシーンズ・コーポレーション UML design method
US7849438B1 (en) * 2004-05-27 2010-12-07 Sprint Communications Company L.P. Enterprise software development process for outsourced developers
US20050278709A1 (en) * 2004-06-15 2005-12-15 Manjula Sridhar Resource definition language for network management application development
US20060036721A1 (en) * 2004-06-15 2006-02-16 Dong Zhao Run-time tool for network management application
US7555743B2 (en) * 2004-06-15 2009-06-30 Alcatel-Lucent Usa Inc. SNMP agent code generation and SNMP agent framework for network management application development
US20050278693A1 (en) * 2004-06-15 2005-12-15 Brunell Edward G Distribution adaptor for network management application development
US20050278708A1 (en) * 2004-06-15 2005-12-15 Dong Zhao Event management framework for network management application development
US20060070082A1 (en) * 2004-06-15 2006-03-30 Manjula Sridhar Managed object framework for network management application development
US20050278361A1 (en) * 2004-06-15 2005-12-15 Brunell Edward G View definition language for network management application development
US20060004856A1 (en) * 2004-06-15 2006-01-05 Xiangyang Shen Data management and persistence frameworks for network management application development
US8341590B1 (en) 2007-12-12 2012-12-25 Accurev, Inc. System for relating workflow status to code component status in a software project
US9292276B1 (en) 2004-07-19 2016-03-22 Micro Focus (IP) Development Limited Method and system for utilizing change packages
US8667465B2 (en) * 2008-03-31 2014-03-04 Accurev, Inc. System for estimating a software product release time from version information
US8473893B2 (en) * 2008-09-30 2013-06-25 Accurev, Inc. Integration of external software analysis processes with software configuration management applications
US8548967B1 (en) * 2007-12-12 2013-10-01 Accurev, Inc. System for visual query and manipulation of configuration management records
CN101052948A (en) * 2004-09-10 2007-10-10 图形公司 Object process graph application development system
US7590942B2 (en) * 2004-09-16 2009-09-15 Novatech Llc System, method and computer program product for documenting and managing execution of procedures in a graphical interface environment
US20060064667A1 (en) * 2004-09-20 2006-03-23 Freitas Jose D System and method of model-driven development using a transformation model
US7979849B2 (en) * 2004-10-15 2011-07-12 Cisco Technology, Inc. Automatic model-based testing
US7822592B2 (en) * 2004-10-18 2010-10-26 Manthatron-Ip Limited Acting on a subject system
US7770159B2 (en) * 2004-10-20 2010-08-03 Microsoft Corporation Virtual types
US8266631B1 (en) 2004-10-28 2012-09-11 Curen Software Enterprises, L.L.C. Calling a second functionality by a first functionality
US7823169B1 (en) 2004-10-28 2010-10-26 Wheeler Thomas T Performing operations by a first functionality within a second functionality in a same or in a different programming language
US7774789B1 (en) 2004-10-28 2010-08-10 Wheeler Thomas T Creating a proxy object and providing information related to a proxy object
US7861218B2 (en) * 2004-10-28 2010-12-28 International Business Machines Corporation Computer method and system for enforcing derived union constraints
US7827522B2 (en) * 2004-10-28 2010-11-02 International Business Machines Corporation Computer method and apparatus for implementing redefinition of model features
US20060101381A1 (en) * 2004-10-29 2006-05-11 International Business Machines Corporation Computer method and apparatus for implementing subsets constraints in programming models
US7861214B2 (en) * 2004-11-08 2010-12-28 International Business Machines Corporation Computer method and apparatus for collapsing programming metamodels
US20060116999A1 (en) * 2004-11-30 2006-06-01 International Business Machines Corporation Sequential stepwise query condition building
US8112459B2 (en) * 2004-12-17 2012-02-07 International Business Machines Corporation Creating a logical table from multiple differently formatted physical tables having different access methods
US8131744B2 (en) * 2004-12-17 2012-03-06 International Business Machines Corporation Well organized query result sets
US7739654B2 (en) * 2004-12-22 2010-06-15 Hewlett-Packard Development Company, L.P. Model curation for integrated circuit designs
JP4335798B2 (en) * 2004-12-28 2009-09-30 富士通マイクロエレクトロニクス株式会社 Verification support device, verification support method, verification support program, and recording medium
US7469402B2 (en) * 2004-12-28 2008-12-23 Sap Aktiengesellschaft Pluggable model framework
US7624097B2 (en) * 2005-01-14 2009-11-24 International Business Machines Corporation Abstract records
US8122012B2 (en) 2005-01-14 2012-02-21 International Business Machines Corporation Abstract record timeline rendering/display
US7853931B2 (en) * 2005-01-19 2010-12-14 Sap Ag System and method for automatically generating flow diagrams
US7610576B2 (en) * 2005-01-19 2009-10-27 Sap Ag System and method for simultaneous display of processes and associated files
US7814457B2 (en) * 2005-01-19 2010-10-12 Sap Ag System and method for revising flow diagrams displaying a process
US7716631B1 (en) * 2005-01-20 2010-05-11 Sprint Communications Company L.P. Architecture blueprint tool and method
US7698293B2 (en) * 2005-01-28 2010-04-13 Microsoft Corporation System and methods for capturing structure of data models using entity patterns
US7636911B2 (en) * 2005-01-28 2009-12-22 Microsoft Corporation System and methods for capturing structure of data models using entity patterns
KR101219960B1 (en) 2005-01-28 2013-01-09 마이크로소프트 코포레이션 System and methods for capturing structure of data models using entity patterns
GB2423163A (en) * 2005-02-11 2006-08-16 Ibm Integrating software into an existing IT infrastructure
US7657868B2 (en) * 2005-03-14 2010-02-02 Research In Motion Limited System and method for applying development patterns for component based applications
US8095553B2 (en) * 2005-03-17 2012-01-10 International Business Machines Corporation Sequence support operators for an abstract database
US7861212B1 (en) 2005-03-22 2010-12-28 Dubagunta Saikumar V System, method, and computer readable medium for integrating an original application with a remote application
US7797688B1 (en) 2005-03-22 2010-09-14 Dubagunta Saikumar V Integrating applications in multiple languages
US8578349B1 (en) * 2005-03-23 2013-11-05 Curen Software Enterprises, L.L.C. System, method, and computer readable medium for integrating an original language application with a target language application
US7546582B2 (en) 2005-03-30 2009-06-09 International Business Machines Corporation Managing dynamic configuration data for producer components in a computer infrastructure
US7770151B2 (en) 2005-04-07 2010-08-03 International Business Machines Corporation Automatic generation of solution deployment descriptors
US7496888B2 (en) * 2005-04-07 2009-02-24 International Business Machines Corporation Solution builder wizard
US7797678B2 (en) 2005-04-07 2010-09-14 International Business Machines Corporation Automatic generation of license package for solution components
US8489728B2 (en) * 2005-04-15 2013-07-16 Microsoft Corporation Model-based system monitoring
US7665073B2 (en) * 2005-04-18 2010-02-16 Microsoft Corporation Compile time meta-object protocol systems and methods
US7669181B2 (en) * 2005-04-29 2010-02-23 Sap (Ag) Client interfaces for packages
US7634771B2 (en) * 2005-04-29 2009-12-15 Sap (Ag) Object generation in packages
US7587705B2 (en) * 2005-04-29 2009-09-08 Sap (Ag) Calls and return calls using client interfaces
US7809597B2 (en) * 2005-05-05 2010-10-05 Siebel Systems, Inc. Progressive refinement model for business processes
US7895070B2 (en) * 2005-05-05 2011-02-22 Siebel Systems, Inc. Providing multiple views of a business process definition to different users
US7831453B2 (en) * 2005-05-05 2010-11-09 Siebel Systems, Inc. Modeling of business process data
US20060265387A1 (en) * 2005-05-20 2006-11-23 International Business Machines Corporation Method and apparatus for loading artifacts
US7720904B2 (en) * 2005-05-27 2010-05-18 Microsoft Corporation Entity projection
WO2006130846A2 (en) * 2005-06-02 2006-12-07 United States Postal Service Methods and systems for evaluating the compliance of software to a quality benchmark
US8549513B2 (en) 2005-06-29 2013-10-01 Microsoft Corporation Model-based virtual system provisioning
US8484065B1 (en) 2005-07-14 2013-07-09 Sprint Communications Company L.P. Small enhancement process workflow manager
US7752606B2 (en) * 2005-08-10 2010-07-06 Capital One Financial Corporation Software development tool using a structured format to generate software code
US7945904B2 (en) * 2005-08-22 2011-05-17 Microsoft Corporation Embedding expression in XML literals
US7941309B2 (en) 2005-11-02 2011-05-10 Microsoft Corporation Modeling IT operations/policies
US7614035B2 (en) * 2005-11-04 2009-11-03 Microsoft Corporation Cartographic software maps
US7440945B2 (en) * 2005-11-10 2008-10-21 International Business Machines Corporation Dynamic discovery of abstract rule set required inputs
US7444332B2 (en) * 2005-11-10 2008-10-28 International Business Machines Corporation Strict validation of inference rule based on abstraction environment
EP1788497A1 (en) * 2005-11-18 2007-05-23 Alcatel Lucent Design pattern and procedure for processing an object model
US8495578B2 (en) * 2005-12-19 2013-07-23 International Business Machines Corporation Integrated software development system, method for validation, computer arrangement and computer program product
US7757204B2 (en) * 2005-12-29 2010-07-13 Sap Ag Limiting extensibility of a visual modeling language
US20070156500A1 (en) * 2005-12-30 2007-07-05 Wilfried Merkel Architectural design for sell from stock application software
US8396731B2 (en) 2005-12-30 2013-03-12 Sap Ag Architectural design for service procurement application software
US8316344B2 (en) 2005-12-30 2012-11-20 Sap Ag Software model deployment units
US8402426B2 (en) * 2005-12-30 2013-03-19 Sap Ag Architectural design for make to stock application software
US8522194B2 (en) 2005-12-30 2013-08-27 Sap Ag Software modeling
US8380553B2 (en) 2005-12-30 2013-02-19 Sap Ag Architectural design for plan-driven procurement application software
US8370794B2 (en) 2005-12-30 2013-02-05 Sap Ag Software model process component
US8327319B2 (en) * 2005-12-30 2012-12-04 Sap Ag Software model process interaction
US20070156550A1 (en) * 2005-12-30 2007-07-05 Der Emde Martin V Architectural design for cash and liquidity management application software
US8448137B2 (en) 2005-12-30 2013-05-21 Sap Ag Software model integration scenarios
US8676617B2 (en) * 2005-12-30 2014-03-18 Sap Ag Architectural design for self-service procurement application software
US8660904B2 (en) * 2005-12-30 2014-02-25 Sap Ag Architectural design for service request and order management application software
US8407664B2 (en) 2005-12-30 2013-03-26 Sap Ag Software model business objects
US8321831B2 (en) 2005-12-30 2012-11-27 Sap Ag Architectural design for internal projects application software
US8326703B2 (en) 2005-12-30 2012-12-04 Sap Ag Architectural design for product catalog management application software
EP1818813A1 (en) * 2006-02-02 2007-08-15 Research In Motion Limited System and method and apparatus for using UML tools for defining web service bound component applications
US7827523B2 (en) * 2006-02-22 2010-11-02 Yahoo! Inc. Query serving infrastructure providing flexible and expandable support and compiling instructions
US8225311B1 (en) * 2006-03-30 2012-07-17 Emc Corporation Deploying and distributing content management code
US8438119B2 (en) 2006-03-30 2013-05-07 Sap Ag Foundation layer for services based enterprise software architecture
US8396749B2 (en) 2006-03-30 2013-03-12 Sap Ag Providing customer relationship management application as enterprise services
US8538864B2 (en) 2006-03-30 2013-09-17 Sap Ag Providing payment software application as enterprise services
US8250518B2 (en) * 2006-03-30 2012-08-21 Microsoft Corporation Per user file associations
US8326702B2 (en) * 2006-03-30 2012-12-04 Sap Ag Providing supplier relationship management software application as enterprise services
US8396761B2 (en) 2006-03-30 2013-03-12 Sap Ag Providing product catalog software application as enterprise services
US8442850B2 (en) 2006-03-30 2013-05-14 Sap Ag Providing accounting software application as enterprise services
US8321832B2 (en) * 2006-03-31 2012-11-27 Sap Ag Composite application modeling
US8312416B2 (en) * 2006-04-13 2012-11-13 Sap Ag Software model business process variant types
WO2007124057A2 (en) 2006-04-21 2007-11-01 Raytheon Company Computer program generating
US7810140B1 (en) 2006-05-23 2010-10-05 Lipari Paul A System, method, and computer readable medium for processing a message in a transport
US7945596B2 (en) * 2006-06-20 2011-05-17 Microsoft Corproation Programming model for customized data objects
US7844759B1 (en) 2006-07-28 2010-11-30 Cowin Gregory L System, method, and computer readable medium for processing a message queue
US20080046858A1 (en) * 2006-08-15 2008-02-21 Zeligsoft Inc. Method and apparatus for merge condition detection
US9569737B2 (en) * 2006-08-16 2017-02-14 Aware Software, Inc. Methods and tools for creating and evaluating system blueprints
US8091071B2 (en) * 2006-08-21 2012-01-03 Sap, Ag Method and system for template-based code generation
US7900188B2 (en) * 2006-09-01 2011-03-01 The Mathworks, Inc. Specifying implementations of code for code generation from a model
US8589869B2 (en) 2006-09-07 2013-11-19 Wolfram Alpha Llc Methods and systems for determining a formula
US8146051B2 (en) * 2006-10-02 2012-03-27 International Business Machines Corporation Method and computer program product for providing a representation of software modeled by a model
US8543978B2 (en) * 2006-10-11 2013-09-24 Michael A. Ponce de Leon Systems and methods for creating software
US7761559B2 (en) * 2006-10-13 2010-07-20 International Business Machines Corporation System and method of remotely managing and loading artifacts
US7720931B2 (en) 2006-10-13 2010-05-18 International Business Machines Corporation System and method of remotely managing and loading artifacts
US8719766B1 (en) * 2006-10-16 2014-05-06 The Math Works, Inc. System and method for identifying and adding files to a project manifest
US20080134132A1 (en) * 2006-11-30 2008-06-05 Microsoft Corporation Developing Software Components Based on Brain Lateralization
US8209662B2 (en) * 2006-12-04 2012-06-26 Microsoft Corporation Application retargeting
US8423496B1 (en) 2006-12-22 2013-04-16 Curen Software Enterprises, L.L.C. Dynamic determination of needed agent rules
US7698243B1 (en) 2006-12-22 2010-04-13 Hauser Robert R Constructing an agent in a first execution environment using canonical rules
US7702604B1 (en) 2006-12-22 2010-04-20 Hauser Robert R Constructing an agent that utilizes supplied rules and rules resident in an execution environment
US7949626B1 (en) 2006-12-22 2011-05-24 Curen Software Enterprises, L.L.C. Movement of an agent that utilizes a compiled set of canonical rules
US7970724B1 (en) 2006-12-22 2011-06-28 Curen Software Enterprises, L.L.C. Execution of a canonical rules based agent
US8200603B1 (en) 2006-12-22 2012-06-12 Curen Software Enterprises, L.L.C. Construction of an agent that utilizes as-needed canonical rules
US7702603B1 (en) 2006-12-22 2010-04-20 Hauser Robert R Constructing an agent that utilizes a compiled set of canonical rules
US7702602B1 (en) 2006-12-22 2010-04-20 Hauser Robert R Moving and agent with a canonical rule from one device to a second device
US7660780B1 (en) 2006-12-22 2010-02-09 Patoskie John P Moving an agent from a first execution environment to a second execution environment
US9311141B2 (en) 2006-12-22 2016-04-12 Callahan Cellular L.L.C. Survival rule usage by software agents
US7664721B1 (en) 2006-12-22 2010-02-16 Hauser Robert R Moving an agent from a first execution environment to a second execution environment using supplied and resident rules
US8132179B1 (en) 2006-12-22 2012-03-06 Curen Software Enterprises, L.L.C. Web service interface for mobile agents
US7660777B1 (en) 2006-12-22 2010-02-09 Hauser Robert R Using data narrowing rule for data packaging requirement of an agent
US7860517B1 (en) 2006-12-22 2010-12-28 Patoskie John P Mobile device tracking using mobile agent location breadcrumbs
US20080163159A1 (en) * 2007-01-03 2008-07-03 Relativity Technologies, Inc. System and method for extracting UML models from legacy applications
US8141032B2 (en) * 2007-02-02 2012-03-20 Microsoft Corporation N-tiered applications support via common interface
US8776015B1 (en) 2007-02-08 2014-07-08 The Mathworks, Inc. Pattern modeling methods and systems
US8336025B1 (en) * 2007-02-08 2012-12-18 The Mathworks, Inc. Pattern modeling methods and systems
US8276167B2 (en) * 2007-03-21 2012-09-25 International Business Machines Corporation Distributed pluggable middleware services
US8024701B2 (en) * 2007-03-27 2011-09-20 Microsoft Corporation Visual creation of object/relational constructs
US7490023B2 (en) * 2007-04-12 2009-02-10 International Business Machines Corporation Method for analyzing effects of performance characteristics of an application based on complex configuration models
US7765241B2 (en) * 2007-04-20 2010-07-27 Microsoft Corporation Describing expected entity relationships in a model
US9489418B2 (en) 2007-04-27 2016-11-08 International Business Machines Corporation Processing database queries embedded in application source code from within integrated development environment tool
US8392880B2 (en) * 2007-04-27 2013-03-05 International Business Machines Corporation Rapid application development for database-aware applications
US8566793B2 (en) * 2007-04-27 2013-10-22 International Business Machines Corporation Detecting and displaying errors in database statements within integrated development environment tool
US9047337B2 (en) * 2007-04-27 2015-06-02 International Business Machines Corporation Database connectivity and database model integration within integrated development environment tool
US8140557B2 (en) 2007-05-15 2012-03-20 International Business Machines Corporation Ontological translation of abstract rules
WO2008147616A1 (en) * 2007-05-25 2008-12-04 Zoot Enterprises, Inc. System and method for rapid development of software applications
US7681180B2 (en) 2007-06-06 2010-03-16 Microsoft Corporation Parameterized test driven development
US8244728B2 (en) * 2007-06-12 2012-08-14 International Business Machines Corporation Method and apparatus for data exploration
US8375351B2 (en) * 2007-06-23 2013-02-12 International Business Machines Corporation Extensible rapid application development for disparate data sources
US8001519B2 (en) * 2007-06-27 2011-08-16 International Business Machines Corporation Model driven development including aspect integration tool
US7917887B2 (en) * 2007-06-28 2011-03-29 Microsoft Corporation DDEX (data designer extensibility) default object implementations for software development processes
EP2012237A1 (en) * 2007-07-02 2009-01-07 Siemens Aktiengesellschaft Method for evaluating at least one characteristic value
US8103495B2 (en) * 2007-08-08 2012-01-24 Microsoft Corporation Feature oriented protocol modeling
US8250534B2 (en) * 2007-08-09 2012-08-21 Infonovus Technologies, Llc Method and system for constructing a software application from a complete and consistent specification in a software development process
US8473910B2 (en) * 2007-08-09 2013-06-25 Infonovus Technologies, Llc Method and system for defining a software application as a complete and consistent specification in a software development process
US8032858B2 (en) * 2007-08-28 2011-10-04 International Business Machines Corporation Method and system for navigationally displaying HTTP session entry and exit points
US20090064098A1 (en) * 2007-08-28 2009-03-05 Jinchao Huang Method and system for scenario-based visualization
US8607197B2 (en) * 2007-08-28 2013-12-10 International Business Machines Corporation Displaying HTTP session entry and exit points
US20090063623A1 (en) * 2007-08-31 2009-03-05 International Business Machines Corporation Determining connection information to use to access an artifact from an application on a remote server
US20090089029A1 (en) * 2007-09-28 2009-04-02 Rockwell Automation Technologies, Inc. Enhanced execution speed to improve simulation performance
US20090089234A1 (en) * 2007-09-28 2009-04-02 Rockwell Automation Technologies, Inc. Automated code generation for simulators
US20090089031A1 (en) * 2007-09-28 2009-04-02 Rockwell Automation Technologies, Inc. Integrated simulation of controllers and devices
US8548777B2 (en) * 2007-09-28 2013-10-01 Rockwell Automation Technologies, Inc. Automated recommendations from simulation
US7801710B2 (en) * 2007-09-28 2010-09-21 Rockwell Automation Technologies, Inc. Simulation controls for model variability and randomness
US8069021B2 (en) * 2007-09-28 2011-11-29 Rockwell Automation Technologies, Inc. Distributed simulation and synchronization
US20090100406A1 (en) * 2007-10-16 2009-04-16 Microsoft Corporation Software factory specification and execution model
WO2009062527A1 (en) * 2007-11-13 2009-05-22 Telefonaktiebogalet Lm Ericsson (Publ) Technique for automatically generating software in a software development environment
US8543994B2 (en) * 2007-12-07 2013-09-24 Sap Ag Developing java server components without restarting the application server
US8458648B2 (en) * 2007-12-10 2013-06-04 International Business Machines Corporation Graphical modelization of user interfaces for data intensive applications
US8352906B2 (en) * 2007-12-28 2013-01-08 Cadence Design Systems, Inc. Method, system, and computer program product for implementing external domain independent modeling framework in a system design
US8447657B2 (en) 2007-12-31 2013-05-21 Sap Ag Architectural design for service procurement application software
US8315900B2 (en) * 2007-12-31 2012-11-20 Sap Ag Architectural design for self-service procurement application software
US8510143B2 (en) * 2007-12-31 2013-08-13 Sap Ag Architectural design for ad-hoc goods movement software
US8401936B2 (en) 2007-12-31 2013-03-19 Sap Ag Architectural design for expense reimbursement application software
US8671032B2 (en) 2007-12-31 2014-03-11 Sap Ag Providing payment software application as enterprise services
US8671034B2 (en) * 2007-12-31 2014-03-11 Sap Ag Providing human capital management software application as enterprise services
US8671033B2 (en) 2007-12-31 2014-03-11 Sap Ag Architectural design for personnel events application software
US20090182689A1 (en) * 2008-01-15 2009-07-16 Microsoft Corporation Rule-based dynamic operation evaluation
US8166453B2 (en) * 2008-01-21 2012-04-24 International Business Machines Corporation Method and system for inconsistency resolution with cycle detection in a model-driven software environment
US8056050B2 (en) * 2008-01-21 2011-11-08 International Business Machines Corporation Method and system for guided inconsistency resolution in a model-driven software environment
US8656349B2 (en) * 2008-03-07 2014-02-18 Sap Ag Systems and methods for template reverse engineering
US8365136B2 (en) * 2008-03-10 2013-01-29 Sap Ag Creating parallel control flows in business process models
US20090271760A1 (en) * 2008-04-24 2009-10-29 Robert Stephen Ellinger Method for application development
US8689195B2 (en) * 2008-06-03 2014-04-01 International Business Machines Corporation Identifying structured data types as requiring designated initializers
US8397210B2 (en) * 2008-06-03 2013-03-12 Microsoft Corporation Evolving the architecture of a software application
US8677310B2 (en) * 2008-06-30 2014-03-18 Rockwell Automation Technologies, Inc. Industry template abstracting and creation for use in industrial automation and information solutions
US8255869B2 (en) * 2008-06-30 2012-08-28 Rockwell Automation Technologies, Inc. Industry template customization and transclusion for use in industrial automation and information solutions
US9639331B2 (en) 2008-07-09 2017-05-02 International Business Machines Corporation Service interface creation and modification for object-oriented services
US8271935B2 (en) 2008-07-09 2012-09-18 International Business Machines Corporation Methods and tools for data-driven application engineering
US10031749B2 (en) * 2008-07-11 2018-07-24 International Business Machines Corporation Creation of a help file
US20100070395A1 (en) * 2008-09-18 2010-03-18 Andreas Elkeles Architectural design for payroll processing application software
US20100082497A1 (en) * 2008-09-18 2010-04-01 Sap Ag Providing Foundation Application as Enterprise Services
US8315926B2 (en) 2008-09-18 2012-11-20 Sap Ag Architectural design for tax declaration application software
US8818884B2 (en) * 2008-09-18 2014-08-26 Sap Ag Architectural design for customer returns handling application software
US8321250B2 (en) 2008-09-18 2012-11-27 Sap Ag Architectural design for sell from stock application software
US8401928B2 (en) 2008-09-18 2013-03-19 Sap Ag Providing supplier relationship management software application as enterprise services
US8326706B2 (en) * 2008-09-18 2012-12-04 Sap Ag Providing logistics execution application as enterprise services
US8380549B2 (en) 2008-09-18 2013-02-19 Sap Ag Architectural design for embedded support application software
US8374896B2 (en) 2008-09-18 2013-02-12 Sap Ag Architectural design for opportunity management application software
US8386325B2 (en) 2008-09-18 2013-02-26 Sap Ag Architectural design for plan-driven procurement application software
US8595077B2 (en) 2008-09-18 2013-11-26 Sap Ag Architectural design for service request and order management application software
US8352338B2 (en) 2008-09-18 2013-01-08 Sap Ag Architectural design for time recording application software
US8453112B1 (en) * 2008-11-13 2013-05-28 Adobe Systems Incorporated Systems and methods for collaboratively creating applications using a multiple source file project that can be accessed and edited like a single file
US8401908B2 (en) 2008-12-03 2013-03-19 Sap Ag Architectural design for make-to-specification application software
US8311904B2 (en) 2008-12-03 2012-11-13 Sap Ag Architectural design for intra-company stock transfer application software
US8738476B2 (en) 2008-12-03 2014-05-27 Sap Ag Architectural design for selling standardized services application software
US8321308B2 (en) * 2008-12-03 2012-11-27 Sap Ag Architectural design for manual invoicing application software
US8321306B2 (en) 2008-12-03 2012-11-27 Sap Ag Architectural design for selling project-based services application software
US8671035B2 (en) * 2008-12-11 2014-03-11 Sap Ag Providing payroll software application as enterprise services
US20100235275A1 (en) * 2009-03-06 2010-09-16 Carl Ansley Card Processing
US8214792B2 (en) * 2009-03-26 2012-07-03 International Business Machines Corporation System for implementing business transformation in an enterprise
US20100250300A1 (en) * 2009-03-26 2010-09-30 International Business Machines Corporation Method for transforming an enterprise based on linkages among business components, business processes and services
US20100250328A1 (en) * 2009-03-26 2010-09-30 International Business Machines Corporation Business assessment method
US8751284B2 (en) * 2009-04-30 2014-06-10 United Parcel Service Of America, Inc. Systems and methods for a real-time workflow platform using Petri net model mappings
US8332811B2 (en) * 2009-04-30 2012-12-11 United Parcel Service Of America, Inc. Systems and methods for generating source code for workflow platform
US8448132B2 (en) * 2009-05-07 2013-05-21 Sap Ag Systems and methods for modifying code generation templates
US8601015B1 (en) 2009-05-15 2013-12-03 Wolfram Alpha Llc Dynamic example generation for queries
US8788524B1 (en) 2009-05-15 2014-07-22 Wolfram Alpha Llc Method and system for responding to queries in an imprecise syntax
US20100299650A1 (en) * 2009-05-20 2010-11-25 International Business Machines Corporation Team and individual performance in the development and maintenance of software
US8726226B2 (en) * 2009-06-05 2014-05-13 Microsoft Corporation Integrated work lists for engineering project change management
US8682630B2 (en) * 2009-06-15 2014-03-25 International Business Machines Corporation Managing component coupling in an object-centric process implementation
US20100325491A1 (en) * 2009-06-18 2010-12-23 International Business Machines Corporation Mining a use case model by analyzing its description in plain language and analyzing textural use case models to identify modeling errors
US8707250B2 (en) * 2009-12-22 2014-04-22 Board Of Regents, The University Of Texas System Automation support for domain modeling
US8739118B2 (en) * 2010-04-08 2014-05-27 Microsoft Corporation Pragmatic mapping specification, compilation and validation
US8484015B1 (en) 2010-05-14 2013-07-09 Wolfram Alpha Llc Entity pages
US9430222B2 (en) * 2010-05-24 2016-08-30 Oracle International Corporation Controlling a running application for live scene graph editing
US8464233B2 (en) 2010-06-21 2013-06-11 Microsoft Corporation Compile time interpretation of markup codes
US8812298B1 (en) 2010-07-28 2014-08-19 Wolfram Alpha Llc Macro replacement of natural language input
CN102479077A (en) * 2010-11-26 2012-05-30 金蝶软件(中国)有限公司 Method and device for dynamically constructing function operation, and application system
US9286037B2 (en) * 2010-12-29 2016-03-15 Microsoft Technology Licensing, Llc Platform for distributed applications
US20120260237A1 (en) * 2011-04-10 2012-10-11 Requirementslive Llc Portable Business Language and Automated Software Application Development System
US9069814B2 (en) 2011-07-27 2015-06-30 Wolfram Alpha Llc Method and system for using natural language to generate widgets
US9734252B2 (en) 2011-09-08 2017-08-15 Wolfram Alpha Llc Method and system for analyzing data using a query answering system
US9851950B2 (en) 2011-11-15 2017-12-26 Wolfram Alpha Llc Programming in a precise syntax using natural language
JP5948926B2 (en) * 2012-02-09 2016-07-06 富士電機株式会社 Object-oriented program generator, program
US9158563B2 (en) * 2012-03-27 2015-10-13 Microsoft Technology Licensing, Llc Dynamic plugin(s) for cloud application(s)
US9405424B2 (en) 2012-08-29 2016-08-02 Wolfram Alpha, Llc Method and system for distributing and displaying graphical items
US9569274B2 (en) 2012-10-16 2017-02-14 Microsoft Technology Licensing, Llc Distributed application optimization using service groups
US20140156547A1 (en) * 2012-11-30 2014-06-05 The Children's Hospital Of Philadelphia Methods and systems for assessing computer applications
CN103049320B (en) 2012-12-17 2016-05-04 广州市动景计算机科技有限公司 In browser, start the method and apparatus of external application
US9021419B2 (en) * 2013-02-15 2015-04-28 Oracle International Corporation System and method for supporting intelligent design pattern automation
US9021432B2 (en) 2013-03-05 2015-04-28 Sap Se Enrichment of entity relational model
US20140325490A1 (en) * 2013-04-25 2014-10-30 Hewlett-Packard Development Company, L.P. Classifying Source Code Using an Expertise Model
US9569187B2 (en) 2013-10-08 2017-02-14 International Business Machines Corporation Irreducible modules
US9229693B1 (en) * 2014-05-28 2016-01-05 Amazon Technologies, Inc. Build service for software development projects
JP2017520842A (en) * 2014-06-13 2017-07-27 ザ・チャールズ・スターク・ドレイパー・ラボラトリー・インコーポレイテッド System and method for software analysis
US9678746B2 (en) * 2014-07-31 2017-06-13 International Business Machines Corporation Coding convention discovery and enforcement
WO2016080948A1 (en) * 2014-11-17 2016-05-26 Hewlett Packard Enterprise Development Lp Linking an entity relating to product development to a document portion
US9733993B2 (en) 2015-07-02 2017-08-15 Microsoft Technology Licensing, Llc Application sharing using endpoint interface entities
US9712472B2 (en) 2015-07-02 2017-07-18 Microsoft Technology Licensing, Llc Application spawning responsive to communication
US10198252B2 (en) 2015-07-02 2019-02-05 Microsoft Technology Licensing, Llc Transformation chain application splitting
US9860145B2 (en) 2015-07-02 2018-01-02 Microsoft Technology Licensing, Llc Recording of inter-application data flow
US9658836B2 (en) * 2015-07-02 2017-05-23 Microsoft Technology Licensing, Llc Automated generation of transformation chain compatible class
US10261985B2 (en) 2015-07-02 2019-04-16 Microsoft Technology Licensing, Llc Output rendering in dynamic redefining application
US9785484B2 (en) 2015-07-02 2017-10-10 Microsoft Technology Licensing, Llc Distributed application interfacing across different hardware
US9733915B2 (en) 2015-07-02 2017-08-15 Microsoft Technology Licensing, Llc Building of compound application chain applications
US10198405B2 (en) 2015-07-08 2019-02-05 Microsoft Technology Licensing, Llc Rule-based layout of changing information
US10031724B2 (en) 2015-07-08 2018-07-24 Microsoft Technology Licensing, Llc Application operation responsive to object spatial status
US9880814B1 (en) * 2015-08-13 2018-01-30 F5 Networks, Inc. Dynamic generation of plugins based on user-customized catalogs
US10277582B2 (en) 2015-08-27 2019-04-30 Microsoft Technology Licensing, Llc Application service architecture
DE202017101371U1 (en) * 2016-03-11 2017-06-29 Tata Consultancy Services Limited System for the development of mobile-based applications using model-driven development
US10204319B2 (en) * 2017-01-20 2019-02-12 Wipro Limited Enterprise system and method for facilitating common platform for multiple-users working parallelly in enterprise environment
US10402173B2 (en) 2017-02-24 2019-09-03 General Electric Company Systems and methods for arbitrary software logic modeling
US10466981B1 (en) * 2017-06-06 2019-11-05 Prattle Analytics, LLC System and method for generative programming in an integrated development environment (IDE)
US10877735B1 (en) * 2017-09-25 2020-12-29 Amazon Technologies, Inc. Automated generation of software applications using analysis of submitted content items
US10705805B1 (en) 2017-12-12 2020-07-07 Amazon Technologies, Inc. Application authoring using web-of-sheets data model
US11586603B1 (en) 2018-05-23 2023-02-21 Amazon Technologies, Inc. Index sheets for robust spreadsheet-based applications
CN108804091A (en) * 2018-05-25 2018-11-13 广州小天软件有限公司 A kind of software code generation method
CN109086043A (en) * 2018-06-27 2018-12-25 珠海宏桥高科技有限公司 A kind of method and apparatus for quickly generating WEB project based on configuration
CN109086325A (en) * 2018-06-29 2018-12-25 阿里巴巴集团控股有限公司 Data processing method and device based on block chain
US10437572B1 (en) * 2018-08-03 2019-10-08 King Fahd University Of Petroleum And Minerals Methods, computer readable media, and systems for compiling concise expressive design pattern source code
US11074070B2 (en) * 2018-11-13 2021-07-27 United States Of America, As Represented By The Secretary Of The Navy Interface effect minimization by software design
CN109814950B (en) * 2019-01-16 2022-04-19 中国联合网络通信集团有限公司 Service scheduling method, device, equipment and computer readable storage medium
FR3097672A1 (en) * 2019-06-21 2020-12-25 Aava Mobile Sas Service application system for payment terminals
CN111061475B (en) * 2019-12-13 2023-12-12 中国南方电网有限责任公司 Software code generating method, device, computer equipment and storage medium
CN111898370B (en) * 2020-07-10 2022-08-16 中国标准化研究院 Method and device for acquiring design rational knowledge and computer storage medium
US11775910B2 (en) 2020-07-15 2023-10-03 Copado, Inc. Applied computer technology for high efficiency value stream management and mapping and process tracking
WO2022015985A1 (en) * 2020-07-15 2022-01-20 Copado, Inc. Methods for software development and operation process analytics and devices thereof
US11468210B2 (en) 2020-10-09 2022-10-11 Sidewalk Labs LLC Methods, systems, and media for generative urban design with spreadsheet and model integration features

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6018627A (en) * 1997-09-22 2000-01-25 Unisys Corp. Tool-independent system for application building in an object oriented development environment with data stored in repository in OMG compliant UML representation
US6199195B1 (en) * 1999-07-08 2001-03-06 Science Application International Corporation Automatically generated objects within extensible object frameworks and links to enterprise resources
US6212672B1 (en) * 1997-03-07 2001-04-03 Dynamics Research Corporation Software development system with an executable working model in an interpretable intermediate modeling language
US6742175B1 (en) * 1998-10-13 2004-05-25 Codagen Technologies Corp. Component-based source code generator

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6212672B1 (en) * 1997-03-07 2001-04-03 Dynamics Research Corporation Software development system with an executable working model in an interpretable intermediate modeling language
US6018627A (en) * 1997-09-22 2000-01-25 Unisys Corp. Tool-independent system for application building in an object oriented development environment with data stored in repository in OMG compliant UML representation
US6742175B1 (en) * 1998-10-13 2004-05-25 Codagen Technologies Corp. Component-based source code generator
US6199195B1 (en) * 1999-07-08 2001-03-06 Science Application International Corporation Automatically generated objects within extensible object frameworks and links to enterprise resources

Cited By (32)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7827524B2 (en) * 2003-04-22 2010-11-02 Computer Associates Think, Inc. System and method for integrating object-oriented model profiles and object-oriented programming languages
US8402430B2 (en) * 2003-04-22 2013-03-19 Ca, Inc. System and method for integrating object-oriented model profiles and object-oriented programming languages
US20040216085A1 (en) * 2003-04-22 2004-10-28 Computer Associates Think, Inc. System and method for integrating object-oriented model profiles and object-oriented programming languages
US20110010686A1 (en) * 2003-04-22 2011-01-13 Computer Associates Think, Inc. System and method for integrating object-oriented model profiles and object-oriented programming languages
US8307337B2 (en) 2006-12-01 2012-11-06 Murex S.A.S. Parallelization and instrumentation in a producer graph oriented programming framework
US8332827B2 (en) 2006-12-01 2012-12-11 Murex S.A.S. Produce graph oriented programming framework with scenario support
US20080134138A1 (en) * 2006-12-01 2008-06-05 Fady Chamieh Producer graph oriented programming and execution
US10481877B2 (en) 2006-12-01 2019-11-19 Murex S.A.S. Producer graph oriented programming and execution
US20080134161A1 (en) * 2006-12-01 2008-06-05 Fady Chamieh Producer graph oriented programming framework with undo, redo, and abort execution support
US8191052B2 (en) 2006-12-01 2012-05-29 Murex S.A.S. Producer graph oriented programming and execution
US9424050B2 (en) 2006-12-01 2016-08-23 Murex S.A.S. Parallelization and instrumentation in a producer graph oriented programming framework
US7865872B2 (en) 2006-12-01 2011-01-04 Murex S.A.S. Producer graph oriented programming framework with undo, redo, and abort execution support
US20080134152A1 (en) * 2006-12-01 2008-06-05 Elias Edde Producer graph oriented programming framework with scenario support
US8607207B2 (en) 2006-12-01 2013-12-10 Murex S.A.S. Graph oriented programming and execution
US8645929B2 (en) 2006-12-01 2014-02-04 Murex S.A.S. Producer graph oriented programming and execution
US9201766B2 (en) 2006-12-01 2015-12-01 Murex S.A.S. Producer graph oriented programming framework with scenario support
US10083013B2 (en) 2006-12-01 2018-09-25 Murex S.A.S. Producer graph oriented programming and execution
US9854064B2 (en) 2009-06-05 2017-12-26 Oracle International Corporation Method of website optimisation
US20140123103A1 (en) * 2009-06-05 2014-05-01 Maxymiser Ltd. Method of website optimisation
US9489178B2 (en) * 2009-06-05 2016-11-08 Maxymiser Ltd. Method of website optimisation
US20110302553A1 (en) * 2010-06-04 2011-12-08 Microsoft Corporation Generating text manipulation programs using input-output examples
US8972930B2 (en) * 2010-06-04 2015-03-03 Microsoft Corporation Generating text manipulation programs using input-output examples
US9613115B2 (en) 2010-07-12 2017-04-04 Microsoft Technology Licensing, Llc Generating programs based on input-output examples using converter modules
CN102063324A (en) * 2010-12-31 2011-05-18 杭州依赛通信有限公司 Method and system for implementing automatic programming
US9552335B2 (en) 2012-06-04 2017-01-24 Microsoft Technology Licensing, Llc Expedited techniques for generating string manipulation programs
US9239707B2 (en) * 2013-06-28 2016-01-19 Successfactors, Inc. Model framework for applications
US20150007128A1 (en) * 2013-06-28 2015-01-01 Successfactors, Inc. Model Framework for Applications
US11256710B2 (en) 2016-10-20 2022-02-22 Microsoft Technology Licensing, Llc String transformation sub-program suggestion
US11620304B2 (en) 2016-10-20 2023-04-04 Microsoft Technology Licensing, Llc Example management for string transformation
US10846298B2 (en) 2016-10-28 2020-11-24 Microsoft Technology Licensing, Llc Record profiling for dataset sampling
US10831451B2 (en) * 2017-12-01 2020-11-10 Microsoft Technology Licensing, Llc Synthesized programming-by-example programs
US10671353B2 (en) 2018-01-31 2020-06-02 Microsoft Technology Licensing, Llc Programming-by-example using disjunctive programs

Also Published As

Publication number Publication date
US20020091990A1 (en) 2002-07-11
US6973640B2 (en) 2005-12-06
US20020133812A1 (en) 2002-09-19
US7047518B2 (en) 2006-05-16

Similar Documents

Publication Publication Date Title
US6973640B2 (en) System and method for computer code generation
US7174533B2 (en) Method, system, and program for translating a class schema in a source language to a target language
US6701381B2 (en) Data processing system and development method
US7454743B2 (en) Java to SNMP MIB mapping
US7194729B2 (en) Dynamic conversion of object-oriented programs to tag-based procedural code
US7191429B2 (en) System and method for managing architectural layers within a software model
US6745208B2 (en) Method and apparatus for synchronizing an XML document with its object model
US7673283B2 (en) Method and system for improved modeling language profile
US8074228B2 (en) Systems and methods for providing mockup business objects
US20080141139A1 (en) Architecture and Process for Presenting Application Content to Clients
US20060129974A1 (en) Service meta model for an enterprise service architecture
US20020066074A1 (en) Method and system for developing and executing software applications at an abstract design level
US20020194263A1 (en) Hierarchical constraint resolution for application properties, configuration, and behavior
US20060242187A1 (en) Type safe data proxy
US7346889B1 (en) Method and system for building message instances
Cheong et al. Frame-based method for customizing generic software architectures
US7305667B1 (en) Call back structures for user defined DOMs
Karsai et al. Tool integration patterns
US20060101388A1 (en) Computer method and apparatus for collapsing programming metamodels
Akbay et al. Design and implementation of an enterprise information system utilizing a component based three-tier client/server database system
Künzl Development of a Workflow-based Infrastructure for Managing and Executing Web Services
Roussev Flexible sharing of distributed objects based on programming patterns
Dahman A UML based methodology for the development of web services: an approach to model tranformation and code generation
Pivl Java metadata interface (jmi)
Ledeczi et al. Framework for the Rapid Evaluation of Modeling Methodologies

Legal Events

Date Code Title Description
STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION