book

Pattern-Oriented Analysis and Design: Composing Patterns to Design Software Systems

by Sherif M. Yacoub, Hany H. Ammar

August 2003

Intermediate to advanced

416 pages

11h 21m

English

Addison-Wesley Professional

Read now

Unlock full access

Dedication
What Do We Reuse?Composing Design PatternsPOADAudiencePrior KnowledgeScopeHow to Read the Book
The Role of Patterns in Software DevelopmentPurpose of POADPattern-Oriented Design IssuesPOAD Is a SolutionWhat Is Covered in this Book?
Design Patterns in the Software LifecyclePOAD and OO TechnologyDesign PatternsWhat Is a Pattern?History of PatternsThe Pattern LifecycleDesign FrameworksWhat Is a Framework?Developing Robust Designs using FrameworksThe Role of Patterns in Developing OO FrameworksDesign Pattern Composition ApproachesSummary
Behavioral Composition TechniquesObject-Oriented Role Analysis and Software SynthesisComposing Design Patterns Using RolesArchitecture Fragments and SuperimpositionRole/Type/Class ModelingStructural Composition of Design PatternsA Pattern-Oriented Composition TechniqueSoftware Composition at the Design Level Using Design ComponentsComponent-Based Frameworks Using PatternsThe Catalysis ApproachComposition Patterns, Subject-Oriented Programming, and Aspect-Oriented Software DevelopmentFurther Reading
Which Patterns to Use in POADSoftware ComponentsA Design ComponentConstructional Design PatternsSpecifying a Pattern as a ComponentA RecipeFormal SpecificationInterface SpecificationComponent InterfacesModule Interconnection LanguagesInterface Definition LanguageInterfaces for Object-Oriented ComponentsApplication/Platform InterfacesInterface PropertiesTypeRoleNatureDynamismDescriptionMultiplicityPattern InterfacesSummary
Pattern Composition ModelsPattern-Level ModelSchematic DiagramRelationshipsDesign DecisionsUML Syntax SupportExamplePattern-Level with Interfaces ModelSchematic DiagramRelationshipsDesign DecisionsUML Syntax SupportExampleDetailed Pattern-Level ModelSchematic DiagramRelationshipsDesign DecisionsUML Syntax SupportExampleCharacteristics of the POAD Design ModelsHierarchyTraceabilityComposabilitySummary

Patterns as MechanismsArchitectural PatternsPatterns as PackagesPatterns and ComponentsModeling Pattern-Oriented DesignsA ComparisonSummary
Stringing Versus OverlappingPOAD Process Outline (The Nutshell)Analysis PhasePurposeProcessProductDesign PhasePurposeProcessProductDesign Refinement PhasePurposeProcessProductPOAD and Code GenerationPOAD CharacteristicsPattern-DrivenComponent-Based DevelopmentArchitectural DevelopmentLibrary-Driven DevelopmentDesign ReuseHierarchical DevelopmentIterative DevelopmentPattern-Oriented FrameworksPattern-Level InstantiationClass-Level InstantiationBenefits and LimitationsBenefitsLimitationsSummary
OverviewRequirements AnalysisPurposeProcessFinding ComponentsAssigning Responsibilities to ComponentsRelationship to Software ArchitectureAnalyzing Large ApplicationsIterating with Other Analysis ActivitiesProductAnalysis TipsAcquaintancePurposeProcessPattern Database ActivitiesWhat Is Acquaintance?What versus How!Rationale and ExampleIterationProductAnalysis TipsRetrievalPurposeProcessSoftware Asset LibrariesThe Database QueryRetrieval GoalsA True Pattern LibraryPractical Guidelines for Matching CriteriaProductAnalysis TipsPattern SelectionPurposeProcessProblem-Solution MatchingSelection Is DifficultIterationUsing Domain-Specific LibrariesStudy Relationships Between PatternsProductAnalysis TipsSummary
OverviewConstructing Pattern-Level ModelsPurposeProcessCreating Pattern InstancesMultiple Instances of the Same TypeDefining Pattern Instance RelationshipsDevelop the Pattern-Level DiagramsSubsystems and FrameworksProductDesign TipsConstructing Pattern-Level with Interfaces ModelsPurposeProcessExposing the Pattern Instance InterfacesIdentifying Relationships Between Pattern Instance InterfacesInterface RelationshipsProductDesign TipsConstructing Detailed Pattern-Level ModelsPurposeProcessExplore the Pattern StructureDynamic Aspects Are Also ImportantRealization of the InterfaceProductDesign TipsSummary
OverviewInstantiating Pattern InternalsPurposeProcessSpecialization (Generic to Application-Specific)Instantiation Through Subclassing and RealizationKeeping the History of the Participants' NamesConcretizationThe ScopeProductDesign-Refinement TipsDeveloping the Initial Class DiagramPurposeProcessRevealing the Instantiated Pattern InternalsTracing the Pattern Interfaces to Internal RealizationTracing the Relationships Between Pattern InstancesProductDesign-Refinement TipsDesign OptimizationPurposeProcessReductionMerging and GroupingProductDesign-Refinement TipsUsing POAD for Developing FrameworksSummary
POAD Analysis for the Feedback Control FrameworkRequirements AnalysisPattern SelectionPOAD Design for the Feedback Control FrameworkConstructing Pattern-Level DiagramsConstructing the Pattern-Level with Interfaces DiagramConstructing Detailed Pattern-Level DiagramsPOAD Design Refinement for the Feedback Control FrameworkInstantiating Pattern InternalsDeveloping an Initial Class DiagramHow About Code Generation?Design OptimizationReductionGroupingExample: Quality Control in Production LinesSystem DescriptionApplication-Specific ConsiderationsInstantiation of the frameworkSample ImplementationSummary
Background and RequirementsDomain EngineeringApplication EngineeringPOAD Analysis for the Waiting-Queues Simulation ArchitectureRequirements AnalysisAcquaintance and RetrievalPattern SelectionPOAD Design for the Waiting-Queues Simulation ArchitectureConstructing Pattern-Level DiagramsConstructing Pattern-Level with Interfaces DiagramsConstructing Detailed Pattern-Level DiagramsPOAD Design Refinement for the Waiting-Queues Simulation ArchitectureInstantiating Pattern InternalsDeveloping an Initial Class DiagramHow About Code Generation?Design OptimizationSample ImplementationSummary
Document UnderstandingApplications and SystemsA DCRM SystemDCRM SubsystemsPattern-Oriented Analysis and Design for the Distribution SubsystemPOAD Analysis for the DCRM Distribution SubsystemRequirements AnalysisAcquaintance and RetrievalPattern SelectionPOAD Design for the DCRM Distribution SubsystemConstructing the Pattern-Level DiagramConstructing the Pattern-Level with Interfaces DiagramConstructing the Detailed Pattern-Level diagramsPOAD Design Refinement for the DCRM Distribution SubsystemInstantiating Pattern InternalsDeveloping an Initial Class DiagramDesign OptimizationPattern-Oriented Analysis and Design for the Filtering SubsystemPOAD Analysis for the DCRM Filtering SubsystemRequirements AnalysisAcquaintance and RetrievalPattern SelectionPOAD Design for the DCRM Filtering SubsystemConstructing the Pattern-Level diagramConstructing Pattern-Level with Interfaces DiagramConstructing Detailed Pattern-Level ViewPOAD Design Refinement for the DCRM Filtering SubsystemInstantiating Pattern InternalsDeveloping an Initial Class DiagramDesign OptimizationSummary
Medical Informatics StandardsDigital Imaging and Communication in Medicine (DICOM)Specification Versus ImplementationDICOM ScopeA Client/Server ArchitecturePattern-Oriented Analysis and Design of the DICOM ULPOAD Analysis for DICOM Upper-Layer SubsystemRequirements AnalysisAcquaintance and RetrievalPattern SelectionPOAD Design for DICOM Upper-Layer SubsystemConstructing Pattern-Level DiagramsConstructing Pattern-Level with Interfaces DiagramsConstructing Detailed Pattern-Level DiagramsPOAD Design Refinement for the DICOM Upper-Layer SubsystemInstantiating Pattern InternalsDeveloping an Initial Class DiagramDesign OptimizationPOAD is Simple Process for Designing Reactive SystemsPattern-Oriented Analysis and Design for the Client Application EntityPOAD Analysis for the Client Application EntityRequirements AnalysisAcquaintance and RetrievalPattern SelectionThe Client User InterfaceCommand InterpreterService Object PairsProtocol MachineMessage CoordinatorDICOM UL ClientPOAD Design for the Client Application EntityConstructing Pattern-Level DiagramsConstructing Pattern-Level with Interfaces DiagramsConstructing Detailed Pattern-Level DiagramPOAD Design Refinement for the Client Application EntityInstantiating Pattern InternalsDeveloping an Initial Class DiagramDesign OptimizationSummary
Syntax Is Not EnoughThe Object Constraint LanguageWhat Is OCL?Using OCLAdding POAD Constructs to the UML MetamodelAbstract SyntaxPatternAttributesPatternDependencyAssociationsPatternAssociationAssociationsPatternInfoPatternInterfaceAssociationsPatternKindPatternPresentationInterfaceBinderWell-Formedness RulesPatternPatternDependencyPatternAssociationPatternInterfaceInterfaceBinderSemanticsPatternRelationshipsSummary
The Need for Tool SupportPattern ToolsFramework Adaptive Composition EnvironmentFragmentation TechniquePSiGeneCode GenerationThe Pattern LintHooks and TemplatesTogetherSoftRequirements and Features of a POAD ToolPatterns as First-Class Design ElementsPOAD Hierarchical ModelsTraceabilityPattern RepositoryModels with MemoryPattern instantiationSummary
Systematic Composition of Design PatternPOAD CharacteristicsPOAD and Software ReuseApplying POADPattern LiteratureFuture Trends in Pattern CompositionConclusion
Strategy PatternObserver PatternComposite PatternReactor PatternTemplatemethod PatternProxy PatternAbstractfactory PatternBuilder PatternMediator PatternCommand Pattern
Pattern MiningPattern Description Formats (Templates)Tool SupportPattern FormalismPattern LanguagesPattern-Based ImplementationMore ChallengesFormal Specification of Design PatternsPattern Instantiation and ImplementationDevelopment MethodologiesDocumentation of Design PatternsEvaluating Existing Design Patterns

Content preview from Pattern-Oriented Analysis and Design: Composing Patterns to Design Software Systems

Part V. Automation and Summary

In Part 5 we present some steps toward the automation of the POAD methodology. Chapter 15 discusses the UML metamodeling support for POAD models. Defining the relationship between POAD models and the UML metamodel is essential to enable tool support by existing UML tools. In Chapter 16 we discuss the existing tool support for applying, modeling, and composing design patterns and their support for POAD. Finally, Chapter 17 wraps the discussion on POAD and presents some plans to take POAD further into mainstream development.

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.

Start your free trial

Tips for Designing Effective Presentation Slide Decks

Publisher Resources

ISBN: 0201776405Purchase book

Pattern-Oriented Analysis and Design: Composing Patterns to Design Software Systems

by Sherif M. Yacoub, Hany H. Ammar

Part V. Automation and Summary

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.

You might also like

Tips for Designing Effective Presentation Slide Decks

Real-Time Agility: The Harmony/ESW Method for Real-Time and Embedded Systems Development

Pattern-Oriented Software Architecture: A Pattern Language for Distributed Computing, 4th Volume

Software Architecture Hour: Incremental Architecture with Allen Holub

Publisher Resources

Part V. Automation and Summary

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,and much more.

You might also like

Tips for Designing Effective Presentation Slide Decks

Real-Time Agility: The Harmony/ESW Method for Real-Time and Embedded Systems Development

Pattern-Oriented Software Architecture: A Pattern Language for Distributed Computing, 4th Volume

Software Architecture Hour: Incremental Architecture with Allen Holub

Publisher Resources

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.