Reusable Asset: Enterprise Vendor |  |

A Vendor for resuable assets in Enterprise

Relationships

Related Elements

- Add to Vendor
- Architecture Owner
- Coach
- Developer/Designer
- Fetch From Vendor
- Project Manager

Main Description

After some time team or business exclusive come to this conclusion that a certain part of project or software is useful and can be used in other projects. This part packaging and put in Enterprise Vendor to reuse in future.

Often, requirements are considered artifacts of a project useful only for the duration of the project. Once the change is executed, the system is modified, or a new process is established, data and process requirements documentation is filed away in an archive folder and forgotten.

This is often a sign of an immature BA practice and a lack of appreciation for the value of reusability. Quality business requirements can (and should) live beyond the scope of change. Once the change is implemented, the requirement – the definition of the desired capability – becomes a description of the actual capability.

In other words, it becomes a snippet of organizational knowledge. Not only this is valuable to the organization’s knowledge management, implemented requirements can be reused in subsequent initiatives to: Describe the current state of a business process, function, or capability. Define relationships between business concepts and its data management.

Reflect needs of internal and external personas. Capture key business rules that either need to be maintained by the new solution or consciously changed. Become templates or starting points for new requirements. Requirement reuse can lead to a significant reduction in analysis time and improve the overall quality of business analysis outcomes.