1. Data Management
  2. RapidValue
  3. General
  4. Publish
  5. Publish documents

Publish business process implementation documents

In RapidValue, you can publish several types of business process implementation documents:

  • Scope statement
  • Process verification
  • Gap analysis


Business analyst Business analyst Publish scope statement Publish scope statement You can publish a document with the scope statement of a solution. For each milestone, only the business processes that are in scope are added to this document. You can configure the level of detail of the information that is added to the document. You can find and download the published document on the Business process file share workspace, on the Documents tab. Procedure 1. Click Business process implementation. 2. Click Publish. 3. Click Scope statement. 4. On the Publish Scope statement document dialog, define the required settings and click OK. Notes You can also publish a scope statement document from the Scope definition page. To do so, click Publish, Scope statement. On the Publish scope statement document dialog, you can define these settings: Language - If you have defined translations for the solution, select the language in which you want to publish the solution. The elements in your solution that are not translated into this language are published in the original language. You can only publish in another language if this language is defined for the solution itself. So, for example, all content of the solution is translated to a specific language. However, no translation for this language is defined for the solution itself. In this case, you cannot publish in this language.Include business strategy - If this check box is selected, the strategy, as defined for the solution, is added to the document. This includes: Mission statement, goals, and metrics.Include business process descriptions - If this check box is selected, for each business process that is added to the document, the description is also added to the document.Scope and gap summary - If this check box is selected, for each business process that is added to the document, information is given on its scope and gap categorization. For example: This process is out of scope, categorized as fit.Include version number - If this check box is selected, the version number of each element is added to the document.Include change history - If this check box is selected, the change history of each element is added to the document.Number of change history records - You can define the maximum number of change history records that is published for each element. For example, if you enter 3, only the latest three changes to the element are published. Publish process verification Publish process verification You can publish a document with the result of the process verification of a solution. Only the business processes that are in scope are added to this document. Separate chapters are created for the business processes with gaps and the business processes that fit. You can configure the level of detail of the information that is added to the document. You can find and download the published document on the Business process file share workspace, on the Documents tab. Procedure 1. Click Business process implementation. 2. Click Publish. 3. Click Process verification. 4. On the Publish Business process verification document dialog, define the required settings and click OK. Notes You can also publish a process verification document from the Verify processes page. To do so, click Publish, Process verification. On the Publish business process verification document dialog, you can define these settings: Language - If you have defined translations for the solution, select the language in which you want to publish the solution. The elements in your solution that are not translated into this language are published in the original language. You can only publish in another language if this language is defined for the solution itself. So, for example, all content of the solution is translated to a specific language. However, no translation for this language is defined for the solution itself. In this case, you cannot publish in this language.Include business process descriptions - If this check box is selected, for each business process that is added to the document, the description is also added to the document.Scope and gap summary - If this check box is selected, for each business process that is added to the document, information is given on its scope and gap categorization. For example: This process is out of scope, categorized as fit.Include version number - If this check box is selected, the version number of each element is added to the document.Include change history - If this check box is selected, the change history of each element is added to the document.Number of change history records - You can define the maximum number of change history records that is published for each element. For example, if you enter 3, only the latest three changes to the element are published. Publish gap analysis Publish gap analysis You can publish a document with the result of the gap analysis of a solution. To each business process with requirements defined, a table is added with the requirements. For the not-business-process-specific requirements for the solution, a table is added in a separate 'General requirements' chapter. For each requirement, this information is shown: Requirement, Type, Status, Priority, Estimate, and Activity. You can configure the level of detail of the information that is added to the document. You can find and download the published document on the Business process file share workspace, on the Documents tab. Procedure 1. Click Business process implementation. 2. Click Publish. 3. Click Gap analysis. 4. On the Publish Gap analysis document dialog, define the required settings and click OK. Notes You can also publish a gap analysis document from the Analyze gaps page. To do so, click Publish, Gap analysis. On the Publish gap analysis document dialog, you can define these Parameters: Language - If you have defined translations for the solution, select the language in which you want to publish the solution. The elements in your solution that are not translated into this language are published in the original language. You can only publish in another language if this language is defined for the solution itself. So, for example, all content of the solution is translated to a specific language. However, no translation for this language is defined for the solution itself. In this case, you cannot publish in this language.Business processes - Define which business processes are added to the document. All - All business processes in the selected solution are added to the document.In scope - Only the business processes that are in scope are added to the document.Gaps - Only the business processes that are marked as a gap are added to the document Include business process descriptions - Set to Yes to add, for each business process that is published to the document, the description as well.Scope and gap summary - Set to Yes to give, for each business process that is added to the document, information on its scope and gap categorization. For example: This process is out of scope, categorized as fit.Scenarios - Set to Yes to publish business processes of type Scenario to the document.Attachment lists - Set to Yes to add a list with attachments to each business process or activity with attachments.Include version number - Set to Yes to add the version number of each element to the document.Include change history - Set to Yes to add the change history of each element to the document.Number of change history records - You can define the maximum number of change history records that is published for each element. For example, if you enter 3, only the latest three changes to the element are published.On the Publish gap analysis document dialog, you can define these Requirements settings:Requirement details - Set to Yes to add the description for each requirement in a separate section below the requirements table.Status - For each of the possible requirement statuses indicate if requirements with that status must be published to the document. Publish requirements specification Publish requirements specification You can publish a document with the requirements specification of a solution. You can configure the level of detail of the information that is added to the document. Procedure 1. Click Business process implementation. 2. On the Requirements tab, in the list, find and select the requirements to be published. 3. Click Publish. 4. Click Requirements specification. 5. On the dialog, define the required settings. 6. Click OK. Notes On the Publish requirements specification document dialog, you can define these settings:Attachment lists - If this check box is selected, a list with attachments is added to each business process or activity with attachments.Include version number - If this check box is selected, the version number of each element is added to the document.Include change history - If this check box is selected, the change history of each element is added to the document.Number of change history records - You can define the maximum number of change history records that is published for each element. For example, if you enter 3, only the latest three changes to the element are published. Start Start End End

Activities

Name Responsible Description

Publish scope statement

Business analyst

You can publish a document with the scope statement of a solution. For each milestone, only the business processes that are in scope are added to this document. You can configure the level of detail of the information that is added to the document.

You can find and download the published document on the Business process file share workspace, on the Documents tab.

Publish process verification

Business analyst

You can publish a document with the result of the process verification of a solution. Only the business processes that are in scope are added to this document. Separate chapters are created for the business processes with gaps and the business processes that fit.

You can configure the level of detail of the information that is added to the document.

You can find and download the published document on the Business process file share workspace, on the Documents tab.

Publish gap analysis

Business analyst

You can publish a document with the result of the gap analysis of a solution.

To each business process with requirements defined, a table is added with the requirements. For the not-business-process-specific requirements for the solution, a table is added in a separate 'General requirements' chapter. For each requirement, this information is shown: Requirement, Type, Status, Priority, Estimate, and Activity.

You can configure the level of detail of the information that is added to the document.

You can find and download the published document on the Business process file share workspace, on the Documents tab.

Publish requirements specification

Business analyst

 		You can publish a document with the requirements specification of a solution. You can configure the level of detail of the information that is added to the document.

Provide feedback