Uses of Package
cb.petal

Packages that use cb.petal

Package	Description
cb.generator	This package contains bases classes and interfaces for the generators.
cb.generator.java	This package contains a simple Java generator that reads in a PetalFile tree as input.
cb.parser	This package contains the Parser for Rational Rose Petal files.
cb.petal
cb.petaltools
cb.util
cb.xmi

Classes in cb.petal used by cb.generator

Class and Description
Association Represents Association object
Attribute Represents Attribute objects used in tagged values @see ClassAttribute for Attributes of classes
Class Represents Class object, there are a lot of convenience methods here for adding super class(es), operations, attributes, etc.
ClassAttribute Represents class attribute (aka field) of class object.
ClassCategory Class category is used for structuring into submodels and -views, it may contain further class categories.
DescendingVisitor By default visits petal tree with DFS.
HasQuidu Denote that a petal object contains a reference to another object via the property "quidu".
InheritanceRelationship Represents inheritance relationship between classes.
Operation Represents operation object, i.e. method.
PetalFile Top level node (aka. model) containing two children: Petal and Design.
PetalObject Super class for all petal objects which have a list of properties.
RealizeRelationship Represents Realize relationship ("implements").
UsesRelationship Represents uses relationship in use case diagrams, in class diagrams this is also used to express dependency relationships.
Visitor Visitor interface.

Classes in cb.petal used by cb.generator.java

Class and Description
Attribute Represents Attribute objects used in tagged values @see ClassAttribute for Attributes of classes
Class Represents Class object, there are a lot of convenience methods here for adding super class(es), operations, attributes, etc.
ClassAttribute Represents class attribute (aka field) of class object.
ClassCategory Class category is used for structuring into submodels and -views, it may contain further class categories.
DescendingVisitor By default visits petal tree with DFS.
Documented Denote that a petal object may have documentation associated with it.
Operation Represents operation object, i.e. method.
Parameter Represents Parameter object for operations (methods).
PetalFile Top level node (aka. model) containing two children: Petal and Design.
PetalNode Super class for all petal nodes, e.g., objects, lists, value, literals, etc..
QuidObject Super class for all petal objects that have a "quid" property defined, i.e. a globally unique identifier.
Role Represents Role object
UsesRelationship Represents uses relationship in use case diagrams, in class diagrams this is also used to express dependency relationships.
Visitor Visitor interface.

Classes in cb.petal used by cb.parser

Class and Description
Association Represents Association object
BooleanLiteral Boolean literal which may obviously either be true or false.
Class Represents Class object, there are a lot of convenience methods here for adding super class(es), operations, attributes, etc.
DescendingVisitor By default visits petal tree with DFS.
FloatLiteral Floating point literal (in fact a double).
IntegerLiteral Integer literal.
List Lists (list foo ...) containing other petal nodes.
Location Tuple of integer values like (1520, 96).
PetalFile Top level node (aka. model) containing two children: Petal and Design.
PetalNode Super class for all petal nodes, e.g., objects, lists, value, literals, etc..
PetalObject Super class for all petal objects which have a list of properties.
StringLiteral There are two kinds of string encodings in Rose: Either the usual "foo bar", or a multi line string where each line starts with a |.
Tag Reference to object.
Tuple Tuple (name, value), like in ("DataBaseSet" 800)
Value Values like in (value Text "foo")
Visitor Visitor interface.

Classes in cb.petal used by cb.petal

Class and Description
AccessObject Super class for all petal objects that have access qualifiers, i.e., "Public", "Protected", "Private", or "Implementation" (whatever that means, probably it reads "language dependent")
AccessQualified Denote that a petal object may have an attribute "exportControl", e.g. classes, methods, ..., which refers to a qualifier like "public", "protected", ...
Action Represents action object
ActionTime Represents ActionTime object
ActivityDiagram Represents ActivityDiagram object
ActivityState Represents ActivityState object
ActivityStateView Represents ActivityStateView object
AssocAttachView Represents AssocAttachView object which is means it is just the line drawn between an association and an association class.
Association Represents Association object
AssociationViewNew Represents AssociationViewNew object, i.e. the view for an association.
AttachView Represents AttachView object which means the line drawn between a note (view) and some entity.
Attribute Represents Attribute objects used in tagged values @see ClassAttribute for Attributes of classes
BooleanLiteral Boolean literal which may obviously either be true or false.
CategoryView This view corresponds to a ClassCategory object.
Class Represents Class object, there are a lot of convenience methods here for adding super class(es), operations, attributes, etc.
ClassAttribute Represents class attribute (aka field) of class object.
ClassCategory Class category is used for structuring into submodels and -views, it may contain further class categories.
ClassDiagram Represents ClassDiagram object contained within a LogicalCategory object.
ClassInstanceView Represents ClassInstanceView object
ClassView Represents ClassView object
Compartment Represents Compartment object
ConnectionRelationship Represents Connection_Relationship object
ConnectionView Represents ConnectionView object
DataFlowView Represents DataFlowView object
Decision Represents Decision object
DecisionView Represents DecisionView object
Defaults Represents defaults for top level design object.
DependencyRelationship Represents Dependency_Relationship object
DependencyView Represents DependencyView object
DerivedClass Super class for instantiated and paramerized class objects.
Design Represents top level design object.
Device Represents Device object
DeviceView Represents DeviceView object
Diagram Super class for diagrams
Documented Denote that a petal object may have documentation associated with it.
Event Represents Event object
ExternalDoc Refer to external documentation, i.e. a file or URL
FloatLiteral Floating point literal (in fact a double).
FocusOfControl Represents Focus_Of_Control object
Font Represents font object.
HasQuidu Denote that a petal object contains a reference to another object via the property "quidu".
HasSupplier Denote that a petal object contains a reference to another object via the property "supplier", i.e., a fully qualified name like "Logical View::University::Professor".
ImportView Represents ImportView object
Inheritable Denote that a petal object may be extended, i.e. classes and use cases.
InheritanceRelationship Represents inheritance relationship between classes.
InheritTreeView Represents InheritTreeView object
InheritView Represents InheritView object, i.e. view for InheritanceRelationship
InstantiatedClass Represents Instantiated_Class object
InstantiateView Represents InstantiateView object
InstantiationRelationship Represents Instantiation_Relationship object
IntegerLiteral Integer literal.
InteractionDiagram Represents InteractionDiagram object
InterfaceView Represents InterfaceView object
InterMessView Represents InterMessView object
InterObjView Represents InterObjView object
ItemLabel Represents ItemLabel object attached to View objects, ClassView in particular
Label Represents Label object
Labeled Denote that a petal object may have a label.
Link Represents Link object
LinkSelfView Represents LinkSelfView object
LinkView Represents LinkView object
List Lists (list foo ...) containing other petal nodes.
Literal Super class for literals like int, String, value, etc.
Location Tuple of integer values like (1520, 96).
LogicalCategory The Logical category contains class diagrams.
Mechanism Represents Mechanism object
Message Represents Message object
MessView Represents MessView object
Module Represents module object
ModuleDiagram Represents Module_Diagram object
ModuleVisibilityRelationship Represents Module_Visibility_Relationship object
ModView Represents ModView object
ModVisView Represents ModVisView object
Named Denote that a petal object has a name parameter, e.g.
NoteView Represents NoteView object, i.e. a note on the screan that may be attached to an entity.
Object Represents Object object
ObjectDiagram Represents ObjectDiagram object
ObjectView Represents ObjectView object
Operation Represents operation object, i.e. method.
Parameter Represents Parameter object for operations (methods).
ParameterizedClass Represents Parameterized_Class object
Partition Represents Partition object
Petal Represents top level petal object.
PetalFile Top level node (aka. model) containing two children: Petal and Design.
PetalNode Super class for all petal nodes, e.g., objects, lists, value, literals, etc..
PetalObject Super class for all petal objects which have a list of properties.
Process Represents Process object
ProcessDiagram Represents Process_Diagram object
Processes Represents Processes object
Processor Represents Processor object
ProcessorView Represents ProcessorView object
Properties Represents Properties object
Qualified Denote that a petal object has a qualified name parameter, e.g.
QuidObject Super class for all petal objects that have a "quid" property defined, i.e. a globally unique identifier.
QuiduObject Super class for all quid objects that also have a quidu property defined.
QuiduView Super class for all view objects with a "quidu" property defined.
RealizeRelationship Represents Realize relationship ("implements").
RealizeView Represents RealizeView object
Relationship Super class for all relationships between classes.
RelationshipView Super class for all relationship view objects.
Role Represents Role object
RoleView Represents RoleView object
SegLabel Represents SegLabel object attached to associations
SegLabeled Denote that a petal object has a SegLabel label
SelfMessView Represents SelfMessView object = message to self in sequence diagram
SemanticInfo Pre or postcondition of method
SendEvent Represents sendEvent object
SimpleObject Very simple object, basically just a record.
SimpleViewObject Very simple object, basically just a record.
State Represents State object
StateDiagram Represents State_Diagram object
StateMachine Represents State_Machine object
StateTransition Represents State_Transition object
StateView Represents StateView object
StereoTyped Denote that a petal object may have an attribute "stereotype", e.g. classes, methods, ...
StringLiteral There are two kinds of string encodings in Rose: Either the usual "foo bar", or a multi line string where each line starts with a |.
SubSystem Represents SubSystem object
SubSysView Represents SubSysView object
Swimlane Represents Swimlane object
SynchronizationState Represents SynchronizationState object
SynchronizationView Represents SynchronizationView object
Tag Reference to object.
Tagged Denote that a petal object has a tag, i.e. @12
TransView Represents TransView object
Tuple Tuple (name, value), like in ("DataBaseSet" 800)
UseCase Represents UseCase object
UseCaseCategory Use case class category.
UseCaseDiagram Represents UseCaseDiagram object
UseCaseView Represents UseCaseView object
UsesRelationship Represents uses relationship in use case diagrams, in class diagrams this is also used to express dependency relationships.
UsesView Represents UsesView object
Value Values like in (value Text "foo")
View Super class for all view objects used in the diagrams.
VisibilityRelationship Represents Visibility_Relationship object
Visitor Visitor interface.

Classes in cb.petal used by cb.petaltools

Class and Description
PetalFile Top level node (aka. model) containing two children: Petal and Design.

Classes in cb.petal used by cb.util

Class and Description
AssocAttachView Represents AssocAttachView object which is means it is just the line drawn between an association and an association class.
Association Represents Association object
AssociationViewNew Represents AssociationViewNew object, i.e. the view for an association.
AttachView Represents AttachView object which means the line drawn between a note (view) and some entity.
Class Represents Class object, there are a lot of convenience methods here for adding super class(es), operations, attributes, etc.
ClassAttribute Represents class attribute (aka field) of class object.
ClassUtility Represents Class Utility object, i.e., helper class
ClassView Represents ClassView object
DescendingVisitor By default visits petal tree with DFS.
Inheritable Denote that a petal object may be extended, i.e. classes and use cases.
InheritanceRelationship Represents inheritance relationship between classes.
ItemLabel Represents ItemLabel object attached to View objects, ClassView in particular
List Lists (list foo ...) containing other petal nodes.
LogicalCategory The Logical category contains class diagrams.
NoteView Represents NoteView object, i.e. a note on the screan that may be attached to an entity.
Operation Represents operation object, i.e. method.
PetalFile Top level node (aka. model) containing two children: Petal and Design.
PetalNode Super class for all petal nodes, e.g., objects, lists, value, literals, etc..
PetalObject Super class for all petal objects which have a list of properties.
RealizeRelationship Represents Realize relationship ("implements").
SegLabel Represents SegLabel object attached to associations
UseCase Represents UseCase object
UseCaseCategory Use case class category.
UseCaseView Represents UseCaseView object
UsesRelationship Represents uses relationship in use case diagrams, in class diagrams this is also used to express dependency relationships.
Visitor Visitor interface.

Classes in cb.petal used by cb.xmi

Class and Description
AccessQualified Denote that a petal object may have an attribute "exportControl", e.g. classes, methods, ..., which refers to a qualifier like "public", "protected", ...
Association Represents Association object
Class Represents Class object, there are a lot of convenience methods here for adding super class(es), operations, attributes, etc.
ClassAttribute Represents class attribute (aka field) of class object.
ClassCategory Class category is used for structuring into submodels and -views, it may contain further class categories.
DependencyRelationship Represents Dependency_Relationship object
DescendingVisitor By default visits petal tree with DFS.
InheritanceRelationship Represents inheritance relationship between classes.
LogicalCategory The Logical category contains class diagrams.
Module Represents module object
Operation Represents operation object, i.e. method.
PetalFile Top level node (aka. model) containing two children: Petal and Design.
PetalObject Super class for all petal objects which have a list of properties.
QuidObject Super class for all petal objects that have a "quid" property defined, i.e. a globally unique identifier.
RealizeRelationship Represents Realize relationship ("implements").
Role Represents Role object
StereoTyped Denote that a petal object may have an attribute "stereotype", e.g. classes, methods, ...
SubSystem Represents SubSystem object
UseCase Represents UseCase object
UseCaseCategory Use case class category.
UsesRelationship Represents uses relationship in use case diagrams, in class diagrams this is also used to express dependency relationships.
Visitor Visitor interface.