mvf:required_features
====== Differences ====== This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
mvf:required_features [2017/07/26 16:49] fred.a.cummins_gmail.com |
mvf:required_features [2017/08/01 10:10] fred.a.cummins_gmail.com |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| ===== Features of the MVF Specification ====== | ===== Features of the MVF Specification ====== | ||
| Line 155: | Line 186: | ||
| ====== User Features ===== | ====== User Features ===== | ||
| - | July 26, 2017 Draft by Fred Cummins | + | July 29, 2017 Draft by Fred Cummins |
| The following features are intended to reflect a user’s perspective on an implementation of the MVF specification. | The following features are intended to reflect a user’s perspective on an implementation of the MVF specification. | ||
| Line 161: | Line 192: | ||
| 1. Vocabulary. A vocabulary is a set of terms/designations that express the concepts of modeling language metamodel(s) and user model(s) in an associated natural language as appropriate to a community of developers and/or users of modeling language(s) and/or user model(s). | 1. Vocabulary. A vocabulary is a set of terms/designations that express the concepts of modeling language metamodel(s) and user model(s) in an associated natural language as appropriate to a community of developers and/or users of modeling language(s) and/or user model(s). | ||
| + | |||
| + | **Use Case**. Users will select a vocabulary for interaction with the modeling environment and some users will create or update specific vocabularies. A vocabulary may be shared as a unit or as a member of a package. | ||
| a. A new vocabulary may reference another vocabulary to specify terms such that a new vocabulary may delegate for terms it does not address, define specialized concepts for certain terms and add terms for additional concepts thus reducing the work required to define a vocabulary for another community of discourse. | a. A new vocabulary may reference another vocabulary to specify terms such that a new vocabulary may delegate for terms it does not address, define specialized concepts for certain terms and add terms for additional concepts thus reducing the work required to define a vocabulary for another community of discourse. | ||
| + | |||
| + | **Use Case**. A user/community may be happy with an existing vocabulary but prefer that certain terms be modified. This allows a new vocabulary to be created that "inherits" the terms of the existing vocabulary and then the selected terms can be modified without affecting the existing vocabulary. | ||
| b. The vocabulary will specify a vocabulary name and version. | b. The vocabulary will specify a vocabulary name and version. | ||
| - | c. A vocabulary will specify the community(S) of discourse for which the vocabulary is intended. | + | **Use Case**. This is information for users to reference and manage updates to vocabularies. An independent user may revise a vocabulary that other users may or may not wish to use. |
| + | c. A vocabulary will specify the community(S) of discourse for which the vocabulary is intended. Community names should be in the natural language associated with the vocabulary. | ||
| + | |||
| + | **Use Case**. This information is for users to identify a vocabulary of interest. __There may be multiple communities shown to be recognizable by potential users. | ||
| + | __ | ||
| d. A vocabulary will specify a natural language that is the basis for the terms/designations specified by the vocabulary. | d. A vocabulary will specify a natural language that is the basis for the terms/designations specified by the vocabulary. | ||
| + | |||
| + | **Use Case**. This is also to assist in user identification of a vocabulary of interest. | ||
| e. A concept that specializes a concept in a referenced vocabulary will have a link to the source concept to clarify the distinction and support the conversational use of the less specific term (may be expressed in the same or different term depending on the community and/or natural language). | e. A concept that specializes a concept in a referenced vocabulary will have a link to the source concept to clarify the distinction and support the conversational use of the less specific term (may be expressed in the same or different term depending on the community and/or natural language). | ||
| + | |||
| + | **Use Case**. If vocabulary B is based on vocabulary A, but a more specific term | ||
| f. A vocabulary will specify an owner (person or organization) that is responsible for managing changes. | f. A vocabulary will specify an owner (person or organization) that is responsible for managing changes. | ||
mvf/required_features.txt · Last modified: 2017/08/03 10:22 by fred.a.cummins_gmail.com
Page Tools
