Lepus3: Information from Answers.com

Example: A composite pattern in LePUS3.

LePUS3 is an object-oriented, visual Design Description Language, namely a software modelling language and a formal specification language^[1] ^[2] that is suitable primarily for modelling large object-oriented (Java, C++, C#) programs and design motifs such as design patterns ^[3]. It is defined as an axiomatized subset of First-order predicate logic. A Codechart is a diagram that is also a well-formed specification in LePUS3.

LePUS is an abbreviation for Language for Pattern Uniform Specification.

Purpose

LePUS3 is tailored for the following purposes:

Scalability: To model industrial-scale programs using small charts with only few symbols
Automated verifiability: To allow programmers to continuously keep the design in synch with the implementation
Program visualization: To allow tools to reverse-engineer legible charts from plain source code modelling their design
Pattern implementation: To allow tools to determine automatically whether your program implements a design pattern
Design abstraction: To specify unimplemented programs without committing prematurely to implementation minutiae
Genericity: To model a design pattern not as a specific implementation but as a design motif
Rigour: To allow software designers to be sure exactly what design charts mean and reason rigorously about them

LePUS3 belongs to the following families of languages:

Object oriented software modelling languages (e.g., UML): LePUS3 is a visual notation that is used to represent the building-blocks in the design of programs object-oriented programming languages
Formal specification Languages: Like other Logic Visual Languages, LePUS3 charts articulate sentences in mathematical logic. LePUS3 is axiomatized in and defined as a recursive (turing-decidable) subset of first-order predicate calculus. Its semantics are defined using finite structure (mathematical logic).
Architecture Description Languages: LePUS3 is a non-functional specification language used to represent design decisions about programs in class-based object-oriented programming languages (such as Java and C++).
Tool supported specification languages: Verification of LePUS3 charts (checking their consistency with a Java 1.4 program) can be established (‘verified’) by a click of a button, as demonstrated by the Two-Tier Programming Toolkit.
Program Visualization Notations are notations which offer a graphical representation of the program, normally generated by reverse-engineering the source code of the program.

LePUS3 was designed to accommodate for parsimony and for economy of expression. Its vocabulary consists of only 15 visual tokens.

LePUS3 Vocabulary

The Two-Tier Programming Toolkit^[4] ^[5] can be used to--

create LePUS3 specifications (charts)
verify automatically ^[6] the consistency of LePUS3 charts with Java 1.4 programs; and
reverse-engineer charts from Java source code.

LePUS3 was specifically designed to model, among others, the 'Gang of Four' design patterns, including Abstract Factory, Factory Method, Adapter, Decorator, Composite, Proxy, Iterator, State, Strategy, Template Method, and Visitor. (See "The 'Gang of Four' Companion") ^[3] The abbreviation LePUS for "Language for Pattern Uniform Specification" became because the precursor of this language was primarily concerned with design patterns. The implementation of design patterns specified in LePSU3 can be automatically verified by the TTP Toolkit ^[6].

LePUS3 is particularly suitable for modelling large programs, design patterns, and object-oriented application frameworks. It is unsuitable for modelling non object-oriented programs, architectural styles, and undecidable and semi-decidable properties.