Book Image

Open Text Metastorm ProVision 6.2 Strategy Implementation

By : Bill Aronson
Book Image

Open Text Metastorm ProVision 6.2 Strategy Implementation

By: Bill Aronson

Overview of this book

Open Text ProVision® (formerly known as Metastorm ProVision®) is an Enterprise Architecture (EA) solution allowing for effective planning and decision making throughout the enterprise. It enables an organization to have a central repository of information about the business, reducing organizational risks and better optimizing business resources. Implemented well, it enables better and more actionable decisions exactly when you need them.This book combines theory and practice to provide a step- by- step guide to building a successful customer- centric model of your business. The approach is simple and down to earth, and along the way, with various real-world examples, you will learn how to make a business case, use a framework, and adopt a methodology with Open Text ProVision®. This book draws on the experience of ProVision® experts around the world. By combining theory with practice from the field you can avoid common mistakes and develop a successful customer centric strategy for implementing ProVision®. Each chapter builds on the previous one to give you the confidence to implement a central repository, dealing with both the technical and human issues that you might face.
Table of Contents (16 chapters)
Open Text Metastorm ProVision® 6.2 Strategy Implementation
Credits
Foreword
About the Author
About the Reviewers
www.PacktPub.com
Preface
References
Index

Project #3—building System Interaction models


Project #3 develops System Interaction models of the systems that underpin the critical processes identified in Project #2.

The history of the twentieth century is defined by automation. Gradually much work moved from being carried out manually to automatically. Thinking and doing have become separate. More and more repetitive work is done by machines, with analysis and interpretation being done by humans.

We have examined System models earlier on. They are hierarchical models. Workflows are one way to represent the meeting point of systems and processes, System Interaction models show another view and focus on the interface between hardware, software, and location.

We make a distinction between the hardware used and the software that is deployed on the hardware.

The IT department really doesn't need to know too much about the process. All they need to know is which processes a system is involved in. The business doesn't need to understand the complexities...