Average Reviews:
(More customer reviews)I was surprised to find no image of the cover of this book and no customer reviews. At the second thought, it makes sense. This book is for IT practitioners with solid theoreteical background in Computer Science. The book is not complex, but requires patience. It is about all the object-oriented theory behind the most fundamental behaviour of object instances - Create - Read - Update - Delete. All explained in terms of theory of sets using logical predicates, which is part of formal logics.
Anyway, once I bought and read this book in 1998 - 5 years ago - I was hooked on object orientation. Microsoft's ADO, J2EE's EJB's and JDO instantly and naturally made sense to me once they surfaced in IT practice as newly emerged technologies.
I have impressed and opened the eyes of many people of intelligence with my super deep understanding of these issues yet numerous hight tech red necks vere left unmoved.
If you want to feel CRUD and brearth CRUD in Obj-Orient. terms, plus to have really deep knowledge of Object-toRelational mapping, buy it and read it. Plus, buy Kilov's 'Business Specifications' book.
Click Here to see more reviews about: Information Modeling: An Object-Oriented Approach
Many of today's business information systemsare notoriously ineffective — due in large part to too many unscientific,haphazard approaches to their development. This book introduces thescientific thought essential to understanding a business and to creatinga successful business information system for a particular business.It shows how to make system analysis as disciplined an activity asprogramming, and how the formal specification of behavior at the rightlevel of abstraction is the desired approach to system analysis. KEYTOPICS: Shows how the system analyst may use the same conceptsof "good thinking"as the programmer — abstraction, preciseunderstanding of behavior, and reuse — to end up with a specificationthat is understandable and formal. For systems analysts,requirements engineers, data modellers, business planners, etc. responsiblefor understanding and developing requirements for information systemsand applications; and for designers, programmers , testers, documentorsinvolved in the information system development process.
Click here for more information about Information Modeling: An Object-Oriented Approach
No comments:
Post a Comment