A note about the use of UML for geodatabase design
There are several strategies for designing and creating geodatabases:
- Existing databases can be migrated to the geodatabase
- Use the schema management and creation tools within ArcGIS
- Use one of the Pre-defined ArcGIS data models to jump-start your design
- Use Unified Modeling Language ( UML) to design a geodatabase schema and then import the schema into your geodatabase.
UML models are created using tools such as Microsoft Visio or Sparx Systems' Enterprise Architect. Using Microsoft Visio to create UML models requires the ArcGIS CASE tools functionality to import the UML schema into the geodatabase. However, ArcGIS CASE tools only support a subset of geodatabase functionality; such as tables, feature classes and relationship classes. They don't support many of the datasets responsible for modeling richer geographic behavior, such as network datasets, topologies, mosaic datasets, etc. For this reason, we do not recommend users create new UML models for use with CASE tools. The CASE tools functionality is only maintained for legacy reasons.
We recommend using Sparx Systems' Enterprise Architect for users interested in geodatabase design with UML as it offers many advantages over the ArcGIS CASE tools functionality. Enterprise Architect uses Geodatabase XML and the XML import\export functionality for the creation of geodatabases based on a UML design. Because of this, many of the limitations that existed with previous UML modeling solutions and CASE tools are not present in Enterprise Architect.
Some of the benefits of using Enterprise Architect include:
- The ability to model a larger set of datasets within the geodatabase, such as network datasets, topology, mosaic datasets and other datasets responsible for modeling richer geographic behavior as part of its UML profile for ArcGIS.
- The ability to reverse engineer an existing geodatabase into UML, since Enterprise Architect uses Geodatabase XML and the XML Workspace Import/Exporting functionality. Using the Export XML Workspace Document wizard or geoprocessing tool, the geodatabase schema can be exported to an XML workspace document. The XML document can then be imported into Enterprise Architect to provide a visual model of your geodatabase, based on industry-standard UML notation.
- Traceability to other analysis and design models
- Access to UML design techniques, such as the ability to logically group elements through the use of abstract classes.
- The ability to share your geodatabase schema and geospatial concepts with analysts and architects versed in UML design
For more information on using Enterprise Architect for geodatabase design, visit Sparx System's website (http://www.sparxsystems.com/arcgis/index.html).