Feature-oriented programming

Feature Oriented Programming (FOP) or Feature Oriented Software Development (FOSD) is a paradigm for program generation in software product lines and for incremental development of programs.

Connection Between Layer Stacks and Transformation Compositions

FOSD arose out of layer-based designs and levels of abstraction in network protocols and extensible database systems in the late-1980s.^[1] A program was a stack of layers. Each layer added functionality to previously composed layers and different compositions of layers produced different programs. Not surprisingly, there was a need for a compact language to express such designs. Elementary algebra fit the bill: each layer was function (program transformation) that added new code to an existing program to produce a new program, and a program's design was modeled by an expression, i.e., a composition of transformations (layers). The figure to the left illustrates the stacking of layers i, j, and h (where h is on the bottom and i is on the top). The algebraic notations i(j(h)), i•j•h, and i+j+h have been used to express these designs.

Over time, layers were equated to features, where a feature is an increment in program functionality. The paradigm for program design and generation was recognized to be an outgrowth of relational query optimization, where query evaluation programs were defined as relational algebra expressions, and query optimization was expression optimization.^[2] A software product line (SPL) is a family of programs where each program is defined by a unique composition of features. FOSD has since evolved into the study of feature modularity, tools, analyses, and design techniques to support feature-based program generation.

The second generation of FOSD research was on feature interactions, which originated in telecommunications. Later, the term feature-oriented programming was coined;^[3] this work exposed interactions between layers. Interactions require features to be adapted when composed with other features.

A third generation of research focussed on the fact that every program has multiple representations (e.g., source, makefiles, documentation, etc.) and adding a feature to a program should elaborate each of its representations so that all are consistent. Additionally, some of representations could be generated (or derived) from others. In the sections below, the mathematics of the three most recent generations of FOSD, namely GenVoca,^[1] AHEAD,^[4] and FOMDD^[5][6] are described, and links to product lines that have been developed using FOSD tools are provided. Also, four additional results that apply to all generations of FOSD are presented elsewhere: MetaModels, Program Cubes, and Feature Interactions.

GenVoca

GenVoca (a portmanteau of the names Genesis and Avoca)^[1] is a compositional paradigm for defining programs of product lines. Base programs are 0-ary functions or transformations called values:

  f      -- base program with feature f
  h      -- base program with feature h

and features are unary functions/transformations that elaborate (modify, extend, refine) a program:

  i + x  -- adds feature i to program x
  j + x  -- adds feature j to program x

where + denotes function composition. The design of a program is a named expression, e.g.:

  p1 = j + f       -- program p1 has features j and f
  p2 = j + h       -- program p2 has features j and h
  p3 = i + j + h   -- program p3 has features i, j, and h

A GenVoca model of a domain or software product line is a collection of base programs and features (see MetaModels and Program Cubes). The programs (expressions) that can be created defines a product line. Expression optimization is program design optimization, and expression evaluation is program generation.

Note: GenVoca is based on the stepwise development of programs: a process that emphasizes design simplicity and understandability, which are key to program comprehension and automated program construction. Consider program p₃ above: it begins with base program h, then feature j is added (read: the functionality of feature j is added to the codebase of h), and finally feature i is added (read: the functionality of feature i is added to the codebase of j•h).

Note: not all combinations of features are meaningful. Feature models (which can be translated into propositional formulas) are graphical representations that define legal combinations of features.^[7]

Note: A more recent formulation of GenVoca is symmetric: there is only one base program, 0 (the empty program), and all features are unary functions. This suggests the interpretation that GenVoca composes program structures by superposition, the idea that complex structures are composed by superimposing simpler structures.^[8][9] Yet another reformulation of GenVoca is as a monoid: a GenVoca model is a set of features with a composition operation (•); composition is associative and there is an identity element (namely 1, the identity function). Although all compositions are possible, not all are meaningful. That's the reason for feature models.

GenVoca features were originally implemented using C preprocessor (#ifdef feature ... #endif) techniques. A more advanced technique, called mixin layers, showed the connection of features to object-oriented collaboration-based designs.

AHEAD

Algebraic Hierarchical Equations for Application Design (AHEAD) ^[4] generalized GenVoca in two ways. First it revealed the internal structure of GenVoca values as tuples. Every program has multiple representations, such as source, documentation, bytecode, and makefiles. A GenVoca value is a tuple of program representations. In a product line of parsers, for example, a base parser f is defined by its grammar g_f, Java source s_f, and documentation d_f. Parser f is modeled by the tuple f=[g_f, s_f, d_f]. Each program representation may have subrepresentations, and they too may have subrepresentations, recursively. In general, a GenVoca value is a tuple of nested tuples that define a hierarchy of representations for a particular program.

Hierarchical Relationships among Program Artifacts

Example. Suppose terminal representations are files. In AHEAD, grammar g_f corresponds to a single BNF file, source s_f corresponds to a tuple of Java files [c₁…c_n], and documentation d_f is a tuple of HTML files [h₁…h_k]. A GenVoca value (nested tuples) can be depicted as a directed graph: the graph for parser f is shown in the figure to the right. Arrows denote projections, i.e., mappings from a tuple to one of its components. AHEAD implements tuples as file directories, so f is a directory containing file g_f and subdirectories s_f and d_f. Similarly, directory s_f contains files c₁…c_n, and directory df contains files h₁…h_k.

Note: Files can be hierarchically decomposed further. Each Java class can be decomposed into a tuple of members and other class declarations (e.g., initialization blocks, etc.). The important idea here is that the mathematics of AHEAD are recursive.

Second, AHEAD expresses features as nested tuples of unary functions called deltas. Deltas can be program refinements (semantics-preserving transformations), extensions (semantics-extending transformations), or interactions (semantics-altering transformations). We use the neutral term “delta” to represent all of these possibilities, as each occurs in FOSD.

To illustrate, suppose feature j extends a grammar by $\Delta$g_j (new rules and tokens are added), extends source code by $\Delta$s_j (new classes and members are added and existing methods are modified), and extends documentation by $\Delta$d_j. The tuple of deltas for feature j is modeled by j=[$\Delta$g_j,$\Delta$s_j,$\Delta$d_j], which we call a delta tuple. Elements of delta tuples can themselves be delta tuples. Example: $\Delta$s_j represents the changes that are made to each class in s_f by feature j, i.e., $\Delta$s_j=[$\Delta$c₁…$\Delta$c_n]. The representations of a program are computed recursively by nested vector addition. The representations for parser p₂ (whose GenVoca expression is j+f) are:

  p2 = j + f                              -- GenVoca expression
     = [$\Delta$gj, $\Delta$sj, $\Delta$dj] + [gf, sf, df]   -- substitution
     = [$\Delta$gj+gf, $\Delta$sj+sf, $\Delta$dj+df]         -- compose tuples element-wise

That is, the grammar of p₂ is the base grammar composed with its extension ($\Delta$g_j+g_f), the source of p₂ is the base source composed with its extension ($\Delta$s_j+s_f), and so on. As elements of delta tuples can themselves be delta tuples, composition recurses, e.g., $\Delta$s_j+s_f= [$\Delta$c₁…$\Delta$c_n]+[c₁…c_n]=[$\Delta$c₁+c₁…$\Delta$c_n+c_n]. Summarizing, GenVoca values are nested tuples of program artifacts, and features are nested delta tuples, where + recursively composes them by vector addition. This is the essence of AHEAD.

The ideas presented above concretely expose two FOSD principles. The Principle of Uniformity states that all program artifacts are treated and modified in the same way. (This is evidenced by deltas for different artifact types above). The Principle of Scalability states all levels of abstractions are treated uniformly. (This gives rise to the hierarchical nesting of tuples above).

The original implementation of AHEAD is the AHEAD Tool Suite and Jak language, which exhibits both the Principles of Uniformity and Scalability. Next-generation tools include CIDE ^[10] and FeatureHouse.^[11]

FOMDD

Derivational and Refinement Relationships among Program Artifacts

Feature Oriented Model Driven Design (FOMDD) ^[5][6] combines the ideas of AHEAD with Model Driven Design (MDD) (a.k.a. Model-Driven Architecture (MDA)). AHEAD functions capture the lockstep update of program artifacts when a feature is added to a program. But there are other functional relationships among program artifacts that express derivations. For example, the relationship between a grammar g_f and its parser source s_f is defined by a compiler-compiler tool, e.g., javacc. Similarly, the relationship between Java source s_f and its bytecode b_f is defined by the javac compiler. A commuting diagram expresses these relationships. Objects are program representations, downward arrows are derivations, and horizontal arrows are deltas. The figure to the right shows the commuting diagram for program p₃ = i+j+h = [g₃,s₃,b₃].

A fundamental property of a commuting diagram is that all paths between two objects are equivalent. For example, one way to derive the bytecode b₃ of parser p₃ (lower right object in the figure to the right) from grammar g_h of parser h (upper left object) is to derive the bytecode b_h and refine to b₃, while another way refines g_h to g₃, and then derive b₃, where + represents delta composition and () is function or tool application:

  b3 = $\Delta$bj + $\Delta$bi + javacc( javac( gh ) ) = javac( javacc( $\Delta$gi + $\Delta$gj + gh ) )

There are $\tbinom{4}{2}$ possible paths to derive the bytecode b₃ of parser p₃ from the grammar g_h of parser h. Each path represents a metaprogram whose execution generates the target object (b₃) from the starting object (g_f). There is a potential optimization: traversing each arrow of a commuting diagram has a cost. The cheapest (i.e., shortest) path between two objects in a commuting diagram is a geodesic, which represents the most efficient metaprogram that produces the target object from a given object.

Note: A “cost metric” need not be a monetary value; cost may be measured in production time, peak or total memory requirements, power consumption, or some informal metric like “ease of explanation”, or a combination of the above (e.g., multi-objective optimization). The idea of a geodesic is general, and should be understood and appreciated from this more general context.

Note: It is possible for there to be m starting objects and n ending objects in a geodesic; when m=1 and n>1, this is the Directed Steiner Tree Problem, which is NP-hard.

Commuting diagrams are important for at least two reasons: (1) there is the possibility of optimizing the generation of artifacts (e.g., geodesics) and (2) they specify different ways of constructing a target object from a starting object.^[5][12] A path through a diagram corresponds to a tool chain: for an FOMDD model to be consistent, it should be proven (or demonstrated through testing) that all tool chains that map one object to another in fact yield equivalent results. If this is not the case, then either there is a bug in one or more of the tools or the FOMDD model is wrong.

Note: the above ideas were inspired by category theory.^[5][6]

Applications

• Network Protocols
• Extensible Database Systems
• Data Structures
• Distributed Army Fire Support Simulator
• Production System Compiler
• Graph Product Line
• Extensible Java Preprocessors
• Web Portlets
• SVG Applications

See also

• FOSD MetaModels—product lines of product lines
• FOSD Program Cubes—multi-dimensional product lines
• FOSD Feature Interactions—other operations on features, including an operation designating feature interaction

References

1. "Design and Implementation of Hierarchical Software Systems with Reusable Components" (PDF).
2. "Access Path Selection In Relational Databases".
3. "Feature-Oriented Programming: A Fresh Look at Objects".
4. "Scaling Step-Wise Refinement" (PDF).
5. "Feature Oriented Model Driven Development: A Case Study for Portlets" (PDF).
6. "Generative Metaprogramming".
7. "Feature Models, Grammars, and Propositional Formulas" (PDF).
8. "An Algebra for Features and Feature Composition" (PDF).
9. "Superimposition: A Language-Independent Approach to Software Composition" (PDF).
10. "Guaranteeing Syntactic Correctness for all Product Line Variants: A Language-Independent Approach" (PDF).
11. "FeatureHouse: Language-Independent, Automated Software Composition" (PDF).
12. "Testing Software Product Lines Using Incremental Test Generation" (PDF).