Enterprise software

Résumé

Enterprise software, also known as enterprise application software (EAS), is computer software used to satisfy the needs of an organization rather than individual users. Such organizations include businesses, schools, interest-based user groups, clubs, charities, and governments. Enterprise software is an integral part of a computer-based information system. Enterprise software handles a number of operations in an organization, for example to enhance the business and management reporting tasks, or support production operations and back-office. The systems must process the information at a relatively high speed. Services provided by enterprise software are typically business-oriented tools. As companies and other organizations have similar departments and systems, enterprise software is often available as a suite of customizable programs. Enterprise software tools cover database management, customer relationship management, supply chain management, business process management and so on. The term enterprise software is used in industry, and business research publications, but is not common in computer science. In academic literature no coherent definition can be found. The computer historian Martin Campbell-Kelly contemplated in 2003 that the growth of the corporate software industry is not well understood. Enterprise application software (EAS) is recognized among academics as enterprise software components and modules which support only a particular business function. These EAS software components and modules can interoperate, so that cross-functional or inter-organizational enterprise systems can be built up. In this context the industry may speak of middleware. Software that is primarily sold to consumers, is not called enterprise software. According to Martin Fowler, "Enterprise applications are about the display, manipulation, and storage of large amounts of often complex data and the support or automation of business processes with that data.

Source officielle

https://en.wikipedia.org/wiki/Enterprise_software

À propos de ce résultat

Cette page est générée automatiquement et peut contenir des informations qui ne sont pas correctes, complètes, à jour ou pertinentes par rapport à votre recherche. Il en va de même pour toutes les autres pages de ce site. Veillez à vérifier les informations auprès des sources officielles de l'EPFL.

Publications associées (4)

Concepts associés (23)

Cours associés (1)

Séances de cours associées (20)

Requirements Elicitation with a Service Canvas for Packaged Enterprise Systems

Gil Regev, Alain Wegmann, Blagovesta Hristova Kostova, Lucien Alexandre Etzlinger

We present a technique for eliciting requirements based on the use of a service canvas and the results of its application in the early phase of a customer relationship management integration project. The project was a collaboration between a research group and two industry partners. We describe (1) our service canvas, (2) how we designed a set of workshops to elicit the requirements, (3) the support tools used for running the workshops, and (4) the resulting canvas, listing the customer relationship management requirements, that was the basis for the project proposal. We explain how, as participant observers, we conducted the project and how we collected and analyzed the data. We describe what worked well and the lessons we learned. We outline some practical problems that remain unsolved.

IEEE2019

Relevant and readily available information is a crucial basis for decision making, problem solving or performing knowledge-intensive work. The motivation for this thesis lays in the fact that in certain situations not all information provided by an application is important and relevant to the end user. Modern enterprise information systems provide huge amounts of information and quite often, in such large volumes of data, users do not know what is important, why something is important and finally, how to find relevant information. Moreover, in complex business environments users may not be fully aware of the current situation which in turn can negatively influence the decision making process. So, it is very important to provide the appropriate information to the user considering the respective situation. However, even if the user is provided with this information, the problem is not essentially solved. The user also has to understand why the provided information is important which means that he/she has to comprehend the current situation or to be aware of the context in which this situation happened. In this way, the user becomes able to fully understand the real meaning of the information. Therefore, it has become crucial for enterprise applications to be aware of the context they are being used in. Nowadays, manufacturing applications collect and store various kinds of data and information. This data describes users as well as the various aspects of business. This means that if properly interpreted, this data could be used to describe the overall user and business context. However, this is no easy task as context data is subject to constant change and can be highly heterogeneous. This work proposes an approach to solve these problems by providing an ontology-based context model and rules for its interpretation. This model will classify with the help of OWL-built ontologies the context of the users (the employees of a business who are accessing the system) and the context of the business. The user and business context will allow for an enterprise application to anticipate which information is important and relevant in order to serve it to the appropriate user. Since the solution utilizes contextual information and provides information and services according to it, the proposed approach could thus be characterized as âcontext-awareâ. In order to correctly model context information, various application domains in which a model could be applied should be taken into account. This basically means that it is necessary to provide a generic model which can be used in various application domains and use-cases. Having a generic model provides the distinct advantages of easy context information exchange as well as reusability of the model. On the other hand, it significantly reduces the expressiveness of the model and requires more computing to interpret it. Therefore, this approach proposes the upper model (ontology) which specifies only the common and generic concepts of context and supports context information exchange. However, it is not possible to model different domains only with the upper model, which means that for each case, a domain specific model should be specified. This domain specific model should extend the generic upper model and describe the specific domain in more detail. [...]

EPFL2014

Today, enterprise applications provide large amounts of data and finding the right information on time for a given purpose is often a challenge. In these environments, users do not know what information is important, why it is important and finally, how to find this important information. Therefore, an enterprise application has to decide which information is,relevant in certain a situation for certain a user. In order to accomplish that, the context of the information must be taken to account. Moreover, this application must be able to capture the context of the application user as well as the overall business context which describes the situation in which information is relevant. In this paper we propose an ontology-based context model which captures the general concepts about user and business context. Also, we discuss the challenges for context reasoning and interpreting and we present a case study to demonstrate the benefits of the developed concepts. (C) 2014 Elsevier B.V. All rights reserved.

Elsevier Science Bv2014

EPFL2014