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 | ||
|
mvf:required_features [2017/07/26 16:58] fred.a.cummins_gmail.com |
mvf:required_features [2017/08/03 10:22] fred.a.cummins_gmail.com |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| ===== Features of the MVF Specification ====== | ===== Features of the MVF Specification ====== | ||
| Line 161: | Line 193: | ||
| 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. | ||
| - | 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**. 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). The source concept may be associated with multiple specialized concepts in different vocabularies or for complementary concepts in a single vocabulary. NOte that these concept relationships have implications to the management of vocabulary updates. | ||
| + | |||
| + | **Use Case**. If vocabulary B is based on vocabulary A, but a more specific definition is needed for vocabulary B, this provides reference to the more general concept and the association may be the basis for a concept taxonomy to help a user locate a desired concept. This is particularly relevant when the source vocabulary (vocabulary A) is a vocabulary of business terms. | ||
| 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. | ||
| + | |||
| + | **Use Case**. There may be shared vocabulary users in different departments or companies. Updates should be coordinated if not validated. | ||
| + | |||
| + | **Use Case**. Vocabularies will evolve and this evolution must be managed to support multiple users of the vocabulary that may be indifferent organizations or companies. If there are problems with a vocabulary, they should be resolved with the owner. The owner would potentially keep track of the users to provide updates and potentially collaborate on changes. | ||
| 2. Vocabulary package/library. One or more vocabularies may be managed as a package or library of vocabularies to exchange and maintain together. | 2. Vocabulary package/library. One or more vocabularies may be managed as a package or library of vocabularies to exchange and maintain together. | ||
| + | |||
| + | **Use Case**. vocabularies should be packaged for convenience in sharing. In addition, there is a need to reconcile concepts of multiple vocabularies for use that may involve some human participation. These reconciled concepts should be preserved by the package. | ||
| a. A concept has only one representation within a package/library or in an operational, MVF-supported modeling environment. | a. A concept has only one representation within a package/library or in an operational, MVF-supported modeling environment. | ||
| + | |||
| + | **Use Case**. A model element must be linked to the MVF Entry that represents the model element concept. If concepts of different vocabularies are not reconciled, then there should be multiple links from the model element for the different vocabularies. The multiple links effectively identify a shared concept. This would also require identification of the multiple links for other occurrences of the shared concept in the same and other models using the same vocabularies (package). | ||
| b. A mechanism will assist with reconciliation of concepts when merging vocabularies from independent sources (i.e., concept identiriers are different for the the same concept from different sources). | b. A mechanism will assist with reconciliation of concepts when merging vocabularies from independent sources (i.e., concept identiriers are different for the the same concept from different sources). | ||
| + | |||
| + | **Use Case**. The use case for item a, above describes the need for this facility. | ||
| c. a package/library or selected vocabularies can be imported/exported as XMI. | c. a package/library or selected vocabularies can be imported/exported as XMI. | ||
| - | d. A modeling tool may have a complementary library for the metamodel and other tool-specific concepts. | + | **Use Case**. A package should preserve the reconciliation of concepts for multiple vocabularies so reconciliation need not be repeated. |
| - | e. A separate vocabulary package/library may be defined for the terms/designations required for a modeling language. | + | |
| + | d. A modeling tool may have a complementary library for the metamodel and other tool-specific concepts. | ||
| + | |||
| + | **Use Case**. A tool provider will provide tool-specific vocabulary(w) for customer satisfaction. A tool-specific vocabulary could provide translation of terms/captions that are incorporated in the user interface but are not associated with the model or metamodel. | ||
| + | |||
| + | e. A separate vocabulary package/library may be defined for the terms/designations required for a modeling language. | ||
| + | |||
| + | **Use Case**. This vocabulary or package of vocabularies may be created/adopted as part of the language specification for consensus, consistency and efficiency. | ||
| f. A package must include any vocabularies that are referenced by vocabularies specified to be included in the package. | f. A package must include any vocabularies that are referenced by vocabularies specified to be included in the package. | ||
| + | |||
| + | **Use Case**. This is addressed in Use Case 1(a), above. | ||
| 3. Terms/designations. Terms/designations are character strings associated with a vocabulary to express modeling concepts in inputs (such as data entry forms) and outputs (such as displays) for a modeling language and user model(s). | 3. Terms/designations. Terms/designations are character strings associated with a vocabulary to express modeling concepts in inputs (such as data entry forms) and outputs (such as displays) for a modeling language and user model(s). | ||
| + | |||
| + | **Use Case**. | ||
| a. Terms may be words or phrases, including spaces and special characters that appear in place of the concept names of the metamodel and user model in displays and may be used for user input to designate the associated concepts. | a. Terms may be words or phrases, including spaces and special characters that appear in place of the concept names of the metamodel and user model in displays and may be used for user input to designate the associated concepts. | ||
mvf/required_features.txt · Last modified: 2017/08/03 10:22 by fred.a.cummins_gmail.com
Page Tools
