These fields are included in the template to describe a Business Use Case (BUC) in the work area in which a service solution (product) is expected to provide a number of (information) services:

Field name Description
BUC Name The name of the BUC.
Category One of these options: core, supporting or management.
Trigger The business event(s) that initiate(s) the execution of the business service for which the business use case provides the scenario.
Interfaces The business interfaces that may "receive" a trigger
Goals A goal is an "end state" that must be achieved following the initiation of the use case. Reference can be made to performance indicators.
Primary Actor Who/what is the essential business actor or application component in the successful execution of the work.
Other Actors Who/what else is acting in this BUC? Besides referring to business actors and application components, you may refer to business roles and application functions.
Preconditions What conditions must be satisfied for this BUC to be triggered?
Postconditions Successful the state after the successful execution of the BUC; and Alternative possible other states after the BUC completes.
Workflow-basic The expected or normal flow of events, if possible with annotation indicating service-requirements or automation possibilities. This flow could be described as a business process or as an event and object flow through a chain of business services.
Alternative Workflows The possible alternative flows of events.
Business rules
Business objects The business objects that are used by the BUC.
Non-functional requirements List known or expected properties of the business use case that matter to non-functional requirements and are specific and important for this BUC. Tag these properties with the relevant type of non-functional requirement. Example: if a BUC is typically performed hundred times a day, then this is relevant to the NFR 12f : Performance requirements / Capacity.
Project Issues List project issues that are specific and important for this BUC, tag them as one or more of the listed types of project issues. Example: if the BUC is currently supported by an application X, then this is relevant as a project issue of type PI 22 : Migration to the New Product.

Example of use: New Legislature in ParliamentWatch debategraph.

Acknowledgement: The choice of most fields in the template has been inspired by the Leslie Munday Universe BUC template, modified for use in a DebateGraph. Inclusion of Non-functional requirements and Project Issues fields in the template is one of the suggested options in Volère1 and a recommended practise in EMPRESS2.