Related products:
Modeling XML Applications with UML: Practical e-Business Applications
Developing Enterprise Java Applications with J2EE and UML
UML Distilled: A Brief Guide to the Standard Object Modeling Language, Third Edition
Applying UML and Patterns : An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition)
|
Uml
Building Web Applications with UML (2nd Edition)
Format: Paperback
Author: Jim Conallen
ReleaseDate: 03 October, 2002
Publisher: Addison-Wesley Professional
Rating:
Good approach but poor depth
The introduction about Web paradigm (you know, client/server architecture, technologies, . It's interesting but it lacks more valued content.. . ) is not useful at all to people looking for uml anaysis and design solutions for it. Anyway I've found it a good lecture for beginners and some intermediates.
why oh why must authors do this.
. I hate it when authors will assume their book is going to read by neophytes so they better include a detailed description of what html is - or what a browser is.. .
Anyone reading this book is probably looking to design enterprise quality web applications using UML. One would think that based on the title at least. . . Which is a fairly advanced goal. How would anyone who requires UML exposure not understand a client-server relationship???
This author wastes time and paper droning on about ridiculously obvious topics. Let me give you an example:::
"HTML defines a set of tags that can be used either to tell the browser how to render something or to define a link to another Web page. All tags are enclosed by angled brackets (< and >). Tags are usually used in pairs, with beginning and ending tags. For example, the emphasis tag: italicizes a word. A sample sentence and the HTML to render it follow:"
WOW!!!! How very relevant!!!!
Anyway he's not the first author to increase the book's shipping weight w/ fluff and he probably wont be the last.
Not useful at all
. The book only covers an overview of modeling, the reference application covers only basic diagraming and looses too much time building diagrams that describe interaction between the web server and the page controller: Aspects already handled automatically by web servers which would be better to oversee.
|
|