Krogstie / Opdahl / Sindre Advanced Information Systems Engineering

19th International Conference, CAiSE 2007, Trondheim, Norway, June 11-15, 2007, Proceedings
2007
ISBN: 978-3-540-72988-4
Verlag: Springer Berlin Heidelberg
Format: PDF
Kopierschutz: 1 - PDF Watermark

E-Book, Englisch, 622 Seiten

Reihe: Information Systems and Applications, incl. Internet/Web, and HCI

This book constitutes the refereed proceedings of the 19th International Conference on Advanced Information Systems Engineering, CAiSE 2007, held in Trondheim, Norway in June 2007.

The 39 revised full papers presented together with one keynote talk were carefully reviewed and selected from 301 submissions. The papers are organized in topical sections on ontologies, extended enterprises, information integration, service-oriented architecture, strategic alignment, requirements, process modeling, method engineering, novel applications, participative modeling, and process-aware information systems.

Written for: Researchers and professionals

Keywords: UML, Web services, agile software development, collaborative business process, conceptual modeling, data engineering, data semantics, enterprise information systems, enterprise modeling, information engineering, knowledge management, mobile information systems, model transformation, operational modeling, process modeling, querying, requirements management, semantic Web, service-oriented architecture, service-oriented computing, software product lines, software requirements, workflow architecture, workflow management systems.

Autoren/Hrsg.

Krogstie, John

Opdahl, Andreas L.

Sindre, Guttorm

Inhaltsverzeichnis

1;Preface;6
2;Organization;8
3;Table of Contents;14
4;Agile Software Development of Mobile Information Systems;18
5;Modal Aspects of Object Types and Part-Whole Relations and the de re/de dicto Distinction;22
6;Change Detection in Ontologies Using DAG Comparison;38
7;Automatic Generation of Model Translations;53
8;Handling Instance Correspondence in Inter-organisational Workflows;68
9;Assessing Feasibility of IT-Enabled Networked Value Constellations: A Case Study in the Electricity Sector;83
10;Behavioral Consistency for B2B Process Integration;98
11;Declarative XML Data Cleaning with XClean;113
12;Personalizing PageRank-Based Ranking over Distributed Collections;128
13;Generic Schema Merging;144
14;Discovering Web Services to Specify More Complete System Requirements;159
15;On ISOA: Intentional Services Oriented Architecture;175
16;WSXplorer: Searching for Desired Web Services;190
17;e3forces : Understanding Strategies of Networked e3value Constellations by Analyzing Environmental Forces;205
18;Aligning IS to Organization’s Strategy: The INSTAL Method;220
19;Towards a Framework for Tracking Legal Compliance in Healthcare;235
20;Conceptual Modeling of Privacy-Aware Web Service Protocols;250
21;Policies for Context-Driven TransactionalWeb Services;266
22;On Automated Generation of Web Service Level Agreements;281
23;RED-PL, a Method for Deriving Product Requirements from a Product Line Requirements Model;296
24;Deciding to Adopt Requirements Traceability in Practice;311
25;Designing Social Patterns Using Advanced Separation of Concerns;326
26;Modeling Business Contexture and Behavior Using Business Artifacts;341
27;Policies and Aspects for the Supervision of BPEL Processes;357
28;Goal Annotation of Process Models for Semantic Enrichment of Process Knowledge;372
29;Stakeholder Identification as an Issue in the Improvement of Software Requirements Quality;387
30;The Impact of Task Structure and Negotiation Sequence on Distributed Requirements Negotiation Activity, Conflict, and Satisfaction;398
31;Introducing Graphic Designers in a Web Development Process;412
32;Communication Abstractions for Distributed Business Processes;426
33;Questionnaire-driven Configuration of Reference Process Models;441
34;Formalization and Verification of EPCs with OR-Joins Based on State and Context;456
35;Towards More Extensible MetaCASE Tools;471
36;Concepts for Incremental Method Evolution: Empirical Exploration and Validation in Requirements Management;486
37;ReeF: Defining a Customizable Reengineering Framework;502
38;Publishing and Discovering Information and Services for Tagged Products;518
39;Automating Standard Operating Procedures in Intensive Care;533
40;Composing Data-Providing Web Services in P2P-Based Collaboration Environments;548
41;Participative Enterprise Modeling: Experiences and Recommendations;563
42;Negotiating Models;578
43;Change Patterns and Change Support Features in Process-Aware Information Systems;591
44;Analyzing the Dynamic Cost Factors of Process-Aware Information Systems: A Model-Based Approach;606
45;Author Index;621

Leseproben

1 Introduction (p. 17)

Agile software development methods have emerged rapidly since the mid 1990’s. The roots of agile methods are placed far beyond the last decade, however [1]. Industry has been keen on adopting agile solutions in recent years. Large software corporations such as Microsoft and SAP have announced publicly of their plans to adopt agile methods. Information systems build in embedded devices such as cars, telecom systems or consumer electronics systems present no exception to this.

Large companies such as Philips, Nokia, British Telecom, to name a few, are either already adopting or plan to adopt agile software solutions as their means to tackle software related challenges. A recent Forrester survey1 suggested that one out of seven software companies already use agile methods. Agile methods have been criticized for the lack of solid, scientifically valid empirical data to back up their claims [2, 3].

Yet, the situation is far from unique in the fields of software and information systems development. Fenton [4] argued that while software professional often seek for rational basis for making a decision about which development method they should adopt, the basis for such rationalization is completely missing. Fenton went as far as claiming that the "methods introduced continue to be based on more on faith than on an empirical data". Based on recent industrial attention, we can suggest that the lack of data has not slowed down the adoption of agile methods.

There is no agreed definition of agile methods in information systems or software engineering fields. In industrial engineering science the situation is quite different. They have proposed 17 competing definitions of the concept of agile manufacturing [5]. In software engineering, the concept of agile software is most often related to the elements presented in the Agile Manifesto (http://www.agilemanifesto.org). To some extent, we can assert that it is the most accepted conceptualization of agile software development as it has received more than 5000 independent signatories over a few years time.

This holds, however, no scientific meaning. Rather, it shows something about the popularity of these methods. In information systems field, the concept of agility emerged in the late 1990’s with studies about internet-speed development [e.g., 6]. Yet, the very concept of agile development still denotes to "more formal than hacking and less formal than traditional methods" [7, p.29].

Mobile information systems, whether they are operated as a stand alone application in mobile terminals or as an access provider to a back end system, are restricted by terminal constraints. Some of these constraints are screen size, keyboard, memory constraints and the battery power. The devices, however, are developing technologically very rapidly and most of the modern handheld devices called smart phones have the processing power of regular computers. Thus, the restrictions that were in place a few years ago do not hold within the next coming years.

Moreover, the mobile telecommunications industry has shown to be comprised of a highly competitive, uncertain and dynamic environment [8]. While, so far, mobile commerce applications have not been very successful, telecommunications companies believe a change in short term due to the adoption of 3G technologies.