This is an old revision of the document!
PADL stands for Pattern and Abstract-level Description Language. It is a meta-model to describe programs at different levels of abstractions.
There are three different levels of abstractions to model programs, collectively called abstract-level models:
ICodeLevelModel
represents the “raw” model of a program, including only data directly extractable from the program source representation (Java bytecodes, Java source code, C/C++ source code…);IIdiomLevelModel
represents a model of a program where some idioms have been reified, typically binary-class relationships computed using some analyses;IDesignLevelModel
represents a model of a program where design information is available. Typical design information is obtained from the idiom-level model, for example occurrences of design motifs or of code and design smells;IDesignMotif
represents a design motif, i.e., the solution to a design pattern model in PADL Design Motifs
.
The following diagram shows the hierarchy of the interface describing models. (This hierarchy has been built using the project Ptidej UI Viewer Standalone Swing
) The root of the models is the interface IAbstractModel
, which describes any model that could be handled by most of Ptidej analyses and tools. This interface abstracts IAbstractLevelModel
, which represents models of programs, and IDesignMotif
, which represents models of design motifs.
The PADL
project also provides the interfaces:
ICodeLevelModelCreator
, along with padl.kernel.ICodeLevelModel.create(ICodeLevelModelCreator)
, is an implementation of the Builder design pattern, to provide a unified interface to create PADL models. Creators exist for Java bytecodes as well as other representations, such as AOL files, AspectJ lst
files, C/C++ and Java source code…The PADL meta-model includes an extensive hierarchy of interfaces to describes binary class relationships. The following figure highlights these relationships. Of particular interest are the following relationships, presented in order from the most constraining to the least constraining. Whenever a relationship is identified between two entities, the following least constraining relationships are not included. For example, if an aggregation relationships exists between two classes A and B, no corresponding use relationship would exist.
The existence of binary class relationships is inferred from an ICodeLevelModel based on the presence of certain fields and methods and method invocations in classes by the AACRelationshipsAnalysis.
The PADL meta-model provides you with two distinct but related visitors: IWalker and IGenerator. Both visitors inherit from IVisitor but provide different methods to retreive the results of the visit: getResult() and getCode() respectively. A typical example of using one of these visitors is:
final IWalker walker = new InheritanceImplementationCounter(); final ICodeLevelModel codeLevelModel = Primitive.getFactory().createCodeLevelModel(""); codeLevelModel.create( new CompleteClassFileCreator( DefaultFileRepository.getInstance(), new String[] { path }, true)); final IIdiomLevelModel idiomLevelModel = (IIdiomLevelModel) new AACRelationshipsAnalysis().invoke(codeLevelModel); walker.reset(); idiomLevelModel.walk(walker); System.out.println(walker.getResult());
Obviously, the class InheritanceImplementationCounter implements IWalker.
As part of an effort to improve code representation in PADL. The concept of method invocation has been added since 2004-2005. An interface IMethodInvocation represents method invocations. This concept is as-of-today not quite clean and is used to describes both method invocations and field accesses. Therefore, the interface IMethodInvocation (and its reference implementation) includes:
Although the getID(), getName(), and getPath() methods form a trio, they have different semantics. The getID() must return a unique identifier for each constituent in a model. The getName() returns the name of a constituent. For binary class relationships and method invocations, the name returned by getName() is less important, it could simply be Method Invocation, for example. (Their ID must still be unique, though.)
Here are some examples of getID() :
Here are some examples of getName() :
The paths are used to represent how to get to a constituent within a model.
The paths start with a '/' and the name of the model (optional).
Then, each constituent to go through until the target is specified the same way:
The class padl.path.Finder can be used to walk the paths.