Information Technology Reference
In-Depth Information
Ta b l e 3
Requirements on EM
Input models and
documentation
Models to be
developed
EM language
requirements
EM process
requirements
EM tool
requirements
Model quality
requirements
Purpose of EM
Develop the business
Develop visions
and strategy
Existing models and
other business
“blueprints”
GM, CM, BPM and
ARM as well as
inter-model links
Notation that domain
stakeholders
understand
Participatory
Plastic wall, simple
documenting tools
Understandability,
correctness,
simplicity,
flexibility
Design/
Redesign the
business
Vision and strategy
models and other
kinds of business
“blueprints”
Business oriented
models (GM, CM,
BPM, ARM,
BRM) as well as
inter-model links
Notation that domain
stakeholders
understand,
established
notation
Participatory
involving multiple
stakeholder
groups
Plastic wall, EM
tools that makes
it possible to
seamlessly move
to requirements
analysis and IS
design
Completeness,
correctness,
flexibility,
integration,
understandability,
usability
Develop IS
Business oriented
models
IS oriented models
(TCRM) as well
as links with
business oriented
models
Enough formality
and precision to
allow modeling of
complex facts
Partly participatory
and partly analyst
driven
Plastic wall, EM
tools or CASE
tools depending
on the
development
approach
Completeness,
correctness,
flexibility,
integration,
usability
Search WWH ::
Custom Search