Creating Solution Creating Solution Architecture TemplatesArchitecture Templates
That align with Business Drivers and reflect real world best practices
John Weiler
CTO
www.ICHnet.org
703 768 0400
That align with Business Drivers and reflect real world best practices
John Weiler
CTO
www.ICHnet.org
703 768 0400
CIOs Feel...Overwhelmed?Ill-equipped?
Behind the market?Over-sold?
At risk?
• No body of knowledge from which to leverage lessons learned
• No evaluation techniques to assess COTS solutions interoperability or usability
• No architecture modeling tools for assessing risks or composability
• No formalisms (lexicons) to describe component feature interactions and dependencies
• No formal XML DTDs to represent architecture “blueprints”
Challenges to implementing Component Challenges to implementing Component ArchitecturesArchitectures
Solution Framework…Solution Framework…
Traceability & Interdependence
OperationalLifecycle Mgmt.
Component Model
LogicalSystem Model
ConceptualProcess Model
ContextualBusiness Model
Architectural ViewsDrivers & Objectives
Presidential Agenda Policy Support & Regulatory
Compliance
Business Requirements & Functions Organizational Considerations
Benefit / Risk Identification Partnerships & Collaboration
System Requirements Standards & Constraints
Governance Best Practices
Products & Results
Stakeholder Acceptance Business Process Improvement
Change Management TCO & Business Case
Trade-offs & Alternatives Priority Refinement
Solution Enablement
Advocacy Congruent Methodologies
A component model is only part of business solution enablement…
A component model is only part of business solution enablement…
How Component-Based How Component-Based Architectures will be used…Architectures will be used…
ComponentArchitectures
ComponentArchitectures
Identify Common Requirements &
Standards
Identify Common Requirements &
Standards
Build / Buy reusable common component
framework
Build / Buy reusable common component
framework
Support the sourcing additional
implementation options
Support the sourcing additional
implementation options
- Led by the Chief Architect (CTO)
- Facilitate communication, integration, and partnership across the E- Gov initiatives
Solution Architects Working Group
(SAWG)
Solution Architects Working Group
(SAWG)
- Guide the identification of solutions that leverage common components of the architecture
Best Practices
A Normalized Solution A Normalized Solution Framework;Framework;
Provide a formal methodology, collaboration tools and information for transformation of business drivers into proven and interoperable solution sets
Propagate a knowledge base of EA artifacts
Provide means of sharing best practices and lessons learned
Increase the integrity, timeliness, and contextual relevance of architecture communications between buyers and suppliers
Supporting Evidence and ResearchSupporting Evidence and Research
ECCWG (DEPSECDEF) established Software Quality and ECCWG (DEPSECDEF) established Software Quality and Interoperability Working Group; finding on www.ICHnet.orgInteroperability Working Group; finding on www.ICHnet.org
AF Scientific Advisory Board Report on Integrating AF Scientific Advisory Board Report on Integrating Commercial items into mission systems, April 2000.Commercial items into mission systems, April 2000.
December 99 report published in Information Week: “Why IT December 99 report published in Information Week: “Why IT Fails”Fails”
Results of DARPA Distributed Component-based Architecture Results of DARPA Distributed Component-based Architecture Modeling ProjectModeling Project
Proceeding from Secure E-Business Executive SummitProceeding from Secure E-Business Executive Summit
Domain Working Groups within OMB, IEEE, and ICH.Domain Working Groups within OMB, IEEE, and ICH.
Solution Framework Objectives
•Reduce uncertainty and risk of mapping solutions to common business requirements
•Improve visibility of key technical features, interfaces, functions
•Provide consistent approach for evolving solution paradigms for COTS product usage
•Generate Industry approval and consensus
•Facilitate compliance with Clinger-Cohen, FAROMB Circulars A119 & A130, S.803, FEAPMO
•Provide “clearinghouse” of reusable artifacts and supporting research
Solution Architecture Framework
Methodology Origins and Inputs
•OSI Reference Model for Open Distributed Processing (views)
•OMG Model Driven Architectures (MDA/UML)•IEEE 1471 •DARPA DCAM
Align Validate IntegrateAlign Validate Integrate
IT Centric EAEffort andFramework
EnterpriseInclusive EAEffort andFramework withinternalAlignment,Metrics,Componentization,Normalization,and Objectivity
“Exerprise”Inclusive EAEffort andFramework withComprehensiveAlignment,Metrics,Componentization,Normalization,and Objectivity
Cost Savings IncrementalImprovement
IncrementalImprovement
IncrementalImprovement
OperationalService Quality
Supportive IncrementalImprovement
IncrementalImprovement
OperationalAlignment
Supportive IncrementalImprovement
IncrementalImprovement
BusinessAlignment
Undetermined IncrementalImprovement
SubstantialImprovement
Validity Undetermined InternalValidity
IncrementalImprovement
Adaptability Undetermined InternalAdaptability
IncrementalImprovement
• Community Based• Comprehensive: “Exerprise”•Alignment Driven•Metric Justified•Adaptive•Normative•Non Prescriptive
Critical Success Factors
Layered Approach Enables separation of concernsLayered Approach Enables separation of concerns
BRMTechnicalSolution & Metrics
Application Layer 1
Common InfrastructureLayer M
BRMServiceElements & Metrics(SRM)
Appl Service Components Layer 1
InfrastructureService ComponentsLayer N
BRMBusinessDrivers & Metrics
Core Business Mission Objectives
BusinessProcesses &Infrastructure
Solu
tion
Rep
osi
tory
C
on
trib
uti
on
to F
ulfi
llmen
t
Fun
ctio
nal Tra
ceab
ility
Associated MetricsReference Models
Performance Metrics
Effectiveness/Efficiency
Interoperability/Security
Enterprise Architecture Drivers/Inhibiters
Missions, Goals and Objectives
Revenue Enhancement/Cost Reduction
Industry Shifts,Obsolescence,Recent Investments
Organizational ChangeConsiderations
Budget Legislative DirectivesMandates,Regulations
Enterprise Architecture
BusinessProcess Layer:
TechnologyEnablement Layer:(Application)
Domain discipline
Architectures Component Security Networking Platform Infrast. Mgmt
Data
Business Driver – Process Mapping
Functional Hierarchies,Location Mappings
Process Maps
ProcessDescriptions,PerformanceMetrics
Security and other Policies
Technology Enabler – Process Mapping
Solution Set: 1. Function/Feature,2. Performance Characteristic3. Performance Measure
BusinessProcessPatterns
Solution Set Patterns
Application Standards & Policies
Information
Layer: Data Dictionary
Key Information Classes
Data Standards & Policies
Data Movement Req.
DataPatterns
InfrastructureServiceLayer:
Solution Set & Information - Infrastructure Mapping
Infrastructure Enabler Description
Topology Mappings, High Level Protocol Stacks
IT Mgmt Architecture, Standards & Policies
Infrastructure Patterns
Solution Set – Information & Infrastructure Mapping
ICH EA Alignment Framework
End User Organizations
ProductVendors Integrators
Composability
Business Fit
Open
ness
Rele
van
cy Dom
ain
Know
ledge
Solution
Experience
Many Stake HolderMany Stake HolderSolution Framework must support many viewsSolution Framework must support many views
IndustryGroups
BusinessDrivers
COTSSpecifications
Best Practices & Past Performance
IT Standards
Common Criteria�Two Phase Commit�Object Storage�Relational Constructs�Row Level Locking�Referential Integrity�ODBC Interface�SQL Interface�JDBC Interface�IDL Interface
Fulfillm
ent
DB Standard X, v2Two Phase Commit�Relational Constructs�Row Level Locking�Referential Integrity�ODBC Interface�SQL Interface�IDL Interface
LexiconDB Product Y Two Phase Commit�Relational Constructs�Row Level Locking�Referential Integrity�ODBC Interface�SQL Interface�JDBC Interface�Triggers�OLE DB Interface�Multiphase converter
Solution ProfileScale, IndustrySolution SuiteProduct A Product B v6.1Product C v2Platform S
Canonicalizing the ViewsCanonicalizing the Views
Infrastructure
Bus. Drivers
External Influences
Solutions Map�Distributed Org�Mobile Force�non-fixed locations�secure communications�concurrent updates�complex data types�unstructured data�central data collection�Open Systems
ICH
Confidence
Level
Resources (cost & time)
Trade Studies
Testing Alone
Traditional approach
ICH advantage
High
Low
RiskDelta
Cost/timeDelta
Why a standardized viewWhy a standardized viewReducing the time, cost, and risk of Reducing the time, cost, and risk of validating proposed solutionsvalidating proposed solutions
“The ICH repository data and analysis methodologies was very helpful in supporting a quick turn around for [Information Assurance] section of COTS security products. Highly detailed ICH technology domain and product evaluation data comprised over 60% of this urgently needed [architecture] report”. Mike Luby, Program Manager, Logicon/PRC
Collaborative VettingCollaborative Vetting
Strength of Evidence Decision Strength of Evidence Decision BasisBasis
Evidence Factors
Str
en
gth
of
Evid
en
ce
85%
50%
25%
Bi-directional
Vendor Claim
FunctionalTesting
Implementation
Successes
IntegrationTesting
Acceptable outcome of the model?
• Confirm acceptability of the solutions model
• Or, if necessary, repropose technical solution and reassess
Purpose of a Shared Purpose of a Shared RepositoryRepository• To share interoperability knowledgeTo share interoperability knowledge
– FeaturesFeatures
– FunctionsFunctions
– InterfacesInterfaces
– StandardsStandards
– Experiential, 3rd-party, testing, marketing, benchmarks, Experiential, 3rd-party, testing, marketing, benchmarks, etc.etc.
• To support the ICH missionTo support the ICH mission
• To collaboratively support ICH methodology To collaboratively support ICH methodology for ICH membersfor ICH members
Implementation Implementation ObjectivesObjectives
• To facilitate the dynamic storage, To facilitate the dynamic storage, management, access and maintenance management, access and maintenance of ICH repository knowledgeof ICH repository knowledge
• To keep the ICH repository open and To keep the ICH repository open and extensibleextensible
• To provide for continual improvement To provide for continual improvement without constant interruptionwithout constant interruption
Component Technologies Component Technologies AddressedAddressed
• Internet and Network Internet and Network TechnologiesTechnologies
• Information Assurance Information Assurance Technologies and Secure Technologies and Secure Information Infrastructure Information Infrastructure ComponentsComponents
• PKI/X509, PGP, VPN, Firewalls, PKI/X509, PGP, VPN, Firewalls, Digital Signature, Intrusion Digital Signature, Intrusion Detection, Encryption…... Detection, Encryption…...
• DBMSs, XML/XMI, UDDI, DBMSs, XML/XMI, UDDI, Portals, Data Warehousing….Portals, Data Warehousing….
• Development Tools, Development Tools, Application Servers, B2B, Application Servers, B2B, B2C, ...B2C, ...
• Web Servers, COM+, Web Servers, COM+, CORBA, EJB, Messaging, CORBA, EJB, Messaging, JINI, ….JINI, ….
• Enterprise Directory: Enterprise Directory: x5000, LDAP, Active x5000, LDAP, Active Directory, NDS…..Directory, NDS…..
• Switches, Routers, Switches, Routers, Wireless, VOIP…..Wireless, VOIP…..
Current Implementation Current Implementation
• MySQL-based (for now)MySQL-based (for now)
• PHP and HTML accessed (for now)PHP and HTML accessed (for now)
• DreamWeaver DevelopedDreamWeaver Developed
• Next PhasesNext Phases
Knowledge Base Data Model
OperatingEnvironment
ProductRelatedService
StandardProfile
ExperienceReport
Organization
Use Case
Interface
Product
Component
usesproduces
hascomposes
may compose
generates
interops with
specifies
validates
executes in
interops with
references
may implement
developsadopts
implements
has
Repository Architecture: Repository Architecture: Technology AreasTechnology Areas
Field Type Defaultid tinyint(4)name varchar(50)description longtextupdated date 0000-00-00originalAnalysis date 0000-00-00currentResearcher tinyint(4) 0originalResearcher tinyint(4) 0POC tinyint(4) 0
statusenum('REGULAR','PROPOSED','DEPRICATED','SPECIAL')
PROPOSED
vetDate date 0000-00-00previousResearchers longtext
Repository Architecture: Repository Architecture: CriteriaCriteria
Field Type Defaultid tinyint(4)name varchar(50)description mediumtext
defaultWeightingenum('ESSENTIAL','IMPORTANT','DESIRABLE','UNDESIRABLE','NO_WEIGHTING')
NO_WEIGHTING
statusenum('REGULAR','PROPOSED','DEPRICATED','SPECIAL')
REGULAR
vetDate date 0000-00-00POC tinyint(4) 0
Repository Architecture: Repository Architecture: ProductsProducts
Field Type Defaultid tinyint(4)primaryTechId tinyint(4) 0secondaryTechId tinyint(4)name varchar(50)version varchar(50)description longtextvendor tinyint(4)history longtextproductPOC tinyint(4) 0techPOC tinyint(4) 0researchInfo longtextvalidationInfo longtextstengths longtextweaknesses longtextinteroperability longtextupdated dateoriginalAnalysis datecurrentResearcher tinyint(4) 0originalResearcher tinyint(4) 0previousResearchers longtext
Repository Architecture: Repository Architecture: DocumentsDocuments
Field Type Defaultid tinyint(4)title varchar(255)subTitle varchar(255)techArea1 tinyint(4) 0techArea2 tinyint(4) 0authorId tinyint(4) 0authorOrgId tinyint(4) 0date date 2001-01-01ownerId tinyint(4) 0ownerOrgId tinyint(4) 0format varchar(32)summary longtext
availabilityenum('NOT_AVAIL','PUBLIC','ICH_PUBLIC','MEMBERS_ONLY','CONTACT_AUTHOR','CONTACT_OWNER','SPECIAL')
MEMBERS_ONLY
docURL varchar(255)topic varchar(50)
localCacheenum('ICH_PUBLIC','ICH_MEMBERS','ICH_PRIVATE','NO_LOCAL_CACHE')
ICH_MEMBERS
Repository Architecture: Repository Architecture: EvidenceEvidence
Field Type Defaultid tinyint(4) 0
typeenum('VENDOR_CLAIM','VENDOR_RESEARCH','INDEPENDENT_RESEARCH',',INTEGRATION_RESULT','OTHER')
VENDOR_CLAIM
validationWeight tinyint(4)validationWeightSetBy
tinyint(4)
validationDate datevalidationNotes longtext
Repository Architecture: Repository Architecture: OrgsOrgs
Field Type Defaultid tinyint(4)name varchar(80)acronym varchar(12)
memberStatusset('MEMBER','CLIENT_PARTNER','RESEARCH_AFFILIATE','FOUNDER','SPECIAL')
MEMBER
ICHRelationship set('FOUNDER','MEMBER','CLIENT_PARTNER','RESEARCHER_TESTER') MEMBERmembershipLevel tinyint(4) 0membershipDate date 0000-00-00ICH_POC tinyint(4) 0ICH_URL varchar(128)URL varchar(127) http://address varchar(127)city varchar(35)state char(2)zip varchar(10)country varchar(35)phone varchar(15)fax varchar(15)
groupsset('CONSORTIA','EDUCATORS','GOVERNMENT_USERS','INDUSTRY_USERS','INTEGRATORS','REGULATORS','RESEARCHERS','STANDARDS_ORGANIZATIONS','TESTING_LABS','VENDORS')
logo varchar(128) http://memberSince date 0000-00-00hide enum('TRUE','FALSE') FALSE
Repository Architecture: HRRepository Architecture: HR
Field Type Defaultid tinyint(4)salut varchar(10)firstName varchar(35)midName varchar(35)lastName varchar(35)suffix varchar(10)address varchar(127)city varchar(35)state char(2)zip varchar(10)country varchar(35) USAemail varchar(30)phone varchar(20)fax varchar(20)cellphone varchar(20)hide enum('TRUE','FALSE') FALSE
Implemented Repository Implemented Repository FeaturesFeatures
• Manage, index, search, share documents, Manage, index, search, share documents, reports, other electronic information reports, other electronic information (“Card Catalog-(“Card Catalog-able” information)able” information)
• Manage ICH “Common Criteria”, Manage ICH “Common Criteria”, – Technology AreasTechnology Areas
– CriteriaCriteria
– Default Weightings (per Criterion and by Technology Area)Default Weightings (per Criterion and by Technology Area)
• Manage Organizations and Points of ContactManage Organizations and Points of Contact
Example: OnLine Example: OnLine DocumentsDocuments
Example: OnLine Example: OnLine DocumentsDocuments
Example 2: Example 2: Technology Area Technology Area Criteria SelectionCriteria Selection
Example 2: Example 2: Technology Area Technology Area Criteria ManagementCriteria Management
Example 2: Example 2: Technology Area Technology Area ViewingViewing
Live DemonstrationLive Demonstration
http://members.ICHnet.org(Click Link to Open Web Page)
Product Information Entry Product Information Entry WorkflowWorkflow
ProductData Sheet
CompositeFeatures
Add NewFeatures
NewProduct/StandardProfiles
Technology Class Profile
DocumentedFeatures
SelectExistingFeatures Establish
XMLURL Links
CreateUML
Template
ConformanceTemplates
Work Flow Manager.
StandardsDirectory
ProductDirectory
StandardSpecification
ValidateNew Features
COTSValidation
Functional Validation ProcessFunctional Validation Process
VendorStatements
Work Flow Manager.
Stds Conform.
Statement
Interop.Statement
FunctionalStatement
Conformance Testing
FunctionalTesting
InteroperabilityTesting
TestingResults
Attach toProductProfile
VendorConcurs
60 DaysPass?
Yes
No
VendorCorrection
No
Yes
UpdateProduct
Directory
Sendto 3rdParties
3rd PartyProduct
StatementSend
Message to Subscribers
InteropValidation
Interoperability Validation Interoperability Validation ProcessProcessIndustry Indirectly Validates Vendor Industry Indirectly Validates Vendor ClaimsClaims
SelectProductsTested
Show CurrentProduct
Connections &Functions
Confirm Connections
ExistingLinks
?
Create newConnection &Component
Vendor Interop.Submissions
Confirm Product
Functions
DetermineLevel of Effort
& Interop.
CreateProduct
LISIAttrib.
UpdateIC