Search

More and more often the organizations need to use a flexible organization model able to adapt quickly the internal structure to the changing market conditions. In many cases, this uninterrupted need of changing is not compliant with the strict structure of the enterprise business process that set the employees and their activities in a fixed schema. To face this situation, in the past years many methodologies are born in order to improve the quality and to reduce the risks of change management into an enterprise. Nowadays, the main innovation in the panorama of the organizational model is the introduction of the Enterprise 2.0 (E2.0) philosophy. The E2.0 main concept of make the enterprise more flexible improving the collaboration between the employees represents a new aspect that before in the traditional approach was not considered. The use inside of an enterprise of the E2.0 is not a simple adoption of a new technology but a more complex change that involves several areas. Today, there is not a unique and well-know process that could lead the enterprise in the adoption of E2.0. This paper wants to provide (describing the introduction process) the guidelines and the methodological steps that an organization could be executed for a correct and complete adoption of the E2.0 philosophy. [ABSTRACT FROM AUTHOR]

More and more often the organizations need to use a flexible organization model able to adapt quickly the internal structure to the changing market conditions. In many cases, this uninterrupted need of changing is not compliant with the strict structure of the enterprise business process that set the employees and their activities in a fixed schema. To face this situation, in the past years many methodologies are born in order to improve the quality and to reduce the risks of change management into an enterprise. Nowadays, the main innovation in the panorama of the organizational model is the introduction of the Enterprise 2.0 (E2.0) philosophy. The E2.0 main concept of make the enterprise more flexible improving the collaboration between the employees represents a new aspect that before in the traditional approach was not considered. The use inside of an enterprise of the E2.0 is not a simple adoption of a new technology but a more complex change that involves several areas. Today, there is not a unique and well-know process that could lead the enterprise in the adoption of E2.0. This paper wants to provide (describing the introduction process) the guidelines and the methodological steps that an organization could be executed for a correct and complete adoption of the E2.0 philosophy. [ABSTRACT FROM AUTHOR]

A problem in the modern web Information Systems is sharing data among companies. Here companies are opened towards new markets and they often need important data, often not present in their Information System yet. Making available data between different companies is a critical success factor for them but this is a problem related to the different semantic used by each company to represent its data in their database and the necessity to use Communication Systems does not require to change the initial Information System. In this paper we propose an architecture that, considering each Information System as an Agent, allows to make in a simple way the data sharing between different Information Systems using from a side ontologies to align the semantic used in the Information Systems to represent data, from the other one a Communication System (Jade) that, using in a native way ontologies, is able to guarantee an efficient data sharing. [ABSTRACT FROM AUTHOR]

A problem in the modern web Information Systems is sharing data among companies. Here companies are opened towards new markets and they often need important data, often not present in their Information System yet. Making available data between different companies is a critical success factor for them but this is a problem related to the different semantic used by each company to represent its data in their database and the necessity to use Communication Systems does not require to change the initial Information System. In this paper we propose an architecture that, considering each Information System as an Agent, allows to make in a simple way the data sharing between different Information Systems using from a side ontologies to align the semantic used in the Information Systems to represent data, from the other one a Communication System (Jade) that, using in a native way ontologies, is able to guarantee an efficient data sharing. [ABSTRACT FROM AUTHOR]

Significant effort is currently invested in Web Application design, particularly in the study of integrating methodologies for designing business processes and Web Applications. However, academia still needs to be further exposed to real world project experiences and best practice where existing conceptual tools are tentatively exploited, and where useful tools can emerge. This paper introduces the overall architecture implemented and recounts the experience and lessons learned integrating the Business Process Modeling Notation (OMG BPMN) whit a methodological approach for the development of an ERP web-based system for a medium-sized enterprise within the wheat mill industry of South East Italy. [ABSTRACT FROM AUTHOR]

Significant effort is currently invested in Web Application design, particularly in the study of integrating methodologies for designing business processes and Web Applications. However, academia still needs to be further exposed to real world project experiences and best practice where existing conceptual tools are tentatively exploited, and where useful tools can emerge. This paper introduces the overall architecture implemented and recounts the experience and lessons learned integrating the Business Process Modeling Notation (OMG BPMN) whit a methodological approach for the development of an ERP web-based system for a medium-sized enterprise within the wheat mill industry of South East Italy. [ABSTRACT FROM AUTHOR]

The growing demand for web applications and the new multi-user and multi-device requirements of these has led to the need for a structured and well-reasoned approach that helps both the application designer and the developer to produce a good quality product. On one hand we have the application designer, who has to describe all aspects of the application and manage the complexity of the tasks; on the other hand both the application customer and the developer need to validate and understand the designer's choices. To conciliate these needs, we propose a prototyping framework based on W2000 [1][2] methodology: in this way the designer has a powerful tool to keep control over the web application, the customer has a point of reference for evaluating the design, and the developer can better understand the design thanks to the prototyped application. [ABSTRACT FROM AUTHOR]

Estimation of time and costs is a crucial factor in an application development project and low error margins are a priority. This principle is also true for development projects for applications based on Web technology (Web Applications - WA), considering that the evolution of this technology makes it possible to model not only specific services (e.g. e-commerce, Internet Banking) but also important modules of a company's information system. The aim of this study is to illustrate the estimating process of a real Web Application which was modelled and implemented as part of a European project called UWA. The model considered in this estimating process is MMWA (Metrics Model for Web Applications), a model classified as "early measures" which takes into account all the specific characteristics of a Web Application. The paper does not go into the principles and planning choices associated with MMWA, but examines how the model must be used, the final results obtained from the estimating process, the difference between this and the actual effort required, and how this experience fits into the broader context of experimentation with MMWA. [ABSTRACT FROM AUTHOR]

Sure that quality applications must be well thought and described before the development phase and that a design methodology can be much more than a help in most occasions, we propose a development framework based on a well organized and tested design methodology for hypermedia applications. In this paper we show its in-the-large structure and explain which modules complete it and how they interact and communicate. We also describe the solution we chose to store and share data and information within the framework itself. Exploiting an ontological vision (preserving the semantic aspects) we hope we will get better results than using a more conventional XML solution. [ABSTRACT FROM AUTHOR]

Sure that quality applications must be well thought and described before the development phase and that a design methodology can be much more than a help in most occasions, we propose a development framework based on a well organized and tested design methodology for hypermedia applications. In this paper we show its in-the-large structure and explain which modules complete it and how they interact and communicate. We also describe the solution we chose to store and share data and information within the framework itself. Exploiting an ontological vision (preserving the semantic aspects) we hope we will get better results than using a more conventional XML solution. [ABSTRACT FROM AUTHOR]

The increased complexity of Web applications makes us sure of the importance of concentrating, before s tarting the development, on a suitable organic design of such an application. Most conceptual design technologies are powerful analysis tools but are too far from the implementation and result almost useless to produce a complete work. We want to build a s et of tools, able to fill the gap, letting the developer use the conceptual result of the W2000 analysis as a "ready to produce" methodology. In this Work In Progress, we refer about the first step of our research, in which, trying to verify the effectiveness of the W2000 methodology [L. Baresi et al] [P. Paolini et al], based upon the well-known HDM model [F. Garzotto et al], we produce a pilot application using a standard technology. This experience will be the base for the framework we are thinking of, in order to guide the developer along all the development process, making the phases as automatic as possible. We describe the reasons and the goals of our work, during its working out, as well as the results we already got. We also express which will be the guidelines we are going to follow, moving on the second step. [ABSTRACT FROM AUTHOR]