Diagram Nodes

Business object model Diagram Nodes consist of Packages, Classes, Association Class, Primitive Types, Attributes and Operations.

See BOM Packages, BOM Classes, Association Class, Primitive Types, Attributes and Operations.

When creating diagram nodes, note that:

• When you create a business object model in the Business Object Modeler, the Business Object Modeler automatically creates a package of the same name in which to place your diagram nodes. Therefore, there is no need to create a package in which to place all your diagram nodes, unless you want to create extra packages in which to group diagram nodes. For example, you might wish to create a package to contain all your Primitive Types.
• The Business Object Modeler uses the following Java programming conventions.
  • Business object names should not use an Invalid Java Identifier.
  • Business object names must not be a Java keyword.
  • Business objects should follow the Java Naming Convention.

    See http://java.sun.com/docs/codeconv/ for more information about these. These Java Programming Conventions are options under Preferences, so you can choose to disable them if you require.

    See "Setting Diagram Preferences" in TIBCO Business Studio Modeling User's Guide for more information.

  • Note: Warning messages are displayed on the Problems tab if these conventions are not followed.

    Warning messages indicating breaches of the Java Naming Convention are displayed only if you are working with the Solution Design capability selected. If you deselect the Solution Design capability, the Business Object Modeler carries out a full revalidation of your model against the Business Analysis capability, and these warnings will no longer be displayed. Similarly if you re-select the Solution Design capability, your model is again revalidated, and any warnings related to the naming conventions will be displayed.