![20
Model to DRM contd…
2. Export UML model using XMI
<!-- ==================== account1::accounts::AccountVO [Class] ==================== -->
<UML:Class xmi.id = 'S.235.1027.15.92'
name = 'AccountVO' visibility = 'public' isSpecification = 'false'
isRoot = 'true' isLeaf = 'true' isAbstract = 'false'
isActive = 'false'
namespace = 'S.235.1027.15.7' supplierDependency = 'G.65' >
<UML:Classifier.feature>
<!-- ==================== account1::accounts::AccountVO.userID_ [Attribute] ==================== -->
<UML:Attribute xmi.id = 'S.235.1027.15.93'
name = 'userID_' visibility = 'private' isSpecification = 'false'
ownerScope = 'instance'
changeability = 'changeable' targetScope = 'instance'
type = 'G.31' >
<UML:StructuralFeature.multiplicity>
<UML:Multiplicity >
<UML:Multiplicity.range>
<UML:MultiplicityRange xmi.id = 'id.2361427.19'
lower = '1' upper = '1' />
</UML:Multiplicity.range>
</UML:Multiplicity>
</UML:StructuralFeature.multiplicity>](https://image.slidesharecdn.com/ombpresentation-240204152601-daa241c0/85/Automated-generation-of-DRM-instances-from-models-20-320.jpg)
Automated generation of DRM instances from models
- 1. Automated generation of DRM instances from models Neelam Kadam August 30, 2005
- 2. 2 Agenda About Unisys My Role and interest in the DRM process Unisys solution 3D-Visible Enterprise Enterprise Visualization Publisher Generating the DRM XML instance Proposed DRM process architecture Adding value to DRM process
- 3. 3 About Unisys Unisys is a worldwide technology services and solutions company • operates in 100+ countries with 37,000+ employees $6B Fortune 500 company with more than $1B in Federal Government Revenue Focuses on three primary industries • Financial Services - Banking - Insurance • Public Sector - Government - Education - Health Care • Commercial - Transportation - Media - Communications - Life Sciences - Consumer / Industrial
- 4. 4 EA Depth and Experience Developed and implemented successful government and commercial EAs, including Demonstrated unique capabilities in partnering with the US Government and commercial organizations • Enterprise and Security Architecture planning, development and evaluation • Business and IT strategy development • Program management and Capital Planning and Investment Control (CPIC) Quality, depth and experience of EA staff who are recognized industry architecture experts TSA DOD GSA CoPA CMS DOJ DuPont ING Northwest Financial
- 5. 5 My Role and interest in the DRM process Product Manager, CTO’s office, Global Public Sector Develop and manage products for EA aggregation and visualization Attended the first FEA Data Reference Model Public Forum on June 13th, 2005 • OMB’s goal - “Concrete measurable implementations” using software • DRM Management Process (Michael Daconta’s presentation) Unisys has developed a solution that applies in the “Collection” Phase of the DRM process Phase 1 Collection Phase 3 Harmonization & Standardization Phase 2 Registration Phase 4 Measure
- 6. 6 Our approach Task at hand • Federal agencies will create DRM XML documents conforming to the DRM XML schema • DRM XML schema has a section for data description that includes - StructuredData – Data described via E-R or class models - UnstructuredData – Data in free-form format - SemiStructuredData – Little of both • An agency will have numerous existing E-R/class/business models created using a commercial modeling tool that can be leveraged to create the StructuredData portion of the DRM instances Solution • Automated generation of the <StructuredData> section of the DRM instance from these models
- 7. 7 Solution overview Unisys solution consists of two components • 3D Visible Enteprise – is a holistic approach to create visibility into how change affects an organization’s strategy, processes, applications and IT infrastructure • Enterprise Visualization Publisher – is a tool that aggregates data from multiple EA repositories and publishes it in a user-friendly and compelling manner with built-in analytic capabilities Benefits of automated generation of DRM XML instance • Leverages existing investment – promotes reuse • Automated generation – less manual data entry, less prone to errors • Repeatable process For more information on 3DVE, please visit the following URL- http://www.unisys.com/services/enterprise__transformation/index.htm
- 8. 8 3D Visible Enterprise Imagine… • Knowing the result of your decisions before you make them. • Knowing the benefits of spending money before you spend it. • Making changes already knowing the consequences of those changes across your entire organization. 3D Visible Enterprise creates a way of seeing all the cause-effect relationships between your vision, operations and the IT systems that support them. Our client experience has shown cost savings from 25 to 60 percent through improvements in cycle time, productivity and reduction of redundancy.
- 9. 9 3D-VE is based on models We build models: maps of your business. Models: • are a representation of the real world • are easier to understand and manipulate • allow you to explore cause and effect without costly mistakes • capture intellectual assets • remain valuable over time View Model 1..* 1..* 0..* +nestedModel 0..*
- 10. 10 The four layers of 3D-VE • Models are organized into four distinct operational layers. • These layers are digitally interconnected, tying the operational architecture to the technology architecture. • Result is traceability across your entire operation. STRATEGY LAYER PROCESS LAYER APPLICATION LAYER INFRASTRUCTURE LAYER
- 11. 11 Cross-enterprise impact analysis We need to offer additional security services to protect the homeland. What will the cost be to offer a new service in geography ‘A’? What processes will be affected where new services are offered? How many people need to be trained? What’s the workload impact? What applications are affected by new security service definitions? How do the attribute changes cascade through the various systems? How much will it cost to create new supporting components? What additional capacity is required to handle additional throughput? What additional capacity is required for additional storage? How many new products or geographies can be supported?
- 12. 12 XML UML XMI Requisite Pro Rose ProVision Excel Word PVX 3D-VE components MOF Repository 3D-VE Metamodel Prospector 3D-VE Impact Analysis Application 3D-VE Transformer XML XML find associations view traceability Software Architect Other Tools Future Interface
- 13. 13 3D-VE in action at VHA
- 14. 14 EVP in action at TSA
- 15. 15 Enterprise Visualization Publisher (EVP) Aggregates enterprise architecture data from multiple EA repositories Publishes the aggregated data in multiple user-friendly formats using advanced visualization technology Application in the DRM process • EVP integrates with the 3D-VE MOF repository to harvest the DRM data elements, their attributes and relationships from various business/technical architecture models (workflow models, class models, data models etc) • Tool has been enhanced to - publish a DRM XML instance using the DRM XML schema - publish a DRM Topic Map instance - publish a user-friendly HTML view of the DRM XML instance - publish other formats (future)
- 16. 16 EVP Architecture 3D-VE MOF Repository (Technical architecture models, Business architecture models) Extract elements to populate <Structured Data> in DRM XML instance DRM XML Instance DRM XML Topic Map Enterprise Visualization Publisher
- 17. 17 Complete solution 3D-VE MOF Repository 3D-VE User Interface Enterprise Visualization Publisher Federal Agency Models created in commercial tools DRM XML Instance Other formats XSLT + Citizen Website 1. Import models 2. Extract DRM data 3. Publish DRM XML 4. Publish user-friendly HTML view
- 19. 19 Model to DRM – An example 1. UML Class Model created in Rational Rose
- 20. 20 Model to DRM contd… 2. Export UML model using XMI <!-- ==================== account1::accounts::AccountVO [Class] ==================== --> <UML:Class xmi.id = 'S.235.1027.15.92' name = 'AccountVO' visibility = 'public' isSpecification = 'false' isRoot = 'true' isLeaf = 'true' isAbstract = 'false' isActive = 'false' namespace = 'S.235.1027.15.7' supplierDependency = 'G.65' > <UML:Classifier.feature> <!-- ==================== account1::accounts::AccountVO.userID_ [Attribute] ==================== --> <UML:Attribute xmi.id = 'S.235.1027.15.93' name = 'userID_' visibility = 'private' isSpecification = 'false' ownerScope = 'instance' changeability = 'changeable' targetScope = 'instance' type = 'G.31' > <UML:StructuralFeature.multiplicity> <UML:Multiplicity > <UML:Multiplicity.range> <UML:MultiplicityRange xmi.id = 'id.2361427.19' lower = '1' upper = '1' /> </UML:Multiplicity.range> </UML:Multiplicity> </UML:StructuralFeature.multiplicity>
- 21. 21 Model to DRM contd… 3. Import Model into MOF Repository Source Model (Rational Rose “Class Diagram”) XML Serialization of “Class Diagram” XML Schema (Metamodel) of “Class Diagram” Rose .MDL File Format uses 3D-VE MOF Repository 3D-VE Transformer
- 22. 22 Model to DRM contd… 4. Publish model data to a DRM XML instance using the Enterprise Visualization Publisher <drm:Entity drm:name="AccountVO" rdf:ID="41574"> <drm:Attributes> <drm:Attribute drm:name="userID_" drm:datatype="String" /> <drm:Attribute drm:name="password_" drm:datatype="String" /> <drm:Attribute drm:name="email_" drm:datatype="String" /> <drm:Attribute drm:name="grantNumber_" drm:datatype="Integer" /> <drm:Attribute drm:name="title_" drm:datatype="String" /> <drm:Attribute drm:name="profileID_" drm:datatype="Long" /> <drm:Attribute drm:name="institutionID_" drm:datatype="Long" /> <drm:Attribute drm:name="ownerID_" drm:datatype="String" /> </drm:Attributes> <drm:Relationships> <drm:Relationship drm:name="Association" drm:key="" drm:cardinality="0..-1"> <drm:RelationshipTarget rdf:resource="41589" drm:key="" drm:cardinality="1..1" /> </drm:Relationship> </drm:Relationships> </drm:Entity>
- 23. 23 Proposed DRM architecture – agency view Agency MOF Repository 3D-VE Metamodel Prospector 3D-VE Traceability Application 3D-VE Transformer 3D-VE Query Interface Enterprise Visualization Publisher EA Models DRM Models Federal agency Created in commercial modeling tools DRM XML Instance DRM Topic Map XSLT + Citizen Agency Website RDF databases (Unstructured Data) Future
- 24. 24 Proposed DRM architecture – Inter-agency view MOF Repository A 3D-VE Transformer Enterprise Visualization Publisher EA Models DRM Models Federal Agency A DRM XML Instance Citizen Website MOF Repository B 3D-VE Transformer EA Models DRM Models Federal Agency B Federated MOF Repository Website
- 25. 25 Adding value to the DRM process MOF repository • Models can be imported from multiple commercial tools today (Rational Suite, Popkin System Architect, ProVision, Word, Excel) • Interfaces are being built to additional tools • User interface to populate and view the repository Automated generation of DRM XML instance • StructuredData can be populated today • Infrastructure exists to build interfaces to populate the Semistructured and Unstructured data using RDF Automated generation of other formats specified by OMB Automated generation of a user-friendly view of the DRM XML instances
- 26. For More Information… Please contact Neelam Kadam at neelam.kadam@unisys.com