EMC - A Modeling Method for Developing Web-based Applications

Early information systems were mainly built around secondary, administrative processes of the value chain (e.g., accounting). But since the internet came into use, more and more primary processes have become accessible to automation: customer acquisition, ordering, billing and, in the case of intangible goods such as software, even delivery. Hence an increasing part of an enterprise has to be modeled and a substantial part thereof is implemented, usually in an object-oriented programming language like Java. To facilitate this complex task, the MEMO methodology (Multi-perspective Enterprise MOdeling) allows the description of the enterprise on three levels – strategy, organization and information system – and from four angles – process, structure, resources and goals. All partial models for the views are integrated via a common object-oriented core. In this framework we suggest a modeling method for the IS layer, the Event-driven Method Chain (EMC). It is based on the Event-driven Process Chain (EPC) by Scheer, which we adapt to fit both the MEMO methodology and the object-oriented paradigm thus making it suitable for the development of web-based applications. To illustrate this we use the example of a software trading company.

Web-Based Cooperative Information Systems Modeling

This chapter presents a modeling for the Web-Based Cooperative Information Systems (WBCISs). This modeling considers the WBCISs as support of the unavoidable interactions among multiple existing heterogeneous subsystems of the information system and external information sources that share business objects and processes. The WBCIS is considered as an artifact that firstly and mainly allow information exchange, coordination and cooperation among these sources; and secondly data restructing and processes reuse or reengineering. The main concepts are Knowledge Sources and Interaction Component. A knowledge source represents a subsystem of the information system (Personal IS, Workgroup IS or Enterprise IS); or any external information source. The modeling considers the knowledge source as a UML package that presents an interface definition (business objects schema and processes). An interactions component is a kind of Web-based broker of business objects and processes. It is a support for communication services and user-oriented semantic services of the knowledge sources. It is based on the Web so that it deals with semi-structured data and accesses any knowledge source (willing to interact) having its URL. It uses a metadata that describes the knowledge sources as UML package. The modeling specializes interactions components according to the interaction situations of the knowledge source namely interactions for coordination that deal with the consistency of the shared business objects, interactions for cooperation related to the coupled processes’ activities or interactions for transmission that deal with informal and unstructured information exchanges. A Coordination Component allows knowledge source location, access, integration, global view and restructing of the business objects. A Cooperation Component allows process’ activities invocation, reuse or reengineering activities. This methodologic specialization allows easier implementation and reuse of the interaction components. An interaction component is modeled as a UML package.

Simulation for Business Engineering of Electronic Markets

Developments in Information and Communication Technology (ICT) enable information systems to intermediate between sellers and buyers in electronic markets (e-markets). A business engineering methodology can be of help to design and develop e-markets by providing insight into current market and potential e-market structures, matching mechanisms and processes, and by evaluating the implications of e-markets. In this chapter, a first concept of an interactive, discrete-event, agent-based simulation approach for the analyses and design of e-markets is presented and evaluated.

Evaluating an ISD Methodology for Software Packages

The Software Package Development Methodology (SPDM) is a methodology for developing complex and customizable software packages supporting business processes, especially Enterprise Resource Planning (ERP) software. Two approaches are applied by this chapter. First SPDM will be compared to a method engineering framework. Method engineering is a discipline to construct new methods from parts of existing methods taking into account situational factors. The second approach is the analysis of the results of a questionnaire, asking users of SPDM their opinion on several issues concerning problems and quality of SPDM. The conclusions, after applying both approaches, are quite similar and some recommendations are made for future research.

From Object-Oriented Modeling to Agent-Oriented Modeling

The use of intelligent agents is on the rise, fueled by the unprecedented growth in the internet and web based applications. Consequently, agent-oriented software is becoming large and complex. To support a systematic development of such software, an agent-oriented software development methodology is necessary. This chapter focuses on the modeling phase of agent-oriented software life cycle and, presents an approach for agent modeling consisting of Agent Elicitation, Intra, and Inter Agent modeling methods. Agent Elicitation deals with identifying and extracting agents from “classes” in the real world. Intra Agent Modeling involves expressing agent characteristics æ Goal, Belief, Plan and Capability æ whereas, Inter Agent modeling incorporates agent mobility and communication in a multi- agent system.

Enforcing Modeling Guidelines in an ORDBMS-based UML-Repository

Due to its rich set of modeling concepts and its broad application spectrum the Unified Modeling Language (UML) has become widely accepted for modeling many aspects of software systems. Since UML is not related to any particular design method, each software development project has to establish its own modeling guidelines. Hence, tool support is needed for guiding the developer throughout the modeling process and for enforcing project-related integrity of UML models. In this chapter, we present our approach for enforcing guidelines in UML-based software development processes. For managing UML models, we implemented a UML repository on top of an object-relational database management system (ORDBMS). Guidelines are expressed as OCL constraints and are enforced either automatically, i. e., by the UML repository, or on user demand. For this purpose, we take advantage of ORDBMS query facilities for checking guidelines by automated mapping of OCL constraints to SQL expressions.

Modelling Business Rules Using Defeasible Logic

We can define business rules as statements that are used by a body or an organization to run their activities. Some of these rules are drafted by the body itself, others are rules that have been drafted by external body but it will have an effect on the organization. Some business rules are documented explicitly, others are used implicitly. Globalization of business and increased competition cause frequent changes in business rules. New rules are added, old rules are modified or retracted. For example, to compete with its rivals, a bank should adjust its interest rate, launch new services etc. In this situation that is very hard to keep the rules consistency, there is the chance that some rule violate the other. Dealing with conflicting business rules is an important aim of our work. In addition there are also situations where a manager should take a decision although not all relevant information is known. He/she must be able to draw conclusions even if the available evidence is insufficient to guarantee their correctness. Obviously, such conclusions are risky and may be invalidated in the light of new, more accurate information. This situation is referred to as reasoning with incomplete information.

Is There a Life After Objects?

We are presently witnessing a rapid paradigm change in software engineering: from objects to models. This chapter discusses some aspects of the emerging domain of model engineering, mainly those related to meta-modelling and uniform representation of models and meta-models. This much recalls the discussions on classes and objects that were taking place in the early eighties. In the last period, the issue of code interoperability has been dealt with such acceptable solutions as CORBA or the associated IDL language. But we are now witnessing the multiplication of non-executable models, as part of the evolving software development practice. In order to cope with this increasing complexity, a general and regular framework has to be defined. This is being achieved, in environments like the OMG, where all the new models are based on a precise meta-model and where all the meta-models are based on a common and unique meta-meta-model called the MOF. The MOF is rapidly gaining practical importance, between UML and XML, in the industrial strategy of several important companies. It is playing the role of a knowledge bus for all kind of models, object models or legacy models, product models or process models, existing models or yet to be defined models. In particular it is helping to provide a smooth transition from objects and components models to the business processes, workflows and service models that are becoming key elements in the area of Web services.

A Three Layered Approach for General Image Retrieval

Several approaches are proposed for retrieving images. Each of them describes image according to application domain requirements. No global approach exists to resolve retrieving image in complex domains (as medical one), in which content is multifaceted. A framework to retrieve medical images is presented. In this paper, we expose our three-dimensional approach applied to medical domain, and required elements for both knowledge base and retrieval process. The proposed approach, built on multifaceted aspect, offers all possibilities to describe image within multifaceted content (context, physical and semantic). Conceptual relations are presented for designing knowledge base for coherent and efficient indexing and retrieval processes. Required spatial relations of processes are also exposed.

A Comparison of Stochastic Models for the Interarrival Times of Packets in a Computer Network

Because of the complexity and over-subscription of today’s networks, the importance of valid simulation techniques to aid in determining sound network design is paramount. A number of studies have shown that the theoretical exponential packet interarrival rates are not appropriate for many network installations. This chapter compares two other modeling techniques: the power law process and Markov chains to the exponential and actual data taken from a ten-minute segment. The results reveal that the exponential and power law models are a poor match to the actual data. The Markov chain model, although not perfect, yielded some promising results.