The overall goal for this committee is to grow the community of Modelers contributing models and also growing the community of companies running Acumos instances, via focus on these areas:
- Release functionality
- Model Management
- Catalog growth
The Meetings page provides meeting schedule, agendas, minutes, etc.
Model Training Pipeline
Model Evaluation and Validation (Test/Harness)
Security sub committee
Cloud Native (MS arch)
Model Life Cycle Management
Design Studio/Model Interoperability
Model Types (New)
LF DL Projects Integration
Integration with ONAP/Akraino/RIC
Updated list of Athena release features. This list of features was approved by the TSC. High priority is targeted to Athena.
has developed a design/implementation plan, that is shared with the Product committee for confirmation that the plan
incorporates the implementation plan into the release plan, assigns the implementation to project teams, and monitors the implementation.
Recording of April 16th 2018 meeting.
Use Case Catalog
This section will provide a use case summary table, and links to specific use case documents/sections as drafted/published. The table columns are intended as:
- Use Case: Unique name/identifier for this use case. Identifiers are recommended for mapping to test cases etc for coverage tracking.
- Description: Short description of the use case in typical form (e.g. "as a <type of user>, I need <description of platform capability/experience>, to <description of rationale for the capability>", or something more high-level/abstract, but clearly scoped).
- Status: drafting, proposed, approved
- Proposed by: who initiated the use case proposal
- Lead: contributors/SMEs for the use case
Note: the use cases below draw a distinction between the "Acumos platform" and "Acumos ecosystem", for clarity. The Acumos ecosystem represents a federated collection of Acumos platforms that as a group support the related use case's goals.
|Use Case||Description||Status||Proposed by||Lead|
|Model Provenance||As a modeler or model user, I need to ensure the provenance of models is preserved by the Acumos ecosystem as models are published, federated, collaborated on, and republished with enhancements, so that my authorship/copyright is preserved and to ensure that I have clear/correct information on the authorship/copyright of models I might want to contribute to.||Proposed|
|User Profile Tied to Organization||As an organization manager, I need to ensure that Acumos users who register when affiliated with my organization are associated in their user profile with that organization, and if they leave the organization their user profile within that organization can be marked as "inactive".||Proposed|
|Distinct Roles for Model Author, Publisher, Manager||As a user of an Acumos platform, I need to be able to take on various roles for models, including that of Author (author of a new Model or changes to a pre-existing Model), Publisher (user that has published a model to a marketplace, however acquired), or Manager (organization member responsible for managing models created by that organization's users).||Proposed|
|Assignment of Author Role||As author of a new model or changes to a pre-existing Model, I need to be automatically associated by the Acumos ecosystem in the Author role for that model version and any subsequent versions based upon it.||Proposed|
|Assignment of Publisher Role||As a user who publishes a model to a marketplace on behalf of myself or my organization, I need to be automatically associated by the Acumos ecosystem in the Publisher role for that Model version.||Proposed|
|Restriction of Publisher Role||As a user responsible for publishing models on behalf of my organization's model authors, I need the Acumos platform to enable restriction of the Publisher role to authorized users of my organization.||Proposed|
|Assignment of Manager Role||As a user who manages models on behalf of my organization (either as authored/published by organization users, or as subscribed to by my organization through Acumos federation), I need the ability to be manually associated to the model Manager role by the Acumos platform.||Proposed|
|Notifications to Publishers and Managers||As users in the role of Publishers and Managers, those users need to receive notifications when relevant events occur in the lifecycle of models for which the user has that role.||Proposed|
|Actionable Error Messages for Onboarding||As a user onboarding a model, I need the Acumos platform to provide accessible, clear, actionable messages about the status of the onboarding process and any errors that occur during it.||Proposed|
|Unpublish Model||As a user who has published a model that I later decide needs to be removed, I need the ability to remove the model from the Acumos platform and ecosystem.||Proposed|
|Replace Model and Remove Previous Version||As a user who has published a model that I later decide needs to be replaced and the previous version made no longer available, I need the ability to replace the model and prevent the earlier version from being accessible through the Acumos platform and ecosystem.||Proposed|
This section will provide a release plan summary table, and links to specific plan component documents as drafted/published, including
- Use Case: Unique name/identifier for use cases as defined above
- Description: Short description of the use case and reference to more detailed description if any (e.g. supporting documents / wiki pages)
- Implementation: Short description of how the use case is to be implemented, e.g. referencing impacted components as defined by the Architecture Committee
- Schedule: planned/actual start/end of implementation
Recent space activity