Examples of use:
These fields are included in the template to describe an (existing) business product. An existing business product may matter to a requirements engineering initiative for a new product because the latter will depend on the former for providing its services.
|Name||The name of the business product|
|Interfaces||Via which (business) interfaces does the product provide its services|
|Services||Which (business) services does the product provide?|
|Business roles||Which business roles are defined in the agreements defining the product|
|Business objects||Which business objects are involved in the providing of the product's services|
|Non-functional requirements||List non-functional requirements that are specific and important for the product, 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 the product, 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 both existing products and products that must be designed and developed.
In an enterprise architecture described in accordance with the ArchiMate framework: business product descriptions are included in the business layer. The rationale for their inclusion in a requirements engineering initiative will often be related to their role in business collaborations among business actors.