The document discusses the challenges and solutions related to adapting domain-specific Adaptive Object Model (AOM) applications. It proposes a metadata mapping approach to create flexible AOM models that can be reused across different domains, highlighting the importance of maintaining code readability while allowing for domain-specific customization. The article also addresses the integration of AOM with existing frameworks and the need for a decoupled architecture to enhance modularity and usability.

1. An Architectural Model for
Adapting Domain-Specific
AOM Applications
Patricia Matsumoto
Eduardo Guerra

2. Understanding
AOM

3. The domain model flexibility
is an essencial requirement in
the context of some
applications.

4. health insurance archeology
defense communications

5. AOM
Adaptive Object Models
An architectural style where classes,
attributes, relationships and behaviors
are represented at runtime as
instances using metadata.

6. AOM
Type Object
Patterns
Properties
Type Square

7. Basic AOM
Structure
http://adaptiveobjectmodel.com/

8. Problems in
Using AOM

9. But it is very complicated to
implement an AOM system,
because I need to implement all
the model and all the components
that handle it.

10. Persistence
Application AOM Model
Domain
Domain Graphical
specific! Interface

12. An application usually creates an
AOM specific to their domain,
and this fact make difficult the
creation of more general
frameworks!
The components
are stuck to their
domain!

13. But the flexibility of an
AOM should be only
enough! We don't want a
new programming
language!
It is good to have the
domain model close to our
domain, because that can
improve code readability
on the business rules.

14. How we can create domain-specific
AOM models and allow the reuse of
the components that deals with it?
?

15. Proposed Solution

16. Metadata
Mapping
Generic
AOM Model
Application Aplication
Domain AOM Model

17. metadata
mapping
Aplication Generic
AOM Model AOM Model
Has some domain- Independent of
specific characteristics application domain
and contains only and is used by the
enough flexibility. components.

18. Integration Model

19. Metadata is used to map
the roles of each element to
the AOM generic model.
AOM generic model is used
to adapt the domain-
specific AOM model.
Frameworks only depends
on the generic model and
can be reused.

20. AOM Role Mapper
http://esfinge.sf.net

21. Metadata Handling
A Metadata Descriptor is used to
represent metadata at runtime.
A Metadata Reader is used to read
annotations, but others can be
implemented.
A Metadata Repository is used
to avoid unnecessary readings.

22. @EntityType
@Entity
@PropertyType
@EntityProperties
@EntityProperty
@PropertyTypeType
@PropertyValue
@CreateEntityMethod

23. @Entity
public class Account {
@EntityType
private AccountType accountType;
…
public AccountType getAccountType() {
return accountType;
}
public void setAccountType(AccountType accountType) {
this.accountType = accountType;
}
}

24. Solution
Example

25. Solution Example

26. AOM Model Adapters
Fixed properties on classes can be
mapped to AOM properties.
Relationships are mapped using a
different property implementation.
The AOM objects can be created
using factories that instatiate the
appropriate classes.

27. Model Manager
Provide a hotspot for persistence
components for model and instances.
Has an internal map to avoid to have
duplication in the model.
Entity types are identified by name and
package, entities by the framework.
A Visitor is used by frameworks to build
the entities and entity types.

28. ModelTalk
Esfinge
Oghma
Not coupled to a domain
Make AOM development easy
Allow domain-specific AOM
Integrate external frameworks
Frameworks can be reused by
different AOM models

29. Validation

30. Application
Domain-specific
AOM Model
Generic AOM
Model Adapters
Persistence
Framework MongoDB

31. Two different AOM models were developed
and mapped using the framework.

32. Application

33. MongoDB

34. Modularity Analysis

35. Domain only depends on the annotations

36. Frameworks depends on the AOM model

37. Applications depends on the API and AOM model

38. It is evaluated that
with this model is
possible to decouple
the application AOM
model from the
AOM frameworks
allowing their reuse.

39. However there are still
many challenges in the
AOM domain and for the
Esfinge AOM Role Mapper!

40. Thank You!