model driven software development experience and · pdf file04.03.2012 · vision...
Post on 06-Mar-2018
223 Views
Preview:
TRANSCRIPT
Slide title
In CAPITALS
50 pt
Slide subtitle
32 pt
Model driven Software
development experience and
vision from EricssonAmsterdam 2009 June 4
Dr. ir. Ard-Jan MoerdijkManager Development
BU Multi-media R&D site Rijen
Ericsson Telecommunications B.V.
e-mail: Ard.Jan.Moerdijk@ericsson.com
Tel : +31 161 242777
Mob: +31 6 15093971
Top right
corner for
field
customer or
partner logotypes.
See Best practice
for example.
Slide title
40 pt
Slide subtitle
24 pt
Text
24 pt
5
20 pt
© Ericsson AB 2009 Ericsson BMUM Modeling experience 2009-05-252
Executive summary
Working in a demanding business on complex
systems in a ‘flat world’ where activities are
done in different geographical locations
requires an approach that supports melting
together Enterprise Architecture with Business
modeling and lower layers of systems &
realization models.
Top right
corner for
field
customer or
partner logotypes.
See Best practice
for example.
Slide title
40 pt
Slide subtitle
24 pt
Text
24 pt
5
20 pt
© Ericsson AB 2009 Ericsson BMUM Modeling experience 2009-05-253
Table of Contents
Background
Why modeling is essential for us
Our approach
Lessons learned
Next steps
Conclusions
Top right
corner for
field
customer or
partner logotypes.
See Best practice
for example.
Slide title
40 pt
Slide subtitle
24 pt
Text
24 pt
5
20 pt
© Ericsson AB 2009 Ericsson BMUM Modeling experience 2009-05-254
Telecom and Ericsson in 2009
4 billion subscriptions
Mobile broadband breakthrough
(HSPA PC modules)
Accelerated focus on all-IP
Financial crisis in focus
But long-term positive
fundamentals remain
Leading vendor of Mobile
networks
A unique position: 130 years –
140 countries
Revenues 2008 22.8 BEuro (+11%)
~80,000 employees
Top right
corner for
field
customer or
partner logotypes.
See Best practice
for example.
Slide title
40 pt
Slide subtitle
24 pt
Text
24 pt
5
20 pt
© Ericsson AB 2009 Ericsson BMUM Modeling experience 2009-05-255
Ericsson in the Netherlands
Services
Networks
Multi-
media
Established in 1920, site: Rijen
Total Ericsson employees in NL:
1200
Activities:
– Marketing & Sales
– Global Services
– R&D
R&D part of BU Multi-media.
Just reorganised ~270 -> 170 heads
but with new setup where activities
will be outsourced by us to low cost
sites and partners all over the world
This presentation is about the
international modeling program on
BU level
Top right
corner for
field
customer or
partner logotypes.
See Best practice
for example.
Slide title
40 pt
Slide subtitle
24 pt
Text
24 pt
5
20 pt
© Ericsson AB 2009 Ericsson BMUM Modeling experience 2009-05-256
Why Modeling is essential for us
The telecom network is a complex system of
systems, – where more flexible integration with business
support systems is a strong driver
Development is done on various locations
across the globe
Production needs to be faster and faster and
at predictable minimum costs
do the right things and do them extremely
efficiently Agile, architecture & reuse and modeling as our
tools
Top right
corner for
field
customer or
partner logotypes.
See Best practice
for example.
Slide title
40 pt
Slide subtitle
24 pt
Text
24 pt
5
20 pt
© Ericsson AB 2009 Ericsson BMUM Modeling experience 2009-05-257
Our approach: Seamless modeling
Bu
sin
ess m
od
el
Serv
ice
mo
de
lD
esig
n m
od
el
[yes]
[yes]
[no]
Need analysis?
Analyze Opportunity
Interesting for Product backlog?
New opportunity
Put on Product Backlog (with priority)
End
Package_1
Package_2Package_3
Interface_1
Interface_2 Interface_3
0..10..*
Class_1 Class_2
Class_3 Class_4
Use cases, business process diagrams
Business services
Notation: BPMN +UML?
Service Architecture (which own, which 3PP)
Service interfaces / contracts
Service Property model
System Architecture (Main system
components, their roles and their relations,
system architecture choices and
principles, system properties)
Per system: Software architecture (Main
software components, their roles and their
relations, software architecture choices
and principles. (using package diagrams,
class diagrams, sequence diagrams, etc))
System characteristics/properties model
CIM
PIM
PS
M
Syste
m
mo
de
l
. .
. .
. .
. .
Requirements (changes) * Verifications/test/simulations *Rules/aspects
/standards*
Ericsson C
om
mon I
nfo
rmation M
odel
Objectives:– Minimize waste by better understand what the customer
needs and what will make money
– Move from document driven development to information
driven development
– Achieve shorter lead-times and increased Business
flexibility by re-use of assets
How:– Melting the EA together with Business modeling and lower
layers of systems & realization models
– Tool cooperation on this with Sybase for 2 years now and
cooperation with e.g. Frontwalker on Business modeling
methodology
Top right
corner for
field
customer or
partner logotypes.
See Best practice
for example.
Slide title
40 pt
Slide subtitle
24 pt
Text
24 pt
5
20 pt
© Ericsson AB 2009 Ericsson BMUM Modeling experience 2009-05-258
Business modeling in our approach
Focus on supply and competition:
Exploit existing demand
Compete in existing market
space
Beat the competition
Make the value-cost trade-off
Low strategic sustainability
Red Ocean Blue Ocean
Focus on demand and value
innovation
Create and capture new demand
Create uncontested market space
Make the competition irrelevant
Break the value-cost trade-off
High strategic sustainability
Top right
corner for
field
customer or
partner logotypes.
See Best practice
for example.
Slide title
40 pt
Slide subtitle
24 pt
Text
24 pt
5
20 pt
© Ericsson AB 2009 Ericsson BMUM Modeling experience 2009-05-259
Business modeling in our approach
Experience (so far) shows that the Blue Ocean strategy can be applied as structured methodology to get a clear picture on customer needs and values. It serves as a complementary to existing processes.
The Swedish consultancy company Frontwalker (IT-Arkitekterna), who had cross-industry experience in this area, is supporting us. The methodology is called Blue Port.
We have also connected the artifacts defined in the Blue Ocean methodology through the system engineering domain into design.
Top right
corner for
field
customer or
partner logotypes.
See Best practice
for example.
Slide title
40 pt
Slide subtitle
24 pt
Text
24 pt
5
20 pt
© Ericsson AB 2009 Ericsson BMUM Modeling experience 2009-05-2510
The method
Top right
corner for
field
customer or
partner logotypes.
See Best practice
for example.
Slide title
40 pt
Slide subtitle
24 pt
Text
24 pt
5
20 pt
© Ericsson AB 2009 Ericsson BMUM Modeling experience 2009-05-2511
The artifacts
Top right
corner for
field
customer or
partner logotypes.
See Best practice
for example.
Slide title
40 pt
Slide subtitle
24 pt
Text
24 pt
5
20 pt
© Ericsson AB 2009 Ericsson BMUM Modeling experience 2009-05-2512
Example artifact: Value curves
Borrowed from Blue
Ocean Strategy
Framework for defining
strategic positioning
Tool for understanding
offering in relation to that
of competition
Top right
corner for
field
customer or
partner logotypes.
See Best practice
for example.
Slide title
40 pt
Slide subtitle
24 pt
Text
24 pt
5
20 pt
© Ericsson AB 2009 Ericsson BMUM Modeling experience 2009-05-2513
Example artifact (Value Curve)Value Curve Chart
02468
10121416
Nic
e f
eatu
res
Local pre
cence
Att
ractive,
flexib
le B
usin
ess
Mutiple
revenue s
tream
sS
hare
d r
isk
Low
investm
ent
Low
cost/
part
ner
setu
p
none
Mass localis
ation
Faste
r T
TC
Larg
er
volu
me o
f serv
ices
Local serv
ice b
undlin
gF
lexib
le s
erv
ice c
om
positio
n
Tru
ste
d &
innovative p
art
ner
Fle
xib
le,
share
d infr
astr
uctu
re
eT
OM
L2-L
3 p
repare
dT
AM
support
3G
PP
TS
22.1
05 V
8.0
.0 c
om
plia
nt
3G
PP
TS
22.2
xx V
y.0
.0 c
om
plia
nt
3G
PP
TS
23.2
xx V
y.0
.0 c
om
plia
nt
Decid
e
what
is r
ele
vant
to o
ffer
that
adds v
alu
e t
o b
usin
ess
can b
e d
one b
y u
sor
oth
er
biz
part
ners
Value Component
Tech
nic
al
Featu
re
Biz
Part
neri
ng
Secu
rity
Serv
iceD
ep
loym
e
Cu
sto
merP
erc
ep
ti
Gre
en
Pro
du
ct
Inte
gra
tio
n E
ffo
rt
Mark
eti
ng
hyp
es
Ad
dW
hat
is H
OT
to t
arg
et
mark
et
Value GROUP
Components Value
Top right
corner for
field
customer or
partner logotypes.
See Best practice
for example.
Slide title
40 pt
Slide subtitle
24 pt
Text
24 pt
5
20 pt
© Ericsson AB 2009 Ericsson BMUM Modeling experience 2009-05-2514
Example artifact (Value Network)
Top right
corner for
field
customer or
partner logotypes.
See Best practice
for example.
Slide title
40 pt
Slide subtitle
24 pt
Text
24 pt
5
20 pt
© Ericsson AB 2009 Ericsson BMUM Modeling experience 2009-05-2515
Linking Business and System domain
Service Oriented approach used to connect business
and system domain all way down to components
Tool allows to keep & manage links between the
various models
Do we consider this use case?
MBUC Manage Service Development
BUC Create a SNA Service
BUC Verify a SNA Service
BUC Register a SNA Service
BUC Update a SNA Service
BUC Integrate a SNA service into a MM
related Service
Is this use case forgotten?
<<include>>
<<include>>
<<include>>
<<include>>
<<include>>
<<include>>
<<include>>
<<include>>
<<include>>
<<include>>
<<include>>
Design Script
Save Script
Load Script
Manage Script
Initiate Red Line Trace
Enterprise Administriator
(Solution Actors)
Deploy (Store) Script
Get (Restore) Script
Undeploy (Remove) Script
Script Designer
(Solution Actors)
Service Provider Administrator
(Solution Actors)
Stop Red Line Trace
Manage Assigned Script Details
Delegate Parameter Changes
Deploy (store) Test Script
Get (Restore) Test Script
Undeploy (Remove) Test Script
Caller
(Solution Actors)
Top right
corner for
field
customer or
partner logotypes.
See Best practice
for example.
Slide title
40 pt
Slide subtitle
24 pt
Text
24 pt
5
20 pt
© Ericsson AB 2009 Ericsson BMUM Modeling experience 2009-05-2516
The framework in the tool
Top right
corner for
field
customer or
partner logotypes.
See Best practice
for example.
Slide title
40 pt
Slide subtitle
24 pt
Text
24 pt
5
20 pt
© Ericsson AB 2009 Ericsson BMUM Modeling experience 2009-05-2517
Example of usage in project
Top right
corner for
field
customer or
partner logotypes.
See Best practice
for example.
Slide title
40 pt
Slide subtitle
24 pt
Text
24 pt
5
20 pt
© Ericsson AB 2009 Ericsson BMUM Modeling experience 2009-05-2518
Lessons learned (1/2)
Changing modeling tool is hard– Own look and feel, lot of pain for users to change
– Exchanging models between tools is (still) utopia
Our modeling architecture was also inspired by Active
Billing / T-Systems (Germany),– They have this in use for some time already to manage new
features and updates in their billing systems, where
immediately it can be shown what systems are impacted,
test specs are generated and component interfaces are
generated for their development partners.
Top right
corner for
field
customer or
partner logotypes.
See Best practice
for example.
Slide title
40 pt
Slide subtitle
24 pt
Text
24 pt
5
20 pt
© Ericsson AB 2009 Ericsson BMUM Modeling experience 2009-05-2519
Lessons learned (2/2)
Model driven development helps in working with partners for development
– Key for understanding the total system– Key for good breakdown into smaller components that can
be off-shored in small iterations.
For complex integration cases between Value Added solutions (the domain of Ericsson R&D in Rijen) we showed it is possible for the domain experts / solution architect
– To define / model the required solution– And to generate code (SCXML, Java) that can be deployed
and tested end2end on our latest platform (JEE based)– With in total 20 hours effort!
Top right
corner for
field
customer or
partner logotypes.
See Best practice
for example.
Slide title
40 pt
Slide subtitle
24 pt
Text
24 pt
5
20 pt
© Ericsson AB 2009 Ericsson BMUM Modeling experience 2009-05-2520
Next steps
Connecting model repository to SW component
inventory
Investigate further promising approach where code of
critical parts of applications and compliance test
harness can be generated (using ASD from Verum)
Top right
corner for
field
customer or
partner logotypes.
See Best practice
for example.
Slide title
40 pt
Slide subtitle
24 pt
Text
24 pt
5
20 pt
© Ericsson AB 2009 Ericsson BMUM Modeling experience 2009-05-2521
Conclusions
Working in a demanding business on complex systems
in a ‘flat world’ where activities are done in different
geographical locations requires an approach– That is information driven in stead of document driven
– Supports melting together Enterprise Architecture with
Business modeling and lower layers of systems &
realization models.
Together with Sybase, Frontwalker and inspired by
others we have set up a methodology and framework
that supports to capture each role's expertise in the
models and zoom in/out on the granularity with
minimum re-work effort
Top right
corner for
field
customer or
partner logotypes.
See Best practice
for example.
Slide title
40 pt
Slide subtitle
24 pt
Text
24 pt
5
20 pt
© Ericsson AB 2009 Ericsson BMUM Modeling experience 2009-05-2522
Top right
corner for
field
customer or
partner logotypes.
See Best practice
for example.
Slide title
40 pt
Slide subtitle
24 pt
Text
24 pt
5
20 pt
© Ericsson AB 2009 Ericsson BMUM Modeling experience 2009-05-2523
BMUM Modeling architecture
Bu
sin
ess m
od
el
Se
rvic
e
mo
de
lD
esig
n m
od
el
[yes]
[yes]
[no]
Need analysis?
Analyze Opportunity
Interesting for Product backlog?
New opportunity
Put on Product Backlog (with priority)
End
Package_1
Package_2Package_3
Interface_1
Interface_2 Interface_3
0..10..*
Class_1 Class_2
Class_3 Class_4
Use cases, business process diagrams
Business services
Notation: BPMN +UML?
Service Architecture (which own, which 3PP)
Service interfaces / contracts
Service Property model
System Architecture (Main system
components, their roles and their relations,
system architecture choices and
principles, system properties)
Per system: Software architecture (Main
software components, their roles and their
relations, software architecture choices
and principles. (using package diagrams,
class diagrams, sequence diagrams, etc))
System characteristics/properties model
CIM
PIM
PS
M
Syste
m
mo
de
l
. .
. .
. .
. .
Requirements (changes) * Verifications/test/simulations *Rules/aspects
/standards*
* Can in principle be applied at all abstraction layers and does not necessarily need to be a separate model
Ericsson C
om
mon I
nfo
rmation M
odel
Business (process) service (eTOM)
System Capabilities (Service)
Infrastructure (Service)
<<Control>>
Control
Entity/Boundary (Service)<<Boundary>>
Boundary
<<Entity>>
Entity
Infrastructure/wrapper (Service)
Business model
Sustainability
Actors
Needs
Ecological Social Financial
Target Market Value NW
Channels
Price
Values Business components
Our
businessPartners
Value offer
Business model
Sustainability
Actors
Needs
Ecological Social FinancialEcological Social FinancialEcological Social Financial
Target Market Value NW
Channels
Price
Values
Channels
Price
Values Business components
Our
businessPartners
Business components
Our
businessPartners
Business components
Our
businessPartners
Value offer
top related