Workshop on
Model Lifecycle Management

Lonnie VanZandt, Enterprise Architect, Sodius
TIMLM Working Group co-Chair

Facilitator Info

• Enterprise Architect, Sodius
• (ex) Chief Architect, No Magic
• (ex) UPDM Co-chair
• INCOSE Tools WG Co-chair
• OMG BPMN2 Certified
• OSLC Developer
• IBM Jazz CLM Integration Partner
• PTC Windchill Integration Partner
• Tasktop Sync Partner
• ~30 years Software and Systems Engineering
• 17 years Consulting
• Hobby Ontologist

Workshop Sessions

• Introduction to the MLM and *LM Definition [Plenary]
• Defining Collaborative and Cooperative Workflows
• Mapping MLM and EA Concepts to PBSE
• Eliciting and Recording MLMS Capabilities
• Eliciting and Recording MLMS Stakeholders and Performers
• Eliciting and Recording MLMS Operational Activities (Use Cases)
• Trade Space Due Diligence and Recording existing Systems
• Specifying MLMS Service Choreographies
• Workshop Conclusion [Plenary]

MLM Vision: Purgatory

We see:

“a community of Systems (and discipline-specific) Engineers struggling to persist and to reference the artifacts of engineering over the lifecycle of each enterprise;

a community of Stakeholders and Decision-makers forced to make decisions irrationally and intuitively due to
a lack of access to the defensible arguments
that both legacy documentary and innovative
model-based systems engineering
should provide."

Doré, Gustave, 1868, Dante purgatorio

MLM Vision: Paradise

We see:

"a day when engineers use distributed systems that automatically persist artifacts in compact, modular form along with the provenance of each modification;

a day when engineers can reference the current and the historical representation of both individual artifacts and collections thereof along with the relational graphs
between artifacts;

a day when stakeholders make rational
decisions using the Systems Engineers’
explicit sound dialectical and rhetorical
arguments based on the provenance of
content and change.”

Doré, Gustave, 1868, Dante e Beatrice

Paraphrasing Charlton and Adras, management is a process by which managers reflectively model and share a representation of their own processes to enable themselves to perform their eponymous information-processing activities of monitoring, evaluating, predicting, and controlling their enterprise and its systems. [@Charlton2003]

Furthermore, managers manage for particular purposes. Purpose-driven, they acquire systems to address the needs of the enterprise and they manage their stakeholders, engineering lifecycle tools, and artifacts during the acquisition processes to attain certain goals. [@VanZandt2016]

Management?

  In “Mob Programming, A Whole Team Approach”, the authors describe, “mob programming”, an evolution of pair programming as, “all the brilliant minds working together on the same thing, at the same time, in the same space, and at the same computer” [@Zuill2016].

  The TIMLMWG intends the term "Collaborative Engineering" to be a variation of this mob programming concept. Blending in Sun Microsystems’ John Gage’s marketing campaign that “the network is the computer” and allowing the “same space” to be the “same virtual space”, the TIMLMWG describes collaborative engineering as: ...

Collaboration?

"All the brilliant minds working together on the same thing, at the same time, in the same virtual space, and on the same worldwide network."

[@VanZandt2016]

Collaboration

Lifecycle Management

Sessions' Mission

Within three hours, starting now, collaboratively come up with a collection of curated instances of the Session's specific Concepts.

Sessions' Tactics

• Choose a scribe
• Choose one or more curators
• Find some Rapid-Prototyping tools: Pens, Papers, Boards
• Choose an electronic authoring tool to capture the contributors' proposals and the curated results
• Whiteboard / brainstorm / research
  ​      Prior Art, Novel Ideas, Known good Solutions
• Take 2-3 breaks
• Capture the contributions
• Curate the contributions
• Share the curated results with the plenary team

Workshop Sessions

• PBSE "Patterns" Session [Lead: Schindel]
• Capabilities Session [Lead: You?]
• Performers Session [Lead: You?]
• Operational Activities Session [Lead: You?]
• Systems Session [Lead: You?]
• Service Choreography Session [Lead: VanZandt]
• Floaters [Lead: Self]

Workshop Conclusion

• Report: PBSE Session
• Report: Capabilities Session
• Report: Performers Session
• Report: Operational Activities Session
• Report: Systems Session
• Report: Service Choreography Session
• Opinion Sharing