Справочная таблица: Business Use Cases |
|
|
This checklist helps make sure that a business Use-Case description is complete and accurate |
|
Взаимосвязи
Элементы справочной таблицы
General
-
Is its name and brief description clear and easy to understand, even to people outside the business-engineering
team?
-
Is the name of each business use case consistent with its description?
-
Does the name of each business use case indicate the result?
-
Does the business use case support at least one business goal?
-
Is the intent and purpose of the business use case clear?
-
Are the supported business goals consistent with the purpose of the business use case?
-
Is each business use case meaningful and complete from an outside (actor's) perspective?
-
Is each business use case involved with at least one actor?
-
Is each core business use case involved with at least one business actor?
-
Is each supporting business use case involved with at least one business actor? If not, it has to be initiated by
an internal event, and does not have to interact with a business actor to perform its activities.
-
Is the business use case workflow clear and understandable?
-
Is the wording informal enough to be understood by people outside the project team?
-
Does it describe the workflow, and not just the purpose of the business use case?
-
Does it describe the workflow from a external viewpoint?
-
Does the use case perform only activities inside the business?
-
Are all possible activities that belong to the use case described?
-
Are only business actors that interact with the use case mentioned?
-
Are only activities that belong to the business use case described?
-
Does it mention only business use cases with which it is connected?
-
Does it clearly indicate when the order of activities is not fixed?
-
Is the workflow well-structured?
-
Are the start and end of the workflow clearly described?
-
Is each extend-relationship described clearly so that it is obvious how and when the use case is inserted?
-
Has a business worker been identified as the business use case owner?
|
For abstract business use cases, you may add
-
Is the business use case substantial enough to be an abstract business use case on its own?
-
Does it contain logically related activities?
-
Is there a reason for the business use case to exist?
|
|
© Copyright IBM Corp. 1987, 2006. Все права защищены..
|
|