4 comments about Coloured Petri Nets: Basic Concepts, Analysis Methods and Practical Use (Monographs in Theoretical Computer Science a Series of Eatcs).

1. It is the best book of CPN for the people who intriest in Coloured Petri nets.And it is very helpful to the research fo CPN.Though I haven't owned this book,I wash Icould get it in the near day!



2. I feel that the writing style is a little confusing even though Jensen is a master. I also recommend to integrate the three volume to one due to the simplicity and vol. 2 just took 182 pages. In addition, the notations relatively differ from the ones in Peterson's Petri nets.



3. I feel that the writing style is a little confusing even though Jensen is a master. I also recommend to integrate the three volumes to one due to the simplicity and vol. 2 just took 182 pages. In addition, the notations relatively differ from the ones in Peterson's Petri nets.



4. I feel that the writing style is a little confusing even though Jensen is a master. I also recommend to integrate the three volumes to one due to the simplicity and vol. 2 just took 182 pages. In addition, the notations relatively differ from the ones in Peterson's Petri nets.

No comments about Turbo Language Essentials.

No comments about Creacion de efectos con InDesign/ The InDesign Effects Book (Diseno Y Creatividad / Design and Creativity).

No comments about Computer Programming in Basic (Software Solutions Series).

No comments about Visual Basic 6.0 - Edicion Profesional En Un.

No comments about Visual Basic .net (Manuales Imprescindibles / Essential Manuals).

No comments about Visual Basic 2005.

3 comments about Iterative UML Development Using Visual Basic 6.0.

1. This book really is more about project management; UML and its application within a VB project to the authors, seems optional. Here's were the book goes bad: 1) There are no UML syntax definitions.

   2) There is no hard reference to UML tools, not even Visual Modeler.

   3) The VB source code for the Case Study is passed over in abut 10 pages. (the author seem more comfortable with project management)

   4) The CD-ROM is one big promotion for Visio, there is source code but the source is not eve rapped up in a Visual Molder file and you get a MS Project outline of their proposed method (ooh! hold me back)

   If you are looking for a book on project management and team development organization, this book is for you. "If you are looking for a no-nonsense book on UML for busy developers looking to unleash the strength of the UML" (from the books intro), this is not the book for you, don't waste your money. If you fall in the later category try "Developing Applications with Visual Basic and UML"

   _shawn




2. This book has a total of 27 pages dedicated to UML. The remaining content is primarily focused on project management and UML is only used in the examples. Even the quality of the project management content is questionable.

   The authors focus on the top down approach. Management makes all decisions. Programmers are considered to be nothing more than allocable resources, despite the fact that they have in-depth knowledge of the technology. A recent project undertaken by my company followed this development process. After two years and six million dollars, there were no deliverables and most involved were no longer with the company. Instead of accepting input from the staff programmers, the management gained all their information from salesmen and sales presentations.

   If you are looking for a UML book, this book will not fulfill your requirements. Therefore, I give it one star.




3. If you want to learn to develop software using UML with VB then don't get this book. It won't help at all. It doesn't explain how to use UML, and it doesn't explain how to develop VB code based on UML diagrams.

   The book has a lot on project management, but I found this also completely useless. There is a huge case study of a concert booking and ticket sales system, which is a good idea, but any meaningful information is lost in a sea of extra-verbose descriptions of what all the different 'architects' are doing and how they are being motivated to do a good job. It's like trying to learn UML and how it gets transformed into VB code by reading the verbal description of a very detailed workflow chart in Microsoft Project.

   If you're interested in a good beginning book on UML with a useful case study, try "Sams Teach Yourself UML in 24 Hours" by Joseph Schmuller (2nd edition).

   Don't waste your money on this book.

No comments about Maximizing Windows 98.

No comments about Microcomputer Systems and Apple Basic.