Enterprise Architect and SysML

1
Enterprise Architect and SysML the story so far

• Sam Mancarella
• Chief Technology Officer
• Sparx Systems
• May 13, 2008

sam.mancarella_at_sparxsystems.com
2
(No Transcript)
3
Overview

• Introduction to Sparx Systems
• Enterprise Architect and MDG Products
• MBSE Market
• Sparx Market breakdown
• Customer Experiences
• What our customers really think
• Conclusion
• Future SysML work

4
Overview

• Introduction to Sparx Systems
• Enterprise Architect and MDG Products
• MBSE Market
• Sparx Market Breakdown
• Customer Experiences
• What our customers really think
• Conclusion
• Future SysML work

5
Who is Sparx Systems?

• Established in 1998
• Leading provider of UML modeling tools
• Enterprise Architect for UML 2.1
• Model Integration with 3rd Party tools
• Visual Studio, Eclipse, DOORS, Visio
• Support for other modeling standards
• Business Process Modeling Notation (BPMN)
• OMG Systems Modeling Language (SysML)
• Architecture Frameworks (DoDAF/MoDAF, Zachman
  Framework, ToGAF)

6
Who is Sparx Systems?

• Headquartered in Australia
• Sister companies
• Japan
• Central Europe
• South America
• China (new for 2008)
• Represented by approx 200 Partners
• Resellers, Trainers, Technical Partners
• Value-Added Resellers (VARs)

7
The Sparx Product Line
8
Enterprise Architect

• Our Flagship UML 2 Modeling Platform
• Supports the latest UML 2.1 standard
• All 13 diagrams supported
• Over 150,000 licenses worldwide
• Visual Requirements Modeling
• One of the first providers to offer visual
  requirements
• UML 2 Extensions to model requirements
• Requirements, Feature, Change, Issue
• Seamless traceability between formal
  specifications and system specifications within
  the model

9
Overview

• Introduction to Sparx Systems
• Enterprise Architect and MDG Products
• MBSE Market
• Sparx Market Breakdown
• Customer Experiences
• What our customers really think
• Conclusion
• Future SysML work

10
MBSE Market

• Tiny Relative Marketshare
• MDG for SysML represents lt 1 of totalEA user
  base
• Customers Industry Segments
• Academia, Defence, Biotechnology, Aerospace
• Govt. Research, Heavy Industries, Automotive
• Resources (Mining)

11
MBSE Market

• Customers Demographics
• Trainers / Educators
• Contractors / Consultants (self-employed)
• RnD Engineers
• Customers Usage Behavior
• System Engineering
• Modeling new, real-world designs, concepts
• Capturing existing designs for documentation
• Small-scale projects - lt10 personnel

12
MBSE Market

• Customers Usage Behavior
• Value Added Modeling
• Using Sparx SysML to extend their own
  products/services
• Training, product extensions
• Many of these users are Sparx Registered
  Partners
• Evaluation
• Evaluating our product (users are savvy in SysML,
  reviewing our product for procurement)
• Evaluating the technology (users are savvy in
  Systems Engineering, reviewing SysML as a
  technology)

13
Overview

• Introduction to Sparx Systems
• Enterprise Architect and MDG Products
• MBSE Market
• Sparx Market Breakdown
• Customer Experiences
• What our customers really think
• Conclusion
• Future SysML work

14
Customer Experiences

• What they like
• Value-for-moneyCost-effectiveness of EA SysML
• Ease of UseUser Interface less imposing to the
  SysML-novice
• Scalable deploymentMulti-user capable using DBMS
  repositories
• What they want improved
• Our SysML implementation is dated, needs
  updating
• Interoperability with other SE tools
  important

15
Overview

• Introduction to Sparx Systems
• Enterprise Architect and MDG Products
• MBSE Market
• Sparx Market Breakdown
• Customer Experiences
• What our customers really think
• Conclusion
• Future SysML work

16
Conclusion

• Very slow adoption
• lt1 of total userbase
• Early Adopters, mainly SysML Evaluators, SysML
  Practitioners, not enough real customers
• Food for thought to consider to broaden adoption
  to the mainstream
• Tool interoperability between SysML-capable
  tools, simulators, analysers and repositories
  (not JUST SysML model vendors) AP233
• Process Frameworks - OOSEM

17
Conclusion

• Food for thought
• Maturity of the language SysML 1.1 RTF efforts
  at the OMG
• UML has enjoyed 10years to develop its ubiquity
  does SysML need just as much time?
• For Further Information
• www.sparxsystems.com/sysml
• 30-day full functional trials of
• Enterprise Architect 7.1
• MDG Technology for SysML

18
thank you for your attention!