10. 10
System Architect/Rhapsody
Interface• Optimizes workflow from high-level SoS
missions, strategies and operations to detailed
embedded systems and real-time software
development
• Users can easily transfer model information between
the two products and more closely align
development of embedded and real-time systems
with defense missions and strategies
• Generic approach supports different end user
workflows from System Architect (MODAF) to
Rhapsody (SysML or DoDAF) and data
synchronization between solutions
15. Modeling product portfolio and positioning
• Rational System Architect
– For EA to support planning, change and transformation of
the business/organization and its supporting technology
– For customers wishing to use IDEF0 for the basis of AF
modeling
– For customer wishing to model business architecture
– Key customers: Government agencies, System
Integrators, Financial Services, large commercial cos.
Rational Rhapsody
Architecture definition down to technical
systems
Single tool for real time and embedded
software
Desire to use UML and SysML as basis for AF
modeling
Key customers: Tier 1 supplier and below
EnterpriseArchitectureSolutionArchitecture
Embedded systems development
Plan
Rational Software Architect
Architecture definition down to systems
Single tool for net-centric software,
oversight programs/portfolios, & IT apps
Desire to use UML as basis for AF modeling
and SysML (via E+ plugin)
Key customers: PEO, Program Office/FSI Tier
1 supplier and below
Business arch. to technical arch. integration
(PEOs, Program Offices)
Information systems development
Build
23. 23
Report and adjust
Understandstrategy
andmotivation
Analyze and prioritize
Managetransformation
Targets to meet
Are we on track?
Harnessing Change - Separate Enterprise Planning concerns from
Solution Delivery concerns
(different time scales => synchronous coordination, NOT round trip engineering)
24. 24
Designs&
Constructs
Models
Building Blocks
Guidance and reuse
Enterprise
Planning
planning and organizing
Enterprise Blueprints
Architecture Building
Blocks, Principles,
Reference Models and
PatternsSolution
Delivery
building and
implementing
Solution
Models and Constructs
Constructions
of things
Collections
of things
Dynamicinteraction
Dynamic, viable interaction between planning and delivery
25. 25
Designs&
Constructs
Models
Building Blocks
Guidance and reuse
Enterprise
Planning
planning and organizing
Enterprise Blueprints
Solution
Delivery
building and
implementing
Solution
Models and Constructs
Constructions
of things
Collections
of things
Dynamicinteraction
Two kinds of building blocks
Transition
Targets
Solution
Accelerators
26. 26
2.1 2.1.1 2.1.2 2.1.3
latest
repository
target version
FEEDBACK &
UPDATE
(no common ancestor)
feedback compliance
& possibly improved target
possibly updated
target version
1.4 1.5 1.6
set
target
Solution model changes
(may or may not originate in the target set)
Planning model changes from continuous evolution
(may or may not originate in feedback from solution model changes)
1.7
Delivery
(continuous)
Planning
(continuous)
cascade
updated target
by inference
Building Codes
City Plan
Skyscraper
Target & Feedback – Architecture Governance Pattern
28. 28
Planned improvement
Process portfolio optimization
Multiple projects
#1: Systems insight #2: EA governance #3: Accelerate design of new systems
Transition
Planning
Architecture
Governance
Enterprise
Architecture
= “the city plan”
Portfolio
baseline
Link
Link
Read &
clone
Three key scenarios
34. 34
Planned improvement
Process portfolio optimization
Multiple projects
#1: Systems insight #2: EA governance #3: Accelerate design of new systems
Transition
Planning
Architecture
Governance
Enterprise
Architecture
= “the city plan”
Portfolio
baseline
Link
Link
Read &
clone
Three key scenarios
41. 41
Planned improvement
Process portfolio optimization
Multiple projects
#1: Systems insight #2: EA governance #3: Accelerate design of new systems
Transition
Planning
Architecture
Governance
Enterprise
Architecture
= “the city plan”
Portfolio
baseline
Link
Link
Read &
clone
Three key scenarios
45. 45
Planned improvement
Process portfolio optimization
Multiple projects
#1: Systems insight #2: EA governance #3: Accelerate design of new systems
Transition
Planning
Architecture
Governance
Enterprise
Architecture
= “the city plan”
Portfolio
baseline
Link
Link
Read &
clone
Three key scenarios
66. 66
Architecture enables organisations to “do the right things
right”
Deployment
& DeliveryProject
Scoping
Build Cycle DeploymentExternal Design InternalDesign
Project
Scoping
Build Cycle DeploymentExternal Design InternalDesign
Project
Scoping
Build Cycle DeploymentExternal Design InternalDesign
Strategic
Intent
Project Prioritisation
& planning
"These are the
projects we
should do”
"These are the
projects we
will do”
“Here you
are!”
The Enterprise’s
Architecture
Smart Strategy
Smart Planning Smart
Design, Develop
ment, Delivery
“Do the
right
things”
“Do things
right”
SOA principles &
platform
67. 67
Architecture… more detail…
“Are our target
architectures still right?”
“Are we still
moving the right
direction?”
Strategic Delivery
Project
Scoping
Build Cycle DeploymentExternal Design InternalDesign
Strategic
Intent
Enterprise IT
Architecture
Functional
Operational
Enterprise Business
Architecture
Project prioritisation
& planning
"These are the
projects we
should do”
Enterprise
Transition
Initiatives
“These are our
roadmaps”
UPSTREAM EA: Identifying viable
projects (including those that will
use BPM) to help realise the
enterprise architecture requires a
good set of “models”, capable of
portraying the overall “as is” and
“to be” architectural landscape
DOWNSTREAM EA: Ensuring projects
can exploit the architecture’s “standard
components” or building blocks, including
those that are doing things the BPM way
requires each part to be described
and published in an easy-to-use, easy-
to-find “catalogue like” format
"These are the
projects we
will do”
“Here you
are!”
Business & IT solution design
Project
Scoping
Build Cycle DeploymentExternal Design InternalDesign
Business & IT solution design
Project
Scoping
Build Cycle DeploymentExternal Design InternalDesign
Business & IT solution design
"This is the way these
systems should be designed”
Architecture
Governance
"Are we designing these
systems the way we said
we want them done?”
70. 70
Architecture… with frequency of change…
Model to Plan
Model to Build
Low Frequency Changes
Merge (from various sources)
Reviewed manually, often
with extended team
High Frequency Changes
Automated Merge
73. 73
EA Workspace Patterns
EA 1.3
EA
V 1.2
Development, Deployment
Program Timelines
Business Process
Set Constrains & Define Guidelines
EA 1.3
EA
V 1.3
Collect and Incorporate Feedback
Outsourcing InitiativeCompliance Program
EA 1.3
EA
V 2.0
Acquisition
E.
Opportunities &
Solutions
G.
Implementation
Governance
F.
Migration
Planning
H.
Architecture
Change
Management
E.
Opportunities &
Solutions
E.
Opportunities &
Solutions
G.
Implementation
Governance
74. 74
Workspace Y
Workspace XTo Be – Alternative X
“AS IS” vs. “TO BE” Scenario: Zoom in
EA 1.3 EA 1.3
EA
V 1.4
Outsourcing Initiative
As Is
To Be – Alternative Y
EA 1.3
EA
V 1.3
78. Jazz: The Simple Premise
• Standards define references (URLs), protocols, and how to represent
standard information types such as pictures and movies
• Extensible via plug-ins such as PDF viewers
Observation
The Internet and the web works quite well despite many types of
information and a loose, distributed structure
What if tool vendors defined standard ways to reference objects,
standard protocols for accessing those objects, and standard
ways to represent those objects in an extensible manner?
81. Models and Data: Traditional versus Jazz
Traditional
• Links within model frequently tool-specific
• Format on disk just a serialized form of in-
memory format
• References into models managed by
other tools determined by those other
tools
Jazz
• Links within model are URLs
• Format on disk is carefully chosen and
well-understood XML resource
representation
• References into models managed by
other tools are also URLs
– Uniform referencing simplifies collaboration
Model or Tool Data
82. Application Model
References in Jazz
Requirements Test Cases
Projects Operations View Business Motivation
All references are URLs, both intra- and inter-model. Traditional import and
export of data for tool point-to-point integrations no longer necessary, greatly
simplifying traceability and impact analysis and copied/duplicate data.
102. Rational Publishing Engine (RPE)
• Build, share and reuse
templates
• Use out-of-the-box templates
and integrated preview
capability for quick ROI
• Leverage templates for
industry standards
• Create and modify templates
using intuitive editing
environment
– Drag and drop capability
– Powerful scripting language
support (Javascript) with
expression editor for ease of
use
Customizable
document
generation
109. Models and Requirements
• Models and Requirements
complement each other
• Diagrams help clarify
understanding of requirements
• Modeling can help identify gaps
and misunderstandings
• A formalized but flexible
graphical notation enables
expressive, ‗people friendly‘
diagrams
• Easily visualize, model and
validate requirements to avoid
costly rework
114. Standards-based modeling
―Rhapsody is the leading UML 2.1 compliant solution for embedded systems.
Reducing OEM development Costs and Enabling Embedded Design
Efficiencies Using the Unified Modeling Language (UML 2.1)‖
Source: ―Reducing OEM Development Costs and Enabling Embedded Design Efficiencies Using the Unified
Modeling Language (UML 2.0)‖, Embedded Market Forecasters
• UML
– Industry standard notation for
representing designs
• SysML
– Extends UML to address needs
of the systems engineer
• Visualize:
– Requirements
– Structure
– Behavior
– Interaction
– Constraints
• Compliance: DoDAF,
MODAF, AUTOSAR, etc.
115. 115 Introduction to SysML 1.0
Shows how System stakeholders interact with the System
Use Cases group requirements
Example: Use Case Diagram
116. Use Case Diagram – for managers
116
Shows how System stakeholders interact with the System
Use Cases group requirements
Introduction to SysML 1.0
121. 121
Balancing trade-offs between often
conflicting stakeholder
requirements
Data held in models can drive
external simulations and help with
trade studies
Early model execution and
simulation helps to reduce costs
Speed
Model-driven Systems Development enables
concurrent analysis of multiple related requirements
Example: Vehicle speed vs. fuel-economy
If the requirement for fuel economy increases, the top
speed of the vehicle will decrease
Fuel economy
128. Jazz: The Simple Premise
• Standards define references (URLs), protocols, and how to represent
standard information types such as pictures and movies
• Extensible via plug-ins such as PDF viewers
Observation
The Internet and the web works quite well despite many types of
information and a loose, distributed structure
What if tool vendors defined standard ways to reference objects,
standard protocols for accessing those objects, and standard
ways to represent those objects in an extensible manner?
131. Models and Data: Traditional versus Jazz
Traditional
• Links within model frequently tool-specific
• Format on disk just a serialized form of in-
memory format
• References into models managed by
other tools determined by those other
tools
Jazz
• Links within model are URLs
• Format on disk is carefully chosen and
well-understood XML resource
representation
• References into models managed by
other tools are also URLs
– Uniform referencing simplifies collaboration
Model or Tool Data
132. Application Model
References in Jazz
Requirements Test Cases
Projects Operations View Business Motivation
All references are URLs, both intra- and inter-model. Traditional import and
export of data for tool point-to-point integrations no longer necessary, greatly
simplifying traceability and impact analysis and copied/duplicate data.
134. What is Jazz?
www.jazz.net
Innovation
A major investment by IBM to create a
scalable, extensible team collaboration
platform
Community
Jazz.net – an online venue for open
commercial development of the
Jazz platform and Jazz-based
products.
Vision
Our vision for the future of software delivery
-- supporting diverse types of teams and a
workforce that is increasingly
organizationally and globally distributed,
fluid and dynamic.
Evolution
Many Rational products will evolve to support
the Jazz technology platform over time,
bringing a host of next-generation
capabilities to the Rational Software
Delivery Platform.
Jazz is a vision for integrating work across the software lifecycle, and a
technology platform designed to enable that vision
135. Jazz: The Simple Premise
• Standards define references (URLs), protocols, and how to represent
standard information types such as pictures and movies
• Extensible via plug-ins such as PDF viewers
Observation
The Internet and the web works quite well despite many types of
information and a loose, distributed structure
What if tool vendors defined standard ways to reference objects,
standard protocols for accessing those objects, and standard
ways to represent those objects in an extensible manner?
141. Ideas/Initiatives
References in Jazz
Requirements Architecture
Projects Operations View Business Motivation
All references are URLs, both intra- and inter-model. Traditional import and
export of data for tool point-to-point integrations no longer necessary, greatly
simplifying traceability and impact analysis and copied/duplicate data.
142. Tools collaboration based on
middleware services
Built on an extensible platform common repository
Tool B Tool C Tool D Tool E Tool F
Team Collaboration Services
Tool ATool A
143. Strategic Planning Platform
Enterprise Architecture
Tools
System Architect
CMDB
(Tivoli or not)
Customer Data
(DB2 or not)
Other Corporate
Data
Corso Elements
Federation
BPM Solution
Tools
WBM/WID+
Information
Management
Solution Tools
RDA+
Appl. Design &
Construction
Solution Tools
Design Manager
Technology &
Deployment
Solution Tools
Requirements
Tools
Req Composer
RequisitePro
DOORS
RAM on Jazz
Asset Governance
Jazz JRS
Repository
Replication Jazz JRS
Repository
EA Assets Solution Assets
Federating Jazz Collaboration Platform
Business
Intelligence
Cognos Family
CUBI
Read EA documents,
consume architecture building
blocks, create solution assets
Principles,
guidelines, views
of infrastructure,
processes,
services, data,
applications
IBM Tools Centric View of SPP
Portfolio Management
Tools
Focal Point
Initiatives, Marke
t
Data, Plans, Sch
edules, Priorities
Socialization
Corso Social
Yammer
Twitter
LinkedIn
Others
Change and
Configuration
Mgt
Team Concert
144. System Architect and Jazz: Interim Steps
(an example)
• For some heritage tools, Jazz is
a journey…
• SA must translate assets from
its repository into resource
representations
• SA presents a REST API for
other tools to access
– Other tool should be able to
dereference a URL that resolves
to an SA repository
– The dereference is received by
SA, which returns a resource
representation for the referenced
item
SA Repository
System
Architect
Assets &
Metadata in
SA Form
Produce &
Consume
Resource
Representations
Tool on Jazz
Jazz Repository
Assets &
Metadata in
Jazz Form
Produce &
Consume
RESTful Web
Services
RESTful
Web
Services
API
As you can see, Corso does look at the IBM suite of Rational products from a holistic view. As our platform continues to mature, we will continue to expand additional enhanced integration between the solutions. If you have a specific request, we are happy to have those discussions at any time.
If I want to create links between data in diverse repositories and report across those links then the data would have to be imported into whichever repository the analysis had to be done within. These importers would have to be written specifically for the purpose. If an object in one repository was to be linked to another such that the target object could be opened in the target tool then again a specific point to point integration would have to be created.