Goals
- To manage logical and lexical models used in template-based authoring service.
Background and strategic fit
We use the term model (or model schema) to refer to a formal specification of a group of concepts, which are belong to the same domain and range. A model has two parts: logical and lexical. A logical model defines the parent(s), attributes, and relationship groups of a group of concepts. A lexical model defines the common parts of the fully specified name, preferred term, and synonym(s). We use a model (both logical and lexical) as a template to create a batch of new concepts.
Assumptions
- Each model includes a logical model and a lexical model.
Requirements - Template based authoring -not discussed or done
| # | Title | User Story | Importance | Notes |
|---|---|---|---|---|
| 1 | Sharing model | As a model user, I want to share my model with other authors and I can view other authors' models as well. | MUST | |
| 2 | Reusing model | As a model user, I want to reuse the existing model when I can so that I can avoid creating redundant models. | MUST | |
| 3 | Validating model | As a model user, I want to validate my model so that I can ensure the quality control on models. | SHOULD | |
| 4 | Versioning model | As a model user, I want to generate versions of a model that shares the common structure but may have different internal structure. | SHOULD |
User interaction and design
Questions
Below is a list of questions to be addressed as a result of this requirements document:
| Question | Outcome |
|---|---|