sysml-autoview:usecases
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
sysml-autoview:usecases [2013-03-12 14:38] araher |
sysml-autoview:usecases [2013-03-12 15:12] (current) araher |
||
|---|---|---|---|
| Line 5: | Line 5: | ||
| ---- | ---- | ||
| + | |||
| ====== Use Cases and Scenarios ====== | ====== Use Cases and Scenarios ====== | ||
| - | ====Categories of Use Cases==== | + | The five categories of use cases we have identified are defined in the table below. In the rest of the page, each category is documented in detail in its own table. |
| ^Category^Use case pertains to^ | ^Category^Use case pertains to^ | ||
| Line 19: | Line 20: | ||
| - | ====Analysis Use Cases==== | + | ======Analysis Use Cases====== |
| ^ID^Usecase family^Usecase qualifier^Scenarios^Notes^ | ^ID^Usecase family^Usecase qualifier^Scenarios^Notes^ | ||
| Line 27: | Line 28: | ||
| |21|I have a broken view|I want to debug an error in the view model|TBD|TBD| | |21|I have a broken view|I want to debug an error in the view model|TBD|TBD| | ||
| - | + | ======Method Use Cases====== | |
| - | + | ||
| - | ====Method Use Cases==== | + | |
| ^ID^Usecase family^Usecase qualifier^Scenarios^Notes^ | ^ID^Usecase family^Usecase qualifier^Scenarios^Notes^ | ||
| Line 48: | Line 47: | ||
| |33|I have several Viewpoints|I want Viewpoint A to be composed of Viewpoint B such that when I instance Viewpoint A, Viewpoint B is instanced as well.|TBD|TBD| | |33|I have several Viewpoints|I want Viewpoint A to be composed of Viewpoint B such that when I instance Viewpoint A, Viewpoint B is instanced as well.|TBD|TBD| | ||
| - | + | ======Organization Use Cases====== | |
| - | ====Organization Use Cases==== | + | |
| ^ID^Usecase family^Usecase qualifier^Scenarios^Notes^ | ^ID^Usecase family^Usecase qualifier^Scenarios^Notes^ | ||
| Line 55: | Line 53: | ||
| - | ====Presentation Use Cases==== | + | ======Presentation Use Cases====== |
| ^ID^Usecase family^Usecase qualifier^Scenarios^Notes^ | ^ID^Usecase family^Usecase qualifier^Scenarios^Notes^ | ||
| Line 71: | Line 69: | ||
| |34|I have an ordered collection of composed views.|I want to view and edit the collection of views. This includes editing properties of the model or adding narrative to the view tree. All changes made online should be ingested back into the model.|TBD|TBD| | |34|I have an ordered collection of composed views.|I want to view and edit the collection of views. This includes editing properties of the model or adding narrative to the view tree. All changes made online should be ingested back into the model.|TBD|TBD| | ||
| - | ====Viewpoint Instance Use Cases==== | + | ======Viewpoint Instance Use Cases====== |
| - | ^ID^Category^Usecase family^Usecase qualifier^Scenarios^Notes^ | + | ^ID^Usecase family^Usecase qualifier^Scenarios^Notes^ |
| - | |1|Viewpoint Instance| I have a viewpoint that renders a table whose first column is the name of the blocks within scope and the second column is the documentation of each block. |I want to conform two views (which may be in separate documents) to this viewpoint. The only difference between the views is that for one view I want the header of the table columns to be “Block, Definition” and the other view I want the header of the table columns to be “Service, Description.”|Viewpoint describes certain parameters like recursion depth or header names or font colors. need to be able to set them in the view when they are view specific. this is BST for Viewpoints and Views.|TBD| | + | |1| I have a viewpoint that renders a table whose first column is the name of the blocks within scope and the second column is the documentation of each block. |I want to conform two views (which may be in separate documents) to this viewpoint. The only difference between the views is that for one view I want the header of the table columns to be “Block, Definition” and the other view I want the header of the table columns to be “Service, Description.”|Viewpoint describes certain parameters like recursion depth or header names or font colors. need to be able to set them in the view when they are view specific. this is BST for Viewpoints and Views.|TBD| |
| - | |2|Viewpoint Instance|I have a viewpoint that renders a table whose first column is the name of all Operation elements within scope and the second column is their corresponding parameters. |I want to specialize this viewpoint such that the table renders only Operation elements that additionally have a stereotype applied from another profile e.g., «function». The only thing I want to specify about the new viewpoint is the additional stereotype filter.|How do we specialize methods and rules etc. example Definition table with additional languages. everything else should inherit directly.|TBD| | + | |2|I have a viewpoint that renders a table whose first column is the name of all Operation elements within scope and the second column is their corresponding parameters. |I want to specialize this viewpoint such that the table renders only Operation elements that additionally have a stereotype applied from another profile e.g., «function». The only thing I want to specify about the new viewpoint is the additional stereotype filter.|How do we specialize methods and rules etc. example Definition table with additional languages. everything else should inherit directly.|TBD| |
| - | |4|Viewpoint Instance|I have a set of viewpoints. |I want to render the viewpoints in a particular read order, including section (e.g., a viewpoint composed into another viewpoint) I want to be able to assert the composition and order at the viewpoint level such that when “first” viewpoint is instanced the subsequent compositioned views are also created with their read order intact.| define a template for a view tree such that the views and the read order are the same for multiple view trees.|TBD| | + | |4|I have a set of viewpoints. |I want to render the viewpoints in a particular read order, including section (e.g., a viewpoint composed into another viewpoint) I want to be able to assert the composition and order at the viewpoint level such that when “first” viewpoint is instanced the subsequent compositioned views are also created with their read order intact.| define a template for a view tree such that the views and the read order are the same for multiple view trees.|TBD| |
| - | |6|Viewpoint Instance|I have a view. |I want to include the same view in two different documents.|Allow x-references to existing views|TBD| | + | |6|I have a view. |I want to include the same view in two different documents.|Allow x-references to existing views|TBD| |
| - | |9|Viewpoint Instance|I have a set of views|I want to model how those views are presented in a document, i.e. a document outline|TBD|TBD| | + | |9|I have a set of views|I want to model how those views are presented in a document, i.e. a document outline|TBD|TBD| |
sysml-autoview/usecases.1363113491.txt.gz · Last modified: 2013-03-12 14:38 by araher
Page Tools
