Press Kit - Graphics

These pictures are intended for press use only. The pictures must not be altered in any way. To download, right-click the link and choose Save Target As...

MetaCase company logos

• metacase_large.tif 8.7 x 2.0 cm, 300 dpi, CMYK (1029 x 236 pixels, for print)
• metacase_small.tif 5.5 x 1.26 cm, 300 dpi, CMYK (649 x 149 pixels, for print)
• metacase_lg.png 700 x 148 pixels, RGB (for WWW and screen) 
• metacase_sm.png 147 x 31 pixels, RGB (for WWW and screen) 

MetaEdit+ product logo

• metaedit.png 499 x 101 pixels, RGB (for WWW and screen)

MetaEdit+ screenshots

• Main window: For reusing and managing metamodel elements

Metamodeling tools (MetaEdit+ Workbench)

• Object tool: For defining modeling concepts and their properties
• Symbol editor: For designing or importing modeling symbols
• Graph types definer: For combining concepts into a modeling language
• Constraints definer: For selecting modeling rules and constraints
• Generator Editor: For specifying the mapping from models to code
• Generator Debugger: For testing and debugging the generator with links back to models

Modeling tools (MetaEdit+ Modeler)

• Diagram editor: For modeling with diagrams: example 1, example 2, example 3 
• Matrix editor: For viewing and editing design information in a matrix format
• Table editor: For viewing and editing design information in a table format

Architecture graphic 

• Modeling in domain-terms versus modeling in code terms
  Application development is about bridging the gap between an idea (in domain terminology) and the finished product. Traditionally, we bridge this gap by mapping the idea to different abstraction layers like code (assembler, 3GL) or more recently, by first making a mapping to a code-based modeling language (e.g. UML). We thus solve the same problem multiple times. DSM takes an approach where we model the idea in domain terms and generate the final code directly from this high abstraction layer, without mapping.