Full description not available
E**R
Not a bad book...
I bought the book because it was required for my class. The book seems to have been rushed through editing as it has some serious omissions and numerous typos. Aside from that, there are areas in the book that are almost completely repetitive from previous sections. I suppose it is better to repeat than to leave it out entirely. Overall the book does a decent job explaining a very complex subject.
F**K
A collection of papers and no page numbers
This book has some good aspects but it shows signs of being thrown together as a collection of papers and is thus a little incoherent .One remarkable think however is that it has the distinction of being the only book I have ever owned that has an index (with page numbers) but pages with no pages numbers. If your are relying on finding something in this book via the index - good luck!
A**A
Five Stars
Highly recommend for people who wanted to design any good robotic or control system projects.
L**D
Three Stars
Decent overview for software.
P**I
Recebi o livro em excelente estado
Eu recebi o livro em casa, em otimo estado de conservação. O livro será muito útil na minha pesquisa sobre requisitos.
M**S
UML 2.0 Internals
I found interesting the UML 2.0 internals (meta-models) discussions along with the application of real-time systems design concepts. Also, the ROPES process, as described in this book, is one of the most comprehensive processes aligned with the model-driven architecture (MDA) view of software design and development. In the software industry there is a variety of perspectives, methods and tools for software design, a working knowledge from those (as many as you can) assists to the professional software designer in her daily job.This book makes an excellent presentation of one of those current software design perspectives.
B**M
Good Book.... needs some improvements too.
Focus on State diagrams is excellent. Chapter 1 is redundant. Choice of Examples is good but the examples could have been more simpler. Coherency is missing when the same example is discussed in multiple chapters. It would have been better if different examples are used to explain concepts in different chapters. An must buy book for those who use the related tools.
Trustpilot
1 month ago
2 weeks ago