Automated generation of DRM instances from models Neelam

  • Slides: 26
Download presentation
Automated generation of DRM instances from models Neelam Kadam August 30, 2005

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 3

Agenda About Unisys My Role and interest in the DRM process Unisys solution 3 D-Visible Enterprise Visualization Publisher Generating the DRM XML instance Proposed DRM process architecture Adding value to DRM process 2

About Unisys is a worldwide technology services and solutions company • operates in 100+

About Unisys is a worldwide technology services and solutions company • operates in 100+ countries with 37, 000+ employees $6 B Fortune 500 company with more than $1 B 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 3

EA Depth and Experience Developed and implemented successful government and commercial EAs, including §

EA Depth and Experience Developed and implemented successful government and commercial EAs, including § TSA § GSA § CMS § Du. Pont § Northwest Financial § DOD § Co. PA § DOJ § ING 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 4

My Role and interest in the DRM process Product Manager, CTO’s office, Global Public

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 13 th, 2005 • OMB’s goal - “Concrete measurable implementations” using software • DRM Management Process (Michael Daconta’s presentation) Phase 1 Collection Phase 2 Registration Phase 3 Harmonization & Standardization Unisys has developed a solution that applies in the “Collection” Phase of the DRM process 5 Phase 4 Measure

Our approach Task at hand • Federal agencies will create DRM XML documents conforming

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 - Structured. Data – Data described via E-R or class models - Unstructured. Data – Data in free-format - Semi. Structured. Data – 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 Structured. Data portion of the DRM instances Solution • Automated generation of the <Structured. Data> section of the DRM instance from these models 6

Solution overview Unisys solution consists of two components • 3 D Visible Enterprise –

Solution overview Unisys solution consists of two components • 3 D 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 3 DVE, please visit the following URLhttp: //www. unisys. com/services/enterprise__transformation/index. htm 7

3 D Visible Enterprise Imagine… • Knowing the result of your decisions before you

3 D 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. 3 D 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. 8

3 D-VE is based on models We build models: maps of your business. Models:

3 D-VE is based on models We build models: maps of your business. Models: • are a representation of the real world • are easier to understand manipulate • allow you to explore cause and effect without costly mistakes • capture intellectual assets • remain valuable over time 9

The four layers of 3 D-VE STRATEGY LAYER • Models are organized into four

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

Cross-enterprise impact analysis We need to offer additional security services to protect the homeland.

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? 11

3 D-VE components Software Architect Requisite Pro. Vision Rose Word Excel In Progress UML

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

3 D-VE in action at VHA 13

3 D-VE in action at VHA 13

EVP in action at TSA 14

EVP in action at TSA 14

Enterprise Visualization Publisher (EVP) Aggregates enterprise architecture data from multiple EA repositories Publishes the

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 3 D-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) 15

EVP Architecture 3 D-VE MOF Repository (Technical architecture models, Business architecture models) Extract elements

EVP Architecture 3 D-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 16

Complete solution Data models created in commercial tools Federal Agency Citizen 1. Import models

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

3 D-VE user interface 18

3 D-VE user interface 18

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

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

Model to DRM contd… 2. Export UML model using XMI <? xml version =

Model to DRM contd… 2. Export UML model using XMI <? xml version = '1. 0' encoding = 'ISO-8859 -1'? > <!-- <!DOCTYPE XMI SYSTEM 'UML 1311. dtd' > --> <XMI xmi. version = '1. 1' xmlns: UML='href: //org. omg/UML/1. 3' timestamp = 'Tue Sep 13 09: 37: 03 2005' > <XMI. content> <!-- ========== account. Class. Model [Model] ========== --> <UML: Model xmi. id = 'G. 0' name = 'account. Class. Model' visibility = 'public' is. Specification = 'false' is. Root = 'false' is. Leaf = 'false' is. Abstract = 'false' > <UML: Namespace. owned. Element> <!-- ========== account. Class. Model: : accounts: : Account. Entity [Class] ========== --> <UML: Class xmi. id = 'S. 255. 0936. 55. 8' name = 'Account. Entity' visibility = 'public' is. Specification = 'false' is. Root = 'true' is. Leaf = 'true' is. Abstract = 'false' is. Active = 'false' namespace = 'S. 255. 0936. 55. 7' client. Dependency = 'G. 83 G. 84 G. 85' > <UML: Classifier. feature> <!-- ========== account. Class. Model: : accounts: : Account. Entity. user. ID <UML: Attribute xmi. id = 'S. 255. 0936. 55. 9' name = 'user. ID' visibility = 'public' is. Specification = 'false' owner. Scope = 'instance' changeability = 'changeable' target. Scope = 'instance' type = 'G. 71' > <UML: Structural. Feature. multiplicity> <UML: Multiplicity > 20 [Attribute] ========== -->

Model to DRM contd… 3. Import Model into MOF Repository Source Model (Rational Rose

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

Model to DRM contd… 4. Publish model data to a DRM XML instance using

Model to DRM contd… 4. Publish model data to a DRM XML instance using the Enterprise Visualization Publisher <drm: Data. Description> <drm: Data> <drm: Structured. Data> <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="date. Time" /> <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: Relationship drm: name="Association" drm: key="" drm: cardinality="n"> <drm: Relationship. Target rdf: resource="48506" drm: key="" drm: cardinality="1" /> </drm: Relationship> <drm: Relationship drm: name="Association" drm: key="" drm: cardinality="n"> <drm: Relationship. Target rdf: resource="48508" drm: key="" drm: cardinality="1" /> </drm: Relationship> 22 </drm: Relationships> </drm: Entity>

Proposed DRM architecture – agency view Created in commercial modeling tools Federal agency EA

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

Proposed DRM architecture – Inter-agency view EA Federal Agency A Models DRM Models EA

Proposed DRM architecture – Inter-agency view EA Federal Agency A Models DRM Models EA Federal Agency B Models 3 D-VE Transformer DRM Models 3 D-VE Transformer MOF Repository A MOF Repository B Citizen Federated MOF Repository Enterprise Visualization Publisher DRM XML Instance Website 24 Website

Adding value to the DRM process MOF repository • Data models can be imported

Adding value to the DRM process MOF repository • Data models can be imported from multiple commercial tools today (Rational Suite, Popkin System Architect, Pro. Vision, 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 • Structured. Data 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 25

For More Information… Please contact Neelam Kadam at neelam. kadam@unisys. com

For More Information… Please contact Neelam Kadam at neelam. kadam@unisys. com