Hi all - use cases for new platform functionality are emerging, so how do we proceed with use case review, architectural review, and, if needed, TSC approval?
The TSC already approved the subcommittees, but I hope we don't have to wait for an official Subcommittee Chair role before we, the Community, can organize subcommittee meetings and start discussing new use cases.

Specifically, the authors of the Authorship Management use case would like community discussion:

• We need to ensure the credit of the original model author is respected and maintained in Acumos
• The original authorship of a model should be maintained when the model is
  • federated from one Acumos to another
  • updated from one version to another
  • downloaded by the user
• There will be 3 attributes associated with a model
  • Authorship – this attribute is part of metadata related to model artifact which should follow provenance rules
  • Catalog Manager – this attribute is not part of metadata and the right of Catalog Manager to a model is limited to local Acumos instance only
  • Publisher – this attribute is part of metadata and it can be an individual or organization
• Do not use the term “ownership” to avoid legal/license complications

Thoughts, suggestions?

Thanks!

-- 

Aimee Ukasick

irc: aimeeu

We need the Architecture and Product committee to form and take responsibility for such efforts. That is the key critical path dependency to avoid organizational chaos.

In the meantime we need to move all offline design processes and sprint/release planning into public view through the wiki, etherpad, etc.

Once the committees have formed, I recommend we apply this process for new feature planning:

1) The goal of an enhancement is brought before the Product committee in Acumos, and documented as use cases on the page https://wiki.acumos.org/display/ACCOM/Product+Committee.

2) The use cases are discussed and approved by the Product committee and handed off to the Architecture committee for design and implementation planning.

3) The Architecture committee creates a high-level design that is documented on / referenced from the wiki at https://wiki.acumos.org/display/AR/Architecture+Home. Documents support any details beyond a high level description of the implementation impacts to Acumos components, and include diagrams, data flows, etc as needed to ensure the technical implementation details are clear, complete, accurate.

4) The Architecture committee agrees with the Product committee oversight, that the detailed design meets the goals of the use case.

5) The design is entered into JIRA as epics etc and the work proceeds in sprints.

A modification of the above is where a design issue or major bug is first discussed in the Architecture committee and referred to the Product committee once the Architecture committee has generally agreed on a high-level approach to implementing a solution. The Product committee needs to consider the impact (of delaying implementation) vs effort of implementing, in their release planning.

Hi all - use cases for new platform functionality are emerging, so how do we proceed with use case review, architectural review, and, if needed, TSC approval?
The TSC already approved the subcommittees, but I hope we don't have to wait for an official Subcommittee Chair role before we, the Community, can organize subcommittee meetings and start discussing new use cases.

Specifically, the authors of the Authorship Management use case would like community discussion:

• We need to ensure the credit of the original model author is respected and maintained in Acumos
• The original authorship of a model should be maintained when the model is
  • federated from one Acumos to another
  • updated from one version to another
  • downloaded by the user
• There will be 3 attributes associated with a model
  • Authorship – this attribute is part of metadata related to model artifact which should follow provenance rules
  • Catalog Manager – this attribute is not part of metadata and the right of Catalog Manager to a model is limited to local Acumos instance only
  • Publisher – this attribute is part of metadata and it can be an individual or organization
• Do not use the term “ownership” to avoid legal/license complications

Thoughts, suggestions?

Thanks!

-- 

Aimee Ukasick

irc: aimeeu