Thank you for that review. Please show in one of the future videos a difference between viewpoint and model view. As one of the benefits coming from modeling.
"A Viewpoint is a specification of the conventions and rules for constructing and using a view for the purpose of addressing a set of stakeholder concerns. The languages and methods for specifying a view may reference languages and methods in another viewpoint. They specify the elements expected to be represented in the view, and may be formally or informally defined. For example, the security viewpoint may require the security requirements, security functional and physical architecture, and security test cases." -SysML Book You can look at figure B27 on page 183 of the SysML book for a pictural example. In simple terms. A "view" is another word for diagram. "Viewpoint" is not a diagram; it is an element in the model. The viewpoint has attributes to fill out such as stakeholders, concerns, purpose, etc. You can think of it like a requirement element where your requirement has a text field to input data. The view is connected to the viewpoint with a conform relationship. Hope this helps.
Thank you for that review. Please show in one of the future videos a difference between viewpoint and model view. As one of the benefits coming from modeling.
"A Viewpoint is a specification of the conventions and rules for constructing and using a view for the purpose of addressing a set of stakeholder concerns. The languages and methods for specifying a view may reference languages and methods in another viewpoint. They specify the elements expected to be represented in the view, and may be formally or informally defined. For example, the security viewpoint may require the security requirements, security functional and physical architecture, and security test cases." -SysML Book
You can look at figure B27 on page 183 of the SysML book for a pictural example.
In simple terms. A "view" is another word for diagram. "Viewpoint" is not a diagram; it is an element in the model. The viewpoint has attributes to fill out such as stakeholders, concerns, purpose, etc. You can think of it like a requirement element where your requirement has a text field to input data. The view is connected to the viewpoint with a conform relationship.
Hope this helps.