Annotation: Used for the purpose of augmenting Tigerstripe artifacts with additional information. The additional information can be anything that the annotation creator wants it to be. As opposed to Stereotypes, Annotations are not stored inside the model so they can be maintain independently.
Artifact: An artifact typically corresponds to a model element. Some examples are Entity, Session Facade, and Datatype artifacts. Usually each artifact is associated with a Java file to promote modularity as much as possible. There are two main categories of artifacts: Information Model Artifacts and Behavior Model Artifacts.
Artifact Rule: Associates a Velocity Template with artifact(s) and indicates various properties about the generated code, including the output file.
Association Artifact: Used to create associations (in the UML sense) between artifacts.
Association Class Artifact: Similar to an association artifact, but can also posses other attributes.
Datatype Artifact: Use a modeled datatype to specify a grouping of attributes.
Dependency Artifact: Creates a dependency (in the UML sense) between artifacts.
Enumeration Artifact: Models domain specific enumerations, ie. set of pre-defined values. For example, a ProbableCause enumeration could be defined with the series of pre-defined ProbableCauses to be used within Alarms.
Exception Artifact: A modeled exception element as thrown from a method.
Event Artifact See Notification Artifact.
Facet: Defines a self-contained sub-model within a Tigerstripe model. The scope allows users to highlight and enforce design features on their model. Consequently, you can generate code for each facet separately.
Generator: Plugin projects are generator projects that specify the model generation details. A plugin project defines the rules by which artifacts are rendered in the output, in terms of format (eg HTML, XML, Java) filename, and detailed file content.
Global Properties: Used to allow specific information for use in a given Tigerstripe Project. For example, the name of a directory where certain file types should be created.
Managed Entity Artifact: This is the main element used to create modeled entities. It's very generic and aimed at representing a thing of logical or physical existence in a model.
Method: Represents an operation available on an artifact.
Method argument: Arguments of the method that's defined in an artifact.
Model: Contains the details of the information that should be collected and persisted.
Model Project See Tigerstripe Model Project.
Notification Artifact: Models a notification to be emitted through an interface typically modeled as a SessionFacade. The payload of the defined notification is captured by the fields of that artifact.
Plugin: See Tigerstripe Plugin Project.
Plugin Project See Tigerstripe Plugin Project.
Plugin Project Descriptor: This is the ts-plugin.xml file in a plugin project. It contains the metadata for the project along with other properties used in the code generation. This file also defines the Artifact Rules
Profile: Tigerstripe Profiles help you to configure your Tigerstripe Workbench by defining stereotype and primitive types. In addition it allows you to enable or disable actions across the workbench.
Project See Tigerstripe Project.
Project Descriptor: This is the metadata for a Tigerstripe model project (tigerstripe.xml). This file is used to store additional properties about the project. Such properties can include the project version, description, dependencies, and also properties that are used when generating code.
Query Artifact: Models a query mechanism to select a set of Entities based on specific criteria. For example in the context of an Alarm Manager, a QueryAllOutstandingAlarms would return all AlarmEntities that correspond to outstanding alarms.
Rule: See Artifact Rule
Session Facade Artifact: Models an integration point for a Service Contract. Through this facade, operations on Managed Entities are exposed, Queries and UpdateProcedure are accessible. Also, this is the logical source of emitted notifications. Defining Session Facades is typically the final step in assembling a Service Contract, where information model and the capabilities of the Service Contract are selected.
Stereotype: Stereotypes are a way to extend the Tigerstripe model in a controlled manner. Stereotypes are defined in a Tigerstripe profile.
Template See Velocity Template.
Tigerstripe: Tigerstripe is a framework for Model Driven Engineering (MDE) with special support for the Telecommunications Industry.
Tigerstripe Perspective: A custom perspective tailored to the needs of Tigerstripe users
Tigerstripe Plugin Project: See Generator
Tigerstripe Project: Contains the information model which can be used to generate code from. The corresponding metadata for a Tigerstripe project is stored in tigerstripe.xml file.
Tigerstripe Workbench: An Integrated Development Environment (IDE) for creating models and generating code from it.
Tigerstripe Explorer: A view responsible for displaying all the relevant contents of the Tigerstripe projects
Update Procedure Artifact: Models a long running procedure to be triggered through a Service Contract. The response to triggering such a procedure will contain information about whether the procedure completed successfully or not.
Velocity: Velocity permits you to use a simple yet powerful template language to reference objects defined in Java code. It is written in 100% pure Java
Velocity Template: Describes how output will be generated based on the artifacts contained within a particular project against which the plug-in is run