The Visio team would like to congratulate Visio MVP David Parker on his new book, Microsoft Visio 2010: Business Process Diagramming and Validation. This book provides an in-depth coverage of creating custom validation rules in Visio 2010.
After reading Microsoft Visio 2010: Business Process Diagramming and Validation, a few key things were apparent. First, this book covers a variety of topics. The book begins with an overview of process management in Visio 2010 and introduces Visio users to an assortment of new Visio 2010 features. Then two chapters are devoted to the Visio Object Model and the Visio ShapeSheet: powerful tools that combine to provide the unique development experience within Visio. Of course, there is a strong focus on the new validation feature but a reader will learn about a wide range of Visio topics.
Second, the book provides a large quantity of coded examples and even a chapter devoted to a worked example. These clear, well-thought-out examples are great for those who want to experiment in Visio as they read the book.
Finally, the book is a great reference for those interested in building custom validation rules. In Visio 2010, validation enables companies to ensure that their diagrams meet certain compliancy, business standards or more general requirements. Visio provides some built-in validation rules, but anyone can create custom validation rules to meet their own needs: you can specify your own custom diagram requirements, for any type of diagram, and Visio will verify these requirements for you. This book was written to teach people how to master this process of designing, implementing and sharing custom validation rules.
For more information about the book, check out David Parker’s book web site. We also have a chapter from the book, Understanding the ShapeSheet, available on MSDN.
We are looking for some books t purchase for our team. Ideally we would like three books as follows: (but is a book covers more than one topic then we could purchase fewer books);
1) Book that eaplins a process for collecting process information, developing an "as is" process map, identifying opportunities for improvement and devloping 'to be" process maps. We are looking at this from a business perspective, not a technical perspective.
2) Book that explains how to use the BPMN notation to delevlop process maps.
3) Book that explains how to use Visio 2010 to develop BPMN process maps.
We are looking to the books to allow us to have a common methodology for developing process models. We currently have people from a number of industries all with our own approach. A book would give us a starting point for establishing a set of standards and a common approach.