内容

目次

Foreword. Preface. I. INTRODUCTION. 1. Object-Oriented Analysisand Design. Applying UML and Patterns in OOA/D. AssigningResponsibilities. What Is Analysis and Design? What Is Object-OrientedAnalysis and Design? An Example. The UML. Further Readings. 2. IterativeDevelopment and the Unified Process. The Most Important UP Idea: IterativeDevelopment. Additional UP Best Practices and Concepts. The UP Phases andSchedule-Oriented Terms. The UP Disciplines (was Workflows). ProcessCustomization and the Development Case. The Agile UP. The Sequential"Waterfall" Lifecycle. You Know You Didn't Understand the UP When... FurtherReadings. 3. Case Study: The NextGen POS System. The NextGen POS System.Architectural Layers and Case Study Emphasis. The Book's Strategy: IterativeLearning and Development. II. INCEPTION. 4. Inception. Inception: AnAnalogy. Inception May Be Very Brief. What Artifacts May Start in Inception?You Know You Didn't Understand Inception When... 5. UnderstandingRequirements. Types of Requirements. Further Readings. 6. Use-Case Model:Writing Requirements in Context. Goals and Stories. Background. Use Casesand Adding Value. Use Cases and Functional Requirements. Use Case Types andFormats. Fully Dressed Example: Process Sale. Explaining the Sections. Goalsand Scope of a Use Case. Finding Primary Actors, Goals, and Use Cases.Congratulations: Use Cases Have Been Written, and Are Imperfect. Write UseCases in an Essential UI-Free Style. Actors. Use Case Diagrams. Requirementsin Context and Low-Level Feature Lists. Use Cases Are Not Object-Oriented.Use Cases Within the UP. Case Study: Use Cases in the NextGen InceptionPhase. Further Readings. UP Artifacts and Process Context. 7. IdentifyingOther Requirements. NextGen POS Examples. NextGen Example: (Partial)Supplementary Specification. Commentary: Supplementary Specification. NextGenExample: (Partial) Vision. Commentary: Vision. NextGen Example: A (Partial)Glossary. Commentary: Glossary (Data Dictionary). Reliable Specifications: AnOxymoron? Online Artifacts at the Project Website. Not Much UML DuringInception? Other Requirement Artifacts Within the UP. Further Readings. UPArtifacts and Process Context. 8. From Inception to Elaboration.Checkpoint: What Happened in Inception? On to Elaboration. Planning the NextIteration. Iteration 1 Requirements and Emphasis: Fundamental OOA/D Skills.What Artifacts May Start in Elaboration? You Know You Didn't UnderstandElaboration When... III. ELABORATION ITERATION. 9. Use-Case Model: DrawingSystem Sequence Diagrams. System Behavior. System Sequence Diagrams.Example of an SSD. Inter-System SSDs. SSDs and Use Cases. System Events andthe System Boundary. Naming System Events and Operations. Showing Use CaseText. SSDs and the Glossary. SSDs Within the UP. Further Readings. UPArtifacts. 10. Domain Model: Visualizing Concepts. Domain Models.Conceptual Class Identification. Candidate Conceptual Classes for the SalesDomain. Domain Modeling Guidelines. Resolving Similar ConceptualClasses-Register vs. "POST". Modeling the Unreal World. Specification orDescription Conceptual Classes. UML Notation, Models, and Methods: MultiplePerspectives. Lowering the Representational Gap. Example: The NextGen POSDomain Model. Domain Models Within the UP. Further Readings. UP Artifacts.11. Domain Model: Adding Associations. Associations. The UML AssociationNotation. Finding Associations-Common Associations List. AssociationGuidelines. 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. DomainModel: Adding Attributes. Attributes. UML Attribute Notation. ValidAttribute Types. Non-primitive Data Type Classes. Design Creep: No Attributesas Foreign Keys. Modeling Attribute Quantities and Units. Attributes in theNextGen Domain Model. Multiplicity From SalesLineItem to Item. Domain ModelConclusion. 13. Use-Case Model: Adding Detail with Operation Contracts.Contracts. Example Contract: enterItem. Contract Sections. Postconditions.Discussion-enterItem Postconditions. Writing Contracts Leads to Domain ModelUpdates. 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 ToDo? No, Not Exactly. On to Object Design. 15. Interaction Diagram Notation.Sequence and Collaboration Diagrams. Example Collaboration Diagram:makePayment. Example Sequence Diagram: makePayment. Interaction Diagrams AreValuable. Common Interaction Diagram Notation. Basic Collaboration DiagramNotation. Basic Sequence Diagram Notation. 16. GRASP: Designing Objects withResponsibilities. Responsibilities and Methods. Responsibilities andInteraction Diagrams. Patterns. GRASP: Patterns of General Principles inAssigning Responsibilities. The UML Class Diagram Notation. InformationExpert (or Expert). Creator. Low Coupling. High Cohesion. Controller. ObjectDesign and CRC Cards. Further Readings. 17. Design Model: Use-CaseRealizations with GRASP Patterns. Use-Case Realizations. ArtifactComments. Use-Case Realizations for the NextGen Iteration. Object Design:makeNewSale. Object Design: enterItem. Object Design: endSale. Object Design:makePayment. Object Design: startUp. Connecting the UI Layer to the DomainLayer. 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 ClassDiagrams. When to Create DCDs. Example DCD. DCD and UP Terminology. DomainModel vs. Design Model Classes. Creating a NextGen POS DCD. Notation forMember Details. DCDs, Drawing, and CASE Tools. DCDs Within the UP. UPArtifacts. 20. Implementation Model: Mapping Designs to Code. Programmingand the Development Process. Mapping Designs to Code. Creating ClassDefinitions from DCDs. Creating Methods from Interaction Diagrams.Container/Collection Classes in Code. Exceptions and Error Handling. Definingthe Sale-makeLineItem Method. Order of Implementation. Test-FirstProgramming. Summary of Mapping Designs to Code. Introduction to the ProgramSolution. IV. ELABORATION ITERATION 2. 21. Iteration 2 and itsRequirements. Iteration 2 Emphasis: Object Design and Patterns. FromIteration 1 to 2. Iteration 2 Requirements. Refinement of Analysis-orientedArtifacts in this Iteration. 22. GRASP: More Patterns for AssigningResponsibilities. Polymorphism. Pure Fabrication. Indirection. ProtectedVariations. 23. Designing Use-Case Realizations with GoF Design Patterns.Adapter (GoF). "Analysis" Discoveries During Design: Domain Model. Factory(GoF). Singleton (GoF). Conclusion of the External Services with VaryingInterfaces Problem. Strategy (GoF). Composite (GoF) and Other DesignPrinciples. Facade (GoF). Observer/Publish-Subscribe/Delegation Event Model(GoF). Conclusion. Further Readings. V. ELABORATION ITERATION 3. 24.Iteration 3 and Its Requirements. Iteration 3 Requirements. Iteration 3Emphasis. 25. Relating Use Cases. The include Relationship. Terminology:Concrete, Abstract, Base, and Addition Use Cases. The extend Relationship.The generalize Relationship. Use Case Diagrams. 26. Modeling Generalization.New Concepts for the Domain Model. Generalization. Defining ConceptualSuperclasses and Subclasses. When to Define a Conceptual Subclass. When toDefine a Conceptual Superclass. NextGen POS Conceptual Class Hierarchies.Abstract Conceptual Classes. Modeling Changing States. Class Hierarchies andInheritance in Software. 27. Refining the Domain Model. AssociationClasses. Aggregation and Composition. Time Intervals and ProductPrices-Fixing an Iteration 1 "Error". Association Role Names. Roles asConcepts vs. Roles in Associations. Derived Elements. Qualified Associations.Reflexive Associations. Ordered Elements. Using Packages to Organize theDomain Model. 28. Adding New SSDs and Contracts. New System SequenceDiagrams. New System Operations. New System Operation Contracts. 29.Modeling Behavior in Statechart Diagrams. Events, States, and Transitions.Statechart Diagrams. Statechart Diagrams in the UP? Use Case StatechartDiagrams. Use Case Statechart Diagrams for the POS Application. Classes thatBenefit from Statechart Diagrams. Illustrating External and Interval Events.Additional Statechart Diagram Notation. Further Readings. 30. Designing theLogical Architecture with Patterns. Software Architecture. ArchitecturalPattern: Layers. The Model-View Separation Principle. Further Readings. 31.Organizing the Design and Implementation Model Packages. PackageOrganization Guidelines. More UML Package Notation. Further Readings. 32.Introduction to Architectural Analysis and the SAD. ArchitecturalAnalysis. Types and Views of Architecture. The Science: Identification andAnalysis of Architectural Factors. Example: Partial NextGen POS ArchitecturalFactor Table. The Art: Resolution of Architectural Factors. Summary of Themesin Architectural Analysis. Architectural Analysis within the UP. FurtherReadings. 33. Designing More Use-Case Realizations with Objects andPatterns. Failover to Local Services; Performance with Local Caching.Handling Failure. Failover to Local Services with a Proxy (GoF). Designingfor Non-Functional or Quality Requirements. Accessing External PhysicalDevices with Adapters; Buy vs. Build. Abstract Factory (GoF) for Families ofRelated Objects. Handling Payments with Polymorphism and Do It Myself.Conclusion. 34. Designing a Persistence Framework with Patterns. TheProblem: Persistent Objects. The Solution: A Persistence Service from aPersistence Framework. Frameworks. Requirements for the Persistence Serviceand Framework. Key Ideas. Pattern: Representing Objects as Tables. UML DataModeling Profile. Pattern: Object Identifier. Accessing a Persistence Servicewith a Facade. Mapping Objects: Database Mapper or Database Broker Pattern.Framework Design with the Template Method Pattern. Materialization with theTemplate Method Pattern. Configuring Mappers with a MapperFactory. Pattern:Cache Management. Consolidating and Hiding SQL Statements in One Class.Transactional States and the State Pattern. Designing a Transaction with theCommand Pattern. Lazy Materialization with a Virtual Proxy. How to RepresentRelationships in Tables. PersistentObject Superclass and Separation ofConcerns. Unresolved Issues. VI. SPECIAL TOPICS. 35. On Drawing and Tools.On Speculative Design and Visual Thinking. Suggestions for UML DrawingWithin the Development Process. Tools and Sample Features. Example Two. 36.Introduction to Iterative Planning and Project Issues. RankingRequirements. Ranking Project Risks. Adaptive vs. Predictive Planning. Phaseand Iteration Plans. Iteration Plan: What to Do in the Next Iteration?Requirements Tracking Across Iterations. The (In)Validity of Early Estimates.Organizing Project Artifacts. Some Team Iteration Scheduling Issues. You KnowYou Didn't Understand Planning in the UP When... Further Readings. 37.Comments on Iterative Development and the UP. Additional UP Best Practicesand Concepts. The Construction and Transition Phases. Other InterestingPractices. Motivations for Timeboxing an Iteration. The Sequential"Waterfall" Lifecycle. Usability Engineering and User Interface Design. TheUP Analysis Model. The RUP Product. The Challenge and Myths of Reuse. 38.More UML Notation. General Notation. Implementation Diagrams. Template(Parameterized, Generic) Class. Activity Diagrams. Bibliography. Glossary.Index.