View
224
Download
1
Category
Tags:
Preview:
Citation preview
© 2004 Flashline Inc.
Managing Enterprise Architecture Artifacts and Assets
Enterprise Architect SummitJune, 2004
Charles Stack Grant Larsen Founder and CEO MDD StrategyFlashline, Inc. IBM Rational
© 2004 Flashline Inc.
© 2004 Flashline Inc.
Topics
EA In Perspective
Why Enterprise Architecture
Dimensions of EA
Applying Asset-based Development with EA
Reusable Asset Specification
EA Asset Management
EA Best Practices
Turning IT Cost into Business Value
© 2004 Flashline Inc.
Software is ImportantOur organizations are defined by our software
Direct Phone systems Web sites Email VRU
Indirect Internal systems Order origination Order processing Customer service Increasingly all business rules
are being embodied in our software systems
Partners Supply chain systems Flexible partnering systems
© 2004 Flashline Inc.
Software is Forever
“Not the 90’s” Long-lived platforms
Java .Net Web Services
Hardware independence = Migrate forever
Software doesn’t wear out Valuable intellectual property Software transcends developers Cost of duplicative systems
Cut maintenance by 20% “Write Less Software”
© 2004 Flashline Inc.
5 Dimensions of Software Complexity
Complexity as primary constraint on software 1000x increase across 5
dimensions Interface, stakeholders,
size, platforms, network Encapsulation best
method for managing complexity
7+2 Methods and Properties
© 2004 Flashline Inc.
Complexity Requires Architecture
Building Architecture versus Urban Planning Building = Static/waterfall City = Dynamic/iterative Building Standards Arch. Review Board Zoning – pc or mainframe Variances Health/Safety inspections Common Services - Roads,
utilities, birth certificates, etc
© 2004 Flashline Inc.
The Problem with Enterprise Systems
Some 673 different and uncoordinated financial systems made it impossible to track $2.3 trillion in financial transactions. – Donald Rumsfeld, DoD
Between various departments there are more than sixty different definitions for the term “net sales.”– Enterprise
Architect, Retail Organization Each development team had its
own DBA, and its own definition of a “store”. – Enterprise Architect, Retail Organization
© 2004 Flashline Inc.
Software as Asset
Beyond people
Beyond process
Two types of software Commodity = expense Strategic = asset
Many types of assets
Increasingly long-lived
Capture and transfer intellectual property
Employee turnover
<< requirements >><< requirements >>
<< interface >><< interface >>
<< documentation >><< documentation >>
<< Web Services >><< Web Services >>
<< CICS >><< CICS >>
<< models >><< models >>
<< application >><< application >>
<< framework >><< framework >>
<< component >>
© 2004 Flashline Inc.
Enterprise Architecture Assets
Architectural assets Process
RUP, CMM Platform Data, Application,
Component Service, Security,
Interface Goals for each asset
Benefit of establishing a standard
Glossary Definitions of key
terms
© 2004 Flashline Inc.
What is an Asset?
An Asset is a collection of Artifacts which provide a solution to a
problem for a given context with rules for usage and variability points
What are Artifacts? Workproducts from the software process
Requirements, Models,Source code, Tests, and so on…
Kinds of assets Components, patterns,
web services, frameworks, templates, …
Problem
Asset
Artifact
Artifact
Artifact
Solution
for a
con
text
with rules for usage
varia
bilit
y p o
int
© 2004 Flashline Inc.
EA Development Workflows
Project Management
Enterprise Architecture Reference Model
Asset-based Development Framework
Co
re A
sset
Dev
elo
pm
ent
&
Cer
tifi
cati
on
Wo
rkfl
ow
Policies / Procedures / Guidelines
Business Solution Architecture Workflow
Create Solution Architecture
Software Architecture Workflow
Create Application Architecture
Application Development Workflow
Create Application
Reference models
Reference models
Business process model (apply IBM patterns for e-busn)Business process solution architecture mapping High-level use case modelNon-functional / functional requirementsSecurity specification
Business process model (apply IBM patterns for e-busn)Business process solution architecture mapping High-level use case modelNon-functional / functional requirementsSecurity specification
Use case modelComponent specification modelTest cases
Use case modelComponent specification modelTest cases
Test casesComponent design modelCode modelComponent / ServiceDeployment model
Test casesComponent design modelCode modelComponent / ServiceDeployment model
Ass
et P
r ov
isio
nin
gB
uil
d /
Acq
uir
e
RAS
© 2004 Flashline Inc.
EA Reference Model: FEA
Business Reference Model (BRM)
• Lines of Business• Agencies, Customers, Partners
Service Component Reference Model (SRM)
• Service Layers, Service Types• Components, Access and Delivery Channels
Technical Reference Model (TRM)• Service Component Interfaces, Interoper…• Technologies, Recommendations
Data Reference Model (DRM)
• Business-focused data standardization • Cross-Agency Information exchanges
Performance Reference Model (PRM)
• Government-wide Performance Measures & Outcomes• Line of Business-Specific Performance Measures & Outcomes
Extend the reference
model(s) to meet your needs
© 2004 Flashline Inc.
Asset-based Development Framework
Process Workflows for identifying, producing,
managing, and consuming assets Standards
Consistent organization of assets, RAS Tooling
Tooling to support process workflows Assets
Standards-based assets
© 2004 Flashline Inc.
Process: Asset-based Development Workflows Used In EA Development Workflows
Workflows for identifying, producing, managing, and consuming assets
Software architecture development
workflow
Business Solution architecture workflow
Core asset development
workflow
Application development
workflow
Core assets for defining architectures, classified with FEA
ref models
Defining solution architectures using assets classified with FEA ref models
Defining software architectures using assets classified with FEA ref models
Using assets which are classified with FEA ref
models
© 2004 Flashline Inc.
Process: Applying The EA Development Workflows
Software architecture development workflow
Business Solution architecture workflowCore asset development
workflow
Application development workflow
Core asset repository App Dev
asset repository
Application Development
Architecture Development
RequirementsReference Model
Guidelines
Solution Architecture
Software Architecture
Application
RequirementsReference Model
Guidelines
Core assets
Core assets
© 2004 Flashline Inc.
Process: Where Does It Fit?
EA development workflows can be instantiations of the process
© 2004 Flashline Inc.
Standards: Reusable Asset Specification (RAS)
Object Management Group (OMG) Standard
Describes the structure and nature of assets
Reduces the friction on development transactions Thru standard, consistent packaging
Each asset is described using these sections Classification Solution Usage Related Assets
AssetClassification
Descriptors: Name/Value pairs
ContextDomain, Development, Test, Deployment, and so on…
UsageUsage Instructions & ActivitiesFilling Variability Points
Related AssetsAssociation, Aggregation, Dependency, Parent
Solution
ArtifactsRequirements
Models, Code, Tests
…Documents
Asset Overview
Name Desc State Ver Profile
© 2004 Flashline Inc.
Standards: Reusable Asset Specification
RAS Why What Who How
Profiles Default Component Web Services
RAS Services Registry
© 2004 Flashline Inc.
Standards: RAS XML Schema Description
A descriptive container/package for an asset's artefacts (models, source code, requirements, test cases, examples, and so on) and and documentation providing guidance on how to apply/use the asset. The artefacts of the asset are the things that are actually reused. The asset
package, as a whole provides the information to allow the asset consumer to decide if
he/she wants to use the asset.
A profile identifies the particular type of asset being described (e.g., Service, Component and so on). A profile also contains information about a profiles history of change. Information here describes the RAS profiles as developed and modified by Rational.
Provides a textual description/ summary of the asset
Contains descriptors which classify the key characteristics and behaviours of the asset that consumers are interested in (who’s using it, domains it belongs in, author, keywords, reuse-scope and son on)
Contains the location of the specific artefacts that comprise the core value of an asset - e.g., requirements documentation, various models (business object model, use-cases, analysis models, design models, class diagrams, test models), interface specifications, messages, supporting documents, location of source code, and other implementation artefacts.
Such artefacts are why consumers go looking for an asset as they define the particular problem space that the asset helps to solve.
Provides information about how to actually apply/use the asset - the artefacts in this make the asset useable to the asset consumer as it provides details with directions and steps to reuse the asset.
The quality of an asset depends to some extent on the quality of this section.Describes (if any) the relationship between
this asset to another asset
There are four kinds of relationships: aggregation, similar, dependency & parent
© 2004 Flashline Inc.
Standards: Packaging Bundled RAS Asset
ClearCase VOB orFile System or
RAS Repository - Flashline
RASAsset
Classification
Usage
Solution
Related Assets
Artifacts & RAS XML file
RAS is realized in rasset.xml
Zipped into a .ras file
stockquote_client.ras
<asset name=“Stock Quote Web Service Client"> <description>This service can be customized for specific stocks, markets, price points, time of day, and other factors.</description> <classification> <descriptor-group> <descriptor name="Author">IBM</descriptor> <descriptor name="Keyword">stock quote, web service</descriptor> <descriptor name=“SRM_ServiceType">XYZ</descriptor> </descriptor-group> </classification> <solution> <artifact name="UseCaseModel.mdx" reference="usecasemodel.mdx" type="XDE Model"/> <artifact name="Java Code Model.mdx" reference="java code model.mdx" type="XDE Model"/> <artifact name="ServiceBindingExample.java" reference="servicebindingexample.java" type="Java"/> <artifact name="sqs-interface.wsdl" reference="sqs-interface.wsdl" type="WSDL File"/> <artifact name="sqs.wsdl" reference="sqs.wsdl" type="WSDL File"/> </solution></asset>
rasset.xml contains
the asset’s meta data
Entries point to
actual files
© 2004 Flashline Inc.
Tooling: IBM Rational And Flashline
Process Guidance
searchXDE XDEMap to multiple
repositories
CC ProductionReady Repository
Asset Production Asset Management Asset Consumption
Program Management
apply & customize
check-in
modify/refine
Flashline
CC Development Repository
© 2004 Flashline Inc.
Standards: Extending RAS for EA And Your Assets
RAS is modeled in Rose Use EMF Eclipse plugin to read Rose model and
produce XMI-based XML schema
Provides a simple RAS profile extension mechanism by extending models in Rose, generating to EMF and generating the XMI XML schema
Rose UML Class Model Eclipse XMI-based XML Schema
© 2004 Flashline Inc.
Standards: Extending RAS – Sample RAS Pattern Profile
Yellow classes are extensions to the gray RAS Default profile classes.
© 2004 Flashline Inc.
Managing EA Assets
Publishing EA assets Registry Ease of access Tracking
Managing compliance Standards Projects Reviews
Measuring benefits Quality Value ROI
© 2004 Flashline Inc.
Levels of Control
Levels of Control No Standard Recommended Standard
Voluntary compliance Mandatory Standard
Degrees of compliance Recommended Implementation
Fail/succeeds on merits Mandatory Implementation
Compliance w/ variances
Iterative dynamic process
© 2004 Flashline Inc.
Compliance Models
Review Architectural Board of
Review Audit
Periodic, selective, punitive
Presumptive We’re all adults here
Variance With Business Case With or without
oversight
© 2004 Flashline Inc.
Enterprise Architecture Grid
Scope Business CaseType Name Recommended Mandatory Recommended Mandatory
SD Process RUP R eview B oard Enterprise Productivity, predictabilitySecurity LDAP A udit Business Unit securityServer O/S Linux A Enterprise cost savings
Windows 2000 A Non-Critical agilityOS/390 RB Business Unit reliability
Server Platform Intel/AMD P resumed Enterprise cost savingsIBM 390 RB Enterprise reliability
Database Oracle RB Enterprise information integrityMySQL RB Non-Critical cost savings
Application Server Websphere A Business Unit reliabilityTomcat P Enterprise cost savings
Standards ImplementationsElement
© 2004 Flashline Inc.
Treasury Enterprise Architecture Framework
© 2004 Flashline Inc.
EA Implementation
ObtainExecutive
Buy-In andSupport
EstablishManagement
Structure and Control
Define anArchitecture
Processand Approach
Develop Baseline Enterprise
ArchitectureDevelopTarget
EnterpriseArchitecture
Develop theSequencing Plan
Usethe
EnterpriseArchitecture
Maintain the EnterpriseArchitecture
Section 3.1
Section 3.2
Section 4
Section 5.2
Section 5.2
Section 5.3
Section 6
Section 7
Controland
Oversight
Controland
Oversight
Recommended