Object-oriented Information Systems Analysis and Design Using UML Paperback – 1 Apr 1999
There is a newer edition of this item:
Customers who viewed this item also viewed
What other items do customers buy after viewing this item?
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Would you like to tell us about a lower price?
If you are a seller for this product, would you like to suggest updates through seller support?
From the Publisher
A new chapter on models, diagrams and the iterative life cycle
Two new Case Study chapters
Updated notation follows the latest version of the UML standard and reflects the most up-to-date approaches to the information systems development process
All chapters have been revised and updated to reflect developments in the world of object-oriented analysis and design --This text refers to an alternate Paperback edition.
About the Author
Simon Bennett (Leicester, UK) is an information systems consultant with Ericsson Intracom Ltd., UK, where he specializes in knowledge management for engineering and Intranet development. --This text refers to an alternate Paperback edition.
Top customer reviews
My problem with this book is that it dwells on a couple of case studies in such a boring wordy way that finding truly useful facts becomes a chore. This book has also tried to be an all-in-one solution to the subject.
If your a student like me who doesn't have enough hours in the day to read all the recommended text thrown your way then I recommend you buy a couple of dedicated books for the same price, one covering just the UML and the other on requirements enginnering.
However, the cover says Object-Oriented Systems Analysis and Design (adding as an afterthought, or so it seems, Using UML). Therein lies the problem, Analysis and Design is precisely that - analysis of software requirements (and I would include in this requirement capture) and design of software through the use of UML. I would expect to see everything to do with use cases, class diagrams and sequence or collaboration diagrams and I would expect to see how the UML model progresses through the stages. I did not see clear evidence of this, and the description of how the model changes is presented in a very weak manner. The example projects, I thought, were boring and half-hearted.
So why are there chapters on Human Computer Interaction and style guides (containing diagrams resembling Jackson Structured Design - its a UML book!). Data Management describing file systems and file organisation (i.e. how data is written to a disk file system - what for?). Relational Database design (someone has to know this, but is it relevant to software objects as to how static data is held). Sections on Implementation, Maintenance and reuse, User Guides, Training and Managing OO projects (What for?). Discussions on waterfall lifecycles without the same emphasis placed on OO lifecyles. These and other topics cover about half the book.
I found the 482 pages very boring, most of which is irrelevant to the topic of systems analysis and design.
This book even as an OO software development book could benefit from 60% of the text being removed and far more diagrams introduced. They seem to be writing for the sake of it. It is complete waffle in places. I do believe it is a book written by academics for academics and students and bears little resemblance to the world of real software development.
Excellent books, even if they are thin, are still purchased by students especially when they get exactly what they are looking for.
Comprehensive, nicely written, excellent examples and an innovative layout with 2 very different but highly explanatory case studies included.. This is a book I expect to hold on to and to refer back to long after my studies are completed.
It's nice to see a book on IT not written by Americans. Good try, but I would recommend looking elsewhere.
You need to read it from start to finish (torture) as it constanstly refers to examples. This makes it useless as a reference book.
It is the recommended text book at my university and has received terrible feedback from all the students.
Most recent customer reviews
Look for similar items by category
- Books > Computing & Internet > Programming > Languages
- Books > Computing & Internet > Programming > Languages & Tools
- Books > Computing & Internet > Programming > Software Design, Testing & Engineering > Design Patterns
- Books > Computing & Internet > Programming > Software Design, Testing & Engineering > UML