SoftwareEngineering

Due to the limited capabilities of the ActionScript 3 reflection API than cannot access private fields, it is necessary to create an externalizable AS3 class (implementing flash.utils.IExternalizable and its corresponding externalizable Java class

In both classes you have to implement two methods

the Gas3 generator can automatically generate the writeExternal and readExternal methods.

With GraniteDS automated externalization and without any modification made to our bean, we may serialize all properties of the Person class, private or not

In order to externalize the Person.java entity bean, we must tell GraniteDS which classes we want to externalize with a

externalize all classes named com.myapp.entity.Person by using the org.granite.hibernate.HibernateExternalizer

you could use this declaration, but note that type in the example above is replaced by

            <include annotated-with="javax.persistence.Entity"/>             <include annotated-with="javax.persistence.MappedSuperclass"/>             <include annotated-with="javax.persistence.Embeddable"/>

: type

annotated-with

Instead of configuring externalizers with the above method, you may use the

feature:

precedence rules for these three configuration options:

by the container in order to realize common use cases

An interface becomes a vehicle for encapsulation or abstraction,

“Interfaces are used to encode similarities which the classes of various types share, but do not necessarily constitute a class relationship. For instance, a human and a parrot can both whistle; however, it would not make sense to represent Humans and Parrots as subclasses of a Whistler class. Rather they would most likely be subclasses of an Animal class (likely with intermediate classes), but both would implement the Whistler interface.” [http://en.wikipedia.org/wiki/Java_interface]

Extensive use of interfaces derives from a

Premature Extensibility Is the Root of Some Evil

The number of artifacts will double and you will have to introduce a configuration facility

composition

(shared) part could be included in several composites

if composite is deleted, shared parts may still exist.

Composition

"strong" form of aggregation.

"weak" form of aggregation

whole/part relationship,

composite (whole) is deleted, all of its composite parts are "normally" deleted with it.

aggregation

"weak" form of aggregation

composition

Aggregation

same (shared) part could be included in several composites

composite is deleted, shared parts may still exist.

Composition

"strong" form of aggregation

whole/part relationship,

part could be included in at most one composite

composite (whole) is deleted, all of its composite parts are "normally" deleted with it.

filled black diamond

N-ary Association

more than two ends can only be drawn this way.

Control is a stereotyped class or object that is used to model flow of control or some coordination in behavior

usually describe some "business logic"

«Entity»

Entity is a stereotyped class or object that represents some information or data, usually but not necessarily persistent.

Features of a class are

Static features are underlined

«Boundary»

«Boundary»

«Control»

«Entity»

«Control»

Interface

An interface is a classifier that declares of a set of coherent public features and obligations

specifies a contract.

Data Type

A data type is a classifier - similar to a class - whose instances are

typical use of data types would be to represent value types

«dataType»

Enumeration

An enumeration is a data type whose values are enumerated in the model as user-defined enumeration literals.

«enumeration».

Multiplicity

Multiplicity allows to specify cardinality (allowed number of instances) of described element

Visibility

UML has the following types of visibility: public package protected private

Package visibility is represented by '~' literal.

Protected visibility is represented by '#' literal.

Private visibility is represented by '-' literal.