Proposed SysML v2 Submission Plan Ed Seidewitz Sandy Friedenthal New Orleans LA 28 September 2017

Topics Strategy Technical Approach Management Approach

Strategy Build on existing standards, particularly SysML 1.x and Executable UML. Deliver value even before completion of the final submission. Develop the submission by developing a conformance test suite, reference model and pilot reference implementation. Continually adjust development goals based on user community feedback. Provide a clear transition path, allowing incremental migration to SysML 2.0. Maintain alignment between language specification and API/services definition

Technical Approach Track 0: Project and Requirements Management Track 1: Profile Development Track 2: Metamodel Development Track 3: Pilot Implementation Track 4: API/Services Development

Release Roadmap Release 1 Release 2 Release 3 Release 4 Management Track 0 Coordinate work Coordinate with users Prepare RFC (s) Update plans Prepare submission Track 1 Profile SysML 1.x profile with precise semantics (RFC) Mapping from SysML 1.x profile to interchange format Re-architect SysML 1.x profile into (initial) SysML 2.0 profile Extend SysML 2.0 profile until complete Metamodel Track 2 (S)MOF-based metamodel for SysML 2.0, with basic diagrams and Alf Interchange format for SysML 2.0 SysML 2.0 concrete and abstract syntax with SysML 1.x semantics (RFC) SysML 2.0 declarative semantics and semantic library Track 3 Pilot Implement extended Alf infrastructure Implement pilot repository for SysML, using (extended) Alf Implement SysML 2.0 with SysML 1.x semantics Implement SysML 2.0 semantics, prototype visualization API/Services Track 4 Develop general platform-independent API approach Define selected platform-specific bindings Implement required services Implement optional services

Track 0: Project and Requirements Management Maintain over-all project task backlog. Monitor work against the RFP requirements. Coordinate with user community Prioritize backlog tasks based on user community needs and risk mitigation. Organize demonstrations to user community. Collect feedback and adjust planning based on it. Coordinate work across tracks. Manage cross-track dependencies. Coordinate common and team-specific tooling infrastructure. Manage deliverable artifacts. Edit specification documents and other artifacts. Approve deliverable work products from the various tracks. Deliver submissions to OMG.

Track 1: Profile Development Specify a SysML 1.x profile with precise semantics. Building on fUML, PSCS, PSSM, consistent with plans for SysML 2.0. Leverage other OMG standards, including UAF, Diagram Definition, ODM, etc. Define the reference model using the new profile. Submit as an RFC. Develop mapping from SysML 1.x profile to planned SysML 2.0 metamodel/interchange format (consistent with Track 2). Stretch goal to include as non-normative annex in RFC. Re-architect and extend SysML 1.x profile to SysML 2.0 profile. Continue to update SysML 1.x profile tracking SysML 2.0 developments (consistent with Track 2). Use RTF or RFC processes as appropriate. Define semantics based on SysML 2.0 semantics (consistent with Track 2). Maintain semantic backward compatibility with SysML 1.x profile.

Track 2: Metamodel Development Define syntactic (S)MOF-based metamodel for SysML 2.0. Include mapping from metamodel to SysML 1.x profile (consistent with Track 1). Use Diagram Definition to define basic graphical views, use Alf for textual views. Define the reference model in the new metamodel representation. Define metamodel-based interchange format for SysML 2.0. Define the SysML 2.0 abstract and concrete syntax as a SysML 2.0 model. Use Pilot tooling (consistent with Track 3). Possibly submit an RFC for the abstract and concrete syntax metamodels with SysML 1.x profile semantics (from Track 1). Define the base declarative semantics for the core of SysML 2.0. Develop the semantic library for SysML 2.0 in SysML 2.0. Maintain semantic backward compatibility with the SysML 1.x subset (consistent with Track 1).

Track 3: Pilot Implementation Implement bootstrap model execution infrastructure Implement by extending existing fUML/Alf tooling. Extend Alf as necessary to provide addition notations (e.g., for components and state machines). Implement pilot repository for SysML using (extended) Alf as textual notation. Implement SysML 2.0 with SysML 1.x semantics (consistent with Tracks 1 and 2). Implement SysML 2.0 semantics Start with base subset having declarative semantics (consistent with Track 2). Extend via implementation of semantics library (consistent with Track 2). Maintain Alf-based textual notation, further extended as necessary. Implement test suite and reference model using executable SysML. Adapt existing tools to prototype other visualizations. Demonstrate general view and viewpoint approach.

Track 4: API/Services Development Develop general platform-independent API approach and generic API model. Use pilot SysML v2 language tooling. Define bindings to selected platform-specific languages. Implement pilot mapping tools for bindings. Implement required Query and Extension services. Use pilot executable SysML implementation (from Track 3). Select and implement additional, optional services (as agreed by team)

Management Approach Managed as one submission team for two RFPs. Distributed team structure Scalable Agile approach Roles and Levels of Commitment Teaming Agreement

Distributed Team Structure Project management team: Product Owner representing user community (Sandy) Technical Lead from development community (Ed) Leaders of track teams. A track team for each of Tracks 1 – 4. The team for Track 4 may start later, depending on the timing of the API/Services RFP.

Scalable Agile Approach Core team coordinates daily (virtual “stand up meeting”). Development teams self-organize. All teams teleconference together weakly. Demonstrations to user community at end of each month (monthly “iteration cycle”).

Roles and Levels of Commitment Submitter Sends OMG Letter of Intent (LOI) to submit to RFP. Provides reasonable commitment of personnel time and/or other resources to support one or more Tracks. Contributor Organization without standing to submit to the RFP (may or may not be an OMG member). Nevertheless, provides reasonable commitment of personnel time and/or other resources to support one or more Tracks, similarly to a submitter. Reviewer Person or organization that reviews technical products while under development (i.e., this does not include review of formal initial and revised submissions per the OMG process).

Roles and Levels of Commitment (cont’d) User Person or organization that agrees to regularly review the technical output of the submission team for demonstrable user value (particularly, though not necessarily exclusively, from monthly iteration demonstrations). Does not contribute any IP that would require copyright or patent releases. Liaison A person who acts as an interface to another standards or industry organization with and interest in SysML v2 or with whom SysML v2 development should be coordinated. Does not necessarily contribute any IP that would require copyright or patent releases, but, if this is necessary, must also act as a submitter or contributor. In addition, a liaison would coordinate any related to using the IP of the represented organization in a SysML v2 submission.

Teaming Agreement All submitters and contributors agree to give the submitters sufficient rights to any IP contributed to the submission effort, so as to allow the submitters to submit to OMG pursuant to the RFP, consistent with OMG IP policy. Submitters continue to maintain these rights, even if a submitter or contributor leaves the submission team, for any material contributed prior to leaving. However, if any submission or part of a submission ultimately does not get adopted by OMG, then all rights in any contributed material reverts to the original owners.