december 2017 deric merino jama software - · pdf filejama jira windchill ni provide a...
TRANSCRIPT
“Public Release”
INCOSE San Diego
December 2017
Deric Merino – Jama Software
www.jamasoftware.com“Public Release”
Discussion Topics
• Systems Engineering (SE) Tool Interoperability Past
• A Web Services Approach: OSLC
• An Alternative Web Services Approach
• What Does The Future Hold?
“Public Release”
Early examples of production scale tool integration
started with ‘SDLC’
Each tool came with its own
• UX (typically installed)
• Application logic (maybe client, maybe server)
• Persistence (DB)
Point to point integrations
• High business cost for users, consultants and
vendors
Just like Systems Engineering…
Requirements
Changes /
Tasks
SCM
Test
The tool bench requires cross-discipline collaboration and cooperation
1
2
6 5
43
“Public Release”
Early examples of production scale tool integration
started with ‘SDLC’
Each tool came with its own
• UX (typically installed)
• Application logic (maybe client, maybe server)
• Persistence (DB)
As users we got
• Brittle integrations
• Administrative complexity
• Teams still working in silos
Just like Systems Engineering…
Requirements
Changes /
Tasks
Field
Service
On Target
Test
The tool bench requires cross-discipline collaboration and cooperation
PLMUML/SysML
Simulation
Off Target
Test
SCM MCAD
ECAD
“Public Release”
Based on internet concepts, it
promises
• Amazing scalability
• Information integration on a
massive scale
• Infinitely extensible
• World-wide information
visibility
https://open-services.net/
A web services approach:
Middleware
RequirementsChanges /
TasksSCMUML/SysML
Off Target
Test
OSLC OSLC OSLC OSLC OSLC
“Public Release”
Basic Concept of OSLC• Instead of moving data,
each item provides a link to itself
• Each item is represented by a URI
• Specification tells each tool what vocabulary to expect
• Users can now view related data and traverse across tool domains
2 eyes
2 arms
2 legs
Handle
Opening
Ceramic
URI
URI
URI
URI
URI
URI
“Public Release”
The Technical Reality of OSLC
Pro
• Click-to-navigate concept is easy for users to understand
• Can be adopted by browser-based and desktop tools
• Provides visibility outside of user’s core domain
Challenges
• Getting linked data out of systems can be complex and time consuming (i.e. documents & reports)
• Metrics gathering is complex
• Impact analysis across multiple layers of information is complex and expensive
“Public Release”
The Business Reality of OSLC
https://open-services.net/software/
Pro
• The standard is easily available to contribute to and review
• A cluster of technology integrators have created adaptors for platforms
• IoT as a vocabulary specification may be well suited for IoT applications
Challenges
• Relatively few platform vendors have natively adopted the standard
• Other integration approaches already exist and continue to evolve
• Very few customers call out OSLC as a must have
“Public Release”
Today’s Engineering Tool Set VariedThe tool bench requires cross-discipline collaboration and cooperation
Jama Polarion
IBM
Mathworks
Sparx
NoMagic
HPE NI
IBMJama
Changes / Tasks (JIRA)
PLM (Windchill, Teamcenter)
“Public Release”
Today’s Engineering Tool Set VariedAn approach to leverage what software already has in place
Jama Polarion
Magic
DrawMatlab
HP ALM NI
Changes / Tasks (JIRA)
PLM (Windchill, Teamcenter)
REST APIRepresentative State Transfer: Web services
allow requesting systems to access and
manipulate textual representations of web
resources using a uniform and predefined set
of operations.
OSLC is a vocabulary specification built on top
of Resource Description Framework (RDF),
Linked Data & REST
*Wikipedia.com
“Public Release”
Today’s Engineering Tool Set VariedTake a queue from DevOps
Jama NIJIRA Windchill
Provide a ‘data bus’ or integration hub that
connects to the API many software titles
already contain.
• Bi-directional synchronization between
1..N software(s)
• Data mappings are defined graphically
and persistently
• Master -> Shadowed
• Polling method (i.e. each minute)
*Wikipedia.com
“Public Release”
Today’s Engineering Tool Set VariedTake a queue from DevOps
Pro
• Users can remain in their tool of choice and see needed information
• Users can click-to-navigate to appropriate tool
• Integration vendor owns adaptor updates
• Deployable Saas or On-Premesis
Challenges
• Data update may have time lag (seconds)
• Data governance must be defined up front (can be iterated)
• Integration hub may be extra cost
Jama NIJIRA Windchill
www.jamasoftware.com“Public Release”
The Future
www.jamasoftware.com“Public Release”
What Must be True?
• Must Maintain Traceability
• When something changes the team needs to know
• One view of truth (single source?)
• Data must sync seamlessly
• No manual downloads
• Cannot Introduce Security Issues
• We are dealing with IP & must be secure
• Must be easy to use
• Cannot have support staff
www.jamasoftware.com“Public Release”
Integrated System…Like Google Maps
www.jamasoftware.com“Public Release”
Related and Relevant
www.jamasoftware.com“Public Release”
Moves to Other Systems
• Allows you to move to other
system to see deeper analysis
• Allows you to keep in mind
where you are
• Allows you to go back
www.jamasoftware.com“Public Release”
Room For Improvements?
• Integrate data from Facebook
to know if your friends liked it?
• The idea being if they liked it
you probably would
• For business it could be a
specific engineer or manager
who was posting data that
knew it would be relevant
www.jamasoftware.com“Public Release”
Conclusions
• The systems engineering ecosystem is evolving
• OSLC is a good concept, but incomplete adoption
• Current solutions get part of the way there
• Connecting these systems in a context correct way is a hard problem
to solve and complete solutions are always getting better
