IBM® Rational® Rhapsody® Developer for C enables
you to create model elements that represent files. A file is
a graphical representation of a specification (.h)
or implementation (.c) source file.
The file
model element enables you to use functional
modeling and take advantage of the capabilities of Rational Rhapsody (modeling,
execution, code generation, and reverse engineering), without radically
changing the existing files.
Note: Files are not
the same as the file functionality
in components that existed in previous versions of the product. To
differentiate between the two, the new file is called File
in Package and the old file element is called File
in Component. A File in Component includes
only references to primary model elements (package, class, object,
and block) and shows their mapping to physical files during code generation.
A file element can include variables, functions,
dependencies, types, parts, aggregate classes, and other model elements.
However, nested files are not allowed.
Rational Rhapsody supports
the following modeling behavior for files:
- You
can drag files onto object model diagrams and
structure diagrams.
- If you use the FunctionalC
profile, then the File tool
is available on the Drawing toolbars for object model diagrams
and structure diagrams.
- You can drag files
onto a sequence diagram, or
realize instance lines as files.
- A file can
have a statechart or activity diagram.
- Files
are implicit and always have a multiplicity
of 1.
- Files are listed in the component scope
and the
initialization tree of a configuration. They have influence in the
initialization tree only in the case of a Derived scope.
- Files can be defined as separate units, and can
have configuration management performed on them.
- Files
can be owned by packages only.