What is a View

On Dragon1, a view is defined as a filter of a model for certain data entities.

An example of a view is: Functionally fit Applications.

This would filter out / hide all applications that are not functionally fit.

Often a view is a meaning aspect or subset of a model.

Other examples of views are:

Technically fit applications
Standards Compliant applications
Cost Heat map application

Dynamic Views

Views are dynamic or real-time. So when the data in the model changes, the view changes.

Viewpoints

A viewpoint is the (abstract) point or location from which a stakeholder is looking at data.

A stakeholder has needs and interests because of his or her experience, expertise, job or role. So there are things they find important to see, understand or know. With views, we can provide that.

Viewpoint examples are: IT Management Viewpoint, TAX Viewpoint, Security Viewpoint, Privacy Viewpoint

A view can be linked to a stakeholder view a viewpoint.

Setting Views via Classes, Attributes and Values

The easiest way of settings views is via Classes. If you provide one or more classes for a view, then these data objects match these classes.

If you provide an attribute and a value, then Dragon1 will only let through data objects that match with these classes, attributes and values.

Setting Views via Relationships

A second way of setting up a view is via relationships. If you provide a relationship in the collaboration application, the Dragon1 will only let through data objects that have a matching relationship.

Setting Views via Rules

The third way of setting up a view is configuring rules.

If you configure one or more rules, Dragon1 will only let through data objects that match the rules.

JSON Example

The JSON definition of a simple view is:

{"class":"view", "name":"functionally fit view", "classes":"application", "attributes":"tag", "values":"functionally fit"}