3.2« Packages »

A set of packages can be found in the application modeling generated with BLU AGE® 2009 EDITION. It partly represents the generated project structure. Packages may be named according to designers preferences. The modeled application must necessarily contain some kinds of packages. See below.

3.2.1Packages tree-structure, « Target Application »

Figure 1 : “Packages” tree structure – target application modeling

Rules and stereotypes for mandatory packages

• PK_TARGET

It stands for the application root package. Previous packages are not mandatory. This package is unique.

• PK_SERVICE

It stands for the package where services are modeled. This package can be an external UML module. It must directly or indirectly descend from the « PK_TARGET » stereotyped package.

• PK_BUSINESS

It stands for the package where the business objects are modeled. This package can be an external UML module. It must directly or indirectly descend from the « PK_TARGET » stereotyped package.

• PK_WEB

It stands for the Packages container where presentations objects are modeled. This package can be an external UML module. It must directly or indirectly descend from the « PK_TARGET » stereotyped package.

• PK_ROLES

It stands for the package where actor’s objects are modeled. This package can be an external UML module. It must directly or indirectly descend from the « PK_TARGET » stereotyped package.

• PK_BUSINESS_OBJECT

It stands for the package where the « business objects » are modeled. This package can be an external UML module. It must directly descend from the « PK_BUSINESS » stereotyped package.

• PK_ENTITY

It stands for the package where entities are modeled. This package can be an external UML module. It must directly descend from the « PK_BUSINESS » stereotyped package.

• PK_REPORT

It stands for the package where the reports are modeled. This package can be an external UML module. It must directly or indirectly descend from the « PK_TARGET » stereotyped package.

3.2.2The « Profile » packages

BLU AGE® provides an extension of UML2 using static packages of type « profile ». These are included for use by the designer and are required in target application modeling allowing consistency in the definition of stereotypes and tags.

Figure 2 : « Profiles » Packages

« Profile » Packages description

• entity

It contains the stereotypes, the tagged values and enumerations for entities modeling.

• bo

It contains the stereotypes, the tagged values and enumerations for business objects modeling.

• presentation

It contains the stereotypes, the tagged values and enumerations for presentation (IHM) modeling.

• service

It contains the stereotypes, the tagged values and enumerations for business services modeling.

• datatype

It contains classes and data types for entities, business objects and services modeling.

• webservice

It contains the stereotypes, the tagged values and enumerations for web services modeling.

• persistence

It contains the stereotypes, the tagged values and enumerations for persistence layers modeling.

3.2.3General rules for target application modeling « Packages »

• Package names must follow naming protocol rules found in J2EE ® SUN or .Net ® Microsoft coding norms :

• • package names must start with ‘$’, ‘_’ or a letter
  • they can only contain ‘$’, ‘_’, letters or numbers.