Name: Software Reuse By Ivar Jacobson
SKU: 9780201924763
Price: 11.69 USD
Availability: InStock

Software Reuse Summary

Software Reuse: Architecture, Process and Organization for Business Success by Ivar Jacobson

"How can I incorporate reuse into my complex software development process in order to gain a competitive edge?" This is a question that many have attempted to answer by taking up object technology, with varying degrees of success. In Software Reuse: Architecture, Process and Organization for Business Success , the authors present a brand new, technically innovative, coherent and systematic model for implementing reuse. They have combined their experience in the fields of object oriented software engineering, business engineering and systematic software reuse to create the Reuse-Driven Software Engineering Business (Reuse Business) framework. Software Reuse: Architecture, Process and Organization for Business Success - introduces the concept of software reuse as a business success enable - describes how the right architecture allows applications and components to evolve gracefull - provides guidelines for implementing software engineering processe - advises on organizational issues such as the structure, transition, day-to-day managment, economics and measurement. Whether you are a software engineer, architect, designer, programmer or manager, whether you are familiar with the concepts of reuse, component-based software engineering, object oriented technology and business engineering or not, you should read Software Reuse: Architecture, Organization and Process for Business Success. In it you will find new ground-breaking information and advice Visit the Rational Web Site http://www.rational.com

Software Reuse Reviews

"There is still a lot of controversy about whether object-oriented software reuse really pays off. This book provides not only many successful examples from Griss' work at Hewlett-Packard, Jacobson's work at Ericsson, and elsewhere, but also an experience-based approach for repeating the successes. The approach involves not just a class-library silver bullet, but an integrated strategy involving business-case analysis, domain engineering, product line architecting, people and process management, and life-cycle software asset management. A particularly nice feature of the book is a reuse-oriented tailoring of the Jacobson-Booch-Rumbaugh Unified Modeling Language." Barry Boehm, TRW Prof of Software Engineering, Director of Center for Software Engineering University of Southern California. "This book tells it as it is: reuse is a business as well as a technical decision that requires engineering discipline and management support. If you are serious about improving your software development productivity and reducing your time to market by making OO work for you, then read this book. You won't be disappointed!" Will Tracz, Senior Programmer in Advanced Technology, Lockheed Martin Federal Systems. "This book is comprehensive in its coverage of the fundamentals of software reuse, the subject that is catalysing the transformation of our industry from a craft to an engineering discipline. I commend Jacobson, Griss and Jonsson for their important contribution to the field." Paul Bassett, Senior Vice President Research, Netron Inc. "This is the best book on software reuse I've ever seen. It should be on the desk of every project manager who wants to improve productivity, quality and timeliness in software development." David Taylor, President, Enterprise Engines Inc.

Preface Systematic software reuse What is this book about? Who needs a Reuse-Driven Software Engineering Business? The essence of the Reuse-Driven Software Engineering Business Our experience How this book is organized What this book offers Acknowledgments Dedications PART I - INTRODUCING THE REUSE-DRIVEN SOFTWARE ENGINEERING BUSINESS 1. Software Reuse Success Factors 1.1 Software reuse is a simple idea 1.2 Components are fueling a revolution in application development 1.3 A systematic approach makes pragmatic reuse work 1.4 Ericsson and Hewlett-Packard reuse experience reveals common principles 1.5 Reuse requires changes in process 1.6 Reuse requires changes in organization 1.7 Adopt reuse systematically and incrementally 1.8 Input from other reuse programs 1.9 It takes a set of principles 1.10 Summary 2. Reuse-Driven Software Engineering Is A Business 2.1 Is it a business for you? 2.2 Make reuse cost-effective 2.3 A Reuse Business has business characteristics 2.3 Architect components and applications 2.4 Software engineering processes 2.5 Establishing and managing a reuse business 2.6 Summary PART II - ARCHITECTURAL STYLE 3. Object-Oriented Software Engineering 3.1 Software engineering transforms requirements into code 3.2 Software engineering is a team process 3.3 Software engineering is systematic model building 3.4 Objects unify the modeling process 3.5 The use case model captures system requirements 3.6 The analysis model shapes system architecture 3.7 The design model defines the implementation 3.8 The implementation model is the code 3.9 The test model validates the system 3.10 Summary 4. Application And Component Systems 4.1 Application developers can reuse OOSE model components 4.2 Application families allow significant reuse 4.3 Application systems are built from reusable components 4.4 Group components into component systems 4.5 Facades control access to component system internals 4.6 Facades and component systems are special kinds of packages 4.7 Component systems export components via facades 4.8 Specialize some components before reuse 4.9 Variability occurs at variation points 4.10 Use several kinds of variability mechanisms 4.11 Reuse variable components to build application systems 4.12 Package and document component systems for reuse 4.13 Summary 5. Use Case Components 5.1 Structure the use case model to ensure component reuse 5.2 The use case model shapes the rest of the system 5.3 Reusing components to build the use case model 5.4 Design the use case components for effective reuse 5.5 Not all use cases should be reusable components 5.6 Reusing concrete or abstract actor and use case components 5.7 Expressing use case variability 5.8 Packaging and documenting use case components 5.9 Summary 6. Object Components 6.1 Object models define system architecture and design 6.2 Reusing analysis and design components 6.3 Expressing variability in object model components 6.4 Tracing use case variability to the object models 6.5 Reusable analysis components 6.6 Subsystem components group related classes 6.7 Reusable design and implementation components 6.8 Packaging and documenting object components and variants 6.9 Summary 7. Layered Architecture 7.1 Architecture defines system structure, interfaces and interaction patterns 7.2 A good architecture is crucial to maintain system integrity 7.3 A layered architecture organizes software according to generality 7.4 A layered architecture reduces software dependencies 7.5 The middleware layer supports distributed object computing 7.6 The business-specific layer supports rap

Additional information

Sku

GOR001444295

ISBN 13

9780201924763

ISBN 10

0201924765

Title

Software Reuse: Architecture, Process and Organization for Business Success by Ivar Jacobson

Author

Ivar Jacobson

Series

Object Technology Series

Condition

Used - Very Good

Binding type

Paperback

Publisher

Pearson Education Limited

Year published

1997-06-26

Number of pages

528

Prizes

N/A

Cover note

Book picture is for illustrative purposes only, actual binding, cover or edition may vary.

Note

This is a used book - there is no escaping the fact it has been read by someone else and it will show signs of wear and previous use. Overall we expect it to be in very good condition, but if you are not entirely satisfied please get in touch with us

Software Reuse Ivar Jacobson

Software Reuse by Ivar Jacobson

Summary

Software Reuse Summary

Software Reuse: Architecture, Process and Organization for Business Success by Ivar Jacobson

Software Reuse Reviews

Table of Contents

Additional information

Customer Reviews - Software Reuse