Purpose
  • To formally verify that the results of business analysis modeling conform to the stakeholders' views of the business.
Role:  Technical Reviewer 
Frequency: As required, typically once for each iteration that includes business analysis modeling activities.
Steps
Input Artifacts:  Resulting Artifacts:   
Tool Mentors:   
More Information: 

Workflow Details: 

General Recommendations To top of page

Purpose General recommendations for each review.

A person acting as business-model reviewer has some essential knowledge of the business domain or the technology envisioned to automate the business. Another skill business-model reviewers need is detailed knowledge of the applied business engineering techniques.

Recommended Review Meetings To top of page

Purpose To define the scope and the goals of the review.
To define the approaches used for each specific scope/goal combination. 

If the model is large, you will have to examine different aspects of the business analysis model at separate review meetings. The following meetings are recommended:

  • Review of the survey of the business analysis model, not looking at details of the business workers and business entities.
  • Review of the business use-case realizations.

Prepare Review Record and Document Defects To top of page

Purpose To document the review results.
To ensure that identified defects are documented. 

Following each review meeting, the results of the meeting are documented in a Review Record. In addition, any defects are documented in accordance with the project's change management process.



Rational Unified Process   2003.06.13