Example: mapping table (in E-Parliament Tagger debategraph).


These fields are included in the template to describe a Business object in the work area in which a service solution (product) is expected to offer a number of (information) services:
Field name Description
Name The name of the business object
Description The meaning of the business object; relevant characteristics
Business Rules What rules govern the creation, maintenance and access classification of the business object
Actors The business actors that are interacting with the business object
Product The (business) products in which the object may play a role
Non-functional requirements List non-functional requirements that are specific and important for this business object, tag them as one or more of the listed types of non-functional requirements
Project Issues List project issues that are specific and important for this business object, tag them as one or more of the listed types of project issues

The availability of an enterprise architecture - preferably as part of an enterprise repository - will impact the amount of work that must be invested in describing the business objects that matter to service solutions..

In an enterprise architecture described in accordance with the ArchiMate framework business objects are included in the passive structure aspect of the business layer.


Acknowledgement: Inclusion of Non-functional requirements and Project Issues fields in the template is one of the suggested options in Volère1 and a recommended practice in EMPRESS.



Other sub-sections under Requirements templates and patterns


Questions, answers and comments

Add a New Comment

FAQ