Chapter 6 Building Implementation Diagrams

Component property sheet General tab

The General Tab contains the following properties:

Property	Description
Name	Specifies the name of the item, which should be clear and meaningful, and should convey the item's purpose to non-technical users.
Code	Specifies the technical name of the object, which is used for generating code or scripts.
Comment	Descriptive comment for the object.
Stereotype	Extends the semantics of the object beyond the core UML definition. The following standard stereotypes are available by default: <<Document>> - Generic file that is not a source file or an executable <<Executable>> - Program file that can be executed on a computer system <<File>> - Physical file in the context of the system developed <<Library>> - Static or dynamic library file <<Table>> - Database table You can modify an existing stereotype or create a new one from an object language. You can also use the extended model definition to create new sets of stereotypes. For more information on how to manipulate categories and entries in the object language, see chapter The Resource Editor in the General Features Guide. For more information on extended model definitions, see section Working with extended model definitions, in chapter Managing Objects in the General Features Guide .
Type	Defines the type of component. You can use a standard or a specific component. A standard component is useful if no specific implementation of the component has been defined. A specific component includes EJB, JSP, Servlet or ASP.NET. For more information on specific component types, see chapter Working with Web Services. To display the type of a component, select Tools→Display Preferences and select the Type option in the component category. Whenever you change the type of a component after creation, the modification triggers a conversion from one type to another: all relevant interfaces, classes, and dependencies are automatically created and initialized. Such a change will affect some property sheets, the Check Model feature, and code generation. For example, if you convert a standard component to an EJB Entity Bean, it will automatically generate a Bean class and a primary key class of the EJB, as well as home and component interfaces. If you convert an EJB to a standard component, the classes and interfaces of the EJB are preserved in the model.
Transaction	Used for a component with transactional behavior
Class diagram	Diagram with classes and interfaces linked to the component. It is automatically created and updated
Web service	Indicates that the component is a Web service

For more information on the class diagram property, see Creating a class diagram for a component.

Copyright (C) 2006. Sybase Inc. All rights reserved.