<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:GuidanceDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-Dfe2VkMg04SnJmlyqyKttQ" name="new_reusable_asset,_P91vcLmMEe2ItPaV9bHRfA" guid="-Dfe2VkMg04SnJmlyqyKttQ" changeDate="2023-03-05T20:20:39.173+0330">
  <mainDescription>&lt;p>&#xD;
    After some time team or&amp;nbsp;business exclusive&amp;nbsp;come to this conclusion that a certain part of project or software&#xD;
    is useful and can be used in other projects. This part packaging and put in Enterprise Vendor to reuse in future.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Often, requirements are considered artifacts of a project useful only for the duration of the project. Once the change&#xD;
    is executed, the system is modified, or a new process is established, data and process requirements documentation is&#xD;
    filed away in an archive folder and forgotten.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    This is often a sign of an immature BA practice and a lack of appreciation for the value of reusability. Quality&#xD;
    business requirements can (and should) live beyond the scope of change. Once the change is implemented, the requirement&#xD;
    – the definition of the desired capability – becomes a description of the actual capability.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    In other words, it becomes a snippet of organizational knowledge. Not only this is valuable to the organization’s&#xD;
    knowledge management, implemented requirements can be reused in subsequent initiatives to: Describe the current state&#xD;
    of a business process, function, or capability. Define relationships between business concepts and its data management.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Reflect needs of internal and external personas. Capture key business rules that either need to be maintained by the&#xD;
    new solution or consciously changed. Become templates or starting points for new requirements. Requirement reuse can&#xD;
    lead to a significant reduction in analysis time and improve the overall quality of business analysis outcomes.&#xD;
&lt;/p></mainDescription>
</org.eclipse.epf.uma:GuidanceDescription>
