No abstract

From the very beginnings of software era, enterprise environments have been one of the greatest generators of demand for complex software systems. Attempts to satisfy these ever growing needs for enterprise software systems have had a m ixed success. Software reuse has been one of the leverage mechanisms software producers had at their disposal, and through the year’s different reuse approaches emerged. One of the most successful large scale reuse approaches in enterprise environment are Enterprise Resource Planning (ERP) systems, which intend to reuse domain analysis and best practices in doing business, as well as software design and implementation. However, in literature, ERP systems are seldom viewed and described as one of the reuse approaches. Therefore, in this paper we aim at systematically analyzing ERP systems from the software reuse perspective in order to gain better insight into their characteristics, constituent elements, and relationships.

No abstract

Technology behind unmanned aircraft vehicles (UAVs) has been rapidly advancing in the recent years. This propelled the adoption rate and widened the range of UAV uses, such as in sport activities, cartography, surveillance, transportation, and military. While using single, individually controlled UAVs is already very common, using UAV constellations is becoming increasingly popular due to advantages in flexibility, scalability and sensing power. However, the use of UAV constellations remains limited to very specific applications due to number of challenges involved. One of the challenges is the lack of generic software system that would allow controlling UAV constellations in different types of flight missions. In order to address this problem, we propose an architectural model of a software module for UAV constellation piloting.

In object-oriented (OO) applications, objects collaborate through message passing, which results in these objects being coupled and mutually dependent. These dependencies can be reactive, i.e. such that, for example, the state change of one object, requires automatic reaction in all dependent objects. Examples of such reactive dependencies can be found in various software systems, including rich graphical interfaces, spreadsheet systems, animation, robotics, etc. Unlike the reactive paradigm which natively provides abstractions and mechanisms for the management of reactive dependencies, the OO paradigm lacks proper support. Object-oriented applications developers often resort to the use of ad-hoc solutions or design patterns such as the well-known Observer pattern, which are not suitable for managing more complex scenarios. In this paper we offer a novel design pattern (REACTOR), which utilizes a graph data structure to improve the management of reactive dependencies in OO applications.