xxx1

Engineer Component
This module addresses development of Windchill solutions, including custom classes, attributes,enumerated types and services.
Objectives
Upon successful completion of this module, you will be able to:
• Perform tasks in the Engineer Component element of the Application Solution Development module of the System RVP work stream.
• Create a new package structure in Rational Rose.
• Extend a Windchill class.
• Model new attributes in Rational Rose.
• Model enumerated types.
• Implement a modeled customization in Windchill.
Modeling Extensions
A customer has identified a requirement for a new business information type similar to WTDocument with some additional attributes.
This new class of object represents orders from customers, so the model name of this class will be CustomerOrder.
• The Java standard for class names is to capitalize ThemLikeThis.
The first attribute of this class is a String that represents the name of the customer for which the CustomerOrder is being created, so the model name of this attribute will be customerName.
• The Java standard for attribute names is to capitalize themLikeThis.
The customer list is constantly changing, so the valid values of customerName are not restricted.
The customer’s domain is “customer.com”, so the package structure for this customization will be com.customer.doc.
At this time, there will be no custom operations or associations.
Modeling a Windchill Solution in Rational Rose
• Create the package structure
– Configure Rose to store extensions in sub-units (“controlled” units)
• Reference classes to be extended
– Add references to existing classes to class diagrams
• Model the new classes
– Add entirely new classes to class diagrams that reference the existing classes just added to the new diagram
• Model attributes
• Model operations
• Model associations
• Implement the model
Create Package Structure
Modifications in Rose will be saved to this master model file unless the package which has been modified is saved in it’s own standalone controlled unit (or sub-unit as it is sometimes called).
Modeled extensions should always be saved to custom controlled units.
The Windchill model represented by WTDesigner.mdl should never be modified.
The “top” unit for a given customer should match the customer’s domain.
• jp.co.toyota
• com.johndeere
Note:
1. Do not include internet terminology like “www” in the package structure; just the domain.
2. In previous releases, customization was placed under a top unit called “ext”.
Controlled Units and Packages
Users can separate a package into controlled units as a way of sharing and controlling modeled development.
Model changes in packages that are in controlled units are stored as “.cat” files outside the top model (WTDesigner.mdl).
This allows developers to independently work on areas of a master model The master model can be updated by loading the sub-units modified by each developer.
Reference Classes to be Extended
In Rose, add a new class.
When naming the class, Rational Rose will provide a scrollable list of existing classes.
From the list, select the existing Windchill class name to be extended.
Note:
1. Although this is a reference to the source class located in another package,any changes made to this reference is changing the source class.
2. Instead of picking the class, the full name of the existing class (minus the package) could be typed in directly.