1. Ikan Software NV CWD4ALL
September 2007

2. Agenda

3. CWD4ALL architecture

4. Logical model

5. Entity relationship Model Domain and data type administration
Logical Model
Entity relationship Model
Domain and data type administration
Naming standaardisation, Glossary
Design rules
Possibility to compare/merge models
Extensive formatting possibilities
Notation
Bachman
Barker
Engineer to Relational model support

6. Dimensional Model

7. Per logical, one or more dimensional models
Import of cube views, XMLA, Oracle ROLAP
Generation of
Oracle AW (Analytical Workspaces)
Cube Views MetaData
Microsoft XMLA

8. Process Model

9. Support for Data Flow Diagrams Information store Process
Process Model
Support for Data Flow Diagrams
Information store
Process
External Agent
Information Flow
Information Structures
Events
Transformation Package (CWM)

10. Relational Model

11. Engineer to Logical model support Selective engineering
Relational Model
Engineer to Logical model support
Selective engineering
Mapping logical/relational
One logical, many relational models

12. Physical Model

13. Support for all physical objects partitioning sequences tablespaces ……
Physical Model
Physical model for
Oracle 8, 9 and 10 (11 comes)
SQL server 2000/2005
UDB 7 and 8
DB2 V7 and V8
Support for all physical objects
partitioning
sequences
tablespaces ……

14. Support for Object Relational Mapping Creation of views
Special Features
Support for Object Relational Mapping
Creation of views
Creation of displays
DDL generation
Model compare
Much more

15. CWD4ALL and Oracle
Support for:
Oracle 8, 9 and 10 (11 to come)
Oracle ROLAP and MOLAP (AW)
Spatial (life sciences, semantics)
Converts to Oracle from
any JDBC/ODBC
from catalog
DB2, UDB, SQL Server
DDL
DB2 cube views, XMLA
XMI, Erwin, Designer
Supports modeling of OWB User defined classes (metadata)

16. SQLDeveloper extension JDeveloper extension
Available as
Standalone
SQLDeveloper extension
JDeveloper extension

17. CWD4ALL and Oracle Designer

18. Extensible Repository
Why Oracle Designer
Why Oracle Designer?
Extensible Repository
Versioning
Code generation

19. Add to existing CWD4ALL following: repository: Extensible
Ikan plan
Add to existing CWD4ALL following:
repository:
Extensible
Versioning capabilities
Relational or CMS
Code generation

20. Designer Import feature list
Easy to use layered wizard that guides you through connections, selected work area, application systems and branches to concrete objects belonging to selected branches.
Import of versioned and non-versioned objects – the last checked-in version of objects belonging to selected branch is imported.
Multiple application systems can be selected for import. Branch can be selected if application system is versioned.
Diagrams belonging to selected application systems are imported and respective “Subviews” are created in Logical, Relational and Data types models (the layout is not preserved). “Subviews” are created in addition to main diagram (for each respective model) that represents all imported objects.
All definitions made with “Entity Relationship Diagrammer” are imported:
domains with all defined constraints – Check, Range, List of values
Entities with their properties and related attributes, keys and relationships
Supertype/Subtypes entities hierarchies
Arc definitions for relationships.
Complete definitions for following objects are imported:
Tables and definitions for columns, primary key, unique keys, foreign keys, indexes, check constraints and triggers
Views
Materialized views
Clusters
Sequences
Object and collection types and their usage in definitions of tables, columns and views
Synonyms for all imported objects
Mappings between entities and tables, attributes and columns, entity and table keys are imported and maintained.

21. Application System selection

22. Designer Object selection