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

Chapter 5. Guidelines 118pervise up to ten students in one semester”. This group may partiallyoverlap with the first group.The first group of rules, due to its simplicity and framework support (forinstance JSF allows to add simple validation rules to controls) should beimplemented on a client side. The second group should be included duringcreation of process services. The third group of requirements can be implementedin logic of the system and in database. The code of Model shouldbe check in order to identify all the code validating business rules (see figure5.8).ViewViewControllerControllerSchemaPolicySchemaBasic ServicesPolicyBasic ServicesUtility+ Rules Centralisation =UtilityResourcesResourcesEntityEntityRulesFigure 5.8: Migration step 89. Provide inventory endpoints to basic services Applied SOA pattern: InventoryEndpointHow to: Inventory Endpoint establishes an additional layer of abstractioncomposed of a set of services that serve as facades. The layer contains bothservices that limit access to the system (check permissions etc) and servicesthat serve as facades to particular inventories like Canonical Resource. Ingeneral, each inventory should have at least one endpoint (facade). Operationsprovided by endpoints should be defined by architects. The operationscan be composed of only operations from underlying services (see figure 5.9).10. Identify all business processes within the legacy applicationApplied SOA pattern: Process AbstractionHow to: Business Process logic describes flow of processes within company;therefore all controlling components from Controller should be investigatedin order to identify processes. The next source of process-related knowledgeis an available documentation. At the moment, all non-controlling