Note: Supplemental materials are not guaranteed with Rental or Used book purchases.
Purchase Benefits
What is included with this book?
Dr. Ivar Jacobson,Vice President of Business Engineering, is the inventor of the OOSE method, and he is also the founder of Objectory AB in Sweden, which recently merged with Rational Software Corporation. Dr. Jacobson is the principal author of two influential and best-selling books Object-Oriented Software Engineering--A Use Case Driven Approach (Computer Language Productivity award winner in 1992) and The Object Advantage--Business Process Reengineering with Object Technology. He has also authored several widely referenced papers on object technology. One of the most famous papers is his first OOPSLA '87 paper entitled "Object-Oriented Development in an Industrial Environment," which presented the first truly object-oriented method ever published. Ivar Jacobson's use-case driven approachhas had a very strong impact on the entireOOAD industry, and he himself has become one of its "icons." Consequently, he isa frequently invited keynote speaker and panelist, debating OOAD topics withcolleagues and methodologists such as Grady Booch, Jim Rumbaugh, StevenMellor, and Rebecca Wirfs-Brock at major OO conferences around the world.
He is well known for his pioneering work and more than 20 years of experience inusing object methods for the design of large real-time systems. His earlyobject-based design technique has evolved into the international standardITU(formerly CCITT)/SDL.
Dr. Jacobson also regularly serves on the OOPSLA, ECOOP, and TOOLSprogram committees, and he is a member of the advisory board of the Journal ofObject-Oriented Programming.
In 1994, Ivar Jacobson received the first Swedish Computer Association (SCA)award (the Kjell Hultman prize) for "extraordinary achievement in promotingefficiency and productivity in the development and use of informationtechnology."
Patrik Jonsson works at Rational Software Corporation in Sweden as a Senior Consultant where he has been developing the architecture and method of the Objectory process with a current focus on reuse and user interface development.
Introduction | |
System development as an industrial process | |
Introduction | |
A useful analogy | |
System development characteristics | |
Summary | |
The system life cycle | |
Introduction | |
System development as a process of change | |
System development and reuse | |
System development and methodology | |
Objectory | |
Summary | |
What is object-orientation? Introduction | |
Object | |
Class andinstance | |
Polymorphism | |
Inheritance | |
Summary | |
Object-oriented system development Introduction | |
Function/data methods | |
Object-oriented analysis | |
Object-oriented construction | |
Object-oriented testing | |
Summary | |
Object-oriented programming Introduction | |
Objects | |
Classes and instances | |
Inheritance | |
Polymorphism | |
An example | |
Summary | |
Concepts | |
Architecture Introduction | |
System development is model building | |
Model architecture | |
Requirements model | |
Analysis model | |
The design model | |
The implementation model | |
Test model | |
Summary | |
Analysis Introduction | |
The requirements model | |
The analysis model | |
Summary | |
Construction Introduction | |
The design model | |
Block design | |
Working with construction | |
Summary | |
Real-time specialization Introduction | |
Classification of real-time systems | |
Fundamental issues | |
Analysis | |
Construction | |
Testing and verification | |
Summary | |
Database Specialization Introduction | |
Relational DBMSObject DBMSDiscussion | |
Summary | |
Components Introduction | |
What is a component?Use of components | |
Component management | |
Summary | |
Testing Introduction | |
On testing | |
Unit testing | |
Integration testing | |
System testing | |
The testing process | |
Summary | |
Applications | |
Case study: warehouse management system Introduction to the examples | |
ACME Warehouse Management Inc | |
The requirements model | |
The analysis model | |
Construction | |
Case study: telecom Introduction | |
Telecommunication switching systems | |
The requirements model | |
The analysis model | |
The design model | |
The implementation model | |
Managing object-oriented software engineering Introduction | |
Project selection and preparation | |
Project development organization | |
Project organization and management | |
Project staffing | |
Software quality assurance | |
Software metrics | |
Summary | |
Other object-oriented methods Introduction | |
A summary of object-oriented methods | |
Object-Oriented Analysis (OOAD/Coad-Yourdon) | |
Object-Oriented Design (OOD/Booch) | |
Hierarchical Object-Oriented Design (HOOD) | |
Object Modeling Technique (OMT) | |
Responsibility-Driven Design | |
Summary | |
Appendix A On the development of Objectory Introduction | |
Objectory as an activity | |
From idea to reality | |
References | |
Index | |
Table of Contents provided by Publisher. All Rights Reserved. |
The New copy of this book will include any supplemental materials advertised. Please check the title of the book to determine if it should include any access cards, study guides, lab manuals, CDs, etc.
The Used, Rental and eBook copies of this book are not guaranteed to include any supplemental materials. Typically, only the book itself is included. This is true even if the title states it includes any access cards, study guides, lab manuals, CDs, etc.