Pattern-oriented architecture design of software for logistics and transport applications

Abstract

Software architecture design plays the key role for logistics and transport software engineering. One of the design approaches is to reuse the architectural patterns, which express a fundamental structural organization of software systems and its behaviour. The usage of the proven and tested solutions allows us to increase the software quality and reduce potential risks. In this paper the technique that allows selecting and evaluating suite of architectural patterns is proposed. It can be used for logistics and transportation software, which is constructed using Multi-tier architecture. The technique allows us to consistently evaluate the impact of specific patterns to software characteristics with a given functionality. Effectiveness and efficiency of the described method is confirmed by a case study.

Study on the Integration of Regional Logistics Resources Based on SOA

“…Therefore in the face of market demand, the enterprises can make a good performance through the cooperation between the enterprises. At the same time, in seeking to meet their business needs in the process of logistics, by the customer relationship management, integrated logistics information platform, customers can find the suitable logistics enterprises or alliance for their needs, thus can realize their business needs [4,5].…”

Multiple Criteria Decision Making for the Structural Organization of Software Architecture

“…As a result, we have obtained four the following vector estimates: y1 = (1,6,8,7,8,8,7,8,9,8,7,6,8,7), (15) y2 = (2,7,6,6,7,7,8,6,7,7,7,7,6,7), (16) y3 = (3,6,5,7,5,4,8,5,6,5,5,7,6,8), (17) y4 = (4,6,7,5,9,5,5,7,8,…”

“…That is why they might be categorized in several groups. There are several approaches of architectural patterns classification [17,18,21,22,23,24,25]. Usually the software isn't limited to a single architectural pattern.…”

“…Some other studies propose the usage of the criteria of efficiency and the architecture efficiency metrics for quantitative evaluation of a software architecture structure [16,17]. The disadvantage of this method is that the components of the architecture efficiency metrics are explicitly defined, and we cannot easily extend them to reflect the required software architecture features.…”