Home » Business Process Modeling, Development, Flowcharting, News, Process Management, Tools, Visio 2010

New Book: Visio 2010 Rules, Validation & Business Process Diagramming

Visio 2010 Premium introduces powerful mechanisms for validating diagrams to insure graphical and semantic correctness. Not only does this feature allow end-users to check and correct their diagrams, it enables developers to create custom rule sets to validate corporate- or discipline-specific diagrams.

David Parker’s new book: Microsoft Visio 2010 Business Process Diagramming and Validation explains Visio diagram validation, the APIs behind it, and helps you to build tools to make it all easier!

You know from his blog and previous work: Visualizing Information with Microsoft Office Visio 2007, that David Parker produces high-quality work. I’m sure that we can expect the same from this book.

The book explains the new validation rules features of Visio 2010, including how to validate diagrams, create new rule sets, publish them, and understand the automation APIs behind them. The book takes you through the development of the RulesTools suite of utilities. RulesTools help you to create, explore and apply validation rules. By building the tools chapter-by-chapter, you will learn how to incorporate validation into your own custom Visio 2010 add-ins and solutions.

Here’s a screenshot of RulesTools in action:

click to view larger image

This book is intended for technical types and developers. While the book is aimed at Visio 2010 Premium, users of the Standard and Professional editions will still find much of it useful. To understand the code and add-in-creation portions of the book, knowledge of .NET will also help. Expertise in business process diagramming is not necessary, however.

Get the book here: Microsoft Visio 2010 Business Process Diagramming and Validation.

Below, I’ve included the preface and table-of-contents from the book to give you more information about what’s inside!

Microsoft Visio 2010 Business Process Diagramming and Validation

This is what Parker’s new book would look like if you went to the book store, pulled it off the shelf and held it in your hands.

Here’s the front:

click to view larger image

And here’s the back:

click to view larger image


Once the creators of Aldus PageMaker, had delivered Desktop Publishing to the masses, they then decided that they could make a smarter diagramming application. Eighteen months later, they emerged with the Visio product. Now they needed to get a foothold in the market, so they targeted the leading process flow diagramming package of the day, ABC Flowcharter, as the one to outdo. They soon achieved their aim to become the number one flowcharting application, and so they went after other usage scenarios, such as network diagramming, organization charts and building plans. In 1999, Microsoft bought Visio Corporation and Visio gradually became Microsoft Office Visio, meaning that all add-ons had to be written in a certain manner, and the common Microsoft Office core libraries like the Fluent UI were ever more increasingly employed.

Flowcharting still accounts for 30% of the typical uses that Visio is put to, but the core product did not substantially enhance its flowcharting abilities. There were some add-ons that provided rules, perhaps most notably for Data Flow Diagrams (which came and went); UML and Database Modelling, and many third parties have built whole flowcharting applications based on Visio. What all of these enhancements have in common is the imposition of a structure to the diagrams, which necessarily means the adoption of one rule set or another. There are a lot of competing and complementary rule sets in use, but what is important is that the chosen rule set fits the purpose it is being used for, and that it can be understood by other related professionals.

It is true that a picture is worth a thousand words, but the particular thousand words understood by each individual are more likely to be the same if the picture was created with commonly available rules. The structured diagramming features and Validation API in Visio 2010 enable business diagramming rules to be developed, reviewed and deployed. The first diagramming types to have these rules applied to are process flowcharts, reminiscent of the vertical markets attacked by the first versions of Visio itself, but these rules can and will be extended beyond this discipline

Table of Contents


Chapter 1 – Overview of Process Management in Microsoft Visio 2010

This chapter introduces the new features that have been added to Microsoft Visio to support structured diagrams and validation. You will see where Visio fits in the Process Management stack, and explore the relevant out of the box content.

Chapter 2 – Understanding the Microsoft Visio Object Model

This chapter explains the Microsoft Visio 14.0 Type Library and the key objects, collections, and methods in the programmer’s interface of Visio, where relevant for structured diagrams.

Chapter 3 – Understanding the ShapeSheet

This chapter explains the Microsoft Visio ShapeSheet and the key sections, rows and cells, and functions available for writing ShapeSheet formulae, where relevant for structured diagrams.

Chapter 4 – Understanding the Validation API

This chapter explains the Microsoft Visio Validation API and the key objects, collections, events and methods in the programmer’s interface for Visio diagram validation.

Chapter 5 – Developing a Validation API interface

Microsoft Visio 2010 does not provide a user interface to the Validation API for rules developers to use, so this chapter is devoted to building a useful tool, called Rules Tools, to enable the tasks to be performed easily.

Chapter 6 – Reviewing Validation Rules and Issues

This chapter will extend the tool, started in Chapter 5, to provide an import/export routine of rules to an XML file, or to an HTML report, and a feature to add issues as annotations in Visio diagrams.

Chapter 7– Creating Validation Rules

In this chapter, the tool created in the previous chapter to create rules for structured diagramming will be used. This chapter will look at common ShapeSheet functions that will be useful for rules, and the new Validation functions. It will also go through different scenarios for creating rules, especially with regard to Filter and Test Expressions.

Chapter 8 – Publishing Validation Rules and Diagrams

This chapter will go through different methods for publishing Visio validation rules for others to use.

Chapter 9 – A Worked Example for Data Flow Model Diagrams

This chapter presents a complete cycle for writing validation rules for the Data Flow Model Diagram methodology. Validation rules are created using the Rules Tools add-in developed in previous chapters, although alternative VBA code is provided.

What you need for this book

Microsoft Visio 2010 (Premium Edition for some of the content)
Microsoft Visio 2010 SDK
Optionally, Microsoft Visual Studio 2010 with knowledge of C#

Who this book is for

This book is primarily for Microsoft Office Visio users or developers who want to know how to use, and extend, the new Validation Rules in Microsoft Office Visio 2010 Premium Edition. There are some rule sets available out of the box, but the capability can be added to many sorts of diagramming, whether they are process flows, network cabling drawings or risk dependency diagrams, for example. This is not a Visio SmartShape developer manual or a Visio automation guide, although these subjects are explored when relevant for writing validation rules, but it does shed light on the possibilities with this new powerful feature of Microsoft Office Visio 2010. This book will be an essential guide to understanding and creating structured diagramming rules, and will add developer tools that are not in the out-of-the-box product.

Update: Get a free Sample Chapter for Rules & Validation Book!

Microsoft Visio 2010 Business Process Diagramming and Validation


Leave a comment!

Add your comment below, or trackback from your own site. You can also subscribe to these comments via RSS.

Be nice. Keep it clean. Stay on topic. No spam.

You can use these tags:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code lang=""> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong> <pre lang="" extra="">

This is a Gravatar-enabled weblog. To get your own globally-recognized-avatar, please register at Gravatar.