220 likes | 234 Views
ARCHITECTURAL MODELING. 主講人 : 李榮華. Outline. Deployment Deployment Diagrams Collaborations Patterns and Frameworks. Deployment- Node and connections.
E N D
ARCHITECTURAL MODELING 主講人:李榮華
Outline • Deployment • Deployment Diagrams • Collaborations • Patterns and Frameworks
Deployment-Node and connections • Node:A node is a physical element that exists at run time and represents a computational resource,generally having at least some memory and,often,processing capability. • Ref.P361,Fig. 26-2 • Connections:An association represents a physical connection among nodes. • Ref.P363,Fig 26-4
Deployment Diagram-Common Modeling Techniques • Modeling an Embedded System Ref.p412.fig30-2 • Modeling a Client/Server System Ref.p414.fig30-3 • Modeling a Fully Distributed System Ref.p415.fig30-4
Collaborations • A collaboration is a society of classes,interfaces,and other elements that work together to provide some cooperative behavior that’s bigger than the sum of all its parts.
Modeling the Realization of a Use case and an Operation • Modeling the Realization of a Use Case Ref.P376,fig 27-5 • Modeling the Realization of an operation Ref.P377,fig27-6
Patterns and frameworks • Patterns:A patterns provides a common solution to a common problem in a given context. • Framework:A framework is typically an architectural pattern that provides an extensible template for applications within a domain.
Mechanisms • A mechanism is just another name for a design pattern that applies to a society of classes. • Mechanisms show up in two ways: • Collaborations.(p382,fig28-1) • Parameterized Collaborations.(p385,fig28-2)
Modeling Design Patterns • Identify the common solution to the common problem and reify it as a mechanism. • Model the mechanism as a collaboration,providing its structural,as well as its behavioral,aspects. • Identify the elements of the design pattern that must be bound to elements in a specific context and render them as parameters to the collaboration. • Ref.p388,fig28-4
Modeling Architectural Patterns • Harvest the framework from an existing,proven architecture • Model the framework as a stereotyped package,containing all the elements(and especially the design patterns)that are necessary and sufficient to describe the various views of that framework. • Expose the slots,tabs,knobs,and dials necessary to adapt the framework in the form of design patterns and collaboration.For the most part,this means making it clear to the user of the pattern which classes must be extended,which operations must be implemented ,and which signals must be handled.(Ref.P386,fig28-3)