How can software developers, programmers and managers meet the challenges of the 90s and begin to resolve the software crisis? This book is based on Objectory which is the first commercially available comprehensive object-oriented process for developing large-scale industrial systems. Ivar Jacobson developed Objectory as a result of 20 years of experience building real software-based products. The approach takes a global view of system development and focuses on minimizing the system's life cycle cost. Objectory is an extensible industrial process that provides a method for building large industrial systems. This revised printing has been completely updated to make it as accessible and complete as possible. New material includes the revised Testing chapter, in which new product developments are discussed.
Ivar Hjalmar Jacobson is a Swedish computer scientist and software engineer, known as major contributor to UML, Objectory, Rational Unified Process (RUP), aspect-oriented software development and Essence.
This is another methodology book on Object-Oriented Analysis and Design from the early 90's, and again the same weaknesses come out. Firts, this is a methodology book, with a process to follow step by step. It's higly conceptual and the process starts with analysis down to implementation. Honestly the implementation part doesn't makes sense. The second part on the engineering domain is more original, but still unconvincing : component model, real time, for instance. The third part with case studies should made Jacobson's method more real, but it doesn't. Even the Use Case approach is not very described here. Ma note de lecture en Français ici
An absolute must for professional Software Engineers - the entire software development process done right, including architecture, modelling and software design. A heavy read, too theoretical and abstract, but worth it.
A MUST READ. From the inventor of Use Cases it is the ultimate introduction to the paradigm. The only way to learn how to do the process completely and correctly.
Dari sini nih, saya belajar bagaimana menerapkan pemahaman disain Object Oriented (OO) yg tingkat lanjut (advance) ke dlm teknis pemrograman. Eiiitt... bukan berarti sebelum membaca buku ini saya ndak mengerti cara memrogram secara OO ya, maksud saya, setelah membaca buku ini saya jadi lebih tau bagaimana menuangkan disain OO ke dalam kode program secara tepat.
Metodologi yang dipaparkan oleh buku ini juga masih saya gunakan (setidaknya pada saat comment ini di-post) untuk mengerjakan software2x skala menengah.
Overall a very interesting approach to turning software design into an actual process. The concrete implementations left plenty to be desired and, quite frankly, I think got a lot wrong. In short, the process is sound and intriguing, but it really needs to be matured by seasoned professionals to actually be useful. I don't think that's too hard and it provides some nice starting points.