Add model development and maintenance processes to the HMMG wiki

[sptws001]

HMMG model development and maintenance processes are not currently described on the HMMG wiki, which can lead to some confusion when navigating ProCloud repository and Reusable Assets Service (RAS), standalone Enterprise Architect projects, and standalone XMI files. With the introduction of the Editorial version of the harmonized model project, it has become even more important for this documentation to be provided.

Activities include:

• Establish based model project development and maintenance workflows to support known use cases
• Add process models and documentation to the HMMG wiki

[sptws001]

Review of existing pages and the following changes are proposed (does not include integration of technical content from UML-Best-Practices wiki):

1. “Home” page:

• Add descriptions and roles of Editorial and Official versions of the Harmonized model
• Add/update descriptions and roles of the EA projects and XMI files (especially given proposal to use the XMI and EA projects as the core editing resources and not ProCloud due to performance and other issues)

2. “About-Subversion-and-Enterprise-Architect” page:

• If SVN is not required, replace page with current Git/GitHub based instructions on an appropriately named page

3. “Connecting to the Harmonized Model Repository”, “Editing the Harmonized Model”, “Moving and renaming XMI files in SVN” pages:

• Replace with pages following the new model development and maintenance workflows
• Replace SVN/Tortoise instructions with Git-based instructions

4. “Prefixes” page:

• Verify and update (if required) list of namespaces, standards and versions, etc.

[sptws001]

As of June 2021, a sandbox instance of each the HMMG and UML Best Practices wikis were established in external repositories for development and testing.
HMMG: https://github.com/sptws001/ISO_Wiki_Sandbox
UML BP: https://github.com/sptws001/ISO_UML_BP_Wiki_Sandbox

The content of the HMMG wiki was updated significantly and the UML BP has been initiated.

Updated plans include merging the two wikis for easier maintenance and eliminating duplication between the repositories.