Information Technology Reference
In-Depth Information
Ta b l e 3
(continued)
Input models and
documentation
Models to be
developed
EM language
requirements
EM process
requirements
EM tool
requirements
Model quality
requirements
Purpose of EM
Ensure the quality of business operations
Ensure
acceptance for
business
decisions
Various types of
business “blueprints”
(e.g. Balanced
Scorecard)
Business oriented
models (GM, CM,
BPM, ARM,
BRM) as well as
inter-model links
Notation that domain
stakeholders
understand
Participatory
involving
knowledge
bearers and users
Plastic wall, simple
tools, tools for
presentation of
models to a wider
audience (e.g.
web-based tools)
Completeness,
correctness,
integration,
simplicity,
understandability,
usability
Maintain and
share
knowledge
about the
business
Business models (GM,
CM, BPM, ARM,
BRM), inter-model
links
“Cleaned” models
that make sense to
a wider audience
Simple and intuitive
modeling
language
Partly participatory,
partly analyst
driven
EM tools with web
interface
Correctness,
integration,
understandability,
usability
Use EM as a problem solving tool
Use EM to
analyze and
solveaspecific
business
problem
Initial problem
statement and other
relevant
documentation
Business oriented
models (GM, CM,
BPM, ARM,
BRM) &
inter-model links
Notation that domain
stakeholders
understand
Participatory
involving multiple
stakeholder
groups
Plastic wall, simple
documenting tools
Correctness,
flexibility,
understandability
Search WWH ::




Custom Search