yyy1

Design Patterns
This module introduces students to Windchill design patterns such as master-version-iteration.
Objectives
Upon successful completion of this module, you will be able to:
• Perform tasks related to the customization process as defined in the Application Solution Development module of the System RVP work stream.
• Explain the concept of design patterns.
• Explain the master-version-iteration design pattern pattern.
• Explain the enumerated type pattern.
Windchill Design Patterns
Windchill design patterns are common/standard ways of doing things to produce common/standard results in the software and UI.
Some of the patterns are “built-in” to Windchill and will appear automatically by extending classes in Rational Rose. Examples include:
• Master-version-iteration
Some of the patterns are implemented by building new customization that copies the existing design pattern.
• Enumerated types
• Services
Master-Version-Iteration
There are 3 distinct functions (represented by modeled Interfaces) that come together to form the master-version-iteration pattern:
1. Master information represents common information that would apply to every version or iteration.
• Examples of masters include WTPartMaster and WTDocumentMaster.
• Common information includes name and number.
• Changing the name or number (re-identification) affects all version and iterations.
2. A version typically represents a branch of development and uniquely releasable data that is separate from other branches which are uniquely releaseable data
• The most common implementation is wt.fc.ControlBranch
• Common information is version identifier, life cycle template.
• Parts and Documents have versions, which actual display information from the latest iteration of a ControlBranch object.
3. An iteration is the incremental details and changes
• Examples of iterations include WTPart and WTDocument.
• The incremental detail information includes content and attribute values.
Properties seen from the UI for an object that implements the master-version-iteration pattern,aggregates information from:
• Name and number from the master
• Version identifier from the version
• Attributes and content information from the latest information associated with the version me of the information is coming from the master, some from the version and some from the iteration From the API documentation for the wt.vc package:
---
Note: Iterations are not shown.
Enumerated Types
Enumerated types are special Windchill attributes that have a discrete set of valid input values.
OOTB Examples:
• Part
– Source (Make, Buy)
– QuantityUnit (Each, As Needed, Liters, Kilograms, Meters)
– PartType (Component, Inseparable Assembly, Separable Assembly)
• Document
– DocumentType (Document, Requirements Document, Test Plan, etc.)
– DepartmentList (Accounting, Design, Manufacturing, etc.)
• Change Objects
– Category (Safety Issue, Cost Reduction, Other etc.)
– IssuePriority (High, Medium, Low, Emergency)
– Complexity (Simple, Complex)
• CAD Documents
– EPMAuthoringAppType (Pro/ENGINEER, AutoCAD, Catia, SolidWorks, Unigraphics, etc.)
– EPMDocSubType (NC Model, Process Plan, Skeleton, Sheet Metal, etc.)
Note: Some of these objects were used more significantly in older versions.
Services
Services provide functionality in two particular areas:
1. A mechanism for clients to call server side methods (which are invoked and processed on
the server) to take advantage of server performance and centralized resources
2. A mechanism for Windchill to “listen” for, and in turn respond to, system events such as:
• Check in
• Check out
• State change
• Update
• Delete