Business views are a semantic data layer that can be used as a basis for the various Application Lifecycle Management (ALM) reporting tools.
The views are based on project entities, and ensure that only information that is relevant to a business consumer is revealed in a report. For example, you can select only those defect related entity fields that represent some business value to a report consumer. You then create a unique view which can be used and reused as a report basis.
For example, a business view based on Baselines could contain the Name, Description, and Baseline ID fields. This is because these fields convey information that could be of importance to the graph consumer who needs to understand baseline information from a business perspective only. By the same logic, the same business view does not include the Attachment and Auto complete type fields, as they are of little business significance.
Creating reports based on business views ensures standardization across the reports, as different reports that are based on the same business view reflect a common frame of reference. This provides genuine business value to the reports consumer, thereby making the reports more meaningful.
Note: Reports are generated according to the permission levels of the user generating them. Therefore, information that is included in a business view that is not available to a user will not appear in any report that user creates.
Business views can be based on a single project entity (for example, defects), or can represent more complex relationships between several entities (for example, defects, requirements, and tests). ALM provides a set of pre-defined business views that are available for selection.
Business views must be designed by a user who understands the business requirements of the organization. In addition, the process of creating business views utilizes DQL, a domain query language that is a flavor of ANSI SQL. It is important that the business view designer be able to understand DQL queries. For details on working with DQL, see Working with DQL.