User Tools

Site Tools


sysml-autoview:se_material

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
sysml-autoview:se_material [2013-03-12 14:05]
araher
sysml-autoview:se_material [2013-03-12 14:49] (current)
araher
Line 1: Line 1:
 ---- ----
 +\\
  
-**Auto View** [[usecases|Use Cases and Scenarios]] ​+[[auto-view_generation_working_group|Auto-View Generation Working Group home page]] - [[requirements|Requirements]] - [[usecases|Use Cases and Scenarios]]
  
 ---- ----
 +\\
 +This page is a rough draft.
  
-====== Requirements ====== 
- 
-We have identified 15 requirements so far. 
- 
-  - Analysis 
-  - Architecture Framework Extensibility 
-  - Configuration Management 
-  - Conformance 
-  - Diagram Views 
-  - Dynamic Views 
-  - Editability 
-  - Executable Independence 
-  - Inclusion 
-  - Interoperability 
-  - Method  
-  - Separation of Models 
-  - Styles 
-  - Tool Independence 
-  - Viewpoint Model 
- 
-^Requirement Name^Requirement^Rationale^Notes^ 
-|Dynamic Views|Viewpoints shall allow for\\ specifying and presenting dynamic Views of the Model.|Views are not static - they can be dynamic. We want to be able to generate any kind view that meets the needs of what we are communicating. This includes animations, interactivity,​ model2model,​ homogeneous,​ heterogeneous. The point is the Expression of the View should only restricted by the needs of communication with stakeholder.|Expression of Views shall support specification of media or format for a range of static and dynamic.| 
-|Styles|The rules for creating the View shall\\ be distinct from the format and presentation styles used to render the View. |This avoids modeling a document directly. it also allows for formats such as slides, interactive web forms, animations etc.|None| 
-|Conformance|The view of the model shall\\ represent the model information in conformance with the rules defined by the viewpoint.|Using a Viewpoint to specify the View  provides a way for stockholders to communicate their expectations with respect to what they will see in the View.|None| 
-|Viewpoint Model|The viewpoint shall include properties for:    ​ 
-  a)    Stakeholders (1..*) 
-  b)    Concerns (1..*) 
-  c)    Purpose (1) 
-|This descriptive information is present to relate the information that describes concerns and purpose of the View to the stakeholders. |Notes| 
-|Method|The viewpoint shall include\\ an executable specification for a method capable of producing the View. |Views of models cannot be created without a concrete explanation of what information is necessary and how it should be communicated.|None.| 
-|Analysis|The viewpoint method shall include provisions to specify: 
-  a)    The query that selects the parts of the model  
-        (e.g., model elements, figures) to be included in the view 
-  b)    Rules to transform the model to another model  
-        (query usecases) 
-  c)    Rules for model checking ​ 
-        (e.g., consistency and/or completeness checking) 
-  d)    Rules to transform the model to another model 
-  e)    Selected output formats ​ 
-        (e.g., doc book, html, excel, ppt ..) 
-  f)    Presentation style (e.g., tabular, text format, ) 
-  g)    Access controls such-as which roles can  
-        create, read, update, and delete information. 
-|Methods need to separate operations on information from format and presentation.|SF update on 12/23/12| 
-|Interoperability|The viewpoint method shall include provisions for: 
-  a)   ​integrating data that is external to the model by reference 
-  b)   ​integrating other text and related information directly 
-|TBD|Under consideration| 
-|Configuration Management|The version of the model and the corresponding views shall\\ be maintained and synchronized as required.|Versions of Views are necessary in order to track the change history.|(Sandy added 12/8/12)| 
-|Editability|The view shall be editable\\ via comments that can be reflected in updates to the model.|Views are inherently interactive where possible. Wether editing a diagram, text or tables |Sandy added 12/8/12| 
-|Inclusion|Shall be capable of including any model element.|The generated document could contain any model element.|Under consideration| 
-|Diagram Views|Diagrams shall be capable of being considered views that conform to Viewpoints.|Diagrams can be considered as a part of the model or as a first-class View of the model.|None.| 
-|Separation of Models|The view model shall be separate\\ from the system model, the format model, and the presentation model.|The document model (definition of chapters, model elements includes, etc.) is separated from the system model.|Under Consideration| 
-|Tool Independence|The definition of the document model\\ shall be tool-independent.|TBD|Under Consideration| 
-|Executable Independence|The viewpoint method shall be independent\\ of a specific modeling tool / version implementation where practical.|Under consideration|Consider a standard api for querying the model)| 
-|Architecture Framework Extensibility|Shall support extension to any\\ compatible architecture framework|The definition of view and viewpoint should be consistent with the latest standard ISO 42010 (to be confirmed)|TBD| 
- 
- 
- 
- 
- 
- 
- 
-====== Qualities ====== 
- 
-^Quality Attribute^Description^Metric^Notes^ 
-|expressivity/​communicability|TBD|TBD|TBD| 
-|extendability|TBD|TBD|TBD| 
-|composability|TBD|TBD|TBD| 
-|reproducibility|TBD|TBD|TBD| 
- 
-====== Principles ====== 
-^Principle^Definition^Rationale^Impact^ 
-|parsimony|TBD|TBD|TBD| 
-|grounded in fundamentals of MBSE - wymore|TBD|TBD|TBD| 
  
 ====== Architectural Decisions ====== ====== Architectural Decisions ======
Line 92: Line 20:
 ** import not scalable. issue is how to specify the argument (model elements as input to) the viewpoint method ** import not scalable. issue is how to specify the argument (model elements as input to) the viewpoint method
 *** describe alternatives:​ method library vs viewpoint library *** describe alternatives:​ method library vs viewpoint library
 +
 +====== Priorities ======
  
 ^Priority^Issue^Description^Rationale^Possible Fixes^Notes^ ^Priority^Issue^Description^Rationale^Possible Fixes^Notes^
Line 104: Line 34:
 |Future|TBD|view is expressed in terms of one to many artifacts such as diagrams, tables, etc. |TBD|TBD|considering adding a concept of a view artifact, where a view is composed of view artifacts| |Future|TBD|view is expressed in terms of one to many artifacts such as diagrams, tables, etc. |TBD|TBD|considering adding a concept of a view artifact, where a view is composed of view artifacts|
 |TBD|TBD|TBD|TBD|TBD|TBD| |TBD|TBD|TBD|TBD|TBD|TBD|
 +
 +====== Principles ======
 +^Principle^Definition^Rationale^Impact^
 +|parsimony|TBD|TBD|TBD|
 +|grounded in fundamentals of MBSE - wymore|TBD|TBD|TBD|
 +
 +====== Qualities ======
 +
 +^Quality Attribute^Description^Metric^Notes^
 +|expressivity/​communicability|TBD|TBD|TBD|
 +|extendability|TBD|TBD|TBD|
 +|composability|TBD|TBD|TBD|
 +|reproducibility|TBD|TBD|TBD|
  
 ====== View Generation Notes ====== ====== View Generation Notes ======
Line 129: Line 72:
  
 -Cory -Cory
- 
-====== Return to View Generation WG Home Page ====== 
-[http://​www.omgwiki.org/​OMGSysML/​doku.php?​id=sysml-autoview:​auto-view_generation_working_group /] 
sysml-autoview/se_material.1363111536.txt.gz ยท Last modified: 2013-03-12 14:05 by araher