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 5. Guidelines 124was implemented intentionally or it is just an artificial product <strong>of</strong> Reverse Engineering.The second criterion is quite obvious having selected pattern for migration inmind.The third criterion rejects projects implemented with frameworks implementedMVC like Zend, JSF, Spring MVC or ASP.NET MVC. This is a serious constraintaking in<strong>to</strong> consideration a number and popularity <strong>of</strong> those frameworks but therequirement is dictated by the nature <strong>of</strong> the framework. A framework ”frames” aproject by providing architecture, Application Programming Interface (API) andpreimplemented functionalities. A framework is meant <strong>to</strong> simplify work by execution<strong>of</strong> own (preimplemented) code “behind the scene”. The code <strong>of</strong> applicationusing framework is more transparent than code that does not use frameworks.Complexity <strong>of</strong> the code using frameworks is also lower because framework providessome core implementation. Unfortunately, it is hard <strong>to</strong> migrate a projectthat uses a framework because functionality provided by frameworks would have<strong>to</strong> be reimplemented. Additionally, even frameworks supporting the same architecturalpattern provide different scope <strong>of</strong> the support. The guidelines that donot exclude framework would need <strong>to</strong> be tailored <strong>to</strong> a particular framework.If more than one projects fulfils the criteria, an additional analysis <strong>of</strong> availabledocumentation <strong>of</strong> the projects is carried out. The project with the most detailedand descriptive documentation will be selectedCompletedocumentationBuild uponMVC patternNo frameworksDetailedanalysisFigure 5.14: Overview <strong>of</strong> the criteria5.3.2 Source <strong>of</strong> projectsSelection <strong>of</strong> the system <strong>to</strong> migrate is not an easy task taking previously statedcriteria in<strong>to</strong> consideration. At the very beginning, open source systems wereconsidered as potential candidates. Unfortunately, found project did not haveany formal documentation- only comments in code (if any) and/or ApplicationProgramming Interface (API). They also did not clearly support any architecturalpattern - lack <strong>of</strong> documentation. Theoretically, architectural metrics (see [65] formore information) could be used <strong>to</strong> identify architectural patterns but themetricsdo not prove that the pattern was used intentionally. Additionally, usage <strong>of</strong>technologies like Java Server Faces (supports MVC) also reduce scope <strong>of</strong> thesearch because those frameworks violate previously stated criteria. Due <strong>to</strong> all the

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

Saved successfully!

Ooh no, something went wrong!