Index
A
- actor, enterprise designer framework elements
- naming convention / Naming convention
- permitted objects / Permitted objects
- permitted models / Permitted models
- relationships / Relationships
- comments / Comments
- ADM
- Requirements Management process / TOGAF9
- agile management
- about / Agile Management
- waterfall approach / Agile Management
- governance structure, implementing / Governance and leadership
- leadership / Governance and leadership
- measurement / Measurement
- stand-up meetings, conducting / Have daily stand-up meetings
- simple model, keeping / Keep it simple
- combined working / Work in pairs
- appreciative inquiry
- ArchiMate
- about / How frameworks can confuse
- Archimate-enterprise designer objects comparison
- business role / Business role
- business collaboration / Business collaboration
- business interface / Business interface
- enterprise designer / Enterprise Designer
- business object / Business object
- business process / Enterprise Designer
- business function / Business function
- business interaction / Business interaction
- business event / Business event
- business service / Business service
- representation / Representation
- meaning / Meaning
- value / Value
- product / Product
- contract / Contract
- ArchiMate, features / What ArchiMate has that Enterprise Designer doesn't
- architectural framework
- levels / Architecture or design
- rules / Architecture or design
- attributes / Comments
B
- benefits, central repository
- designed to scale / Designed to scale
- multiple usage / Store once, reuse many times
- working collaboratively / Working collaboratively
- architecture / Architecture or design
- decision making / Better decisions now
- BPM
- business class models, building
- business context, Metastorm Provision®
- recommendations / Recommendation
- business framework
- about / What is a business framework
- cons / How frameworks can confuse
- clarifying / Making sense of frameworks
- metaphors / Making sense of frameworks
- business framework, components
- customers / Customers
- products and services / Products and services
- critical processes / Critical processes
- critical elements / Critical elements
- goals / Goals
- business rules, enterprise designer framework elements
- defining / Business rules
- naming convention / Naming convention
- permitted objects / Permitted objects
- permitted models / Permitted models
- relationships / Relationships
- comments / Comments
C
- CIF / Linking to other sources
- CMDB / Comments
- computer system, enterprise designer framework elements
- naming convention / Naming convention
- permitted objects / Permitted objects
- permitted models / Permitted models
- relationships / Relationships
- comments / Comments
- critical elements, business framework components
- actors / Actors
- business rules / Business rules
- computer systems / Computer systems
- data / Data
- events / Events
- facilities / Facilities
- Gear (equipment) / Gear (equipment)
- Critical Process model
- Help / Critical Process model
- about / Critical Process model
- building, steps / Steps
- tips / Tips
- Customer Product model / Next phase
D
- data, enterprise designer framework elements
- naming convention / Naming convention
- permitted objects / Permitted objects
- permitted models / Permitted models
- relationships / Relationships
- comments / Comments
E
- elements, enterprise designer framework
- actor / Actor
- business rules / Business rules
- computer system / Computer system
- data / Data
- gear / Gear
- Enterprise Designer
- enterprise designer framework
- basic components / Enterprise Designer framework
- components, defining / How to read this section
- elements, defining / Seven elements A—G
- processes, classifying / Ten processes H—Q
- receivables / Receivables and services
- service / S—Service or product
- customer / Customers and clients, Markets
- oragnizations / Organizations
- goals / Goals
- eTOM / How frameworks can confuse
- about / eTOM (enhanced Telecom Operations Map)
- enterprise designer framework, aspects / eTOM (enhanced Telecom Operations Map)
- business functions / Is it a service or a process?
- consistent framework / Consistent framework
- deliverable models / Deliverable models
- Event model
- diagram / Comments
- events, enterprise designer framework elements
- about / Event
- naming convention / Naming convention
- permitted objects / Permitted objects
- permitted models / Permitted models
- relationships / Relationships
- comments / Comments
- receivable event / Comments
F
- facility, enterprise designer framework elements
- naming convention / Naming convention
- permitted objects / Permitted objects
- permitted models / Permitted models
- relationships / Relationships
- comments / Comments
- FEA
- about / Federal Enterprise Architecture
- components / Federal Enterprise Architecture
- project preparation, steps / Federal Enterprise Architecture
- evidence / Evidence
- lifecycle, script / Evidence
- framework
- uses / How frameworks can confuse
G
- gear,enterprise designer framework elements
- naming convention / Naming convention
- permitted objects / Permitted objects
- permitted models / Permitted models
- relationships / Relationships
- comments / Comments
- goals, enterprise designer framework
- naming convention / Naming convention
- permitted objects / Permitted objects
- permitted models / Permitted models
- relationships / Relationships
- comments / Comments
- vocational / Comments
- workflow / Comments
- X Factor / Comments
- Your Funder / Comments
- Customer / Comments
- governance
- about / What is governance
- governance structure modeling, Metastorm ProVision® used
- procedures / Policies and procedures, No need for everything
- information, linking to sources / Linking to other sources
- information, visualizing / Visualize information
- processes / Processes
H
- high level model, building
- steps / Project #1—building the high-level model
- preparing, steps / Preparation
- Customer model, building / Customer model
- tips / Tips
- product and service model / Product and Service model, Tips
- Critical Customer Product model / Critical Customer Product model, Steps, Tips
I
- idea communication
- steps / Four steps
K
- Knowledge Exchange
- features / Sharing models without Knowledge Exchange®
L
- level1-level 2 framework comparison
- ArchiMate framework / ArchiMate framework
- Archimate-enterprise designer objects comparison / ArchiMate and Enterprise Designer objects comparison
- level1-level 3 framework comparison / Comparing level 1 and level 3 frameworks
- leverage
- about / Leverage
- sample development program / Sample development program
M
- Metastorm
- objects / Object
- link / Link
- model / Model
- notebooks / Notebook and file
- repositories / Repository
- strengths / Open Text Metastorm's unique strengths
- advantage / The competitive advantage
- network, defining / Comments
- technology, defining / Comments
- platform, defining / Comments
- Metastorm BPM
- about / Open Text Metastorm BPM
- Metastorm ProVision®
- governance structure, modeling / Modeling a governance structure with ProVision®
- using, steps / Policies and procedures
- ProVision, features / ProVision® features and functionality
- Knowledge Exchange, features / ProVision® features and functionality
- features / ProVision® features and functionality
- grid format / Model and grid
- information, interpreting / Model and interpret
- simulating / Model and simulate
- executing / Model and execute
- Metastorm Provision®
- need for / Why choose ProVision®
- problem solving, features / Why choose ProVision®
- differences / Why choose ProVision®
- personal context / Personal context
- business context / Business context
- next phase / Next phase
- methodology
- about / What is a methodology
- projects / What is a methodology
- high level model, building / Project #1—building the high-level model
- workflow models, building / Project #2—building workflow models
- business class models, building / Project #4—building Business Class models
- organization models, building / Project #5—building Organization models
- case study / Case study—the consultant's view
- model
- motorola
- process / Motorola change process
N
- Navigator Model / Relationships
O
- operations / Comments
- oragnizations, enterprise designer framework
- naming convention / Naming convention
- permitted objects / Permitted objects
- permitted models / Permitted models
- relationships / Relationships
- comments / Comments
- organization models, building
- about / Project #5—building Organization models
- critical elements / Other critical elements
- business rule models / Business Rule models
- event models / Event models
- outside-in approach
P
- personal context, Metastorm Provision®
- time / Time
- responsibility / Responsibility
- scope / Scope
- scope, project scope / Project scope
- scope, enterprise scope / Enterprise scope
- platform / Comments
- processes, enterprise designer framework
- naming convention / Naming convention
- permitted objects / Permitted objects
- permitted models / Permitted models
- relationships / Relationships
- comments / Comments
- Help / Comments
- Inform / Comments
- Join / Comments
- Collect / Comments
- Logistics / Comments
- Market / Comments
- New / Comments
- Organize / Comments
- Pay / Comments
- Quit / Comments
- process modeling
- process modeling, tips
- process owner, identifying / #1 Identify and engage the process owner
- process owner, engaging / #1 Identify and engage the process owner
- people, communicating with / #2 Talk to the people who deal with errors
- what aspect / #3 Capture the current "What" in detail but not the "How"
- process simplification / #4 Reduce moments of truth
- handoffs, reducing / #5 Reduce handoffs
- non-essential checking, eliminating / #6 Eliminate non-essential checking
- high volume processes focus / #7 Focus on high-volume processes
- right process, implementing / #8 Implement the right process for right now
- enterprise designer processes, using / #9 Use the 10 Enterprise Designer processes
- automation / #10 Don't automate a broken process
- backword, modeling / #11 Bonus tip—model backwards
- project implementation
- about / Implementation
- components, lists / Lists
- lists, building / Building your lists
- information, gathering / Who is responsible for initially gathering the information
- objects, naming / How do you name objects
- object maintainence, ensuring / Who ensures that the object is maintained
- object storage, location / Where is the object stored
- model publishing, process / What is the publishing process for models
- information transfer, from Metastorm ProVision® / How do you move the information from another system to ProVision®
- project management methodology
- about / Project management methodology
- business framework, components / Build sequence
- ProVision
- about / Visio or ProVision
- features / Visio or ProVision
- objects / Everything is an object
- limitations / Modeling, not configuration management
R
- receivables, enterprise designer framework
- naming convention / Naming convention
- permitted objects / Permitted objects
- permitted models / Permitted models
- relationships / Relationships
- comments / Comments
- referencing
- about / Visio or ProVision
S
- SCI / Six step processsix step processdiagrammatic view
- service, enterprise designer framework
- naming convention / Naming convention
- permitted objects / Permitted objects
- permitted models / Permitted models
- relationships / Relationships
- comments / Comments
- six step process
- diagrammatic view / Six step processsix step processdiagrammatic view
- agenda / Agenda
- Fact find / feel find / Fact find/feel find
- present / Present
- pause / Pause
- summary / Pause
- open / Open
- states / Comments
- strategy
- about / Strategy
- dividing, on key aspect basis / Strategy
- The business case / The business case
- The framework and methodology / The framework and methodology
- The toolset / The toolset
- Governance / Governance
- Strategy / Five goals V—Z
- System Interaction Model
- diagram / Comments
- about / Relationships
- system interaction models, building
T
- Tactic / Five goals V—Z
- transformation
- distinguishing, from change / Distinguishing between change and transformation
- transformation, qualities
- emotional color / Distinguishing between change and transformation
- cheap / Distinguishing between change and transformation
- respect / Distinguishing between change and transformation
- acceptance / Distinguishing between change and transformation
- self remembering / Distinguishing between change and transformation
V
- Visio
- about / Visio or ProVision
- using / Visio or ProVision
W
- workflow models, building
- about / Project #2—building workflow models
- Critical Process model / Critical Process model
- steps / Steps, Steps
- tips / Tips, Tips