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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 2. Related Work 23between all the provided data. In order <strong>to</strong> allocate services, architects have <strong>to</strong>set cutting points manually and divide the diagram in<strong>to</strong> sub–trees. The sub–treebecome services. During service selection, architects have <strong>to</strong> take in<strong>to</strong> considerationother information retrieved during previous steps as well as the amount <strong>of</strong>dependencies in order <strong>to</strong> receive coarse grained and loosely coupled services (see4.3.1).<strong>Service</strong> Packaging and Integration This is the last step <strong>of</strong> presented Gray–Boxtechnique. The step accomplishes the process <strong>of</strong> migration from legacy system <strong>to</strong>wards<strong>Service</strong>–<strong>Oriented</strong> Architecture. The last step is composed from a sequence<strong>of</strong> three sub–steps [84]:1. Refinement –the services obtained as a result <strong>of</strong> all the previous steps areloosely coupled, but they still contain some dependencies. Refinement increasesindependence <strong>of</strong> those services and improve their quality by removal<strong>of</strong> all the “dead” code and unrelated interactions <strong>of</strong> interfaces. During thisprocess also an interface for service communication is established [84].2. Component integration and packaging –component integration takes previouslyrefined services and connects them with a “glue code” that serves asan adapter in order <strong>to</strong> transform ingoing and outgoing invocation. Additionally,some differences between domain and retrieved model may appear.The differences should be filled up with new services.3. Interface design –this step is meant <strong>to</strong> create interfaces[84],but in fact theoutput is a contract that specifies exact input and output for each operation<strong>of</strong> the service. Also an interface –a representation <strong>of</strong> the contract–is created.Application <strong>of</strong> clustering seems <strong>to</strong> be very promising solution because it base onvery basic human activity–classification [4]. Generally, clustering is meant <strong>to</strong> reorganizegroups <strong>of</strong> entities by taking in<strong>to</strong> consideration their similarity and basedon that divide them in<strong>to</strong> more homogenous groups[4]. The similarity can vary asa domain <strong>of</strong> analysis and can be unders<strong>to</strong>od as for instance similarity <strong>of</strong> propertieswhich is measured with metrics. Method applied in this approach bases onan improved agglomerative hierarchical clustering [4],This technique emphasizesfunctional aspects [4]that are essential in SOA. The technique is presented as aset <strong>of</strong> processes and an algorithm.2.1.5 Advantages and drawback <strong>of</strong> Taxonomy AnalysisTaxonomy Analysis analyses code <strong>of</strong> the migrated application in order <strong>to</strong> identifyservices and relationships between them.

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

Saved successfully!

Ooh no, something went wrong!