What do you think?
Rate this book
Business Objects: Re-Engineering for Re-Use
Business Re-engineering for re-use is one of the first books to describe a revolutionary new way to build much better computer systems. Unlike other computing revolutions, this is not concerned with technology or computer languages.
Instead it involves changing the way we see (and so think about) the things that information stored in computers represents - what is called our paradigms. These currently have antiquated entity-oriented foundations that were developed to work with paper and ink technology. Until recently system builders were embedding these in computer systems. They are now starting to update the paradigms, bringing them into line with computer technology. They are re-engineering their entity foundations, transforming their business entities into more general, and so more re-usable, business objects. This makes the business paradigms (and so computer systems) both much simpler and functionally richer.
Instead it involves changing the way we see (and so think about) the things that information stored in computers represents - what is called our paradigms. These currently have antiquated entity-oriented foundations that were developed to work with paper and ink technology. Until recently system builders were embedding these in computer systems. They are now starting to update the paradigms, bringing them into line with computer technology. They are re-engineering their entity foundations, transforming their business entities into more general, and so more re-usable, business objects. This makes the business paradigms (and so computer systems) both much simpler and functionally richer.
- GenresBusiness
442 pages, Paperback
First published June 1, 1996
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 - 2 of 2 reviews
November 3, 2023
Many people recommend this book as a fundamental for system thinking. But honestly... I found no single idea or concept that is new to a software engineer in 202x.
Not trying to say the book is bad. But it was written in 1996, and if some of the ideas were fresh and original back then, today it's like "Well... thanks for spending so much time explaining common sense things".
Not trying to say the book is bad. But it was written in 1996, and if some of the ideas were fresh and original back then, today it's like "Well... thanks for spending so much time explaining common sense things".
May 13, 2021
Одна из инженерных основ системного мышления.
Displaying 1 - 2 of 2 reviews