by @z Bentley programming pearls LITTLE LANGUAGES When you say " language, " most programmers think of the big ones, like FORTRAN or COBOL or Pascal. programming pearls BUMPER-STICKER COMPUTER SCIENCE Every now and then, programmers have to convert units of time. If a program processes 100 records per programming pearls THE ENVELOPE IS BACK The February 1984 column was about " back-of-the-envelope " calculations. When you're deciding programming pearls-Frank Starmer by ]an Bentley programming pearls SELF-DESCRIBING DATA You just spent three CPU hours running a simulation to forecast your company's financial future, and

Software engineering: theory and practice

Requirements capture is arguably the most important step in software engineering, and yet the most difficult and the least formalized one [Phalp and Shepperd 2000] Enterprises build information systems to support their business processes Software engineering research has typically focused on the development process, starting with user requirements—if that—with business modeling often confused with software system modeling [Isoda 2001] Researchers and practitioners in management information systems have long recognized that understanding the business processes that an information system must support is key to eliciting the needs of its users (see eg, Eriksson and Penker 2000]), but lacked the tools to model such business processes or to relate such models to software requirements Researchers and practitioners in business administration have long been interested in modeling the processes of organizations for the purposes of understanding, analyzing, and improving such processes [Hammer and Champy 1993], but their models were often too coarse to be of use to software engineers The advent of ecommerce and workflow management systems, among other things, has led to a convergence of interests and tools, within the broad IT community, for modeling and enabling business processes In this article we present an overview of business process modeling languages We first propose a categorization of the various languages and then describe representative languages from each family

Business process modeling languages: Sorting through the alphabet soup

We may not be able to make you love reading, but production workflow concepts and techniques will lead you to love reading starting from now. Book is the window to open the new world. The world that you want is in the better stage and level. World will always guide you to even the prestige stage of the life. You know, this is some of how reading will give you the kindness. In this case, more books you read more knowledge you know, but it can mean also the bore is full.

Production workflow: concepts and techniques

Understanding the business is an important step in information system (IS) development. Conceptual models are descriptions of the organizational context for which a system is developed, and are used to help understanding this context. However, conceptual modelling methods do not provide well-formalized ways to create domain descriptions. On the other hand, in the area of IS design and software modelling, languages exist (such as UML) that possess a high level of formality. Extending the use of these IS design languages to conceptual modelling, even though they have not been specifically intended for this, can lead to several advantages. In particular, it can enable the use of similar notation in several stages of system development. However, while object-oriented constructs such as “object” and “operation” have clear meaning in the context of software design, it is not clear what they might mean in terms of the application domain, and no rules or guidelines exist for using them to create useful descriptions of such domains. This paper suggests specific semantics for object-oriented constructs based on a mapping between ontologically derived concepts and object-oriented language constructs. The paper also proposes modelling rules to guide the construction of object-oriented conceptual models and to assure that such models describe only ontologically feasible application domain situations. While the results are applicable to object-oriented constructs in general, UML is used as an example. A case study to test the use of the proposed semantics and modelling rules is described.

Ontology based object-oriented domain modelling: fundamental concepts

Purpose – Many business process improvement efforts emphasize better integration, yet process integration can mean many things. The purpose of this paper is to emphasize the importance of information flows to modern business processes, and draw upon recent organizational and information systems literature to characterize process integration and to derive four principles of process integration: accessibility, timeliness, transparency, and granularity of information flows.Design/methodology/approach – Using a field study, the four principles of process integration are applied to analyze ten different business processes across five organizations.Findings – In total, 18 generalized activities are identified that describe non‐integrated behavior, and “keying in known data” was found to be the most common. Among other findings, analysis highlights the importance of documentation to modern business processes, especially for coordination roles, and the paper describes three different purposes for documentation fo...

Information flows and business process integration

This paper evaluates the dynamic aspects of the UML in the context of inter-organizational workflows. Two evaluation methodologies are used. The first one is ontological and is based on the BWW (Bunge-Wand-Weber) models. The second validation is based on prototyping and consists of the development of a workflow management system in the aerospace industry. Both convergent and divergent results are found from the two validations. Possible enhancements to the UML formalism are suggested from the convergent results. On the other hand, the divergent results suggest the need for a contextual specification in the BWW models.

An Evaluation of Inter-Organizational Workflow Modelling Formalisms

Le debut des annees 90 a ete une periode caracterisee par un certain scepticisme vis-a-vis des technologies de l'information (TI). En effet, malgre l'evolution des technologies et l'importance des investissements realises, on ne mesurait toujours pas des gains en performance notables et tout particulierement en terme de productivite. Plusieurs travaux furent publies durant meme periode pour promouvoir de profonds changements organisationnels lors de l'implantation de systemes dans les organisations. Les gains de productivite seraient obtenus quand les TI ne seraient plus de simples outils d'automatisation mais seraient utilisees pour mettre fin aux divisions des organisations par fonctions. L'ere du Re-engineering et des systemes integres tels que SAP R/3, Peoplesoft et autres debutait. L'implantation de ces systemes connut un sommet a la fin des annees 90 lorsque ces derniers ont permis de remplacer des systemes herites pour lesquels le passage a l'an 2000 aurait entraine des mises a jour couteuses. A ce jour, cette phase d'integration intra-organisationnelle est completee ou est en bonne voie de l'etre pour nombre d'organisations. L'interet se tourne donc maintenant vers une integration inter-organisationnelle ou de nombreux gains en terme d'efficacite sont esperes. En effet, en 2002, une grande partie des echanges entre organisations n'est pas encore automatisee et se fait par des moyens traditionnels tels que le telephone, le fax ou le courrier. L'objectif de ce rapport est de presenter un ensemble de technologies, d'exemples concrets et enfin de concepts relies aux systemes d'information inter-organisationnels (SIIO). Il appert que le veritable defi pour l'implantation d'un SIIO ne se situe generalement pas a un niveau technologique. Des differences au niveau des objectifs, un mauvais alignement avec les differentes strategies d'affaires, un manque de confiance ou le refus d'une situation dite de lock-in (prisonnier) a un partenaire d'affaires pourront mener a un echec rapide du systeme, quelle que soit sa qualite technologique. De plus, lorsqu'on envisage la mise en place d'un SIIO dans une relation de chaine d'approvisionnement, il est important, au-dela des gains d'efficacite qui seront faits avec notre partenaire d'affaires direct, de determiner comment ces gains se repercuteront sur le consommateur final. Trop souvent, on oublie que c'est sa decision d'achat qui soutient l'ensemble de la chaine. Les decisions doivent donc tenir compte de l'ensemble de la chaine de valeur, et idealement rester avantageuses pour tous les partenaires d'affaires.

Systèmes d'information inter-organisationnels

This chapter presents a twofold methodology for the evaluation of interorganizational workflows modeling formalisms. The first approach is ontological and based on the Bunge-Wand-Weber models. The second is based on prototyping and consists in the development of a WFMS for language evaluation. The dual evaluation methodology is then applied to the UML with a practical example from the aerospace industry. Both convergent and divergent results are found from the two validations. IDEA GROUP PUBLISHING 701 E. Chocolate Avenue, Suite 200, Hershey PA 17033-1240, USA Tel: 717/533-8845; Fax 717/533-8661; URL-http://www.idea-group.com ITB11174 This chapter appears in the book, Business Systems Analysis with Ontologies, edited by Peter Green and Michael Rosemann. © 2005, Idea Group Inc. Evaluating Inter-Organizational Workflow Modeling Formalisms 271 Copyright © 2005, Idea Group Inc. Copying or distributing in print or electronic forms without written permission of Idea Group Inc. is prohibited. Possible enhancements to the UML formalism are suggested from the convergent results. On the other hand, the divergent results suggest the need for a contextual specification in the BWW models.

A Twofold Approach for Evaluating Inter-Organizational Workflow Modeling Formalisms

This paper evaluates the dynamic aspects of the UML in the context of inter-organizational workflows Two evaluation methodologies are used The first one is ontological and is based on the BWW (Bunge-Wand-Weber) models The second validation is based on prototyping and consists in the development of a workflow management system in the aerospace industry Both convergent and divergent results are found from the two validations Possible enhancements to the UML formalism are suggested from the convergent results On the other hand, the divergent results suggest the need for a contextual specification in the BWW models Ce travail consiste en une evaluation des aspects dynamiques du language UML dans un contexte de workflow inter-organisationnel Le choix du language par rapport a d'autres est motive par sa richesse grammaticale lui offrant une tres bonne adaptation a ce contexte L'evaluation se fait par une validation ontologique basee sur les modeles BWW (Bunge-Wand-Weber) et par la realisation d'un prototype de systeme de gestion de workflows inter-organisationnels A partir des resultats convergents obtenus des deux differentes analyses, des ameliorations au formalisme UML sont suggerees D'un autre cote, les analyses divergentes suggerent une possibilite de specifier les modeles BWW a des contextes plus particuliers tels que ceux des workflows et permettent egalement de suggerer d'autres ameliorations possibles au langage

Handle everyday research tasks with reliable, citation-backed results

Your personal Research Agent to handle research tasks with citation-backed results

Popular Tasks used by Researchers

How can I help with your research?

Meet SciSpace

Get more enhanced response by uploading the PDFs you want me to reference.

No relevant PDFs in your library

SciSpace is the AI research assistant for academics. Run systematic literature reviews on 280M+ papers, and write papers with cited sources. Trusted by 1M+ students, PhDs & researchers.

SciSpace | AI for Research

Analyze PDFs

Code & Manuscripts

Funding & Grants

Literature & Patents

Medical & Clinical Data

Systematic Review

Visualize & Present

Web & Data

Build a Google Scholar-like website for your research.

Build a website

Create charts and images for your research

Create a Chart

Write a paper for submission to a journal

Draft a manuscript

Patent Search

Design eye-catching scientific posters in minutes.

Scientific Poster Generation

Systematic Literature Review

One task is running at the moment. Your messages will be shown right after.

Drag and drop or click here to browse

Loved by <highlight>1 million+</highlight> researchers

Extract a list of specific topics and their sources from unstructured text

Topics

Compare and analyze relevant papers that matches with your search

Papers

Get insights from PDFs and bookmarked papers from your library

My library

Recent searches

Try searching for:

Catch AI-generated content in scholarly and non-scholarly content

{ai} Detector

Ai Writer

Get PDF Summaries, highlighted text explanations 

Chat with PDF

Effortlessly create in-text citations and bibliographies in APA and 2,500 other formats

Citation generator

Get explanations, summaries, and answers on academic papers

Ease up your research workflow with {scispace}'s cohort of exciting AI tools

Elevate your academic writing skills and convey your ideas the way you want

Paraphraser

Explore our range of reading and writing tools

Your file is being prepared and should be ready in a few minutes. If it's a large file, it might take a bit longer. You can close this window, and we'll email you the file when it's done.

You have reached a maximum limit of <strong>{limit}</strong> columns in the table. Remove at least <strong>1</strong> column to add or create another one.

Aymeric Dussart

Author Tools

Chat about Author

Papers

An Evaluation of Inter-Organizational Workflow Modelling Formalisms

Systèmes d'information inter-organisationnels

A Twofold Approach for Evaluating Inter-Organizational Workflow Modeling Formalisms

An Evaluation of Inter-Organizational Workflow Modelling Formalisms