Scribd
Upload
412 views4 pages

Pattern Distributive Object V 1.0 Dated Aug 09 2010

This document describes the Fragmented Object pattern. The pattern addresses how to define a business entity that can grow over time as new attributes are added. It involves dividing the business entity into separate but related parts (fragments) so that new attributes can be added without modifying the original code or data structure. This allows the entity to remain configurable as needs evolve while minimizing changes to existing code. The pattern is applicable when the full structure of a business entity is unknown initially.

Uploaded by

Tushar
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
412 views4 pages

Pattern Distributive Object V 1.0 Dated Aug 09 2010

This document describes the Fragmented Object pattern. The pattern addresses how to define a business entity that can grow over time as new attributes are added. It involves dividing the business entity into separate but related parts (fragments) so that new attributes can be added without modifying the original code or data structure. This allows the entity to remain configurable as needs evolve while minimizing changes to existing code. The pattern is applicable when the full structure of a business entity is unknown initially.

Uploaded by

Tushar
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

http://architecture-soa-bpm-eai.blogspot.

com/ Page 1 of 4
Tushar Jain [email protected], [email protected]

Pattern Name: Fragmented Object


Pattern Class: Architecture Version: 1.0
Pattern ID: Release Date:

Table of Content

1. Pattern Name ........................................................................................... 2


2. Also Known As.......................................................................................... 2
3. Class Name.............................................................................................. 2
4. Intent ..................................................................................................... 2
5. Motivation (Forces) ................................................................................... 2
6. Applicability ............................................................................................. 2
7. Structure ................................................................................................. 2
8. Participants .............................................................................................. 3
9. Collaboration............................................................................................ 3
10. Consequences .......................................................................................... 3
11. Implementation ........................................................................................ 3
12. Sample Code............................................................................................ 3
13. Known Uses ............................................................................................. 4
14. Related Patterns ....................................................................................... 4
15. Reference ................................................................................................ 4

http://architecture-soa-bpm-eai.blogspot.com/ Page 1 of 4
http://architecture-soa-bpm-eai.blogspot.com/ Page 2 of 4
Tushar Jain [email protected], [email protected]

1. Pattern Name
Fragmented Object

2. Also Known As
N/A

3. Class Name
Architectural

4. Intent
To define a grow-able business entity. In contemporary enterprise
systems, business entities tend to grow in its scope as peripheral or
supporting systems evolve.

5. Motivation (Forces)
For example in a system one like to add one or more set of
attribute to an existing business entity. The business entity has
one set of attributes (say intrinsic set – name, description, date of
creation, date of updation, who has created, who has updated, etc)
at inception of system. Later on another set of attributes come in to
picture (say pricing details). In traditional systems one need to
modify the data structure and code of existing business entity. Over
the time period business entity become complex so the code and
data structure.

6. Applicability
This pattern is applicable whenever business entities’ full structure
is not known at inception.

7. Structure
This pattern can be looked into from various angles. First from
system’s original developers and then future developers. Original
set of developers would not like to tinker with original definition so
with code and data structure. But future developers need to add

http://architecture-soa-bpm-eai.blogspot.com/ Page 2 of 4
http://architecture-soa-bpm-eai.blogspot.com/ Page 3 of 4
Tushar Jain [email protected], [email protected]

sets of attributes to existing business entity. More over these sets


may be related or unrelated.

8. Participants
N/A

9. Collaboration
N/A

10. Consequences
Due to usage of this patterns data model become complex but
configurable and developers have to follow certain style of coding.

11. Implementation
To understand implementation of this pattern, assume a business
entity having two or more set of attributes (say intrinsic: name,
description, date of creation etc.; pricing: cost, markup, price,
etc). To implement such case one should divide this business object
into two parts.

BE = BEi + BEp

So the data structure,

This implementation can be thought of equivalent to composition in


Object model.

12. Sample Code


N/A

http://architecture-soa-bpm-eai.blogspot.com/ Page 3 of 4
http://architecture-soa-bpm-eai.blogspot.com/ Page 4 of 4
Tushar Jain [email protected], [email protected]

13. Known Uses


ComViva RCMS and Global Data Logistix’s XiiNG! provisioning
engine.

14. Related Patterns


N/A

15. Reference
N/A

http://architecture-soa-bpm-eai.blogspot.com/ Page 4 of 4

You might also like