Applying UML and Patterns

Enhanced descriptions from Syndetics:

The world's no.1 best-selling introduction to object-oriented analysis/design, iterative development, and the UML-now completely updated Applying UML and Patterns, second edition, helps any developer or student master the core principles and best practices of object-oriented analysis and design (OOA/D)-not just drawing UML, but really applying it in the context of software design. Renowned object technology and iterative methods leader Craig Larman presents three iterations of a single, cohesive case study, incrementally introducing the critical skills of OOA/D, while emphasizing the most essential activities, principles, and patterns. Coverage includes: *Requirements and Use Cases: Identifying and recording requirements *Domain Object Modeling: Understanding domain objects of interest, their attributes, and relationships *Architecture: Creating layered architectures that maximize applicationflexibility, robustness, and maintainability *Essential Object Design: Mastering key skills, including assigning responsibilities to objects, and designing collaborations with principles such as Information Expert, Indirection, and Protected Variations *Design Patterns: Creating robust objec

Table of contents provided by Syndetics

• Foreword
• Preface
• I Introduction
• 1 Object-Oriented Analysis and Design
• Applying UML and Patterns in OOA/D
• Assigning Responsibilities
• What Is Analysis and Design?
• What Is Object-Oriented Analysis and Design?
• An Example
• The UML
• Further Readings
• 2 Iterative Development and the Unified Process
• The Most Important UP Idea: Iterative Development
• Additional UP Best Practices and Concepts
• The UP Phases and Schedule-Oriented Terms
• The UP Disciplines (was Workflows)
• Process Customization and the Development Case
• The Agile UP.
• The Sequential "Waterfall" Lifecycle
• You Know You Didn''t Understand the UP When...
• Further Readings
• 3 Case Study
• The NextGen POS System
• The NextGen POS System
• Architectural Layers and Case Study Emphasis
• The Book''s Strategy: Iterative Learning and Development
• II Inception
• 4 Inception
• Inception: An Analogy
• Inception May Be Very Brief
• What Artifacts May Start in Inception?
• You Know You Didn''t Understand Inception When...
• 5 Understanding Requirements
• Types of Requirements
• Further Readings
• 6 Use-Case Model
• Writing Requirements in Context
• Goals and Stories
• Background
• Use Cases and Adding Value
• Use Cases and Functional Requirements
• Use Case Types and Formats
• Fully Dressed Example: Process Sale
• Explaining the Sections
• Goals and Scope of a Use Case
• Finding Primary Actors, Goals, and Use Cases
• Congratulations: Use Cases Have Been Written, and Are Imperfect
• Write Use Cases in an Essential UI-Free Style
• Actors
• Use Case Diagrams
• Requirements in Context and Low-Level Feature Lists
• Use Cases Are Not Object-Oriented
• Use Cases Within the UP
• Case Study: Use Cases in the NextGen Inception Phase
• Further Readings
• UP Artifacts and Process Context
• 7 Identifying Other Requirements
• NextGen POS Examples
• NextGen Example: (Partial) Supplementary Specification
• Commentary: Supplementary Specification
• NextGen Example: (Partial) Vision
• Commentary: Vision
• NextGen Example: A (Partial) Glossary
• Commentary: Glossary (Data Dictionary)
• Reliable Specifications: An Oxymoron?
• Online Artifacts at the Project Website
• Not Much UML During Inception?
• Other Requirement Artifacts Within the UP
• Further Readings
• UP Artifacts and Process Context
• 8 From Inception to Elaboration
• Checkpoint: What Happened in Inception?
• On to Elaboration
• Planning the Next Iteration
• Iteration 1 Requirements and Emphasis: Fundamental OOA/D Skills
• What Artifacts May Start in Elaboration?
• You Know You Didn''t Understand Elaboration When...
• III Elaboration Iteration
• 9 Use-Case Model
• Drawing System Sequence Diagrams
• System Behavior
• System Sequence Diagrams
• Example of an SSD
• Inter-System SSDs
• SSDs and Use Cases
• System Events and the System Boundary
• Naming System Events and Operations
• Showing Use Case Text
• SSDs and the Glossary
• SSDs Within the UP
• Further Readings
• UP Artifacts
• 10 Domain Model
• Visualizing Concepts
• Domain Models
• Conceptual Class Identification
• Candidate Conceptual Classes for the Sales Domain
• Domain Modeling Guidelines
• Resolving Similar Conceptual Classes-Register vs. "POST"
• Modeling the Unreal World
• Specification or Description Conceptual Classes
• UML Notation, Models, and Methods: Multiple Perspectives
• Lowering the Representational Gap
• Example: The NextGen POS Domain Model
• Domain Models Within the UP
• Further Readings
• UP Artifacts
• 11 Domain Model
• Adding Associations
• Associations
• The UML Association Notation
• Finding Associations-Common Associations List
• Association Guidelines
• Roles
• How Detailed Should Associations Be?
• Naming Associations
• Multiple Associations Between Two Types
• Associations and Implementation
• NextGen POS Domain Model Associations
• NextGen POS Domain Model
• 12 Domain Model
• Adding Attributes
• Attributes
• UML Attribute Notation
• Valid Attribute Types
• Non-primitive Data Type Classes
• Design Creep: No Attributes as Foreign Keys
• Modeling Attribute Quantities and Units
• Attributes in the NextGen Domain Model
• Multiplicity From SalesLineItem to Item
• Domain Model Conclusion
• 13 Use-Case Model
• Adding Detail with Operation Contracts
• Contracts
• Example Contract: enterItem
• Contract Sections
• Postconditions
• Discussion-enterItem Postconditions
• Writing Contracts Leads to Domain Model Updates
• When Are Contracts Useful?
• Contracts vs. Use Cases?
• Guidelines: Contracts
• NextGen POS Example: Contracts
• Changes to the Domain Model
• Contracts, Operations, and the UML
• Operation Contracts Within the UP
• Further Readings
• 14 From Requirements to Design in this Iteration
• Iteratively Do the Right Thing, Do the Thing Right
• Didn''t That Take Weeks To Do?
• No, Not Exactly
• On to Object Design
• 15 Interaction Diagram Notation
• Sequence and Collaboration Diagrams
• Example Collaboration Diagram: make Payment
• Example Sequence Diagram: make Payment
• Interaction Diagrams Are Valuable
• Common Interaction Diagram Notation
• Basic Collaboration Diagram Notation
• Basic Sequence Diagram Notation
• 16 GRASP
• Designing Objects with Responsibilities
• Responsibilities and Methods
• Responsibilities and Interaction Diagrams
• Patterns
• GRASP: Patterns of General Principles in Assigning Responsibilities
• The UML Class Diagram Notation
• Information Expert (or Expert)
• Creator
• Low Coupling
• High Cohesion
• Controller
• Object Design and CRC Cards
• Further Readings
• 17 Design Model
• Use-Case Realizations with GRASP Patterns
• Use-Case Realizations
• Artifact Comments
• Use-Case Realizations for the NextGen Iteration
• Object Design: make NewSale
• Object Design: enter Item
• Object Design: end Sale
• Object Design: make Payment
• Object Design: start Up
• Connecting the UI Layer to the Domain Layer
• Use-Case Realizations Within the UP
• Summary
• 18 Design Model
• Determining Visibility
• Visibility Between Objects
• Visibility
• Illustrating Visibility in the UML
• 19 Design Model
• Creating Design Class Diagrams
• When to Create DCDs
• Example DCD
• DCD and UP Terminology
• Domain Model vs. Design Model Classes
• Creating a NextGen POS DCD
• Notation for Member Details
• DCDs, Drawing, and CASE Tools
• DCDs Within the UP
• UP Artifacts
• 20 Implementation Model
• Mapping Designs to Code
• Programming and the Development Process
• Mapping Designs to Code
• Creating Class Definitions from DCDs
• Creating Methods from Interaction Diagrams
• Container/Collection Classes in Code
• Exceptions and Error Handling
• Defining the Sale--makeLineItem Method
• Order of Implementation
• Test-First Programming
• Summary of Mapping Designs to Code
• Introduction

Author notes provided by Syndetics

CRAIG LARMAN serves as Director of Process and Methodology at Valtech, a leading international e-business consulting group. He is known throughout the international software community as an expert in object technologies, patterns, the UML, modeling, and iterative development. Since the 1980s, Larman has been helping people learn objects and iterative development, having personally guided thousands of developers. He is also the co-author of Java 2 Performance and Idiom Guide , and holds a B.Sc. and M.Sc. in Computer Science from Simon Fraser University in Vancouver, B.C.