12.07.2015 Views

Migration of a Chosen Architectural Pattern to Service Oriented ...

Migration of a Chosen Architectural Pattern to Service Oriented ...

Migration of a Chosen Architectural Pattern to Service Oriented ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 3. <strong>Architectural</strong> <strong>Pattern</strong>s 42source. Those patterns are not taken in<strong>to</strong> consideration during next steps. Thetable contains also Publisher-Subscriber. Publisher–Subscriber is also rejectedbecause it is a known design pattern [22][34] while the table should contain onlyarchitectural patterns. This exception is important because it confirms previouslyaddressed problem that says that it can be very hard <strong>to</strong> distinguish both architecturaland design patterns from each other. Moreover, authors <strong>of</strong> the secondsource claim that all architectural patterns were checked before in terms <strong>of</strong> theiradherence <strong>to</strong> domain <strong>of</strong> architectural patterns. This finding means that othersources may also present a design pattern as an architectural pattern.3.2 CategorisationIn the previous section, nineteen architectural patterns out <strong>of</strong> thirty two werechosen. Analysis <strong>of</strong> feasibility <strong>of</strong> migration <strong>of</strong> this number <strong>of</strong> architectural patternswould require a lot <strong>of</strong> effort, consequently, the number <strong>of</strong> pattern will bereduced during the next selection. The selection is based on categorisation <strong>of</strong>patterns. The patterns are grouped and the most general pattern is chosen as arepresentative. This approach reduces considerably amount <strong>of</strong> patterns <strong>to</strong> analyse.The most general means that a pattern can be compared <strong>to</strong> other patternsbecause they have similar structure and purpose. Additionally, its structure isthe simplest. The representatives <strong>of</strong> each category reconsidered in next sections.This section presents process <strong>of</strong> selection <strong>of</strong> representatives <strong>of</strong> categories. Thesection is organized in following manner:1. Description <strong>of</strong> selected <strong>Architectural</strong> <strong>Pattern</strong>s – the subsection provides descriptions<strong>of</strong> patterns selected in the previous section. Each description hasfour elements: overview, elements and relationships between elements. Additionallya picture presenting an example usage <strong>of</strong> a pattern is provided.Since P. Avgerious in opposite <strong>to</strong> authors <strong>of</strong> other sources does not providedescriptions <strong>of</strong> patterns in his work, the descriptions and pictures base onremaining two sources <strong>of</strong> patterns.2. Methods <strong>of</strong> patterns categorisation – this subsection presents shortly identifiedways <strong>of</strong> pattern categorisation. Since creation <strong>of</strong> own categorisationmethod is not in scope <strong>of</strong> the work, one <strong>of</strong> presented approach is chosen.3. Allocation <strong>of</strong> pattern <strong>to</strong> categories – the purpose <strong>of</strong> this subsection is <strong>to</strong> allocatepatterns described in the first subsection <strong>to</strong> categories <strong>of</strong> categorisationmethod selected in the second subsection.4. Selection <strong>of</strong> representatives – this section provides comparison <strong>of</strong> patternswithin categories. As the result <strong>of</strong> comparison, representatives <strong>of</strong> categoriesare selected. The pattern for migration will be selected from those representatives.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!