During implementation, you can at any time collect and specify requirements with regards to the scope of the implementation project and what need to be done to fit the available business processes to the customer needs. You can also specify requirements when you define the business strategy.
You can link:
- Several requirements to a business process.
- A requirement to several business processes.
Name | Responsible | Description |
---|---|---|
Create requirement on solution |
Business analyst |
During implementation, you can create requirements for your solution and for specific records in your solution. Besides to the solution, you can assign requirements to:
You can assign requirements to these records on the Requirement page (as explained in the steps) and in the Requirements FactBox for these records.
|
Create requirement on scope definition |
Business analyst |
You can create requirements for business processes when you define the scope of the implementation project. |
Create requirement on process verification |
Business analyst |
You can create requirements for business processes when you verify business processes. Usually, you do so for the business processes that you mark as Gap. |
Create requirement on gap analysis |
Business analyst |
You can create requirements for the business processes when you analyze the gaps. Usually, you do so for the business processes that are marked as Gap. |
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. |
Manage requirements |
Business analyst |
Review, estimate, and complete the requirements that are created for the solution. All requirements that are related to a solution are shown at the solution level. If a requirement applies to several records, you can add a relation to these records. |
Create requirement on Business strategy designer |
Business analyst |
You can create requirements for business processes when you define the strategy. You can do so on the Business strategy designer. |
Name | Responsible | Description |
---|---|---|
Create requirement on solution |
Business analyst |
During implementation, you can create requirements for your solution and for specific records in your solution. Besides to the solution, you can assign requirements to:
You can assign requirements to these records on the Requirement page (as explained in the steps) and in the Requirements FactBox for these records.
|
Create requirement on scope definition |
Business analyst |
You can create requirements for business processes when you define the scope of the implementation project. |
Create requirement on process verification |
Business analyst |
You can create requirements for business processes when you verify business processes. Usually, you do so for the business processes that you mark as Gap. |
Create requirement on gap analysis |
Business analyst |
You can create requirements for the business processes when you analyze the gaps. Usually, you do so for the business processes that are marked as Gap. |
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. |
Manage requirements |
Business analyst |
Review, estimate, and complete the requirements that are created for the solution. All requirements that are related to a solution are shown at the solution level. If a requirement applies to several records, you can add a relation to these records. |
Create requirement on Business strategy designer |
Business analyst |
You can create requirements for business processes when you define the strategy. You can do so on the Business strategy designer. |
Related to | Notes |
---|---|
Collect and manage requirements |
  |
Collect and manage requirements |
  |