Nancy Alexopoulou | Johannes Kepler University Linz (original) (raw)

Papers by Nancy Alexopoulou

Computer Applications in Industry and Engineering, 2005

Distributed system configuration is a complex process, since it involves solving interrelated iss... more Distributed system configuration is a complex process, since it involves solving interrelated issues, corresponding to different configuration stages usually supported by automated or semiautomated independent tools. A common model for distributed system representation in all configuration stages enables the identification of unclear application specific dependencies between discrete stages. It should also be easily realized in various software tools used to automate discrete configuration stages and facilitate the designer to efficiently provide system specifications. We propose to use UML to model all aspects of distributed system configuration process by extending and integrating different diagram types. Alternative views of the system emphasizing specific configuration stages are offered through the realization of extended UML diagrams. Rational Rose software platform is used for implementation purposes.

International Conference on Software Engineering Advances, 2006

Enterprise Information Systems can be described according to the Open Distributed Processing Refe... more Enterprise Information Systems can be described according to the Open Distributed Processing Reference Model (RM-ODP), where five different viewpoints are specified analyzing various aspects of the system. Configuration issues are explored in the Engineering Viewpoint of RM-ODP. In practice, configuration issues are explored in discrete stages, supported by autonomous software tools, each of which adopts its own metamodel for system representation. We propose a platform independent framework, which focuses on the Engineering Viewpoint of Enterprise Information Systems managing application configuration and network design issues independently of application development progress. In order to apply this framework using existing tools, model exchangeability and tool coordination must be supported by standard, open methods. Thus, a common metamodel is proposed to generate enterprise information system models, which are stored in XML. A UML 2.0 profile is defined to visualize these models, facilitate the designer to interact with them and coordinate specific tool invocation.

International Conference on Software Engineering Advances, 2007

Extension mechanisms offered by UML 2.0 are often explored in order to define UML profiles that s... more Extension mechanisms offered by UML 2.0 are often explored in order to define UML profiles that serve specific modeling purposes. These UML 2.0 profiles should be effectively accommodated by standard UML-based modeling tools, which provide the means for applying them in practice. Almost every UML 2.0 modeling tool supports the definition of stereotypes and the description of constraints in Object Constraint Language. However, implementing a profile in practice often entails the development of additional functionality. This requirement mainly stems from the fact that when dealing with complex models it is more efficient for end-users to help them enforce a constraint rather than notify them when it is broken. Such issues, encountered when developing a UML 2.0 profile for enterprise information systems engineering using Rational Software Modeler as a standard UML 2.0 modeling tool, are discussed in the paper.

International Conference on Engineering of Complex Computer Systems, 2006

Enterprise information system configuration is a complex process dealing with interrelated issues... more Enterprise information system configuration is a complex process dealing with interrelated issues. A four-stage methodology has been proposed in order to effectively explore configuration issues. The main advantage of the proposed methodology is the adoption of a common meta-model for the representation of systems throughout all configuration stages, ensuring interoperability and model consistency. In practice, configuration stages are supported by automated or semiautomated tools, each of which adopts its own meta-model for system representation. In order to apply the methodology using existing autonomous tools, model exchangeability (thus metamodel transformation) and tool co-ordination must be facilitated by standard, open methods. Thus, the common meta-model is implemented in a standard, exchangeable format, as XML. To provide a standard method to visualize the common meta-model, facilitate the designer to interact with it and co-ordinate specific tool invocation, a UML 2.0 profile was defined. Different UML 2.0 diagrams are integrated to support different views of the system. The representation of relationships and restrictions among discrete meta-model entities must be facilitated to identify and explore the dependencies between configuration stages. Constraints are extensively used for this purpose. A case study where the proposed profile utilized the configuration of a large-scale banking system is also presented.

International Conference on Engineering of Complex Computer Systems, 2006

Enterprise information system configuration is a complex process dealing with interrelated issues... more Enterprise information system configuration is a complex process dealing with interrelated issues. A four-stage methodology has been proposed in order to effectively explore configuration issues. The main advantage of the proposed methodology is the adoption of a common meta-model for the representation of systems throughout all configuration stages, ensuring interoperability and model consistency. In practice, configuration stages are supported by automated or semiautomated tools, each of which adopts its own meta-model for system representation. In order to apply the methodology using existing autonomous tools, model exchangeability (thus metamodel transformation) and tool co-ordination must be facilitated by standard, open methods. Thus, the common meta-model is implemented in a standard, exchangeable format, as XML. To provide a standard method to visualize the common meta-model, facilitate the designer to interact with it and co-ordinate specific tool invocation, a UML 2.0 profile was defined. Different UML 2.0 diagrams are integrated to support different views of the system. The representation of relationships and restrictions among discrete meta-model entities must be facilitated to identify and explore the dependencies between configuration stages. Constraints are extensively used for this purpose. A case study where the proposed profile utilized the configuration of a large-scale banking system is also presented.

... Panagiotis Kanellis, Department of Informatics and Telecommunications, University of Athens, ... more ... Panagiotis Kanellis, Department of Informatics and Telecommunications, University of Athens, Greece kanellis@di.uoa.gr ... Vol. 5. Mantzana V., Themistocleous M., Irani Z and Morabito V., 2007. 'Identifying HealthCare Actors Involved in the Adoption of Information Systems'. ...

International Conference on Enterprise Information Systems, 2004

... instances of application-defined data types and a convention for representing remote procedur... more ... instances of application-defined data types and a convention for representing remote procedure ... can be embodied into the infrastructure and communicate with existing applications via the common ... at the user and business unit level, but with the necessary culture, policies and ...

Modern enterprise information systems are distributed systems usually built on multi-tiered clien... more Modern enterprise information systems are distributed systems usually built on multi-tiered client server architectures and can be defined using well-established frameworks such as the Zachman framework or the Open Distributed Processing Reference Model (RM-ODP). Both frameworks identify views regarding the system designer's viewpoint, but they do not suggest a methodology for view creation. A consistent framework for enterprise information system engineering, compatible with both the Zachman framework and RM-ODP is proposed by the authors. It consists of a metamodel describing alternative system views, a corresponding methodology comprising discrete stages performed either by the system designer or software tools and a UML 2.0 profile for view representation. In this paper, a case study where the proposed framework was applied is discussed, focusing on the features provided to the system designer using the UML 2.0 profile. The profile is implemented by extending the Rational Software Modeler functionality.

International Conference on Software Engineering Advances, 2006

Enterprise Information Systems can be described according to the Open Distributed Processing Refe... more Enterprise Information Systems can be described according to the Open Distributed Processing Reference Model (RM-ODP), where five different viewpoints are specified analyzing various aspects of the system. Configuration issues are explored in the Engineering Viewpoint of RM-ODP. In practice, configuration issues are explored in discrete stages, supported by autonomous software tools, each of which adopts its own metamodel for system representation. We propose a platform independent framework, which focuses on the Engineering Viewpoint of Enterprise Information Systems managing application configuration and network design issues independently of application development progress. In order to apply this framework using existing tools, model exchangeability and tool coordination must be supported by standard, open methods. Thus, a common metamodel is proposed to generate enterprise information system models, which are stored in XML. A UML 2.0 profile is defined to visualize these models, facilitate the designer to interact with them and coordinate specific tool invocation.

Hawaii International Conference on System Sciences, 2009

There are numerous enterprise information system (EIS) engineering methodologies in the literatur... more There are numerous enterprise information system (EIS) engineering methodologies in the literature, each covering different aspects. However, in order to integrate them in an enterprise architecture, model-based engineering can be adopted. In such a case, a central system model is defined supporting all engineering activities. Zachman's matrix may be used as a basis for constructing such a model. Based on this assumption, we propose a systematic approach for the support of model-based EIS engineering process using Zachman matrix as EIS central model. Basic EIS engineering activities and the way they may be served by specific rows is explored, while the contribution of each system aspect (matrix column) is also taken into account. A conceptual model for model-based EIS engineering is also introduced. To explore the proposed concepts in practice, the system network cell is used as an example. Corresponding engineering tasks and sub-models are formed based on the proposed guidelines in a technology and methodology independent fashion. A case study based on the proposed concepts is also presented.

International Conference on Enterprise Information Systems, 2006

Distributed system configuration consists of distributed application component placement and unde... more Distributed system configuration consists of distributed application component placement and underlying network design, thus is a complex process dealing with interrelated issues and comprising various stages. A common metamodel for distributed system representation in all configuration stages is thus required, so that unclear dependencies between discrete stages can be easily identified. This model should also be easily adopted by autonomous software tools used for the automation of discrete configuration stages and for the efficient development of system specifications by designers. We propose such a metamodel using UML 2.0. More specifically, we introduce a UML 2.0 profile facilitating distributed system configuration process. In this profile, different UML 2.0 diagrams are integrated and properly extended, in order to model all aspects of the distributed system configuration process.

Enterprise Distributed Object Computing Conference, 2006

System engineering is the process of defining the desired architecture of a system and exploring ... more System engineering is the process of defining the desired architecture of a system and exploring performance requirements, ensuring that all system components are identified and properly allocated and system resources can provide the desired performance. A consistent framework for enterprise information engineering, compatible to Zachman framework is proposed. It consists of a metamodel describing different system views and the relations between them, a corresponding methodology of discrete stages, performed by the system designer or software tools, and a UML 2.0 profile for view representation.

Expert Systems With Applications, 2009

Customer evaluation plays an important role as a part of the order acceptance process of supplier... more Customer evaluation plays an important role as a part of the order acceptance process of suppliers in optimally allocating resources and prioritizing orders accordingly. In this paper, a new class of fuzzy methods for evaluating customers is applied. Firstly, our approach tackles the issue of uncertainty that is inherent in the problem of customer evaluation that involves qualitative criteria by employing the method proposed by Yong [Yong, D. (2006). Plant location selection based on fuzzy TOPSIS. International Journal of Advanced Manufacturing Technology, 28(7–8), 839–844] in order to efficiently transform linguistic assessments of the weights of criteria and of the ratings of customers into crisp numbers. Secondly, the TOPSIS method is modified in order to integrate the behavioral pattern of the decision maker into its “principle of compromise”. In this context, a new model for the aggregating function of TOPSIS that is based on a fuzzy set representation of the closeness to the ideal and the negative ideal solution is applied. In particular, we use the class of intersection connectives proposed by Yager [Yager, R. R. (1980). On a general class of fuzzy connectives. Fuzzy Sets and Systems, 4(3), 235–242] that enables a formal definition of the relation between the closeness to the ideal solution and the closeness to the negative ideal solution. Thus, a class of methods is formulated whose different instances correspond to different behavioral patterns of the decision makers, e.g. with preference to customers that make as much profit as possible but also avoid as much risk as possible or to customers that are performing well in at least one of the profit and risk criteria. A numerical example, illustrating the application of this class of methods to customer evaluation is given.

Lecture Notes in Business Information Processing, 2010

The number of BPM products available has increased substantially in the last years, so that choos... more The number of BPM products available has increased substantially in the last years, so that choosing among these products became a difficult task for potential BPM users. This paper defines a framework for evaluating BPM products, and discusses how this framework has been applied in the development of an open and objective evaluation method for these products. Our framework has been developed based on the BPM lifecycle we developed as a result of a thorough literature survey. Our method consists of a set of criteria, a test case and a rating schema. The paper also discusses how we evaluated our method (and indirectly our framework) by applying it to three BPM tool suites. We show that our method allows the rigorous comparison of these products according to different criteria, so that the choice of BPM product can be tuned to the specific goals of the users of these products.

Lecture Notes in Business Information Processing, 2013

ABSTRACT INTRODUCTION Operating in highly turbulent environments, organiza-tions today are faced ... more ABSTRACT INTRODUCTION Operating in highly turbulent environments, organiza-tions today are faced with the need to continually adjust their infrastructure and strategies in order to remain com-petitive. Globalization and continual technological evolu-tion are the main drivers of this turbulence (Dove, 1999b). To adapt at the same pace as their changing environment, organizations have to be agile. Loosely defined, an agile enterprise is one that is characterized by change profi-ciency. Change proficiency is the defining characteristic of agility and denotes the competency in which an adap-tive transformation occurs (Dove, Benson, & Hartman, 1996). In a more detailed definition, an agile enterprise is one that is characterized as a fast moving, adaptable, and robust business, which is capable of rapid adaptation in response to unexpected and unpredicted changes and events, market opportunities, and customer requirements (Henbury, 1996). According to Dove (1999b), agility is very much re-lated to the ability to manage and apply knowledge effec-tively. Dove (1999b) felicitously associates agility with cats. A cat is both physically adept at movement and also mentally adept at choosing useful movement appropriate for the situation. If a cat has merely the ability to move quickly but moves inappropriately and to no gain (e.g., a cat on a hot tin roof), it might be called spastic or confused but never agile. On the other hand, a cat that knows what should be done but finds itself unable to move (e.g., a cat that's got itself up a tree), might be called catatonic, confused, or paralyzed but never agile. This example implies that agility cannot be easily attained. It requires knowledge, experience, and skill. Enterprise agility depends on many factors such as per-sonnel capabilities, information technology (IT) infra-structure, business strategy, and so forth. When an enterprise is agile, all its constituents are agile and vice versa. This article focuses particularly on IT infrastruc-ture. It defines agility in IT infrastructure and explains how it contributes to enterprise sensing and response agility. Sensing agility is defined as a firm's ability to rapidly discover and interpret the market opportunities through its information systems, and it concerns not only an ability to distinguish information from noise quickly, but also to transform apparent noise into meaning faster (Haeckel, 1999). Response agility relates to the organiza-tional capability to quickly transform knowledge into action in response to the environmental signals (Haeckel, 1999).

Proceedings of the 41st Annual Hawaii International Conference on System Sciences (HICSS 2008), 2008

Agility is a key characteristic for modern enterprises operating in a highly dynamic environment.... more Agility is a key characteristic for modern enterprises operating in a highly dynamic environment. The attainment of agility is a difficult issue involving all organizational aspects, such as business processes, information systems, personnel, organizational structure, etc. The ability to respond rapidly to changes by utilizing agile business processes is an important constituent of an agile enterprise. The focus of this paper is business process agility outlining the benefits of event-based business process modeling. To this end, an event-based approach is proposed enabling on-the-fly composition of business processes. The introduced approach adopts the concepts of Complex Event Processing. A conceptual architecture for an information technology infrastructure supporting event-driven business process execution is also proposed.

International Conference on Software Engineering Advances (ICSEA 2007), 2007

Extension mechanisms offered by UML 2.0 are often explored in order to define UML profiles that s... more Extension mechanisms offered by UML 2.0 are often explored in order to define UML profiles that serve specific modeling purposes. These UML 2.0 profiles should be effectively accommodated by standard UML-based modeling tools, which provide the means for applying them in practice. Almost every UML 2.0 modeling tool supports the definition of stereotypes and the description of constraints in Object Constraint Language. However, implementing a profile in practice often entails the development of additional functionality. This requirement mainly stems from the fact that when dealing with complex models it is more efficient for end-users to help them enforce a constraint rather than notify them when it is broken. Such issues, encountered when developing a UML 2.0 profile for enterprise information systems engineering using Rational Software Modeler as a standard UML 2.0 modeling tool, are discussed in the paper.

2006 International Conference on Software Engineering Advances (ICSEA'06), 2006

Enterprise Information Systems can be described according to the Open Distributed Processing Refe... more Enterprise Information Systems can be described according to the Open Distributed Processing Reference Model (RM-ODP), where five different viewpoints are specified analyzing various aspects of the system. Configuration issues are explored in the Engineering Viewpoint of RM-ODP. In practice, configuration issues are explored in discrete stages, supported by autonomous software tools, each of which adopts its own metamodel for system representation. We propose a platform independent framework, which focuses on the Engineering Viewpoint of Enterprise Information Systems managing application configuration and network design issues independently of application development progress. In order to apply this framework using existing tools, model exchangeability and tool coordination must be supported by standard, open methods. Thus, a common metamodel is proposed to generate enterprise information system models, which are stored in XML. A UML 2.0 profile is defined to visualize these models, facilitate the designer to interact with them and coordinate specific tool invocation.

Computer Applications in Industry and Engineering, 2005

Distributed system configuration is a complex process, since it involves solving interrelated iss... more Distributed system configuration is a complex process, since it involves solving interrelated issues, corresponding to different configuration stages usually supported by automated or semiautomated independent tools. A common model for distributed system representation in all configuration stages enables the identification of unclear application specific dependencies between discrete stages. It should also be easily realized in various software tools used to automate discrete configuration stages and facilitate the designer to efficiently provide system specifications. We propose to use UML to model all aspects of distributed system configuration process by extending and integrating different diagram types. Alternative views of the system emphasizing specific configuration stages are offered through the realization of extended UML diagrams. Rational Rose software platform is used for implementation purposes.

International Conference on Software Engineering Advances, 2006

Enterprise Information Systems can be described according to the Open Distributed Processing Refe... more Enterprise Information Systems can be described according to the Open Distributed Processing Reference Model (RM-ODP), where five different viewpoints are specified analyzing various aspects of the system. Configuration issues are explored in the Engineering Viewpoint of RM-ODP. In practice, configuration issues are explored in discrete stages, supported by autonomous software tools, each of which adopts its own metamodel for system representation. We propose a platform independent framework, which focuses on the Engineering Viewpoint of Enterprise Information Systems managing application configuration and network design issues independently of application development progress. In order to apply this framework using existing tools, model exchangeability and tool coordination must be supported by standard, open methods. Thus, a common metamodel is proposed to generate enterprise information system models, which are stored in XML. A UML 2.0 profile is defined to visualize these models, facilitate the designer to interact with them and coordinate specific tool invocation.

International Conference on Software Engineering Advances, 2007

Extension mechanisms offered by UML 2.0 are often explored in order to define UML profiles that s... more Extension mechanisms offered by UML 2.0 are often explored in order to define UML profiles that serve specific modeling purposes. These UML 2.0 profiles should be effectively accommodated by standard UML-based modeling tools, which provide the means for applying them in practice. Almost every UML 2.0 modeling tool supports the definition of stereotypes and the description of constraints in Object Constraint Language. However, implementing a profile in practice often entails the development of additional functionality. This requirement mainly stems from the fact that when dealing with complex models it is more efficient for end-users to help them enforce a constraint rather than notify them when it is broken. Such issues, encountered when developing a UML 2.0 profile for enterprise information systems engineering using Rational Software Modeler as a standard UML 2.0 modeling tool, are discussed in the paper.

International Conference on Engineering of Complex Computer Systems, 2006

Enterprise information system configuration is a complex process dealing with interrelated issues... more Enterprise information system configuration is a complex process dealing with interrelated issues. A four-stage methodology has been proposed in order to effectively explore configuration issues. The main advantage of the proposed methodology is the adoption of a common meta-model for the representation of systems throughout all configuration stages, ensuring interoperability and model consistency. In practice, configuration stages are supported by automated or semiautomated tools, each of which adopts its own meta-model for system representation. In order to apply the methodology using existing autonomous tools, model exchangeability (thus metamodel transformation) and tool co-ordination must be facilitated by standard, open methods. Thus, the common meta-model is implemented in a standard, exchangeable format, as XML. To provide a standard method to visualize the common meta-model, facilitate the designer to interact with it and co-ordinate specific tool invocation, a UML 2.0 profile was defined. Different UML 2.0 diagrams are integrated to support different views of the system. The representation of relationships and restrictions among discrete meta-model entities must be facilitated to identify and explore the dependencies between configuration stages. Constraints are extensively used for this purpose. A case study where the proposed profile utilized the configuration of a large-scale banking system is also presented.

International Conference on Engineering of Complex Computer Systems, 2006

Enterprise information system configuration is a complex process dealing with interrelated issues... more Enterprise information system configuration is a complex process dealing with interrelated issues. A four-stage methodology has been proposed in order to effectively explore configuration issues. The main advantage of the proposed methodology is the adoption of a common meta-model for the representation of systems throughout all configuration stages, ensuring interoperability and model consistency. In practice, configuration stages are supported by automated or semiautomated tools, each of which adopts its own meta-model for system representation. In order to apply the methodology using existing autonomous tools, model exchangeability (thus metamodel transformation) and tool co-ordination must be facilitated by standard, open methods. Thus, the common meta-model is implemented in a standard, exchangeable format, as XML. To provide a standard method to visualize the common meta-model, facilitate the designer to interact with it and co-ordinate specific tool invocation, a UML 2.0 profile was defined. Different UML 2.0 diagrams are integrated to support different views of the system. The representation of relationships and restrictions among discrete meta-model entities must be facilitated to identify and explore the dependencies between configuration stages. Constraints are extensively used for this purpose. A case study where the proposed profile utilized the configuration of a large-scale banking system is also presented.

... Panagiotis Kanellis, Department of Informatics and Telecommunications, University of Athens, ... more ... Panagiotis Kanellis, Department of Informatics and Telecommunications, University of Athens, Greece kanellis@di.uoa.gr ... Vol. 5. Mantzana V., Themistocleous M., Irani Z and Morabito V., 2007. 'Identifying HealthCare Actors Involved in the Adoption of Information Systems'. ...

International Conference on Enterprise Information Systems, 2004

... instances of application-defined data types and a convention for representing remote procedur... more ... instances of application-defined data types and a convention for representing remote procedure ... can be embodied into the infrastructure and communicate with existing applications via the common ... at the user and business unit level, but with the necessary culture, policies and ...

Modern enterprise information systems are distributed systems usually built on multi-tiered clien... more Modern enterprise information systems are distributed systems usually built on multi-tiered client server architectures and can be defined using well-established frameworks such as the Zachman framework or the Open Distributed Processing Reference Model (RM-ODP). Both frameworks identify views regarding the system designer's viewpoint, but they do not suggest a methodology for view creation. A consistent framework for enterprise information system engineering, compatible with both the Zachman framework and RM-ODP is proposed by the authors. It consists of a metamodel describing alternative system views, a corresponding methodology comprising discrete stages performed either by the system designer or software tools and a UML 2.0 profile for view representation. In this paper, a case study where the proposed framework was applied is discussed, focusing on the features provided to the system designer using the UML 2.0 profile. The profile is implemented by extending the Rational Software Modeler functionality.

International Conference on Software Engineering Advances, 2006

Enterprise Information Systems can be described according to the Open Distributed Processing Refe... more Enterprise Information Systems can be described according to the Open Distributed Processing Reference Model (RM-ODP), where five different viewpoints are specified analyzing various aspects of the system. Configuration issues are explored in the Engineering Viewpoint of RM-ODP. In practice, configuration issues are explored in discrete stages, supported by autonomous software tools, each of which adopts its own metamodel for system representation. We propose a platform independent framework, which focuses on the Engineering Viewpoint of Enterprise Information Systems managing application configuration and network design issues independently of application development progress. In order to apply this framework using existing tools, model exchangeability and tool coordination must be supported by standard, open methods. Thus, a common metamodel is proposed to generate enterprise information system models, which are stored in XML. A UML 2.0 profile is defined to visualize these models, facilitate the designer to interact with them and coordinate specific tool invocation.

Hawaii International Conference on System Sciences, 2009

There are numerous enterprise information system (EIS) engineering methodologies in the literatur... more There are numerous enterprise information system (EIS) engineering methodologies in the literature, each covering different aspects. However, in order to integrate them in an enterprise architecture, model-based engineering can be adopted. In such a case, a central system model is defined supporting all engineering activities. Zachman's matrix may be used as a basis for constructing such a model. Based on this assumption, we propose a systematic approach for the support of model-based EIS engineering process using Zachman matrix as EIS central model. Basic EIS engineering activities and the way they may be served by specific rows is explored, while the contribution of each system aspect (matrix column) is also taken into account. A conceptual model for model-based EIS engineering is also introduced. To explore the proposed concepts in practice, the system network cell is used as an example. Corresponding engineering tasks and sub-models are formed based on the proposed guidelines in a technology and methodology independent fashion. A case study based on the proposed concepts is also presented.

International Conference on Enterprise Information Systems, 2006

Distributed system configuration consists of distributed application component placement and unde... more Distributed system configuration consists of distributed application component placement and underlying network design, thus is a complex process dealing with interrelated issues and comprising various stages. A common metamodel for distributed system representation in all configuration stages is thus required, so that unclear dependencies between discrete stages can be easily identified. This model should also be easily adopted by autonomous software tools used for the automation of discrete configuration stages and for the efficient development of system specifications by designers. We propose such a metamodel using UML 2.0. More specifically, we introduce a UML 2.0 profile facilitating distributed system configuration process. In this profile, different UML 2.0 diagrams are integrated and properly extended, in order to model all aspects of the distributed system configuration process.

Enterprise Distributed Object Computing Conference, 2006

System engineering is the process of defining the desired architecture of a system and exploring ... more System engineering is the process of defining the desired architecture of a system and exploring performance requirements, ensuring that all system components are identified and properly allocated and system resources can provide the desired performance. A consistent framework for enterprise information engineering, compatible to Zachman framework is proposed. It consists of a metamodel describing different system views and the relations between them, a corresponding methodology of discrete stages, performed by the system designer or software tools, and a UML 2.0 profile for view representation.

Expert Systems With Applications, 2009

Customer evaluation plays an important role as a part of the order acceptance process of supplier... more Customer evaluation plays an important role as a part of the order acceptance process of suppliers in optimally allocating resources and prioritizing orders accordingly. In this paper, a new class of fuzzy methods for evaluating customers is applied. Firstly, our approach tackles the issue of uncertainty that is inherent in the problem of customer evaluation that involves qualitative criteria by employing the method proposed by Yong [Yong, D. (2006). Plant location selection based on fuzzy TOPSIS. International Journal of Advanced Manufacturing Technology, 28(7–8), 839–844] in order to efficiently transform linguistic assessments of the weights of criteria and of the ratings of customers into crisp numbers. Secondly, the TOPSIS method is modified in order to integrate the behavioral pattern of the decision maker into its “principle of compromise”. In this context, a new model for the aggregating function of TOPSIS that is based on a fuzzy set representation of the closeness to the ideal and the negative ideal solution is applied. In particular, we use the class of intersection connectives proposed by Yager [Yager, R. R. (1980). On a general class of fuzzy connectives. Fuzzy Sets and Systems, 4(3), 235–242] that enables a formal definition of the relation between the closeness to the ideal solution and the closeness to the negative ideal solution. Thus, a class of methods is formulated whose different instances correspond to different behavioral patterns of the decision makers, e.g. with preference to customers that make as much profit as possible but also avoid as much risk as possible or to customers that are performing well in at least one of the profit and risk criteria. A numerical example, illustrating the application of this class of methods to customer evaluation is given.

Lecture Notes in Business Information Processing, 2010

The number of BPM products available has increased substantially in the last years, so that choos... more The number of BPM products available has increased substantially in the last years, so that choosing among these products became a difficult task for potential BPM users. This paper defines a framework for evaluating BPM products, and discusses how this framework has been applied in the development of an open and objective evaluation method for these products. Our framework has been developed based on the BPM lifecycle we developed as a result of a thorough literature survey. Our method consists of a set of criteria, a test case and a rating schema. The paper also discusses how we evaluated our method (and indirectly our framework) by applying it to three BPM tool suites. We show that our method allows the rigorous comparison of these products according to different criteria, so that the choice of BPM product can be tuned to the specific goals of the users of these products.

Lecture Notes in Business Information Processing, 2013

ABSTRACT INTRODUCTION Operating in highly turbulent environments, organiza-tions today are faced ... more ABSTRACT INTRODUCTION Operating in highly turbulent environments, organiza-tions today are faced with the need to continually adjust their infrastructure and strategies in order to remain com-petitive. Globalization and continual technological evolu-tion are the main drivers of this turbulence (Dove, 1999b). To adapt at the same pace as their changing environment, organizations have to be agile. Loosely defined, an agile enterprise is one that is characterized by change profi-ciency. Change proficiency is the defining characteristic of agility and denotes the competency in which an adap-tive transformation occurs (Dove, Benson, & Hartman, 1996). In a more detailed definition, an agile enterprise is one that is characterized as a fast moving, adaptable, and robust business, which is capable of rapid adaptation in response to unexpected and unpredicted changes and events, market opportunities, and customer requirements (Henbury, 1996). According to Dove (1999b), agility is very much re-lated to the ability to manage and apply knowledge effec-tively. Dove (1999b) felicitously associates agility with cats. A cat is both physically adept at movement and also mentally adept at choosing useful movement appropriate for the situation. If a cat has merely the ability to move quickly but moves inappropriately and to no gain (e.g., a cat on a hot tin roof), it might be called spastic or confused but never agile. On the other hand, a cat that knows what should be done but finds itself unable to move (e.g., a cat that's got itself up a tree), might be called catatonic, confused, or paralyzed but never agile. This example implies that agility cannot be easily attained. It requires knowledge, experience, and skill. Enterprise agility depends on many factors such as per-sonnel capabilities, information technology (IT) infra-structure, business strategy, and so forth. When an enterprise is agile, all its constituents are agile and vice versa. This article focuses particularly on IT infrastruc-ture. It defines agility in IT infrastructure and explains how it contributes to enterprise sensing and response agility. Sensing agility is defined as a firm's ability to rapidly discover and interpret the market opportunities through its information systems, and it concerns not only an ability to distinguish information from noise quickly, but also to transform apparent noise into meaning faster (Haeckel, 1999). Response agility relates to the organiza-tional capability to quickly transform knowledge into action in response to the environmental signals (Haeckel, 1999).

Proceedings of the 41st Annual Hawaii International Conference on System Sciences (HICSS 2008), 2008

Agility is a key characteristic for modern enterprises operating in a highly dynamic environment.... more Agility is a key characteristic for modern enterprises operating in a highly dynamic environment. The attainment of agility is a difficult issue involving all organizational aspects, such as business processes, information systems, personnel, organizational structure, etc. The ability to respond rapidly to changes by utilizing agile business processes is an important constituent of an agile enterprise. The focus of this paper is business process agility outlining the benefits of event-based business process modeling. To this end, an event-based approach is proposed enabling on-the-fly composition of business processes. The introduced approach adopts the concepts of Complex Event Processing. A conceptual architecture for an information technology infrastructure supporting event-driven business process execution is also proposed.

International Conference on Software Engineering Advances (ICSEA 2007), 2007

Extension mechanisms offered by UML 2.0 are often explored in order to define UML profiles that s... more Extension mechanisms offered by UML 2.0 are often explored in order to define UML profiles that serve specific modeling purposes. These UML 2.0 profiles should be effectively accommodated by standard UML-based modeling tools, which provide the means for applying them in practice. Almost every UML 2.0 modeling tool supports the definition of stereotypes and the description of constraints in Object Constraint Language. However, implementing a profile in practice often entails the development of additional functionality. This requirement mainly stems from the fact that when dealing with complex models it is more efficient for end-users to help them enforce a constraint rather than notify them when it is broken. Such issues, encountered when developing a UML 2.0 profile for enterprise information systems engineering using Rational Software Modeler as a standard UML 2.0 modeling tool, are discussed in the paper.

2006 International Conference on Software Engineering Advances (ICSEA'06), 2006

Enterprise Information Systems can be described according to the Open Distributed Processing Refe... more Enterprise Information Systems can be described according to the Open Distributed Processing Reference Model (RM-ODP), where five different viewpoints are specified analyzing various aspects of the system. Configuration issues are explored in the Engineering Viewpoint of RM-ODP. In practice, configuration issues are explored in discrete stages, supported by autonomous software tools, each of which adopts its own metamodel for system representation. We propose a platform independent framework, which focuses on the Engineering Viewpoint of Enterprise Information Systems managing application configuration and network design issues independently of application development progress. In order to apply this framework using existing tools, model exchangeability and tool coordination must be supported by standard, open methods. Thus, a common metamodel is proposed to generate enterprise information system models, which are stored in XML. A UML 2.0 profile is defined to visualize these models, facilitate the designer to interact with them and coordinate specific tool invocation.