Example: mapping table (in E-Parliament Tagger debategraph).
These fields are included in the template to describe a data object in the work area.
|Name||The name of the data object|
|Description||The meaning of the data object; relevant characteristics, refer to business objects if needed|
|Business Rules||What rules govern the creation, maintenance and access classification of the data object|
|Application components||The application components that are accessing the data object|
|Non-functional requirements||List non-functional requirements that are specific and important for this data 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 data 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.
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.