Platinum Erwin Erx 3.5
среда 22 апреляadmin
Bridge Specifications
View Virginia Greene’s profile on LinkedIn, the world's largest professional community. Virginia has 1 job listed on their profile. See the complete profile on LinkedIn and discover Virginia’s.
Ponyprog is very powerful and popular microchip programmer. Ponyprog enables the user to program EEPROM, FLASH and PIC's using user friendly tools and multiple programmer types. Ponyprog supports AVR, SPI eeprom, AVR micro, 12C bus 8bit eeprom, PIC 16 micro, PIC 12 micro, AT89S micro and SDE2506 eeprom family chips. Ponyprog is a very powerful and popular microchip programmer. Ponyprog enables the user to program EEPROM, FLASH and PIC's using user friendly tools and multiple programmer types. Key Features of Ponyprog: - Ponyprog supports AVR, SPI eeprom, AVR micro, 12C bus 8bit eeprom. Apple Software Update is a software tool by Apple that installs the latest version of Apple software. It was originally introduced to Mac users in Mac OS 9. A Windows version has been available since the introduction of iTunes 7. 
PonyProg is a serial device programmer based on some simple and cheap interfaces for the PC and a user friendly GUI available for WindowsXP/7/8/10 and Intel Linux. Its purpose is programming every serial device like eeproms and microcontrollers. Ponyprog software free download. Development Tools downloads - PonyProg2000 by Claudio Lanconelli and many more programs are available for instant and free download.
| Vendor | erwin, Inc. |
| Tool Name | erwin Data Modeler |
| Tool Version | 3.x |
| Tool Web Site | https://erwin.com/products/erwin-data-modeler/ |
| Supported Methodology | [Data Modeling] Data Store (Physical Data Model, Logical Data Model, Stored Procedure Expression Parsing), Graphical Layout via erwin 3 (.ERX) File |
Export tool: erwin, Inc. erwin Data Modeler 3.x (https://erwin.com/products/erwin-data-modeler/)
Export interface: [Data Modeling] Data Store (Physical Data Model, Logical Data Model, Stored Procedure Expression Parsing), Graphical Layout via erwin 3 (.ERX) File to erwin 3.x (ERX) Export bridge: 'CaErwin3Erx' 11.0.0
Please enter a description
Bridge Parameters
| Parameter Name | Description | Type | Values | Default | Scope | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Version | Select here the version of erwin you want to use. | ENUMERATED |
| 3.5 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| File | The bridge generates a erwin ERX file. In order to load the converted model in erwin: 1. Choose 'Open' from the File menu. 2. In the 'List files of type' list box select erwin ERX (*.erx). 3. Locate the drive and the folder that contains the file you want to open. Double-click on the folders in the 'Folders' list in order to switch to a different folder. If necessary, switch to a different drive by selecting a specific drive from the Drives list. 4. Locate the file you want to open. Type the name of the file in the 'File Name' text box, or select it from the 'File Name' list. 5. Click 'OK'. In order to load the converted model into another Design Tool that supports the ERX format, please refer to the tool documentation. | FILE | *.erx | Mandatory | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Target database | Specify the target database. 'Auto Detect' means that the bridge will try to auto-detect the target database from the originating model. | ENUMERATED |
| Auto Detect | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Order Attributes on Primary Key position | Order the attributes in the order of the Primary key. The default is to order the Attributes based on their position in the Entity. | BOOLEAN | False | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Export dimensional properties | This option enables the dimensional modeling features for this model and exports the dimensional role (Fact, Dimension, Outrigger) and dimensional type (fixed vs slowly changing) of the tables. | BOOLEAN | False | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Encoding | Specifies the character set encoding of the model to be imported or exported: If there are multiple choices for a language, the actual encoding will be indicated between parentheses. The default is 'Western European (Windows 1252)' on Windows and 'Western European (ISO 8859-1)' on other platforms. | ENUMERATED |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Connection | Allows selecting a connection by name, if the source model contains multiple database connections. If the source model contains multiple connections and this parameter value is left empty, the connection with the most objects is selected. | STRING |
Bridge Mapping
| Meta Integration Repository (MIR) Metamodel (based on the OMG CWM standard) | 'erwin 3.x (ERX)' Metamodel CaErwin3Erx | Mapping Comments |
| Association | Relationship | |
| Aggregation | Identifying/ Non Identifying | Identifying if True |
| Description | Definition | |
| DesignLevel | Logical Only/Physical Only | |
| PhysicalName | Foreign Key Constraint Name | |
| AssociationRole | Relationship | |
| DesignLevel | Logical Only/Physical Only | |
| ExtraConstraint | Referential Integrity Rules | If the field does not contain formatted information it is not mapped. |
| Multiplicity | Cardinality | |
| Name | Verb Phrase | |
| Source | It is used to determine the Parent entity and the Child entity | |
| AssociationRoleNameMap | Relationship | A rolename is set for each renamed attribute |
| Attribute | Attribute/Column | |
| Comment | Column Comment | |
| Description | Attribute Definition | |
| DesignLevel | Logical Only/Physical Only | |
| Name | Logical Name | |
| Optional | Null Option | |
| PhysicalName | Physical Name | |
| Position | Sequence Number | |
| BaseType | Domain, Attribute Data Type | |
| DataType | Data Type | See datatype conversion array |
| Description | Definition | |
| Length | Data Type Length | |
| Name | Name | |
| PhysicalName | Physical Name | |
| Scale | Data Type Precision | |
| CandidateKey | Key Group/Index | |
| Name | Name | |
| PhysicalName | Physical Name | if set by the user |
| UniqueKey | Key Group Type | If uniqueKey is False the index is an inversion entry |
| Class | Entity/Table | |
| Comment | Table Comment | |
| CppClassType | Set to ENTITY | |
| CppPersistent | Set to True | |
| Description | Entity Definition | |
| DesignLevel | Logical Only/Physical Only | |
| DimensionalRole | Dimensional Modeling Role | |
| Name | Name | |
| PhysicalName | Physical Name | |
| ClassDiagram | Subject Area,Stored Display,Stored Display Options | A stored display is created for each subject area, some display options are set in order to see attributes and foreign keys. |
| Description | Subject Area Definition | |
| Name | Name | |
| DatabaseSchema | Owner | Table, View or Index owner |
| Name | Name | |
| DerivedType | Domain, Attribute Data Type, Validation Rule | |
| DataType | Data Type | See datatype conversion array |
| Description | Definition | For domain (see userDefined) |
| DesignLevel | Logical Only/Physical Only | |
| InitialValue | The Default name is set to the name of the Type; only the server part of the Default is set. | |
| Length | Data Type Length | |
| LowerBound | Validation Rule Minimum | a Validation Rule is created if the Type defines a lower bound, an upper bound or type values. |
| Name | Name | For domain (see userDefined) |
| PhysicalName | Physical Name | |
| Scale | Data Type Precision | |
| UpperBound | Validation Rule Maximum | |
| UserDefined | If True a Domain is created. Else the attribute data type is set. | |
| DesignPackage | No equivalent, All model elements of a package are exported in the ERwin file. | |
| ForeignKey | Foreign Key Group/Index | |
| Generalization | Supertype/Subtype | All subtype relationships are Complete |
| GeneralizationRole | Supertype/Subtype Relationship | All subtype relationships are Complete |
| Index | Key Group/Index | Indexes that are not related to a Key are mapped to an inversion entry |
| Name | Name | |
| PhysicalName | Physical Name | |
| IndexMember | Key Group Member/Index Member | |
| Position | Position in the Key Group Members list | |
| SortOrder | Ascending/descending order | |
| Note | Note | |
| PhysicalObject | DB2 TableSpace, DB2 Database, DB2 StorageGroup | Only for DB2 |
| PhysicalRelationship | Only for DB2: Connects the Physical Object | |
| PhysicalTarget | Target Server | Only for DB2 |
| Projection | Diagram View Object | Graphical Information |
| BackgroundColor | fill color | |
| FontColor | font color | |
| FontName | font | |
| FontSize | font size | |
| Height | height | |
| LineColor | line color | |
| Width | width | |
| X | x | |
| Y | y | |
| RelationshipProjection | Diagram View Object | Graphical Information |
| FontName | font | |
| FontSize | font size | |
| LineColor | line color | |
| LinePoints | relationship path | |
| SQLViewAssociation | View Relationship | |
| SQLViewAttribute | View Column | |
| Description | Comment | Only if the comment property is empty |
| Name | Name | |
| PhysicalName | Name | |
| Position | Column Position | |
| SQLViewEntity | View Entity | |
| Comment | Comment | |
| Description | Comment | Only if the comment property is empty |
| Name | Name | |
| WhereClause | SQL statement | |
| Shape | Text Block | |
| Height | Calculated property | |
| Width | Calculated property | |
| StoreModel | Model/Diagram | |
| Description | Definition | |
| Name | Name | |
| SystemType | Target Server | |
| SystemTypeOld | Target Server | |
| Name | Display Value/Valid Value | |
| TypeValue | Validation Rule | A validation rule is created for each type that defines Type Values. |
| Name | Display Value/Valid Value | |
| Position | Valid values in the Validation Rule are ordered on the position. | |
| Value | Value |