1 / 26

Automated generation of DRM instances from models

Automated generation of DRM instances from models. Neelam Kadam August 30, 2005. 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

balin
Télécharger la présentation

Automated generation of DRM instances from models

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Automated generation of DRM instances from models Neelam Kadam August 30, 2005

  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. 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. 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

  5. Phase 1 Collection Phase 2 Registration Phase 3 Harmonization & Standardization Phase 4 Measure 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

  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. Solution overview • Unisys solution consists of two components • 3D Visible Enterprise – 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. 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. 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

  10. STRATEGY LAYER PROCESS LAYER APPLICATION LAYER INFRASTRUCTURE LAYER The four layers of 3D-VE • Models are organized into four distinct operational layers. • These layers are digitallyinterconnected, tying the operational architecture to the technology architecture. • Result is traceability across your entire operation.

  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. 3D-VE components Software Architect ProVision Word Excel Rose Requisite Pro In Progress XML PVX UML XMI XML Other Tools (Popkin SA, etc) Future Interface XML 3D-VE Transformer view traceability find associations MOF Repository 3D-VE Metamodel Prospector 3D-VE Impact Analysis Application

  13. 3D-VE in action at VHA

  14. EVP in action at TSA

  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 • EVP 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 user-friendly HTML view of the DRM XML instance • publish other formats (future)

  16. EVP Architecture 3D-VE MOF Repository (Technical architecture models, Business architecture models) Extract elements to populate <Structured Data> in DRM XML instance Enterprise Visualization Publisher DRM XML Instance

  17. Citizen Complete solution Data models created in commercial tools Federal Agency 1. Import models 3D-VE MOF Repository 3D-VE User Interface DRMXMLInstance 2. Extract DRM data 4. Publish user-friendlyHTML view XSLT + Enterprise Visualization Publisher Other formats Website 3. Publish DRM XML

  18. 3D-VE user interface

  19. Model to DRM – An example 1. UML Class Model created in Rational Rose

  20. Model to DRM contd… 2. Export UML model using XMI <?xml version = '1.0' encoding = 'ISO-8859-1'?> <!-- <!DOCTYPE XMI SYSTEM 'UML1311.dtd' > --> <XMI xmi.version = '1.1' xmlns:UML='href://org.omg/UML/1.3' timestamp = 'Tue Sep 13 09:37:03 2005' > <XMI.content> <!-- ==================== accountClassModel [Model] ==================== --> <UML:Model xmi.id = 'G.0' name = 'accountClassModel' visibility = 'public' isSpecification = 'false' isRoot = 'false' isLeaf = 'false' isAbstract = 'false' > <UML:Namespace.ownedElement> <!-- ==================== accountClassModel::accounts::AccountEntity [Class] ==================== --> <UML:Class xmi.id = 'S.255.0936.55.8' name = 'AccountEntity' visibility = 'public' isSpecification = 'false' isRoot = 'true' isLeaf = 'true' isAbstract = 'false' isActive = 'false' namespace = 'S.255.0936.55.7' clientDependency = 'G.83 G.84 G.85' > <UML:Classifier.feature> <!-- ==================== accountClassModel::accounts::AccountEntity.userID [Attribute] ==================== --> <UML:Attribute xmi.id = 'S.255.0936.55.9' name = 'userID' visibility = 'public' isSpecification = 'false' ownerScope = 'instance' changeability = 'changeable' targetScope = 'instance' type = 'G.71' > <UML:StructuralFeature.multiplicity> <UML:Multiplicity >

  21. Source Model (Rational Rose “Class Diagram”) uses XML Serialization of “Class Diagram” XML Schema (Metamodel) of “Class Diagram” Rose .MDL File Format Model to DRM contd… 3. Import Model into MOF Repository 3D-VE Transformer 3D-VE MOF Repository

  22. Model to DRM contd… 4. Publish model data to a DRM XML instance using the Enterprise Visualization Publisher <drm:DataDescription> <drm:Data> <drm:StructuredData> <drm:Entities> <drm:Entity drm:name="ubbi_artifactdocs" rdf:ID="48501"> <drm:Attributes> <drm:Attribute drm:name="ubbartifactdocid" drm:datatype="int" /> <drm:Attribute drm:name="ubbartifacttypeid" drm:datatype="int" /> <drm:Attribute drm:name="ubbartifactdocname" drm:datatype="string" /> <drm:Attribute drm:name="uri_path" drm:datatype="string" /> <drm:Attribute drm:name="ubbartifactdocdatetime" drm:datatype="dateTime" /> <drm:Attribute drm:name="ubbstatus" drm:datatype="int" /> <drm:Attribute drm:name="archive_dimension" drm:datatype="int" /> <drm:Attribute drm:name="ubbprojectid" drm:datatype="int" /> <drm:Attribute drm:name="ubbi_project_ubbprojectid" drm:datatype="int" /> </drm:Attributes> <drm:Relationships> <drm:Relationship drm:name="Association" drm:key="" drm:cardinality="n"> <drm:RelationshipTarget rdf:resource="48506" drm:key="" drm:cardinality="1" /> </drm:Relationship> <drm:Relationship drm:name="Association" drm:key="" drm:cardinality="n"> <drm:RelationshipTarget rdf:resource="48508" drm:key="" drm:cardinality="1" /> </drm:Relationship> </drm:Relationships> </drm:Entity>

  23. Citizen Proposed DRM architecture – agency view Created in commercial modeling tools RDF databases(Unstructured Data) EAModels DRMModels Federal agency Future 3D-VE Transformer 3D-VE Query Interface Agency MOF Repository 3D-VE Traceability Application 3D-VE Metamodel Prospector DRMXMLInstance XSLT + Enterprise Visualization Publisher AgencyWebsite

  24. Citizen Proposed DRM architecture – Inter-agency view EAModels DRMModels EAModels DRMModels Federal Agency A Federal Agency B 3D-VE Transformer 3D-VE Transformer MOF Repository A MOF Repository B Federated MOF Repository DRMXMLInstance Enterprise Visualization Publisher Website Website

  25. Adding value to the DRM process • MOF repository • Data 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 • DRM models can be linked to EA models • 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

More Related