It is a nego- tiated settlement of competing interests and aims. In this case, OMG initially tried to take its abstract, language-independent Business Process Definition Metamo- del and simply rebrand it BPMN 2.0, even though its graphical notation, almost an afterthought, had only passing resemblance to BPMN 1.2 and its terminology no similarity at all.

The content of this book is fully copyrighted under international copyright law and may not be distributed or data extracted therefrom without written permission by the publisher, Future Strategies Inc.

You are licensed to print one copy for your own use.This Extract from the Digital Edition is licensed for your personal enjoyment only.

To license multiple copies for distribution in a library or academic environment, please contact the publisher.

ISBN-13: 978-0-9819870-7-1 (Digital Edition) All brand names and product names mentioned in this book are trademarks or service marks of their respective companies.

Any omission or misuse should not be regarded as intent to infringe on the property of others.

The Publisher recognizes and respects all marks used by companies, manufacturers and developers as a means to distinguish their products.

The authors and the publisher expressly disclaim all implied warrantees, including merchantability or fitness for any particular purpose.

There will be no duty on the authors or Publisher to correct any errors or defects in the software.

No part of this work covered by the copyright hereon may be reproduced or used in any form or by any meansgraphic, electronic, or mechanical, including photocopying, recording, taping, or information storage and retrieval systemswithout written permission of the publisher, except in the case of brief quotations embodied in critical articles and reviews.

Publishers Cataloging-in-Publication Data Library of Congress Catalog Card LCCN No.

BPMN 2.0 Handbook:Layna Fischer (editor) p.

Includes bibliographical references, appendices and index.

Business Process Management Notation.

BPMN 2.0 Standard 3.

Technological Innovation.

Business Process Management.

Business Process Technology.

Organizational Change 7.

We now have a tool-independent graphi- cal process definition language that is widely adopted by both business and IT for purposes ranging from basic process documentation to detailed performance analysis, requirements specification, and executable design.

While the notation on the diagram surface seems little changed from BPMN 1.2, under the covers there is much that is new: a formal UML metamodel, more precisely defined operational semantics, and an XML Schema and conformance classes supporting model in- terchange.

As such it represents something new for a broad spectrum of process modelers, from business process analysts and architects to BPM academics to process automation engine designers.

The BPMN 2.0 Handbook illustrates this diversity of interest in the new standard.

We also have many suggestions for how BPMN could be extended, improved, or enhanced to meet the broader goals of business process management.

One thing you wont read much about in the Handbook is the arduous path and hard work it took to complete the BPMN 2.0 specification.

I was a fringe member of the BPMN 2.0 team from the fall of 2008 until publication of the beta spec and launch of the Finalization Task Force (FTF) in the summer of 2009.

As such I got to see for myself how this sausage was made, and as you might suspect, it was not a pretty sight.

I tried to represent the interests of the majority of existing BPMN users, typically business process analysts and architects modeling non- executable processes, and I often felt overwhelmed by the focus on process execu- tion.

But however frustrating the process seemed at times, it was ultimately fair and achieved a remarkable result.

For that we owe a debt of gratitude to the managers of the BPMN 2.0 spec development effort in OMG.

We owe an equally large debt to two Handbook authors, Robert Shapiro and Denis Gagn, who suc- ceeded where I could not in two critical parts of the specprocess modeling con- formance classes and a proper XML schema for diagram graphics information developing and driving them from near-oblivion at the start of FTF to inclusion in the final standard.

When model interchange among BPMN tools eventually be- comes commonplace, we will all have Robert and Denis to thank.

What most people fail to realize is that a specification as wide-ranging as BPMN 2.0 is of necessity a political document as much as a technical one.

It is a nego- tiated settlement of competing interests and aims.

Real-Life Bpmn Pdf