The Unified Software Development Process
Ivar Jacobson
Grady Booch, Rational Software Corporation
James Rumbaugh

ISBN-10: 0201571692
ISBN-13: 9780201571691

Publisher: Addison-Wesley Professional
Copyright: 1999
Format: Cloth; 512 pp
Published: 02/04/1999

Suggested retail price: $69.99
Buy from myPearsonStore



This landmark book provides a thorough overview of the Unified Process for software development, with a practical focus on modeling using the Unified Modeling Language. The Unified Process goes beyond mere object-oriented analysis and design to spell out a proven family of techniques that supports the complete software development life cycle. The result is a component-based process that is use-case driven, architecture-centric, iterative, and incremental. The Unified Process takes full advantage of the industry-standard Unified Modeling Language. This book demonstrates how the notation and process complement one another, using UML models to illustrate the new process in action. The authors clearly describe the semantics and notation of the different higher-level constructs used in the models. Constructs such as use cases, actors, subsystems, classes, interfaces, active classes, processes, threads, nodes, and most relations are described in the context of a model. Object technology practitioners and software engineers familiar with the authors' past work will appreciate The Unified Software Development Process as a useful means of learning the current best practices in software development.



Preface.

I. THE UNIFIED SOFTWARE DEVELOPMENT PROCESS.

1. The Unified Process: Use-Case Driven, Architecture-Centric, Iterative, and Incremental.

The Unified Process in a Nutshell.

The Unified Process Is Use-Case Driven.

The Unified Process Is Architecture-Centric.

The Unified Process Is Iterative and Incremental.

The Life of the Unified Process.

The Product.

Phases within a Cycle.

An Integrated Process.

2. The Four Ps: People, Project, Product, and Process in Software Development.

People Are Crucial.

Development Processes Affect People.

Roles Will Change.

Turning “Resources” into “Workers.”

Projects Make the Product.

Product Is More Than Code.

What Is a Software System?

Artifacts.

A System Has a Collection of Models.

What Is a Model?

Each Model Is a Self-Contained View of the System.

Inside a Model.

Relationships between Models.

Process Directs Projects.

Process: A Template.

Related Activities Make Up Workflows.

Specializing Process.

Merits of Process.

Tools Are Integral to Process.

Tools Impact Process.

Process Drives Tools.

Balance Process and Tools.

Visual Modeling Supports UML.

Tools Support the Whole Life Cycle.

References.

3. A Use-Case-Driven Process.

Use-Case-Driven Development in Brief.

Why Use Cases?

To Capture the Value Adding Requirements.

To Drive the Process.

To Devise the Architecture and More...

Capturing the Use Cases.

The Use-Case Model Represents the Functional Requirements.

Actors Are the Environment of the System.

Use Cases Specify the System.

Analysis, Design, and Implementation to Realize the Use Cases.

Creating the Analysis Model from the Use Cases.

Each Class Must Fulfill All Its Collaboration Roles.

Creating the Design Model from the Analysis Model.

Subsystems Group Classes.

Creating the Implementation Model from the Design Model.

Testing the Use Cases.

Summing Up.

References.

4. An Architecture-Centric Process

Architecture in Brief.

Why We Need Architecture.

Understanding the System.

Organizing Development.

Fostering Reuse.

Evolving the System.

Use Cases and Architecture.

The Steps to an Architecture.

The Architecture Baseline Is a “Small, Skinny” System.

Using Architecture Patterns.

Describing Architecture.

The Architect Creates the Architecture.

Finally, an Architecture Description!

The Architectural View of the Use-Case Model.

The Architectural View of the Design Model.

The Architectural View of the Deployment Model.

The Architectural View of the Implementation Model.

Three Interesting Concepts.

What Is Architecture?

How Is It Obtained?

How Is It Described?

References.

5. An Iterative and Incremental Process.

Iterative and Incremental in Brief.

Develop in Small Steps.

What Iteration Is Not.

Why Iterative and Incremental Development?

Mitigating Risks.

Getting a Robust Architecture.

Handling Changing Requirements.

Allowing for Tactical Changes.

Achieving Continuous Integration.

Attaining Early Learning.

The Iterative Approach is Risk-Driven.

Iterations Alleviate Technical Risks.

Management Is Responsible for Nontechnical Risks.

Dealing with Risks.

The Generic Iteration.

What an Iteration Is.

Planning the Iterations.

Sequencing the Iterations.

The Result of an Iteration Is an Increment.

Iterations over the Life Cycle.

Models Evolve from Iterations.

Iterations Challenge the Organization.

References.

II. THE CORE WORKFLOWS.

6. Requirements Capture: From Vision to Requirements.

Why Requirements Capture Is Difficult.

The Purpose of the Requirements Workflow.

Overview of Requirements Capture.

The Role of Requirements in the Software Life Cycle.

Understanding the System Context Using a Domain Model.

What Is a Domain Model?

Developing a Domain Model.

Use of the Domain Model.

Understanding the System Context Using a Business Model.

What Is a Business Model?

How to Develop a Business Model.

Find Use Cases from a Business Model.

Supplementary Requirements.

Summary.

References.

7. Capturing the Requirements as Use Cases.

Introduction.

Artifacts.

Artifact: Use-Case Model.

Artifact: Actor.

Use Case.

Artifact: Architecture Description (View of the Use-Case Model).

Artifact: Glossary.

Artifact: User-Interface Prototype.

Workers.

Worker: System Analyst.

Worker: Use-Case Specifier.

User-Interface Designer.

Worker: Architect.

Workflow.

Activity: Find Actors and Use Cases.

Activity: Prioritize Use Cases.

Activity: Detail a Use Case.

Activity: Prototype User Interface.

Activity: Structure the Use-Case Model.

Summary of the Requirements Workflow.

References.

8. Analysis.

Introduction.

Analysis in Brief.

Why Analysis Is not Design or Implementation.

The Purpose of Analysis: Summary.

Concrete Examples of When to Employ Analysis.

The Role of Analysis in the Software Life Cycle.

Artifacts.

Artifact: Analysis Model.

Artifact: Analysis Class.

Artifact: Use-Case Realization—Analysis.

Artifact: Analysis Package.

Artifact: Architecture Description (View of the Analysis Model).

Workers.

Worker: Architect.

Worker: Use-Case Engineer.

Worker: Component Engineer.

Workflow.

Activity: Architectural Analysis.

Activity: Analyze a Use Case.

Activity: Analyze a Class.

Activity: Analyze a Package.

Summary of Analysis.

References.

9. Design.

Introduction.

The Role of Design in the Software Life Cycle.

Artifacts.

Artifact: Design Model.

Artifact: Design Class.

Artifact: Use-Case Realization—Design.

Artifact: Design Subsystem.

Artifact: Interface.

Artifact: Architecture Description (View of the Design Model).

Artifact: Deployment Model.

Artifact: Architecture Description (View of the Deployment Model).

Workers.

Worker: Architect.

Worker: Use-Case Engineer.

Worker: Component Engineer.

Workflow.

Activity: Architectural Design.

Activity: Design a Use Case.

Activity: Design a Class.

Activity: Design a Subsystem.

Summary of Design.

References.

10. Implementation.

Introduction.

The Role of Implementation in the Software Life Cycle.

Artifacts.

Artifact: Implementation Model.

Artifact: Component.

Artifact: Implementation Subsystem.

Artifact: Interface.

Artifact: Architecture Description (View of the Implementation Model).

Artifact: Integration Build Plan.

Workers.

Worker: Architect.

Worker: Component Engineer.

Worker: System Integrator.

Workflow.

Activity: Architectural Implementation.

Activity: Integrate System.

Activity: Implement a Subsystem.

Activity: Implement a Class.

Activity: Perform Unit Test.

Summary of Implementation.

References.

11. Test.

Introduction.

The Role of Testing in the Software Life Cycle.

Artifacts.

Artifact: Test Model.

Artifact: Test Case.

Artifact: Test Procedure.

Artifact: Test Component.

Artifact: Plan Test.

Artifact: Defect.

Artifact: Evaluate Test.

Workers.

Worker: Test Designer.

Worker: Component Engineer.

Worker: Integration Tester.

Worker: System Tester.

Workflow.

Activity: Plan Test.

Activity: Design Test.

Activity: Implement Test.

Activity: Perform Integration Test.

Activity: Perform System Test.

Activity: Evaluate Test.

Summary of Testing.

References.

III. ITERATIVE AND INCREMENTAL DEVELOPMENT.

12. The Generic Iteration Workflow.

The Need for Balance.

The Phases Are the First Division of Work.

Inception Phase Establishes Feasibility.

Elaboration Phase Focuses on “Do-Ability.”

Construction Phase Builds the System.

Transition Phase Moves into the User Environment.

The Generic Iteration Revisited.

Core Workflows Repeat in Each Iteration.

Workers Participate in the Workflows.

Planning Precedes Doing.

Plan the Four Phases.

Plan the Iterations.

Think Long Term.

Plan the Evaluation Criteria.

Risks Affect Project Planning.

Manage a Risk List.

Risks Affect the Iteration Plan.

Schedule Risk Action.

Use-Case Prioritization.

Risks Specific to a Particular Product.

Risk of Not Getting the Architecture Right.

Risk of Not Getting Requirements Right.

Resources Needed.

Projects Differ Widely.

A Typical Project Looks Like This.

Complex Projects Have Greater Needs.

New Product Line Calls for Experience.

Paying the Cost of the Resources Used.

Assess the Iterations and Phases.

Criteria Not Achieved.

The Criteria Themselves.

The Next Iteration.

Evolution of the Model Set.

13. Inception Launches the Project.

The Inception Phase in Brief.

Early in the Inception Phase.

Before the Inception Phase Begins.

Planning the Inception Phase.

Expanding the System Vision.

Setting the Evaluation Criteria.

The Archetypal Inception Iteration Workflow.

Introduction to the Five Core Workflows.

Fitting the Project into the Development Environment.

Finding Critical Risks.

Execute the Core Workflows, Requirements to Test.

Capture the Requirements.

Analysis.

Design.

Test.

Make the Initial Business Case.

Outline Business Bid.

Estimate Return on Investment.

Assess the Iteration(s) in the Inception Phase.

Planning the Elaboration Phase.

The Deliverables for the Inception Phase.

14. The Elaboration Phase Makes the Architectural Baseline.

The Elaboration Phase in Brief.

Early in the Elaboration Phase.

Planning the Elaboration Phase.

Building the Team.

Modifying the Development Environment.

Setting Evaluation Criteria.

The Archetypal Elaboration Iteration Workflow.

Capture and Refine Most of the Requirements.

Develop the Architectural Baseline.

Iterate While the Team Is Small.

Execute the Core Workflows—Requirements to Test.

Capture the Requirements.

Analysis.

Design.

Implementation.

Test.

Make the Business Case.

Prepare the Business Bid.

Update Return on Investment.

Assess the Iterations in the Elaboration Phase.

Planning the Construction Phase.

The Key Deliverables.

15. Construction Leads to Initial Operational Capability.

The Construction Phase in Brief.

Early in the Construction Phase.

Staffing the Phase.

Setting the Evaluation Criteria.

The Archetypal Construction Iteration Workflow.

Execute the Core Workflows—Requirements to Testing.

Requirements.

Analysis.

Design.

Implementation.

Test.

Controlling the Business Case.

Assess the Iterations and the Construction Phase.

Planning the Transition Phase.

The Key Deliverables.

16. Transition Completes Product Release.

The Transition Phase in Brief.

Early in the Transition Phase.

Planning the Transition Phase.

Staffing the Transition Phase.

Setting the Evaluation Criteria.

The Core Workflows Play a Small Role in this Phase.

What We Do in the Transition Phase.

Getting the Beta Release Out.

Installing the Beta Release.

Responding to the Test Results.

Adapting the Product to Varied User Environments.

Completing the Artifacts.

When Does the Project End?

Completing the Business Case.

Controlling Progress.

Review of the Business Plan.

Assess the Transition Phase.

Assess the Iterations and the Phase.

Postmortem of the Project.

Planning the Next Release or Generation.

The Key Deliverables.

17. Making the Unified Process Work.

The Unified Process Helps You Deal with Complexity.

The Life Cycle Objectives.

The Life Cycle Architecture.

Initial Operational Capability.

Product Release.

The Major Themes.

Management Leads Conversion to Unified Process.

The Case for Action.

The Reengineering Directive Persuades.

Implementing the Transition.

Specializing the Unified Process.

Tailoring the Process.

Filling in the Process Framework.

Relate to the Broader Community.

Get the Benefits of the Unified Process.

References.

Appendix A: Overview of the UML.

Introduction.

Vocabulary.

Extensibility Mechanisms.

Graphical Notation.

Structural Things.

Behavioral Things.

Grouping Things.

Annotational Things.

Dependency Relationships.

Association Relationships.

Generalization Relationships.

Extensibility Mechanisms.

Glossary of Terms.

References.

Appendix B: The Unified Process-Specific Extensions of the UML.

Introduction.

Stereotypes.

Tagged Values.

Graphical Notation.

References.

Appendix C: General Glossary.

Introduction.

Terms.

Index. 0201571692T04062001

Ivar Jacobson, Ph.D., is “the father” of many technologies, including components and component architecture, use cases, modern business engineering, and the Rational Unified Process. He was one of the three amigos who originally developed the Unified Modeling Language. He is the principal author of five best-selling books on these methods and technologies, in addition to being the coauthor of the two leading books on the Unified Modeling Language. Ivar is a founder of Jaczone AB, where he and his daughter and cofounder, Agneta Jacobson, are developing a ground-breaking new product that includes intelligent agents to support software development. Ivar also founded Ivar Jacobson Consulting (IJC) with the goal of promoting good software development practices throughout teams worldwide.

Grady Booch, is the Chief Scientist at Rational Software Corporation and developer of the Booch Method of object-oriented analysis and design. He is also co-developer of the Unified Modeling Language (UML). Widely recognized for these and many contributions in the field, he is a popular speaker at technology conferences around the world. Booch has twice received Software Development magazine's coveted Jolt-Cola Product Excellence Award for his seminal text, Object-Oriented Analysis and Design with Applications. Dr. James Rumbaugh is one of the leading object-oriented methodologists. He is the chief developer of the Object Modeling Technique (OMT) and the lead author of the best-selling book Object-Oriented Modeling and Design. Before joining Rational Software Corporation in October 1994, he worked for more than 25 years at General Electric Research and Development Center in Schenectady, New York.

He has been working on object-oriented methodology and tools for many years. He developed the DSM object-oriented programming language, the state tree model of control, the OMT object modeling notation, and the Object Modeling Tool graphic editor. The foundations for the OMT notation were developed more than 10 years ago with Mary Loomis and Ashwin Shah of Calma Corporation. The OMT methodology was developed at GE R&D Center with coauthors Mike Blaha, Bill Premerlani, Fred Eddy, and Bill Lorensen.

Dr. Rumbaugh received his Ph.D. in computer science from MIT. During his Ph.D. research under Professor Jack Dennis, Dr. Rumbaugh was one of the inventors of data flow computer architecture. His career has dealt with semantics of computation, tools for programming productivity, and applications using complex algorithms and data structures. Dr. Rumbaugh has published journal articles on his work and has spoken at leading object-oriented conferences. He writes a regular column for the Journal of Object-Oriented Programming.

Dr. Rumbaugh is the lead author of the recent best-selling book Object-Oriented Modeling and Design, published by Prentice Hall. His latest book, OMT Insights: Perspectives on Modeling from the Journal of Object-Oriented Programming, was released in October 1996. He and his colleagues developed the OMT methodology described in the book based on real-world applications at GE, and they have worked to extend the original methodology. He has taught courses based on the methodology to different audiences around the world, ranging from one-hour seminars to intensive several-day training courses.

He has a B.S. in physics from MIT, an M.S. in astronomy from Caltech, and a Ph.D. in computer science from MIT.

During his career at GE, he worked on a variety of problems, including the design of one of the first time-sharing operating systems, early work in interactive graphics, algorithms for computed tomography, use of parallel machines for fast image generation, VLSI chip design, and finally, object-oriented technology.

Jim developed OMTool, an interactive graphical editor for manipulation of object model diagrams. The editor is commercially available. In addition, he led a five-year programming effort producing production-quality software.

In addition, Jim was the manager of the Software Engineering Program at GE, where he led a team of eight to ten Ph.D. and M.S. scientists performing research in software engineering in the areas of algorithm development, programming languages, program proving, and VLSI computer-aided design. In addition, he performed personal research.

Jim developed Chipwright, an interactive graphical CAD system for VLSI layout with incremental design rule checking. He also led a team of four programmers in implementation.

Jim developed and implemented the object-oriented language DSM, combining object-oriented concepts with database concepts and distributed it within GE for use on production applications. The language was heavily used at Calma Corporation and was extensively extended based on user feedback with a preliminary version.

Jim also developed Vista, a hierarchical interactive standard graphics system (similar to the PHIGS system) written in the object-oriented DSM language. He implemented user-interface applications based on this system, including a configuration-management tool and a user-interface generation tool.

Jim developed the concept of state trees, a structured extension of finite state machines incorporating a new model of object-oriented control. He applied it to the design of user interfaces, and the technique was used as a main aspect of the CHIDE user-interface system developed by colleagues at GE-CRD. Later, it was used in the OMTool object editor.

Jim also developed the Flow Graph System, a generic interactive graphic system for controlling a network of design engineering jobs, including management of multiple versions of data and coordination of information flow among applications. He received a patent on the underlying concepts.

In addition, Jim developed algorithms for the reconstruction of images for computerized tomography using fewer input points and with reduced noise in the reconstructed images. He also developed algorithms for display of three-dimensional images in real time using array processors, and he developed Parallax, a language for programming pipelined array processors.

Jim has served on various committees, including the OOPSLA Program Committee and the TOOLS Program Committee.



This landmark book provides a thorough overview of the Unified Process for software development, with a practical focus on modeling using the Unified Modeling Language (UML). The Unified Process goes beyond mere object-oriented analysis and design to spell out a proven family of techniques that supports the complete software development life cycle. The result is a component-based process that is use-case driven, architecture-centric, iterative, and incremental.

The Unified Process takes full advantage of the industry-standard Unified Modeling Language. This book demonstrates how the notation and process complement one another, using UML models to illustrate the new process in action. The authors clearly describe the semantics and notation of the different higher-level constructs used in the models. Constructs such as use cases, actors, subsystems, classes, interfaces, active classes, processes, threads, nodes, and most relations are described in the context of a model. Object technology practitioners and software engineers familiar with the authors' past work will appreciate The Unified Software Development Process as a useful means of learning the current best practices in software development.

0201571692B04062001

View a Sample Chapter PDF:

Pearson Higher Education offers special pricing when you choose to package your text with other student resources. If you're interested in creating a cost-saving package for your students, contact your Pearson Higher Education representative for pricing and ordering information.

This title is a member of the Addison-Wesley Object Technology Series, which also contains the titles below . You can also visit the Addison-Wesley Object Technology Series page.

  • 0321159624ATL Internals: Working with ATL 8, 2/E
    Tavares, Fertitta, Rector & Sells
    © 2007 | Addison-Wesley Professional | Paper; 888 pages | Instock
    ISBN-10: 0321159624 | ISBN-13: 9780321159625
    Buy from myPearsonStore

    • Guidance, advice, and a real-world case study teach the reader how to successfully implement the Rational Unified Process (RUP). The reader will find a management-perspective description of the RUP, and details on the effects that the RUP has on projects. In exploring an actual implementation, the authors present a definition of goals and metrics, advice on selecting strategies, and steps toward the development of an implementation plan. A discussion of implementation best practices and proven strategies is included. The book ends with descriptions from actual implementations, and a comparison of the content of the book with what can be found regarding this subject in the RUP itself.

  • 0321202945Adopting the Rational Unified Process: Success with the RUP
    Bergström & Råberg
    © 2004 | Addison-Wesley Professional | Paper; 272 pages | Instock
    ISBN-10: 0321202945 | ISBN-13: 9780321202949
    Brief Description | Buy from myPearsonStore

  • 0201615924Advanced Use Case Modeling: Software Systems
    Armour, Armour & Miller
    © 2001 | Addison-Wesley Professional | Paper; 464 pages | Instock
    ISBN-10: 0201615924 | ISBN-13: 9780201615920
    Buy from myPearsonStore

  • 0321321308Agility and Discipline Made Easy: Practices from OpenUP and RUP
    Kroll & MacIsaac
    © 2006 | Addison-Wesley Professional | Paper; 448 pages | Instock
    ISBN-10: 0321321308 | ISBN-13: 9780321321305
    Buy from myPearsonStore

  • 0201895420Analysis Patterns: Reusable Object Models
    Fowler
    © 1997 | Addison-Wesley Professional | Cloth; 384 pages | Instock
    ISBN-10: 0201895420 | ISBN-13: 9780201895421
    Buy from myPearsonStore

  • 0201325713Applied Software Architecture
    Hofmeister, Nord & Soni
    © 2000 | Addison-Wesley Professional | Cloth; 432 pages | Instock
    ISBN-10: 0201325713 | ISBN-13: 9780201325713
    Buy from myPearsonStore

  • 0201730391Applying Use Case Driven Object Modeling with UML: An Annotated e-Commerce Example
    Rosenberg & Scott
    © 2001 | Addison-Wesley Professional | Paper; 176 pages | Instock
    ISBN-10: 0201730391 | ISBN-13: 9780201730395
    Brief Description | Buy from myPearsonStore

    • Use case analysis is a methodology for defining the outward features of a software system from the user's point of view. Applying Use Cases, Second Edition, offers a clear and practical introduction to this cutting-edge software development technique. Using numerous realistic examples and a detailed case study, students are guided through the application of use case analysis in the development of software systems.

    This new edition has been updated and expanded to reflect the Unified Modeling Language (UML) version 1.3. It also includes more complex and precise examples, descriptions of the pros and cons of various use case documentation techniques, and discussions on how other modeling approaches relate to use cases.

  • 0201708531Applying Use Cases: A Practical Guide, 2/E
    Schneider & Winters
    © 2001 | Addison-Wesley Professional | Paper; 272 pages | Instock
    ISBN-10: 0201708531 | ISBN-13: 9780201708530
    Brief Description | Buy from myPearsonStore

  • 0321262204Art of ClearCase® Deployment, The: The Secrets to Successful Implementation
    Buckley & Pulsipher
    © 2005 | Addison-Wesley Professional | Paper; 432 pages | Instock
    ISBN-10: 0321262204 | ISBN-13: 9780321262202
    Buy from myPearsonStore

    • PLEASE PROVIDE DESCRIPTION

  • 0201711613Art of Objects, The: Object-Oriented Design and Architecture
    Lau
    © 2001 | Addison-Wesley Professional | Paper; 384 pages | Estimated Availability: 10/16/2000
    ISBN-10: 0201711613 | ISBN-13: 9780201711615
    Brief Description | Buy from myPearsonStore

    • Aspect-oriented software development is emerging as a proven approach for

    allowing the separate expression of multiple concerns, along with "weaving"

    technologies for knitting together these separate expressions into coherent

    systems. In other words, it offers great promise as an approach to simplifying

    the development of complex modern software systems. Many expert observers

    view AOSD as a worthwhile successor to the popular object-oriented paradigm

    that is prevalent in contemporary software engineering. In this new book,

    AOSD experts Clarke and Baniassad apply proven theory to the practical realm

    of real-world development. The result is an applicable and easy-to-digest

    methodology for simplifying and optimizing the development of thoroughly

    modern software systems.

  • 0321246748Aspect-Oriented Analysis and Design: The Theme Approach
    Clarke & Baniassad
    © 2005 | Addison-Wesley Professional | Paper; 400 pages | Instock
    ISBN-10: 0321246748 | ISBN-13: 9780321246745
    Brief Description | Buy from myPearsonStore

    • Aspect orientation promises to be the next big wave in software engineering,

    following on the heels of the object-oriented paradigm. Proponents tout the

    value of aspect orientation in providing the ability to add extremely useful

    mechanisms such as security, logging, persistence, debugging, tracing,

    distribution, performance monitoring, and exception handling. To state it

    simply, it makes programming and programs more efficient.

    This highly-anticipated new book demonstrates how to apply use cases and

    aspect orientation in building robust and extensible systems. The authors show

    you how to identify, design, implement, test, and refactor use case modules and

    how to extend them. The book also demonstrates how to design use case

    modules with UML including some enhancements made in UML 2.0 to better

    support the modeling of use case modules.

  • 0321268881Aspect-Oriented Software Development with Use Cases
    Jacobson & Ng
    © 2005 | Addison-Wesley Professional | Paper; 464 pages | Instock
    ISBN-10: 0321268881 | ISBN-13: 9780321268884
    Brief Description | Buy from myPearsonStore

  • 0201730383Building Web Applications with UML, 2/E
    Conallen
    © 2003 | Addison-Wesley Professional | Paper; 496 pages | Instock
    ISBN-10: 0201730383 | ISBN-13: 9780201730388
    Buy from myPearsonStore

  • 0201657937Designing Concurrent, Distributed, and Real-Time Applications with UML
    Gomaa
    © 2000 | Addison-Wesley Professional | Cloth; 816 pages | Instock
    ISBN-10: 0201657937 | ISBN-13: 9780201657937
    Buy from myPearsonStore

  • 080535350XDesigning Object-Oriented User Interfaces
    Collins
    © 1995 | Addison-Wesley Professional | Paper; 608 pages | Estimated Availability: 12/31/1994
    ISBN-10: 080535350X | ISBN-13: 9780805353501
    Buy from myPearsonStore

  • 0201775956Designing Software Product Lines with UML: From Use Cases to Pattern-Based Software Architectures
    Gomaa
    © 2005 | Addison-Wesley Professional | Cloth; 736 pages | Instock
    ISBN-10: 0201775956 | ISBN-13: 9780201775952
    Buy from myPearsonStore

  • 0201615797Developing Applications with Visual Basic and UML
    Reed
    © 2000 | Addison-Wesley Professional | Paper; 592 pages | Estimated Availability: 11/04/1999
    ISBN-10: 0201615797 | ISBN-13: 9780201615791
    Buy from myPearsonStore

  • 0201738295Developing Enterprise Java Applications with J2EE™ and UML
    Ahmed & Umrysh
    © 2002 | Addison-Wesley Professional | Paper; 368 pages | Instock
    ISBN-10: 0201738295 | ISBN-13: 9780201738292
    Buy from myPearsonStore

    • Practical guide to exploiting the power of Object Technology & UML in your software development process.

  • 020175603XDeveloping Software with UML: Object-Oriented Analysis and Design in Practice, 2/E
    Oestereich
    © 2002 | Addison-Wesley Professional | Paper; 320 pages | Instock
    ISBN-10: 020175603X | ISBN-13: 9780201756036
    Brief Description | Buy from myPearsonStore

  • 0805327207Discovering Smalltalk
    LaLonde
    © 1994 | Addison-Wesley Professional | Paper; 576 pages | Estimated Availability: 12/31/1993
    ISBN-10: 0805327207 | ISBN-13: 9780805327205
    Buy from myPearsonStore

  • 0201498375Doing Hard Time: Developing Real-Time Systems with UML, Objects, Frameworks, and Patterns
    Douglass
    © 1999 | Addison-Wesley Professional | Cloth Bound w/CD-ROM; 800 pages | Instock
    ISBN-10: 0201498375 | ISBN-13: 9780201498370
    Buy from myPearsonStore

    • In Effective COM, the authors, Don Box, Keith Brown, Tim Ewald, and Chris Sells, offer 50 concrete guidelines for creating COM based applications that are more efficient, robust, and maintainable. Drawn from the authors' extensive practical experience working with and teaching COM, these rules of thumb, pitfalls to avoid, and experience-based pointers will enable you to become a more productive and successful COM programmer.

    These guidelines appear under six major headings: the transition from C++ to COM; interfaces, the fundamental element of COM development; implementation issues; the unique concept of apartments; security; and transactions. Throughout this book, the issues unique to the MTS programming model are addressed in detail.

    Readers will gain a deeper understanding of COM concepts, capabilities, and drawbacks, and the know-how to employ COM effectively for high quality distributed application development. A supporting Web site, including source code, can be found at http://www.develop.com/effectivecom.

  • 0201379686Effective COM: 50 Ways to Improve Your COM and MTS-based Applications
    Box, Brown, Ewald & Sells
    © 1999 | Addison-Wesley Professional | Paper; 240 pages | Estimated Availability: 12/03/1998
    ISBN-10: 0201379686 | ISBN-13: 9780201379686
    Brief Description | Buy from myPearsonStore

  • 0201433133Enterprise Modeling with UML: Designing Successful Software through Business Analysis
    Marshall
    © 2000 | Addison-Wesley Professional | Paper; 288 pages | Instock
    ISBN-10: 0201433133 | ISBN-13: 9780201433135
    Buy from myPearsonStore

  • 032111230XEnterprise Patterns and MDA: Building Better Software with Archetype Patterns and UML
    Arlow & Neustadt
    © 2004 | Addison-Wesley Professional | Paper; 528 pages | Instock
    ISBN-10: 032111230X | ISBN-13: 9780321112309
    Buy from myPearsonStore

  • 0201748045Executable UML: A Foundation for Model-Driven Architecture
    Mellor & Balcer
    © 2002 | Addison-Wesley Professional | Paper; 416 pages | Instock
    ISBN-10: 0201748045 | ISBN-13: 9780201748048
    Buy from myPearsonStore

  • 020169946XFundamentals of Object-Oriented Design in UML
    Page-Jones
    © 2000 | Addison-Wesley Professional | Paper; 480 pages | Instock
    ISBN-10: 020169946X | ISBN-13: 9780201699463
    Buy from myPearsonStore

  • 080530908XIBM Smalltalk: The Language
    Smith
    © 1995 | Addison-Wesley Professional | Paper; 584 pages | Estimated Availability: 01/26/1995
    ISBN-10: 080530908X | ISBN-13: 9780805309089
    Buy from myPearsonStore

  • 0201788918MDA Distilled
    Mellor, Scott, Uhl & Weise
    © 2004 | Addison-Wesley Professional | Paper; 176 pages | Instock
    ISBN-10: 0201788918 | ISBN-13: 9780201788914
    Buy from myPearsonStore

  • 032119442XMDA Explained: The Model Driven Architecture™: Practice and Promise
    Kleppe, Warmer & Bast
    © 2003 | Addison-Wesley Professional | Paper; 192 pages | Instock
    ISBN-10: 032119442X | ISBN-13: 9780321194428
    Buy from myPearsonStore

    • Iterative processes help software developers reduce risk and cost, manage change, improve productivity, and deliver more effective, timely solutions. Now, there’s a practical, easy guide to planning, organizing, estimating, staffing, and running any iterative project: Managing Iterative Software Development Projects. Kurt Bittner and Ian Spence introduce a proven approach that improves both agility and control, satisfying developers, managers, and the business. Their techniques can be used with any iterative methodology, and scaled from the smallest projects to the very largest. For everyone involved in iterative projects: team leaders, program managers, project managers, developers, sponsors, and user representatives alike.

  • 032126889XManaging Iterative Software Development Projects
    Bittner & Spence
    © 2007 | Addison-Wesley Professional | Paper; 672 pages | Instock
    ISBN-10: 032126889X | ISBN-13: 9780321268891
    Brief Description | Buy from myPearsonStore

    • This Second Edition of the popular text Managing Software Requirements focuses on this critical cause of failure and offers a practical, proven approach to building systems that meet customers' needs on time and within budget.

    Using an approachable style, their own war stories and a comprehensive case study, the authors show how students can effectively identify requirements by applying a variety of techniques, centered on the power of use cases. The book illustrates proven techniques for determining, implementing, and validating requirements.

  • 032112247XManaging Software Requirements: A Use Case Approach, 2/E
    Leffingwell & Widrig
    © 2003 | Addison-Wesley Professional | Cloth; 544 pages | Instock
    ISBN-10: 032112247X | ISBN-13: 9780321122476
    Brief Description | Buy from myPearsonStore

  • 0201709155Modeling XML Applications with UML: Practical e-Business Applications
    Carlson
    © 2001 | Addison-Wesley Professional | Paper; 368 pages | Instock
    ISBN-10: 0201709155 | ISBN-13: 9780201709155
    Buy from myPearsonStore

  • 0321179366Object Constraint Language, The: Getting Your Models Ready for MDA, 2/E
    Warmer & Kleppe
    © 2004 | Addison-Wesley Professional | Paper; 240 pages | Instock
    ISBN-10: 0321179366 | ISBN-13: 9780321179364
    Buy from myPearsonStore

  • 0805305947Object Solutions: Managing the Object-Oriented Project
    Booch
    © 1996 | Addison-Wesley Professional | Paper; 336 pages | Estimated Availability: 10/12/1995
    ISBN-10: 0805305947 | ISBN-13: 9780805305944
    Buy from myPearsonStore

    • The previous editions of this book have taught tens of thousands how to apply the concepts and ideas behind object technology to design successful software applications. This revision will bring the book up to date with the many changes in technology that have happened since the second edition was first published in 1994. New topics covered in the third edition include the Unified Software Development Process, UML, Patterns, Java, and Components.

  • 020189551XObject-Oriented Analysis and Design with Applications, 3/E
    Booch, Maksimchuk, Engel, Young, Conallen & Houston
    © 2007 | Addison-Wesley Professional | Cloth; 720 pages | Instock
    ISBN-10: 020189551X | ISBN-13: 9780201895513
    Brief Description | Buy from myPearsonStore

    • In the Second Edition of his award-winning book, Grady Booch draws upon the rich and varied results of the hundreds of projects which have applied the notation and method presented in the First Edition to offer improved methods for object development-including a unified notation. The winner of the Jolt Cola book award in both editions, Object-Oriented Analysis and Design with Applications has been a major force in moving object technology into the mainstream of software development. With numerous examples, now implemented in C++, the Second Edition illustrates essential concepts, explains the method, and shows successful applications in a variety of fields. It also offers pragmatic advice on a variety of issues-including classification, implementation strategies, and cost-effective project management.

  • 0805353402Object-Oriented Analysis and Design with Applications, 2/E
    Booch
    © 1994 | Addison-Wesley Professional | Cloth; 608 pages | Instock
    ISBN-10: 0805353402 | ISBN-13: 9780805353402
    Brief Description | Buy from myPearsonStore

  • 0201895501Object-Oriented Programming Using C++, 2/E
    Pohl
    © 1997 | Addison-Wesley Professional | Paper; 576 pages | Instock
    ISBN-10: 0201895501 | ISBN-13: 9780201895506
    Buy from myPearsonStore

    • This book teaches the student how to use objects, frameworks, and UML notation to design, build, and reuse component-based software. Catalysis is a rapidly emerging UML-based method for object- and component-based development. It provides a clear meaning of and systematic uses for the UML notation. "The Catalysis Approach" explains how patterns can be characterized as model frameworks. Through the application of frameworks in requirements, specifications, architectures, and designs, students will find that all models contain recurring patterns of structure, behavior, and refinement. This opens the way to building models and designs rapidly by adapting and composing both generic and domain-specific modeling frameworks.

  • 0201310120Objects, Components, and Frameworks with UML: The Catalysis(SM) Approach
    D'Souza & Wills
    © 1999 | Addison-Wesley Professional | Paper; 816 pages | Instock
    ISBN-10: 0201310120 | ISBN-13: 9780201310122
    Brief Description | Buy from myPearsonStore

  • 0201722291Performance Solutions: A Practical Guide to Creating Responsive, Scalable Software
    Smith & Williams
    © 2002 | Addison-Wesley Professional | Paper; 544 pages | Instock
    ISBN-10: 0201722291 | ISBN-13: 9780201722291
    Buy from myPearsonStore

    • PLEASE PROVIDE DESCRIPTION

  • 0201325640Practical Guide to Testing Object-Oriented Software, A
    McGregor & Sykes
    © 2001 | Addison-Wesley Professional | Paper; 416 pages | Instock
    ISBN-10: 0201325640 | ISBN-13: 9780201325645
    Brief Description | Buy from myPearsonStore

  • 0321136195Practical Software Engineering: Analysis and Design for the .NET Platform
    Manassis
    © 2004 | Addison-Wesley Professional | Paper; 304 pages | Estimated Availability: 09/16/2003
    ISBN-10: 0321136195 | ISBN-13: 9780321136190
    Buy from myPearsonStore

  • 0201758210Process Quality Assurance for UML-Based Projects
    Unhelkar
    © 2003 | Addison-Wesley Professional | Paper; 432 pages | Out of Stock
    ISBN-10: 0201758210 | ISBN-13: 9780201758214


    • This book is a comprehensive guide to modern software development practices, as embodied in the Rational Unified Process, or RUP. The Rational Unified Process Made Easy will teach students the key points involved in planning and managing iterative projects, the fundamentals of component design and software architecture, and the proper employment of use cases. Students will learn that the RUP is a flexible, versatile process framework that can be tailored to suit the needs of development projects of all types and sizes.

  • 0321166094Rational Unified Process Made Easy, The: A Practitioner's Guide to the RUP
    Kroll & Kruchten
    © 2003 | Addison-Wesley Professional | Paper; 464 pages | Instock
    ISBN-10: 0321166094 | ISBN-13: 9780321166098
    Brief Description | Buy from myPearsonStore

    • The Rational Unified Process, Third Edition, is a concise introduction to IBM's Web-enabled software engineering process. Rational Unified Process®, or RUP®, Lead Architect Philippe Kruchten quickly and clearly describes the concepts, structure, content, and motivation that are central to the RUP. Readers will learn how this approach to software development can be used to produce high-quality software, on schedule and on budget, using the Unified Modeling Language (UML), software automation, and other industry best practices.

  • 0321197704Rational Unified Process, The: An Introduction, 3/E
    Kruchten
    © 2004 | Addison-Wesley Professional | Paper; 336 pages | Instock
    ISBN-10: 0321197704 | ISBN-13: 9780321197702
    Brief Description | Buy from myPearsonStore

    • The two previous editions were written as easy-to-read introductions to the UML, and how to apply its notation and semantics to the unique requirements involved with the development of real-time and embedded systems. This third edition is no exception. Although the book's emphasis is on UML, it is also about capturing the requirements, structure, and behavior of real-time systems. The most significant change in this revision will be it's integration throughout the book of UML 2.0, and all indications are that UML 2.0 is even more accepting of the unique aspects of real-time and embedded systems development.

  • 0321160762Real Time UML: Advances in the UML for Real-Time Systems, 3/E
    Douglass
    © 2004 | Addison-Wesley Professional | Paper; 752 pages | Instock
    ISBN-10: 0321160762 | ISBN-13: 9780321160768
    Brief Description | Buy from myPearsonStore

    • PLEASE PROVIDE SUMMARY

  • 0201699567Real-Time Design Patterns: Robust Scalable Architecture for Real-Time Systems
    Douglass
    © 2003 | Addison-Wesley Professional | Paper Bound w/CD-ROM; 528 pages | Instock
    ISBN-10: 0201699567 | ISBN-13: 9780201699562
    Brief Description | Buy from myPearsonStore

    • Refactoring is about improving the design of existing code. It is the process of changing a software system in such a way that it does not alter the external behavior of the code, yet improves its internal structure. With refactoring you can even take a bad design and rework it into a good one. This book offers a thorough discussion of the principles of refactoring, including where to spot opportunities for refactoring, and how to set up the required tests. There is also a catalog of more than 40 proven refactorings with details as to when and why to use the refactoring, step by step instructions for implementing it, and an example illustrating how it works The book is written using Java as its principle language, but the ideas are applicable to any OO language.

  • 0201485672Refactoring: Improving the Design of Existing Code
    Fowler, Beck, Brant, Opdyke & Roberts
    © 1999 | Addison-Wesley Professional | Cloth; 464 pages | Instock
    ISBN-10: 0201485672 | ISBN-13: 9780201485677
    Brief Description | Buy from myPearsonStore

    • In this comprehensive introduction to Ada programming, programmers learn how to maximize the potential of this powerful language using an object-oriented methodology. Grady Booch and Doug Bryan combine their expertise to explain how to create large-scale Ada systems using good software engineering principles. Five large-scale Ada programming examples build upon these principles using an object-oriented methodology while illuminating topics such as database systems and generic tree packages. The Third Edition also incorporates more small-sized code examples, exercises based on the programming applications, a new chapter on Ada's impact on the software crisis, and an appendix on Ada 9X.

  • 0805306080Software Engineering with ADA, 3/E
    Booch & Bryan
    © 1994 | Addison-Wesley Professional | Paper; 576 pages | Out of Stock
    ISBN-10: 0805306080 | ISBN-13: 9780805306088
    Brief Description

    • This book provides a clear and provocative discussion of the economics, metrics, and management strategies necessary to plan and execute a software project successfully. Royce discusses, with refreshing candor, some of the fads, follies, and excesses of the software industry, clearly differentiating proven techniques and obsolete methods. Paired with this insightful examination are compelling arguments for new management approaches that are sure to stimulate debate. The relative impacts of these new techniques are quantified through simple economic analyses, common sense, and anecdotal evidence. The resulting framework strikes a pragmatic balance between theory and practice that can be readily applied in today's challenging development environment. An extensive case study analysis of a large-scale, million-line project deployed successfully on schedule and under budget using these methods further illustrates their application.

  • 0201309580Software Project Management: A Unified Framework
    Royce
    © 1998 | Addison-Wesley Professional | Cloth; 448 pages | Instock
    ISBN-10: 0201309580 | ISBN-13: 9780201309584
    Brief Description | Buy from myPearsonStore

  • 0201809389Testing Object-Oriented Systems: Models, Patterns, and Tools
    Binder
    © 2000 | Addison-Wesley Professional | Cloth; 1248 pages | Instock
    ISBN-10: 0201809389 | ISBN-13: 9780201809381
    Buy from myPearsonStore

    • This thoroughly revised second edition is based upon the authors' successful

    training courses, and gives the reader a quick, focused tour through a proven

    object-oriented analysis and design process. It introduces and explains the

    need-to-know concepts and key elements of both Unified Modeling Language

    (UML) and the Unified Process (UP). The book allows the reader to get up to

    speed on successful techniques that can be immediately applied. The structure

    of the book aims to give the reader as clear and uncomplicated a guide as

    possible. It takes the reader through an introduction to UML, an introduction

    to the UP, then covers the basics of software requirements and use case

    modeling. The key aspects of the analysis and design stages are covered in stepby-

    step detail, finishing off with implementation.

  • 0321321278UML 2 and the Unified Process: Practical Object-Oriented Analysis and Design, 2/E
    Arlow & Neustadt
    © 2005 | Addison-Wesley Professional | Paper; 624 pages | Instock
    ISBN-10: 0321321278 | ISBN-13: 9780321321275
    Brief Description | Buy from myPearsonStore

    • Series: The Addison-Wesley Object Technology Series

    The long-awaited third edition of the best-selling UML book on the market; fully-updated and compliant with UML 2.0. This eagerly-anticipated third edition gets students thinking about efficient object-oriented software design using the latest version of the industry-standard for modeling software: UML 2.0. The author has retained the book's convenient, concise format that has made it an essential resource in courses introducing UML. The book describes all the major UML 2.0 diagram types, what they are intended to do, and the basic notation involved in creating and deciphering them. A true treasure for the software engineering community.

  • 0321193687UML Distilled: A Brief Guide to the Standard Object Modeling Language, 3/E
    Fowler
    © 2004 | Addison-Wesley Professional | Paper; 208 pages | Instock
    ISBN-10: 0321193687 | ISBN-13: 9780321193681
    Brief Description | Buy from myPearsonStore

    • This pragmatic guide introduces UML while leading the student through the process of UML-based database modeling and design. The book presents the different types of UML diagrams, explaining how they apply to the database world, and shows how data modeling with the UML can be tied into the Rational Unified Process.

    UML for Database Design is structured around the database design process: business use case modeling, business object modeling, database requirements definition, analysis and preliminary design, and, finally, detailed design and deployment. For each phase of development the book describes the overall objectives and workflow of that phase, the status of the case study, the relevant UML constructs, and the nuts and bolts of database modeling and design with the UML. Drawing on their extensive industry experience, the authors reveal the trials and tribulations of database development teams, lessons learned, and pointers for success.

  • 0201721635UML for Database Design
    Naiburg & Maksimchuk
    © 2002 | Addison-Wesley Professional | Paper; 320 pages | Instock
    ISBN-10: 0201721635 | ISBN-13: 9780201721638
    Brief Description | Buy from myPearsonStore

    • The latest version of the Unified Modeling Language–UML 2.0–has increased its capabilities as the standard notation for modeling software-intensive systems. Like most standards documents, however, the official UML specification is difficult to read and navigate. In addition, UML 2.0 is far more complex than previous versions, making a thorough reference book more essential than ever.

    In this significantly updated and expanded edition of the definitive reference to the standard, James Rumbaugh, Ivar Jacobson, and Grady Booch–the UML’s creators–clearly and completely describe UML concepts, including major revisions to sequence diagrams, activity models, state machines, components, internal structure of classes and components, and profiles.

  • 0321245628The Unified Modeling Language Reference Manual, 2/E
    Rumbaugh, Jacobson & Booch
    © 2005 | Addison-Wesley Professional | Cloth Bound w/CD-ROM; 752 pages | Instock
    ISBN-10: 0321245628 | ISBN-13: 9780321245625
    Brief Description | Buy from myPearsonStore

  • 020130998XThe Unified Modeling Language Reference Manual
    Rumbaugh, Jacobson & Booch
    © 1999 | Addison-Wesley Professional | Cloth Bound w/CD-ROM; 576 pages | Instock
    ISBN-10: 020130998X | ISBN-13: 9780201309980
    Buy from myPearsonStore

  • 0321267974The Unified Modeling Language User Guide, 2/E
    Booch, Rumbaugh & Jacobson
    © 2005 | Addison-Wesley Professional | Cloth; 496 pages | Instock
    ISBN-10: 0321267974 | ISBN-13: 9780321267979
    Buy from myPearsonStore

    • This landmark book provides a thorough overview of the Unified Process for software development, with a practical focus on modeling using the Unified Modeling Language. The Unified Process goes beyond mere object-oriented analysis and design to spell out a proven family of techniques that supports the complete software development life cycle. The result is a component-based process that is use-case driven, architecture-centric, iterative, and incremental. The Unified Process takes full advantage of the industry-standard Unified Modeling Language. This book demonstrates how the notation and process complement one another, using UML models to illustrate the new process in action. The authors clearly describe the semantics and notation of the different higher-level constructs used in the models. Constructs such as use cases, actors, subsystems, classes, interfaces, active classes, processes, threads, nodes, and most relations are described in the context of a model. Object technology practitioners and software engineers familiar with the authors' past work will appreciate The Unified Software Development Process as a useful means of learning the current best practices in software development.

  • 0201571692The Unified Software Development Process
    Jacobson, Booch & Rumbaugh
    © 1999 | Addison-Wesley Professional | Cloth; 512 pages | Instock
    ISBN-10: 0201571692 | ISBN-13: 9780201571691
    Brief Description | Buy from myPearsonStore

  • 0201432897Use Case Driven Object Modeling with UML: A Practical Approach
    Rosenberg & Scott
    © 1999 | Addison-Wesley Professional | Paper; 192 pages | Instock
    ISBN-10: 0201432897 | ISBN-13: 9780201432893
    Buy from myPearsonStore