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.
To define the scope and the goals of the review. To define the approaches used for each specific scope/goal combination.
Normally, you should divide the review into the following meetings:
A review of the entire business use-case model.
A review of the business use cases (for each use case), along with their
diagrams. If the model is large, break this review into several meetings,
possibly one per business use-case package.
Even if you can review everything at the same meeting, you probably won’t get
approval of your conclusions the first time. Be prepared to carry out new
reviews for each new version of the business use-case model. It is important to
involve employees, domain experts, as well as members of the
business-engineering team in the review, to make sure the model describes the
business properly.
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.