We have identified 15 requirements so far.

1. Analysis
2. Architecture Framework Extensibility
3. Configuration Management
4. Conformance
5. Diagram Views
6. Dynamic Views
7. Editability
8. Executable Independence
9. Inclusion
10. Interoperability
11. Method
12. Separation of Models
13. Styles
14. Tool Independence
15. Viewpoint Model

a)    Stakeholders (1..*)
b)    Concerns (1..*)
c)    Purpose (1)

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.

a)   integrating data that is external to the model by reference
b)   integrating other text and related information directly

*view centric over document centric → views and viewpoints over documents and sections *method - > reproducible *viewpoint composition → *libraries - > reusability

*Write up general issue of scalability viewpoint methods aren't executable 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

From Cory Casanave in an email to Len Levine on December 7, 2012: The following is the in-progress definitions being developed as part of the MDA guide:

View and Viewpoint A viewpoint specifies a reusable set of criteria for the construction, selection, and presentation of a portion of the information about a system, addressing particular stakeholder concerns. The by far most widely used construct since 1976 is the SQL view construct.

A view is a representation of a particular system that conforms to a viewpoint. We could, for example, have a view representing the security concerns of a payroll system.

For example, if we are creating a model information of a system that shares information there may be views for:

• The meaning of the information to be shared
• How the information is to be structured when shared
• What information is to be shared with whom and under what conditions
• The protocol by which the information consumer requests or is sent the information
• What technology is used to actually transmit the information (in a technology model, not in a conceptual model)
• How the information is protected during transmission
• How we identify the parties involved
• How the shared information is derived from our internal data

Note that the above views are interrelated, that is there are connections between them that are contained in the ground level, the model and the metamodel but that may or may not be visible in any one viewpoint.

—editorial— While not specifically addressed, I think the intent is that a diagram is part of (could be all of) a view and that a diagram type is part of (could be all of) a viewpoint.

-Cory

[http://www.omgwiki.org/OMGSysML/doku.php?id=sysml-autoview:auto-view_generation_working_group /]