mbse:modelmgt:operational_analysis
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
mbse:modelmgt:operational_analysis [2015/10/31 14:30] lvanzandt |
mbse:modelmgt:operational_analysis [2015/12/13 19:12] (current) lvanzandt |
||
|---|---|---|---|
| Line 11: | Line 11: | ||
| ===== Proposed Set ===== | ===== Proposed Set ===== | ||
| - | * State your proposals here. \\ | + | * State your proposals here. \\ |
| - | (Follow a pattern of [Tag Alias] Narrative sentential statements describing operational activity, not a System Function, Service Function, Requirement, Feature, or Benefit.) \\ | + | |
| - | Note that the first seven shown here are copied verbatim from the 2014 White Paper. | + | (Follow a pattern of [Tag Alias] Narrative sentential statements describing operational activity, not a System Function, Service Function, Requirement, Feature, or Benefit.) \\ |
| + | |||
| + | Note that the first seven shown here are copied verbatim from the 2014 White Paper. | ||
| * [OPA-INFO-101] A stakeholder of a Model/Model Element who is not the editor of the entire set of information within the Model/Model Element needs curated information within the model in order to make decisions or present definitive information to other parties. | * [OPA-INFO-101] A stakeholder of a Model/Model Element who is not the editor of the entire set of information within the Model/Model Element needs curated information within the model in order to make decisions or present definitive information to other parties. | ||
| Line 22: | Line 24: | ||
| * [OPA-DIFF-601] An organization is requested to describe, present, or instantiate a system that was created some past time even perhaps with different knowledge tools and by individuals no longer associated with the organization. During such a representation, the organization is requested to demonstrate the differences between the current systems and the legacy systems. | * [OPA-DIFF-601] An organization is requested to describe, present, or instantiate a system that was created some past time even perhaps with different knowledge tools and by individuals no longer associated with the organization. During such a representation, the organization is requested to demonstrate the differences between the current systems and the legacy systems. | ||
| * [OPA-SECU-550] An enterprise-scale team which aggregates functional and domain teams from a variety of corporations works contemporaneously and serially on a common problem that requires access to different model elements in different lifecycle phases, different levels of abstraction, in different disciplines, and with different information access rights. | * [OPA-SECU-550] An enterprise-scale team which aggregates functional and domain teams from a variety of corporations works contemporaneously and serially on a common problem that requires access to different model elements in different lifecycle phases, different levels of abstraction, in different disciplines, and with different information access rights. | ||
| + | * [OPA-CREA-101] A stakeholder responsible for modeling a change request to an aspect of the system needs to relate the rationale and decision making criteria to the resultant model change to ensure other stakeholders comprehend the merit behind the change set. | ||
| + | * [OPA-DIFF-610] Two or more stakeholders are collaborating on subsets of a common model. They modify an intersection of content contemporaneously yet in isolation to obtain two or more change sets that differ in their content. They need to merge their respective change sets with the original common model to obtain a well-formed union that is both syntactically and semantically correct. | ||
| ===== Definition of Terms ===== | ===== Definition of Terms ===== | ||
mbse/modelmgt/operational_analysis.1446316207.txt.gz · Last modified: 2015/10/31 14:30 by lvanzandt
Page Tools
