Books and Info for object oriented design & analysis OOD OML UML books ood/a uml oml adarts OO D&A UML rational rose OOD OML UML BOOKS ood/a uml oml adarts OO D&A UML rational rose OOD OML UML Books ood/a uml oml adarts OO D&A UML rational rose

Object Oriented Design & Analysis using UML

Object Oriented Design & Analysis books
Internet Design & Web programming books

OOD/A Synopsis:
Today, a software designer or architect who seeks to represent the design of a software system can choose from a wide variety of notational languages, each aligned with a particular analysis and design methodology. Ironically, this wide variety of choice is one impediment to the significant benefits promised by software reuse. The emergence of the Unified Modeling Language (UML)-created by the joint efforts of leading object technologists Grady Booch, Ivar Jacobson, and James Rumbaugh with contributions from many others in the object community-represents one of the most significant developments in object technology.

Unified Modeling Language (UML) is the leading notation used by the three most popular object orientated design & analysis methodologies (OOD/OOA): Booch, OOSE (use-cases) and OMT.
UML is the most widely used modeling language that can be used with any of these methods and according to Grady Booch :
Method = Notation + Process

Notations:
Boochgram notations emphasized the concepts of Modularity and Encapsulation. The key advance, from a software engineering perspective, was to place primary emphasis on designing software as interacting "modules" For implementation, classes provide the obvious mechanism for modules. The mechanisms of namespaces (in C++) and packages (in Java and Ada) provide additional support in larger systems.
Cloud or Blob notations emphasized the concepts of Abstraction and Generalization. The key advance was to move from specific single instances of modules to many instances (many "objects" from a given "class"). Classes themselves could be instances of metaclasses, or completed from partial specifications (generic units, or templates). For implementation, C++'s notion of classes as types, and templates as partial specifications for classes, both support these ideas. Another important step forward was the concept of Inheritance as a key type of relationship between modules. Together with polymorphism, the essential ingredients for object-oriented programming are used with this notation. For implementation, derived classes and virtual functions provide the key mechanisms.
The Unified Modeling Language (UML) notation is an iterative refinement, based on experience gained over a decade, improving and formalizing the most effective parts of these prior notations. The key advance is an increased emphasis on object interaction and statechart diagrams. These give an equal emphasis to the dynamic behavior in a design.

Process:
The major phases in the Unified Process are Inception, Elaboration, Construction, and Transition and each phase has a number of iterations. Each process phase produces different work products including a business model, use cases, class diagrams, sequence and collabration diagrams. The incremental/iterative process of OOA/D is an improved element for this method. In most software development organizations today, their software process definition (if they have one at all) is typically based on the so-called "waterfall" model. This model dictates that all requirements analysis be completed before doing any design, all design be completed before doing any implementation, that all implementation be completed before doing any testing, and that all testing be completed before release. The incremental/iterative process is a much lower-risk approach, by getting a core subset of the product designed, implemented, and tested early. Using this core subset, the product evolves towards its final form -- with an explicit goal of encouraging end-user feedback. Such a process can lead to a product that is much more effective at satisfying the end users real requirements. Of course, this approach has its hazards, without a strong configuration management discipline, a software project can find itself in chaos. It's especially deadly if the feedback from end users causes major upheaval in the design continuously, preventing the product from approaching a steady-state design that can be implemented and released.

OOD, OOA, UML, OML Books :

Uml Distilled : Applying the Standard Object Modeling Language (Addison-Wesley Object Technology Series) by Martin Fowler, Kendall Scott (Contributor), Grady Booch; UML Distilled offers a useful perspective on what UML is and what it's good for. The author, an experienced software engineer, gives his own opinions of which diagrams are best to use. He is never doctrinaire and is always willing to put common sense design ahead of rigid adherence to models and documents. He runs through the basic notation used in UML for such design documents as use case, class, sequence, state, activity, and deployment diagrams. In addition, he includes concise examples of the details of working with objects, with an excellent step-by-step rendition of many of the details involved in UML. The author even includes some actual C++ code so you can see what all these design documents lead to.
Doing Hard Time: Developing Real-Time Systems with UML, Objects, Frameworks and Patterns by Bruce Powel Douglass; Author Bruce Powel Douglass begins by championing the advantages of objects for embedded development and then shows off basic UML document types. Next he addresses the difficulties of writing embedded systems (which are used in hospitals, aircraft, nuclear power plants, and other life-or-death environments). He looks at the restricted resources of embedded hardware and design issues regarding memory management and event handling.
The book expertly discusses the difference between the reliability and safety of software. (It describes the use of a number of patterns that can be used to provide safe operation in the event of single-point failure of a system.)
Rapid Object-Oriented Process for Embedded Systems (ROPES) finds its way to the heart of the text, a development process tailored to real-time software. Besides an introduction to iterative software development, the author walks the reader through the steps required for analysis, design, and eventual implementation of real-time software. The samples (which include several medical devices and a small air traffic control system) are exceptionally rich in detail and often use advanced aspects of UML notation.
Later sections concentrate on the latest in pattern design for embedded software used to manage threads and schedulability. The book closes with a tour of dynamic modeling, real-time frameworks--specifically, the I-Logix Rhapsody Object Execution Framework (OXF)--and details of the Rhapsody modeling tool. In all, Doing Hard Time delivers real technical expertise for any potential embedded software developer in a thorough and digestible format.
The Unified Modeling Language User Guide (Addison-Wesley Object Technology Series) by James Rumbaugh, Ivar Jacobson, Grady Booch; The "Unified Modeling Language User Guide" is the first of two UML works written by the creators of UML. This book will introduce the core 80% of UML, approaching it in a layered fashion and providing numerous examples of its application. The title is suitable for developers unfamiliar with UML or with modeling in general.
The Unified Modeling Language Reference Manual (Addison-Wesley Object Technology Series) by James Rumbaugh, Ivar Jacobson, Grady Booch; The Unified Modeling Language Reference Manual is the bible for this most widely used design methodology !
Analysis Patterns : Reusable Object Models by Martin Fowler; Besides general purpose designs, patterns can be specific to particular areas of computing. Martin Fowler's Analysis Patterns: Reusable Object Models contributes to the literature of patterns by defining over 70 patterns derived from the health care and financial areas. The book begins with some intriguing patterns from the business world include the Party and Accountability patterns, which define the players in organizations and whom they report to. A considerable number of patterns are drawn from the health care industry--principally doctor-patient interactions--with patterns such as Observation, Measurement, and Protocol. Obviously, these will be most applicable to object modelers who work in this industry (though, of course, patterns can often be used profitably in other fields). The patterns for financial markets will probably be more interesting for most readers. Fowler defines a Transaction pattern (and related patterns) as well as several for the accounting of objects. He moves on to modeling stock markets with patterns for Portfolio, Quote, and Scenario (which defines how a price for a stock is defined for a given moment). Interestingly, he defines patterns for Forward Contracts (for derivatives) as well as Options, and so takes on a complicated area of so much activity in today's financial markets.
Applying Uml and Patterns : An Introduction to Object-Oriented Analysis and Design by Craig Larman; Written for the developer with previous programming and design experience, Applying UML and Patterns combines UML, software patterns, and Java to illustrate the author's own design strategy. Though author Craig Larman sometimes relies heavily on the jargon of software engineering, there's no doubt that his book contains some immediately useful ideas on software design, using the latest and greatest in software-engineering research. Applying UML and Patterns provides beginning object programmers with a detailed activity roadmap to guide them through each step of requirements, analysis, design, and coding. This book strongly emphasizes translating theoretical concepts to practical applications, including:
*Mapping object-oriented diagrams directly to Java code
*Expressing models using UML
*Integrating patterns for analysis and design
*Creating layered architectures
*Building frameworks
Visual Modeling With Rational Rose and Uml (Addison-Wesley Object Technology Series) by Terry Quatrani; Presenting a condensed version of the Object Software Development Project, this book teaches readers how to analyze and design an application using the UML and how to implement it using Rational Rose 4.0. This latest version of Rational Rose, the industry-leading visual modeling tool, allows modelers to express their designs using the UML. Author Terry Quatrani is the Rose Evangelist for Rational Software Corporation and is responsible for successfully training and transitioning Fortune 500 customers (Xerox, Chemical Bank, NYNEX, Dun & Bradstreet, AT&T, CIGNA, Deutsche Bank, Lehman Brothers) to object technology. She has more than seventeen years experience in the development and deployment of large software systems. Prior to joining Rational, she worked for General Electric, where she was one of the founding consultants of the GE Advanced Concepts Center.

Search Amazons 2.5-Million-Title Catalog
Enter Keywords:

This page was created by mail me and we'll talk.

(Request TelNum joesch woodtennis@woodtennis.com)

Cyber bookstore