Process Model
A
process model is a
modeling work product that models
operational requirements in terms of
actors and their associated
use
cases.
The typical objectives of a process model are to:
- Provide an analysis of operational requirements.
- Provide a way to specify operational requirements.
The typical benefits of a process model include:
- It can be used to develop functional test suites of test
cases.
- It can be used to schedule the development effort.
- It helps set the scope, size, and complexity of the
application.
The typical contents of a process model are:
- Context Specifications:
- Use Case Specifications:
The typical stakeholders of a process model are:
- Producer:
- Evaluator:
- Approvers:
- Maintainers:
- Users:
-
Requirements Team, which uses the use case model to
analyze requirements and specify them in the system
requirements specification.
A process model is typically developed during the following
phases:
A process model can typically be started if the following
preconditions hold:
The typical inputs to a process model include:
- Work Products:
- Stakeholders:
- This is a living model that is developed incrementally
and iteratively in parallel with other work products (e.g.,
system requirements specification).
- Different parts of this model are due at different times:
- Context specifications before corresponding use case
specifications.
- Actor specifications before corresponding use case
diagrams.
- Some parts of this model are typically mandatory (actor
specifications) whereas some parts are optional (activity
diagrams).
- Identify and reuse use cases by using a combination of:
- The standard function to use case mapping
- The major functions listed in the
application vision statement
- Reusable requirements based on functional areas (e.g.,
Content Management).
A process model is typically constrained by the following
conventions:
- Business enterprise process model
- Application process model
- Component process model
- Framework process model