Informatica

The symbiosis between an enterprise architecture and service-oriented architecture results in so-called service-oriented enterprise architecture and brings up new problems for service-oriented enterprise systems engineering. One of the most important is a business service quality definition, specification and evaluation. The paper proposes a formal model of enterprise business service quality evaluation framework to encompass and balance all the viewpoints and perspectives on an enterprise business service quality.

The paper proposes a novel predictive-reactive planning and scheduling framework in which both approaches are combined to complement each other in a reasonably balanced way. Neither original scheduling algorithms nor original techniques can be find in this paper. It also does not intend to invent new mechanisms or to propose some cardinally new ideas. The aim is to choose, adapt and test ideas, mechanisms and algorithms already proposed by other researchers. The focus of this research is set on make-to-order production environments. The proposed approach aims not only to absorb disruptions in shop floor level schedules but also to mitigate the impacts of potential exceptions, which disrupt mid-term level production plans. It is based on application of risk mitigation techniques and combines various simulation techniques extended by optimization procedures. The proposed approach is indented to be implemented in Advanced Planning and Scheduling system, which is an add-on for Enterprise Resources Planning system. To make it easier to understand the focus of the paper, at the beginning the position from which we start is clarified.

The aim of the paper is to investigate applicability of object-oriented software design patterns in the context of aspect-oriented design. The paper analyses which of the GoF 23 patterns have a meaning in this context and how they are affected by it. The main assumption is that there exist design patterns that solve software engineering paradigm independent design problems and that such patterns, in the contrast to the patterns solving paradigm-specific design problems, can be expressed in terms of any software engineering paradigm. However, the paper deals only with two paradigms: aspect-oriented (AO) paradigm and object-oriented (OO) paradigm. It proposes a classification of design problems based on this assumption and a technique for redesigning object-oriented patterns into pure aspect-oriented ones. It presents a number of examples how to apply this technique and discusses the results obtained. The results show that 20 of the GoF 23 design patterns solve such design problems that are common at least for both mentioned paradigms and demonstrate in which way these patterns can be adapted for the needs of aspect-oriented design.

Enterprise systems should be assembled out of components and services according to an orchestration schema and taking into account not only functional requirements but also the resulting Quality of Service (QoS). In other words, QoS-aware composition of services and components must be performed. The problem is to find which components or services have to be employed that the resulting system would optimize some QoS attributes while satisfying some other QoS constraints. The paper proposes to use the Constraint Logic Programming approach to solve this problem, that is, we see this problem as a discrete optimization and satisfaction problem.

In the context of enterprise engineering, strategic planning, information systems engineering, and software engineering activities should be tightly integrated. Traditional, interview-based requirements gathering and elicitation techniques are suited for this aim not enough well and often lead to the violation of the strategic alignment. The vision-driven requirements engineering has been proposed to solve this problem. The paper contributes to the further development of vision-driven requirements engineering techniques. It proposes a methodical framework that defines a complete scheme to organize different level requirements and allows to flowdown requirements from business to software level preserving their business-orientation.

Business process engineering is an important part of the advanced enterprise engineering. One of the still open issues is the question how in the enterprise system design to reuse ontological knowledge about business processes. The paper proposes to consider a family of similar business processes as a generic process and to represent knowledge about generic processes in a domain independent way. It describes the main scheme for reuse of such a domain independent knowledge when developing enterprise-wide information systems (IS). The main attention is paid to the process configuration problem. In order to solve this problem, a configurator (human being or machine) must find a set of components that fit together to satisfy the problem specification. An approach based on Description Logics is proposed for this aim. The main contribution of the paper is the proposed process configuration technique.

The paper proposes a methodology for evaluation of specification language functionality characteristics. It describes background of the proposed methodology, discusses the methodology in detail, and shortly describes experimental results obtained using the proposed methodology to evaluate the functionality of Z and UML languages.

The paper analyses the problem of aggregation of internal quality characteristics of an information system specification language. It surveys main categories of aggregation operators, their mathematical and behavioural properties and proposes how to aggregate quality characteristics taking into account measurements of all lowest-level characteristics in a proper way. The paper shows that four different kinds of dependencies can occur among characteristics of internal quality and discusses in detail what aggregation techniques are reasonable for each case. It also describes a heuristic for minimisation of possible deviations of measurement results obtained after using a number of different metrics or because of the inaccuracy of used measurement techniques.