| DOME (Source) | 53-RH-80.2 | |
| DoMESystem (Source) | 53-RH-80.2 | |
| emapps (Source) | 53-RH-80.0 | ENVY/Manager Application Support |
| DoME-Win32Support (Source) | 53-RH-80.1 | From 'Kernel-changes.st' |
| Tgen (Source) | 53-RH-80.1 | |
| GrapEVisualizationModel (Source) | 53-RH-80.0 | |
| GrapEUICore (Source) | 53-RH-80.2 | |
| GrapEWidgets (Source) | 53-RH-80.2 | |
| DoMEInspectorSystem (Source) | 53-RH-80.2 | |
| GrapEInfoModel (Source) | 53-RH-80.2 | |
| GrapEDependencyModel (Source) | 53-RH-80.2 | |
| GrapEFilePersistence (Source) | 53-RH-80.1 | |
| GrapEInfoModel (Source) | 53-RH-80.2 | |
| GrapEHyperLinks (Source) | 53-RH-80.2 | |
| GrapEPreferencesSystem (Source) | 53-RH-80.2 | |
| DoMESystem (Source) | 53-RH-80.2 | DoMESystem supports the creation of domain specific graphical editors.
DoMESystem adds a DoME submenu with three entries to the VisualWorks Launcher Tools menu. These entries perform the following actions:
Launcher : Opens the primary DoME user interface from which users can
create new models, load existing models, and create new notations.
Load Startup Script : Loads and executes the user's start up script. Refer to the
documentation for details.
Initialize : Re-initializes DoMESystem. This may be necessary when making
modifications to the DoMESystem library. |
| DoMESystem-Overrides (Source) | 53-RH-80.0 | |
| ExportingSystem (Source) | 53-RH-80.2 | |
| DoMEAuxiliaryUI (Source) | 53-RH-80.2 | |
| FileBrowserSystem (Source) | 53-RH-80.2 | |
| HierarchyBrowserSystem (Source) | 53-RH-80.1 | |
| DoMEAuxiliaryUI (Source) | 53-RH-80.2 | |
| AlterSystem (Source) | 53-RH-80.2 | |
| AlterParserSystem (Source) | 53-RH-80.1 | |
| AlterSystem (Source) | 53-RH-80.2 | |
| AlterUI (Source) | 53-RH-80.2 | |
| ProjectorSystem (Source) | 53-RH-80.2 | Projector Diagram: A visual programming language that DOME can execute directly, and that can interface with Alter functions.
All of the Alter primitives are also available in Projector.
Projector diagrams can call user-defined Alter functions and vice-versa.
You can use Projector to define plug-in functions.
|
| OOASystem (Source) | 53-RH-80.1 | Coad-Yourdon OOA: An extension to the Coad-Yourdon Object Oriented Analysis notation.
This tool supports typed attributes, services with signatures, dataflows between objects, and ordinality on both attributes and relationships.
Several code generators are also available, most notably SQL.
|
| MetaDoMESystem (Source) | 53-RH-80.2 | DOME Tool Specification: A DOME Tool Specification allows a would-be DOME toolsmith to quickly create an editor for a new, specialized graphical notation, complete with textual, numeric, and symbolic annotations.
The DOME Tool Specification notation allows you to define new node types, arc types, appearances, annotations, semantic relationships, menus, tool buttons, and other elements of your new tool.
From such a specification, the DOME Tool Specification tool can install all of the Smalltalk code needed to implement the specification.
|
| ProtoDoMESubsystem (Source) | 53-RH-80.2 | ProtoDOME Model: A Meta-CAD tool for prototyping new graphical language systems.
Given a DOME Tool Specification, ProtoDOME will interpret it directly to realize an editing environment for the specified graphical language.
|
| CyberDoMESubsystem (Source) | 53-RH-80.2 | CyberDOME Model: A Meta-CAD tool for prototyping new graphical language systems.
CyberDOME allows the user to create a new modeling language by example, automatically producing and maintaining the DOME Tool Specification behind it.
|
| MetaScribeSubsystem (Source) | 53-RH-80.1 | |
| MetaScribeUISubsystem (Source) | 53-RH-80.1 | |
| MeatScribeModelSubsystem (Source) | 53-RH-80.1 | |
| MetaScribeRenderingSubsystem (Source) | 53-RH-80.1 | |
| MetaScribeSubsystem (Source) | 53-RH-80.0 | |
| UDPSystem (Source) | 53-RH-80.1 | User-Defined Property Specification: This can be used to extend existing tools with additional object properties.
A UDP spec must be coupled to a DOME Tool Specification.
Specifications for existing tools can be found in DOME's "tools" directories.
|
| ColbertSystem (Source) | 53-RH-80.2 | Colbert OOSD Project: The Colbert Object-Oriented Software Development (OOSD) Methodology, developed by Absolute Software Inc, includes a collection of notations supporting object-oriented analysis (OOA):
Object-Class Diagrams - used to describe the nature, structure and operations of each class, and the relationships that exist between classes and between objects and classes;
Object-Oriented Statecharts - an object-oriented version of Harel Statecharts used to describe the dynamic behavior of an object or a class;
Object-Interaction Diagrams - used to represent the nature and structure of objects and their interactions.
Those familiar with common COTS methodologies, such as OMT, Booch or UML, should be immediately comfortable with these notations. For further information on the Colbert Methodology or related engineering techniques contact:
Absolute Software Inc.
4593 Orchid Drive,
Los Angeles, CA 90043-3320
(213) 293-0783
email: colbert@abssw.com
DOME editors have been developed to support each of the Colbert OOSD notations listed above. The DOME editors support the development of an integrated system model by maintaining constraints and dependencies between the three different system views used in the OOSD method.
|
| ColbertSystem (Source) | 53-RH-80.1 | |
| ColbertOIDSystem (Source) | 53-RH-80.2 | |
| ColbertOCDSystem (Source) | 53-RH-80.1 | |
| ColbertSDSystem (Source) | 53-RH-80.1 | |
| PetriNetSystem (Source) | 53-RH-80.1 | Petri Net Model: A classical condition-event Petri Net that can be marked and executed.
|
| STDSystem (Source) | 53-RH-80.1 | State-Transition Diagram: Classical state-transition diagram (hierarchical).
|
| DFDSystem (Source) | 53-RH-80.2 | Data Flow Diagram (DFD): The data flow diagram supports the graphic representation of a system's information flow.
Transformations are applied to the information flow, via process nodes, as the data moves from input to output. External data source, data sink, and data store nodes are used as the input and outputs while data flow arcs are used to represent information flow.
|
| IDEF0System (Source) | 53-RH-80.1 | IDEF-0 Diagram:
During the 1970s, the U.S. Air Force Program for Integrated Computer Aided Manufacturing (ICAM) identified the need for better analysis and communication techniques for people involved in improving manufacturing productivity.
As a result, the ICAM program developed a series of techniques known as the IDEF (ICAM Definition) techniques which included IDEF0, used to produce a "function model".
A function model is a structured representation of the functions, activities or processes within the modeled system or subject area.
|
| MultiPageSystem (Source) | 53-RH-80.1 | Multi-Page Model: This is a generic top-level model that you can use for linking more specialized models together.
A multi-page model consists of a set of "anchors".
Each anchor can hold a different type of model as its subdiagram.
|
| PaperOutlineSystem (Source) | 53-RH-80.1 | Document Outline: A simple "concept mapping" notation for use during the early stages of writing.
Topics are represented by circles, and connected to subtopics.
Content for each topic resides in the description property.
You can generate a "Starter Document" with DOME's document generator.
|
| Dome-FixMe (Source) | 53-RH-80.2 | |