|
26 of 26 people found the following review helpful:
5.0 out of 5 stars
a practical look on a practical book for VB/COM developers!, December 3, 1999
Subject: FYI: Review of ISBN 0-201-61579-7 Date: Thu, 02 Dec 1999 15:42:30 -0800 From: Ravi <jayanta@silcon.com> To: ra@rosearchitect.com CC: prreed@jacksonreed.com, egb@rational.com, Grant Larsen <glarsen@blueprint-technologies.com>, ckobryn@acm.org, ravindra_tadwalkar@thru-transport.com, jayanta@silcon.com"Developing apps with VB and UML"- a practical look on a practical book for VB/COM developers! After reading this classic down-to-earth book (I bought it at @OOPSLA99, Denver), I was quite happly able to dive in. The book starts with a philosophical theme called "synergy" process, yet another RUP based process model, I thought. But as I started reading further, I felt I should recommend every systems analyst to read from chapter 2 until chapter 7. I liked the appraoch of creating event tables to get to use cases. Salient "analytical" pointers here: chapter 3: "event lists/tables", where an event = subject (actor) + verb + object chapter 4: dissection of the Ivor'y definition of use case; thinking ahead in time of deployment componentized architecture. chapter 5: use case template (looks similar to Alister Cockbern's one); static modeling- particularly "analysis classes" illustrated chapter 6: "screen structure charts" (as a diagram "type") should be a good addition to UML, with some work (-e.g. web UI, Say Grady, Cris?) chapter 7: usage matrices; dynamic modeling (-I like when he says "happy path" of use case, as in `sequence diagram of the happy path' ;-) And as I got to the chapter 8 "technology landscape", the architect in me got hooked onto the rest of the book, since the architectural layers started shaping up. I thought I should recommend every architect and developer (VB or otherwise) in our company to read chapters 8 onwards. Salient "techie" pointers here: Chapter 8: some "anti-patterns" (pp. 194-5) for out-of-process communication in COM.(May be when someone writes a book for EAI modeling audience including me and surely Grady and Cris, s/he will have to scale this beyond DCOM). Chapter 9: design of a persistance framework layer for data access; mapping class design to relational design, rose-scripting for DDL gen. Chapter 10: services layers need for applying the infrastructure for CBD. Chapter 11: layers in depth; Rose/VB RTE -interestingly I am toying around with Rose2000 on cleaner RTE and got some food for beta team. Chapter 12: -- do -- + code change management in VB for enhanced requirements/change requests (VB was known to defy maintenance in past!) Chapter 13: continues constructing distributed implementation with DCOM/MTS Chapter 14: Internet based design issues (-maybe redo screen structure charts now, supplementing with Jim Conallen's web modeling concepts;-) The only glitch in this techie portion of the book is that the author does not mention patterns. Patterns gurus will forgive him for that, I suspect, especially after the trial of the GoF at OOPSLA99 conference at Denver ;-) Now after reading this book, how can I influence our 40+ developers? We are a Microsoft shop, using UML successfully, say 8, on a scale of 1 to 10. We follow a homegrown process based on RUP, to develop software for the global transportation industry, specializing in the supply chain execution space. (-this sounds like a business plan ;-) While reading this book; I kept comparing what we do, how we do that, and where we need to go. I am reasonably clear now. I am sure, like me, after reading this book, you too, regardless of any industry background, will recommend it to COM developer as a compulsory reading after the first compulsion- the astounding UML user guide by Grady. Thanks, Ravindra Tadwalkar Chief Architect, Thru Transport Systems Intl, San Francisco
|