Rose/Java mapping: introduction, definition of terms, страница 4

The name generated in an import statement is scoped to be relative to the CLASSPATH.

5  REVERSE ENGINEERING

5.1  Mapping File System Elements to the Rose Model

The parent directory hierarchy of a reverse engineered Java file is realized in the Rose model as a hierarchy of packages rooted in the Component View.  The Java file is realized as a component in the package which represents its parent directory.

If the Java file exists directly in a directory which is a CLASSPATH entry it is realized as a component in the Component View package.

5.2  Creating Rose Model Elements

If the required component package hierarchy exists it is used.  Otherwise it is created.  The names of the directories are used as the names of the packages.

The Java file is realized as a component with the same name as the file minus its extension.  If such a component already exists within the appropriate package hierarchy it is used.  Otherwise it is created.

5.3  Reverse Engineering an import

Each import in a file being reverse engineered generates a dependency from the component representing the client file to the component or package representing the supplier.

6  PROPERTY DEFINITIONS

This section provides a definition of the Rose/Java property sets by Rose model element. Each property is annotated as ORIG (holdover property from previous Rose/IDL version), NEW (new property for this version), or DEL (a property from the previous version which will no longer be used in this version).

6.1  PROJECT Properties

6.2  MODULE Properties

6.3  CLASS Properties