E-Book, Englisch, 974 Seiten
Papadopoulos / Wojtkowski / Wrycza Information Systems Development
2010
ISBN: 978-0-387-84810-5
Verlag: Springer US
Format: PDF
Kopierschutz: 1 - PDF Watermark
Towards a Service Provision Society
E-Book, Englisch, 974 Seiten
ISBN: 978-0-387-84810-5
Verlag: Springer US
Format: PDF
Kopierschutz: 1 - PDF Watermark
This volume constitutes the published proceedings of the 17th International Conference on Information Systems Development. They present the latest and greatest concepts, approaches, and techniques of systems development - a notoriously transitional field.
Autoren/Hrsg.
Weitere Infos & Material
1;Preface;5
2;Contents;7
3;Conference Organisation;37
3.1;Programme Chair;37
3.2;Organising Chair;37
3.3;International Advisory Committee;37
3.4;Local Organising Committee;37
3.5;Track Chairs;37
3.6;Information Systems Engineering & Management;37
3.7;Business Systems Analysis & Design;38
3.8;Intelligent Information Systems;38
3.9;Agile and High-Speed Systems Development Methods;38
3.10;Enterprise Systems Development & Adoption;38
3.11;Public Information Systems Development;38
3.12;Information Systems Development Education;38
3.13;Information Systems Development in Developing Nations;38
3.14;Legal and Administrative Aspects of Information Systems Development;38
3.15;Information Systems Research Methodologies;38
3.16;Service-Oriented Analysis and Design of Information Systems;39
3.17;IT Service Management;39
3.18;Philosophical and Theoretical Issues in Information Systems Development;39
3.19;Model-driven Engineering in ISD;39
3.20;Human Computer Interaction (HCI) in Information Systems Development;39
3.21;International Programme Committee;39
4;Contributors;44
5;Designing Class Methods from Dataflow Diagrams;54
5.1;1. Introduction;54
5.2;2. Overview of the Design Phase of FOOM;55
5.3;3. Transactions and Their Descriptions;56
5.3.1;3.1 What is a Transaction?;56
5.3.2;3.2 Top-Level Descriptions of Transactions;58
5.4;4. Detailed Design of Transactions and Class Methods;59
5.4.1;4.1 Steps in the Design of Transaction and Class Methods;59
5.4.2;4.2 From Top-Level to Detailed Transaction Descriptions;59
5.4.3;4.3 From Detailed Descriptions of Transaction to Class Methods;60
5.4.4;4.4 Message Charts;62
5.5;5. Summary;62
5.6;References;63
6;On The Human, Organizational, and Technical Aspects of Software Development and Analysis;64
6.1;1. Introduction;64
6.2;2. Non-Technical Aspects of Software Development;65
6.2.1;2.1 Social Aspects;65
6.2.2;2.2 Organizational Aspects;65
6.2.3;2.3 Psychological Aspects;66
6.2.4;2.4 Cultural Aspects;66
6.3;3. Social Disciplines of Computer Science;66
6.4;4. Socio-Technical Software Analysis;68
6.4.1;4.1 Concept, Context, and Aims of Socio-Technical Software Analysis;68
6.4.2;4.2 Socio-Technical Software Analysis vs. Traditional Domain Analysis;68
6.5;5. Discussion and Conclusions;69
6.6;References;70
7;Toward Modeling Language-Independent Integration of Dynamic Schemata;73
7.1;1. Introduction;73
7.2;2. Related Work;74
7.3;3. Guidelines for Language Independent Schema Integration;75
7.3.1;3.1 Phase 1 - Preparation of Source Schemata;75
7.3.2;3.2 Phase 2 - Recognition of Conflicts and Commonalities Between Source Schemata;76
7.3.3;3.3 Phases 3 and 4: Conflict Resolution and Schema Merging;76
7.4;4. Applying the Guidelines - A Motivating Example;77
7.4.1;4.1 The Applied Modeling Languages;77
7.4.2;4.2 Integrating Language-Independent Source Schemata;78
7.5;5. Summary and Conclusion;81
7.6;References;81
8;Improving Knowledge Management in the Health Service: Re-Engineering Approach Towards Successful Implementation;82
8.1;1. Introduction;82
8.2;2. Business Process Re-Engineering (BPR);83
8.3;3. Knowledge Management (KM);84
8.4;4. The Case Study;84
8.5;5. BPR Processes and Activities;86
8.5.1;5.1 Set Business Goals and Objectives for Implementing KM;87
8.5.2;5.2 Review Programme, Activities and Identify Communication Strategies;87
8.5.3;5.3 Estimate and Justify Cost for KM;87
8.5.4;5.4 Examine the Technical Challenges;87
8.5.5;5.5 ReDesign the Health-Care Project Management Process;88
8.5.5.1;5.5.1 Re-Engineer Towards IT Infrastructure;88
8.5.5.2;5.5.2 Consideration of KMS;88
8.5.6;5.6 Evaluate Change Management Issues;88
8.5.7;5.7 Implement the System;89
8.6;6. Limitations;89
8.7;7. Summary and Recommendations;89
8.8;8. Conclusion;89
8.9;Acknowledgement;90
8.10;References;90
9;Accounting, Charging and Billing for Dynamic Service Composition Chains;92
9.1;1. Introduction;92
9.2;2. ACB in Service Composition Chains;93
9.2.1;2.1 ACB in Static Service Composition Chains;94
9.2.1.1;2.1.1 Static Business Relationships;94
9.2.1.2;2.1.2 Static Service Composition Chains;94
9.2.1.3;2.1.3 ACB in Static Service Composition Chains;95
9.2.2;2.2 ACB in Dynamic Service Composition Chains;96
9.2.2.1;2.2.1 Dynamic Business Relationships;96
9.2.2.2;2.2.2 Dynamic Service Composition Chains;96
9.2.2.3;2.2.3 Impact on ACB in Dynamic Service Composition Chains;96
9.3;3. Dynamic Service Composition ACB Framework;97
9.3.1;3.1 Dynamic Service Composition Architecture;97
9.3.2;3.2 Framework Function Descriptions;98
9.3.2.1;3.2.1 Negotiation Layer;99
9.3.2.2;3.2.2 ACB Management Layer;99
9.4;4. Conclusion;99
9.5;References;99
10;Web Service Execution and Monitoring in Integrated Applications in Support of Business Communities;100
10.1;1. Introduction;100
10.2;2. Basic Business Scenario;101
10.3;3. Conceptual Architecture;102
10.3.1;3.1 Integration Tools;103
10.3.2;3.2 Component Execution;104
10.3.3;3.3 System Monitoring;105
10.4;4. Implementation Aspects;106
10.5;5. Summary and Conclusions;107
10.6;References;107
11;Scrutinizing UML Activity Diagrams;109
11.1;1. Introduction;109
11.2;2. The Flow Model;110
11.3;3. Some FM Features;110
11.4;4. Comparison of Some FM Features with UML;111
11.5;5. Conceptual Class Diagrams;113
11.6;6. Example of FM Capabilities: Exceptions in UML 2.0;115
11.7;7. Conclusion;117
11.8;References;117
12;Integration of Weakly Heterogeneous Semistructured Data;118
12.1;1. Introduction;118
12.2;2. Oceanographic Data Example;119
12.2.1;2.1 Querying Weakly Heterogeneous Data;120
12.3;3. Related Research;121
12.4;4. Proposed Approach;122
12.4.1;4.1 Query System Architecture;122
12.4.2;4.2 Mapping Schema;123
12.5;5. Conclusions and Future Work;126
12.6;Acknowledgments;126
12.7;References;126
13;Investigating the Applicability of Structural Analysis Techniques in Distributed Systems;128
13.1;1. Introduction;128
13.2;2. Structural Analysis Techniques;129
13.2.1;2.1 Support from Structural Analysis Techniques;130
13.3;3. Application to Distributed Systems;131
13.3.1;3.1 Proposed Technique;131
13.3.2;3.2 Application of Proposed Technique;133
13.4;4. Conclusion;137
13.5;References;137
14;Web-Based Systems Development: Analysis and Comparison of Practices in Croatia and Ireland;139
14.1;1. Introduction;139
14.2;2. The Software Industry in Croatia and Ireland;140
14.3;3. Research Method;140
14.4;4. Findings and Discussion;142
14.4.1;4.1 Small Development Teams and Collective Knowledge;142
14.4.2;4.2 Project Management and Requirements Management;142
14.4.3;4.3 Development Processes and Procedures;144
14.4.4;4.4 Attitudes Towards Documented Plans;145
14.5;5. Conclusions;146
14.6;References;147
15;The Solution Space Organization: Linking Information Systems Architecture and Reuse;149
15.1;1. Introduction;149
15.2;2. The Software Reuse Paradigm: A Literature Review;150
15.3;3. The Software Global Model;151
15.4;4. The Solution Space Structure;153
15.4.1;4.1 A Layered Description of the Solution Space;153
15.4.2;4.2 The Reuse Approach;155
15.5;5. Conclusion and Future Research Directions;156
15.6;References;156
16;Designing Cognition-Adaptive Human-Computer Interface for Mission-Critical Systems;158
16.1;1. Introduction;158
16.2;2. Literature Review;159
16.3;3. Design of Cognition-Adaptive Multimodal Interface (CAMI);161
16.3.1;3.1 Motivation and Objectives;161
16.3.2;3.2 CAMI Design and Analysis;162
16.4;4. Multimodal Interface Development and Cognitive Task Analysis;164
16.5;5. Cognitive Load Analysis and Measurement;165
16.6;6. Conclusions and Future Work;165
16.7;References;166
17;Conceptual Web Users’ Actions Prediction for Ontology-Based Browsing Recommendations;167
17.1;1. Introduction;167
17.2;2. Related Works;168
17.3;3. Mining of Users’ Interest Concepts for Predictions;169
17.3.1;3.1 Web Ontology;169
17.3.2;3.2 Extraction of Users’ Interest Concepts into Prediction Model;170
17.4;4. Predictions on Sequential and Conceptual Models;171
17.4.1;4.1 Conceptual Distance Between Pages Accessed;172
17.4.2;4.2 Empirical Study of the Prediction Models;172
17.5;5. Conclusions;174
17.6;References;174
18;Web Portal Design: Employment of a Range of Assessment Methods;176
18.1;1. Introduction;176
18.2;2. Background to the Research;177
18.3;3. Study 1: Usability Testing;177
18.3.1;3.1 Research Design and Methodology;178
18.3.2;3.2 Results and Discussion of Findings;179
18.4;4. Study 2: Guideline-Based Inspection;180
18.4.1;4.1 Assessment Procedure;181
18.4.2;4.2 Results and Analysis;181
18.5;5. Conclusion and Future Steps;183
18.6;Acknowledgements;184
18.7;References;184
19;A Proposed Extension of the CODAM Model for Human Attention;185
19.1;1. Introduction;185
19.2;2. Control Theory Approach for Computational Modeling of Attention;186
19.3;3. Brief Description of the CODAM Model;186
19.4;4. Some Important Issues and Questions on Specific Characteristics of Attention;187
19.5;5. Proposed Modifications on the Attention Model;188
19.6;6. Discussion;190
19.7;References;190
20;Aligning Service Requirements with Business Strategy: A Proposed Stakeholder Value Model for SOA;192
20.1;1. Introduction;192
20.2;2. Service-Oriented Requirements Engineering - A Review;193
20.3;3. Applying a Value-Based Approach to Service Requirements;194
20.3.1;3.1 An Empirical Understanding of the Business Drivers for SOA;194
20.3.2;3.2 The Value Proposition of SOA;195
20.3.2.1;3.2.1 Strategic Value Proposition;195
20.3.2.2;3.2.2 Tactical Value Proposition;196
20.3.2.3;3.2.3 Operational Value Proposition;196
20.3.3;3.3 Proposing a Stakeholder Value Model for SOA;197
20.4;4. Contributions and Future Research;198
20.5;References;199
21;A New Method for Conceptual Modelling of Information Systems;200
21.1;1. Introduction;200
21.2;2. Intersubjective and Objective View in System Analysis;201
21.3;3. Integration of Static and Dynamic Aspects;203
21.4;4. Service-Oriented Modelling of Information Systems;205
21.5;5. Concluding Remarks;207
21.6;References;208
22;Using ESB and BPEL for Evolving Healthcare Systems Towards Pervasive, Grid-Enabled SOA;210
22.1;1. Introduction;210
22.2;2. A System Evolution Process;211
22.3;3. Motivating Scenario;213
22.4;4. System Architecture;214
22.5;5. Security Framework;216
22.5.1;5.1 Access Control Mechanism;216
22.5.2;5.2 Context Information Management;217
22.6;6. Concluding Remarks;217
22.7;References;218
23;MISS: A Metamodel of Information System Service;219
23.1;1. Introduction;219
23.2;2. Information System Service;220
23.2.1;2.1 Static Space;221
23.2.2;2.2 Dynamic Space;222
23.2.3;2.3 Rule Space;223
23.3;3. Examples of ISS;223
23.4;4. Modularity and Autonomy of ISS;225
23.5;5. Positioning and Future Work;226
23.6;6. Conclusion;227
23.7;References;227
24;An Examination on Service Science: A View from e-Service;229
24.1;1. Introduction;229
24.2;2. A Structure for Service Science;231
24.2.1;2.1 Representative Concepts;232
24.2.2;2.2 Four Subtopics from the Four Parts;233
24.2.3;2.3 Interdependencies Among the Four Parts;233
24.3;3. Context of Service Science;234
24.3.1;3.1 Service Interoperability;234
24.3.2;3.2 Service Management and Quality Control;235
24.4;4. Conclusion;235
24.5;References;237
25;Mapping SOA Artefacts onto an Enterprise Reference Architecture Framework;238
25.1;1. Introduction;238
25.2;2. The Reference Framework;239
25.3;3. Mapping Typical SOA Artefacts on the Reference Framework;240
25.3.1;3.1 SOA Ontologies;240
25.3.2;3.2 SOA Metamodels;240
25.3.3;3.3 SOA Reference Models and Reference Architectures;241
25.3.4;3.4 SOA Modelling/Documentation Framework;241
25.3.5;3.5 SOA Life Cycle and Service Life Cycle;242
25.3.6;3.6 SOA Vision;243
25.3.7;3.7 SOA Governance;244
25.3.8;3.8 The SOA Team;244
25.3.9;3.9 SOA Methodologies;244
25.3.10;3.10 SOA Quality of Service and Quality Control;244
25.3.11;3.11 Enterprise Service Bus and Policies;245
25.4;4. Conclusions and Further Work;245
25.5;References;245
26;Comparing Architectural Styles for Service-Oriented Architectures - a REST vs. SOAP Case Study;247
26.1;1. Motivation and Outline;247
26.2;2. Case Study;248
26.3;3. SOAP-Style architecture;250
26.4;4. REST-Style Architecture;251
26.5;5. Evaluation and Outlook;254
26.6;Acknowledgments;255
26.7;References;255
27;A Method for Transforming Existing Web Service Descriptions into an Enhanced Semantic Web Service Framework;256
27.1;1. Introduction;256
27.2;2. Enhanced CbSSDF (CbSSDF+);257
27.3;3. Transformation Method;259
27.3.1;3.1 Step One: Ontology-Based Service Classification;259
27.3.2;3.2 Step Two: CUPs generation;260
27.3.3;3.3 Step Three: S-CGs Generation;260
27.3.4;3.4 An Illustrative Example;261
27.4;4. Evaluation;262
27.5;5. Conclusion;264
27.6;References;265
28;An Extensible ADL for Service-Oriented Architectures;266
28.1;1. Introduction;266
28.2;2. Meta Types;267
28.3;3. Interface Types;268
28.4;4. Connector Types;269
28.5;5. Component Types;270
28.6;6. Pattern Templates;273
28.7;7. Features;273
28.8;8. System;274
28.9;9. Discussion;275
28.10;References;275
29;Specification and Verification of an Agent-Based Auction Service;277
29.1;1. Introduction;277
29.2;2. Agent Negotiation Model;278
29.3;3. FSP Model of Agent Negotiation;280
29.3.1;3.1 Overview of the Modelling Approach;280
29.3.2;3.2 Auction Host;281
29.3.3;3.3 Auction Service Host;282
29.3.4;3.4 Buyer and Seller Roles;283
29.3.5;3.5 System with Buyers, Sellers and an Auction Service;283
29.4;4. Modelling System Properties;284
29.5;5. Conclusions and Future Work;285
29.6;References;285
30;A Practical Environment to Apply Model-Driven Web Engineering;287
30.1;1. Introduction;287
30.2;2. The Methodology;288
30.2.1;2.1 MÕtrica v3;288
30.2.2;2.2 NDT - Navigational Development Techniques;289
30.2.3;2.3 A Practical Combination Between MÕtrica v3 and NDT;290
30.3;3. Tool Support;291
30.3.1;3.1 NDT-Profile;291
30.3.2;3.2 CADI;292
30.4;4. The Practical Experience: The Diraya Project;293
30.5;5. Conclusions and Future Works;294
30.6;References;295
31;An Approach to Generating Program Code in Quickly Evolving Environments;297
31.1;1. Introduction;297
31.2;2. Related Works;298
31.3;3. Properties and Limitations of Standard Approach to Generating Program Code from Abstract Program Models;299
31.4;4. Analysis of Information Required to Configure Program Code Generator;300
31.5;5. Properties of Program Code Exploited by Program Code Generators;300
31.6;6. An Approach to Generating Program Code in Quickly Evolving Environments;301
31.7;7. A Method Proposal for the Structural Part of the Program Model;302
31.8;8. Conclusions and Future Work;303
31.9;References;304
32;Devising a New Model-Driven Framework for Developing GUI for Enterprise Applications;306
32.1;1. Introduction;306
32.2;2. Presentation Technologies;307
32.3;3. Diverse Presentation Technology Dilemma;310
32.4;4. Customizable Enterprise Data Administrator (CEDAR);310
32.4.1;4.1 CEDAR Development Technology;311
32.4.2;4.2 CEDAR Presentation Designer;311
32.4.3;4.3 CEDAR Data Storage;311
32.4.4;4.4 CEDAR Application Architecture;312
32.4.5;4.5 CEDAR Designer Essentials;312
32.4.6;4.6 Technology-Specific Generation;315
32.5;5. Conclusion and Future Work;315
32.6;References;315
33;Model-Driven Development of Decision Support Systems: Tackling the Variability Problem;317
33.1;1. Introduction;317
33.2;2. Variability;318
33.3;3. Variability Management in BOM;319
33.3.1;3.1 The First Variability in BOM;321
33.3.2;3.2 The Second Variability in BOM;321
33.4;4. Model Transformations in BOM;322
33.5;5. Conclusions and Future Work;323
33.6;References;323
34;Foundations on Generation of Relationships Between Classes Based on Initial Business Knowledge;325
34.1;1. Introduction;325
34.2;2. Aggregation;327
34.3;3. Dependency;329
34.4;4. Generalization;331
34.5;5. Conclusions;332
34.6;Acknowledgements;333
34.7;References;333
35;Expert Systems Development Through Software Product Lines Techniques;334
35.1;1. Introduction;334
35.2;2. Foundations;335
35.3;3. The Architecture of the Expert Systems;335
35.3.1;3.1 The Variability in the Architecture of the Expert Systems;336
35.3.1.1;3.1.1 Variability in the Expert Systems Structure;336
35.3.1.2;3.1.2 Variability in the Expert Systems Behavior;337
35.4;4. Variability Management in BOM;339
35.5;5. Expert Systems Development in BOM;340
35.6;6. Conclusions and Future Work;341
35.7;Acknowledgments;341
35.8;References;341
36;Framework for Using Patterns in Model-Driven Development;343
36.1;1. Introduction;343
36.2;2. Model-Driven Development Paradigm and Software Patterns Overview;343
36.2.1;2.1 Model-Driven Development Paradigm;343
36.2.2;2.2 Software Patterns;344
36.2.2.1;2.2.1 Definition and Characteristics of Patterns;344
36.2.2.2;2.2.2 Pattern Classification and Standardization;345
36.3;3. Conditions for Using Patterns in MDD;345
36.4;4. Framework Development;346
36.4.1;4.1 Pattern Identification;347
36.4.2;4.2 Pattern Development;348
36.4.3;4.3 Pattern Use;349
36.4.4;4.4 Pattern Management;350
36.5;5. Conclusions;350
36.6;References;351
37;Ontology of Domain Analysis Concepts in Software System Design Domain;352
37.1;1. Introduction;352
37.2;2. Domain Ontology Engineering: Concepts, Aims, and Definitios;353
37.3;3. Domain Concepts in Known DA Approaches;354
37.4;4. Domain Taxonomy and Ontology;356
37.5;5. Taxonomy of Domain Analysis Concepts;358
37.6;6. Conclusions and Further Work;359
37.7;References;359
38;An Anonymity Revocation Technology for Anonymous Communication;361
38.1;1. Introduction;361
38.2;2. Current Work in the Area of Anonymity Revocation Technologies;362
38.3;3. Principles of an Anonymity Revocation Technology;362
38.4;4. Requirements of an Anonymity Revocation Technology;363
38.5;5. Analysis of an Anonymity Revocation Technology;365
38.6;6. Analysis of the Existing ARTs Based on the Requirements;366
38.7;7. Discussion;367
38.8;8. Conclusion and Future Work;368
38.9;References;368
39;The Fight Against Piracy in Peer-to-Peer Networks: the Sword of Damocles Hanging over ISP’s Head?;370
39.1;1. Introduction;370
39.2;2. The Role of ISPs as Neutral Intermediaries Endangered?;371
39.2.1;2.1 Developments in European Member States;371
39.2.2;2.2 Developments on European Level;372
39.3;3. The Danger of Private Censorship;372
39.4;4. The Protection of the Secrecy of Communications;373
39.4.1;4.1 Looking for an Appropriate Legal Ground: An Analysis of Article 15(1) of the E-Privacy Directive;374
39.4.2;4.2 The Existence of a Pressing Social Need;374
39.4.3;4.3 The Principle of Proportionality;375
39.5;5. Conclusion;376
39.6;References;377
40;Information Technology Projects - Leaving the ‘Magic’ to the ‘Wizards’;379
40.1;1. In Search of the Magic Wand;379
40.2;2. A Cloak of Invisibility;381
40.3;3. Conclusions;384
40.4;References;385
41;Analysis of Academic Results for Informatics Course Improvement Using Association Rule Mining;387
41.1;1. Introduction;387
41.2;2. Principles of Association Rule Mining and Rule Metrics;388
41.3;3. Framework for Educational Data Mining Using Association Rules;389
41.4;4. Case Study: Mining Association Rules in ‘‘Object-Oriented Programming’’ Course;390
41.5;5. Conclusion and Future Work;392
41.6;References;392
42;The Automatic Integration of Folksonomies with Taxonomies Using Non-axiomatic Logic;394
42.1;1. Introduction;394
42.2;2. The Problem of Integration;395
42.3;3. An Approach to Tagging with Non-axiomatic Logic;396
42.4;4. Experiment;398
42.5;5. Evaluation;399
42.6;6. Conclusions;400
42.7;References;401
43;Using Rules in an ‘Intelligent’ Information Retrieval Environment;402
43.1;1. Introduction;402
43.2;2. A Rule System for ‘Intelligent’ Information Retrieval;404
43.2.1;2.1 Some Information about NKRL;404
43.2.2;2.2 General Principles about ‘Reasoning’ in NKRL;406
43.2.3;2.3 Some Additional Details;407
43.2.4;2.4 Integrating the Two Inference Modes of NKRL;408
43.3;3. Conclusion;409
43.4;References;410
44;Genetic Programming Modeling and Complexity Analysis of the Magnetoencephalogram of Epileptic Patients;411
44.1;1. Introduction;411
44.2;2. Genetic Programming;413
44.3;3. Results;414
44.4;4. Conclusions;418
44.5;References;418
45;A Three-Layer Approach to Testing of Multi-agent Systems;420
45.1;1. Introduction;420
45.1.1;1.1 Three-Layer Approach;421
45.2;2. First Layer - Unit Testing;421
45.2.1;2.1 Stochastic Approach;422
45.2.2;2.2 Agent’s Perception;423
45.3;3. Second Layer - Testing of Agent Interactions;423
45.4;4. Third Layer - Testing of the Whole System;425
45.4.1;4.1 System Bottlenecks;425
45.4.2;4.2 System Stability during Mass Crashes of Agents;425
45.5;5. Conclusions and Future Work;426
45.6;Acknowledgments;427
45.7;References;427
46;Risk Analysis Based Business Rule Enforcement for Intelligent Decision Support;429
46.1;1. Introduction;429
46.2;2. Related Works;430
46.3;3. A Method for Decision Automation Using Risk Analysis Based Business Rule Enforcement;432
46.4;4. Experimental Validation of the Method Using XForms;434
46.5;5. Conclusions;435
46.6;Acknowledgements;436
46.7;References;437
47;Sound Processing Features for Speaker-Dependent and Phrase-Independent Emotion Recognition in Berlin Database;438
47.1;1. Introduction;438
47.2;2. Basic Emotions;439
47.3;3. Sound/Speech Features;440
47.3.1;3.1 Sound Feature Selection;441
47.3.2;3.2 Calculation of Sound Features;442
47.4;4. Classification;443
47.4.1;4.1 Utterance-Dependent Emotion Recognition;443
47.4.2;4.2 Utterance-Independent Emotion Recognition;444
47.5;5. Conclusion and Future Work;444
47.6;References;445
48;An Approach for Implementation of Project Management Information Systems;447
48.1;1. Introduction;447
48.2;2. State of Art;448
48.2.1;2.1 Project Management Methodologies;448
48.2.2;2.2 Project Management Information System;449
48.2.3;2.3 Implementation of COTS Systems;449
48.3;3. Approach;449
48.4;4. Project Management Methodology Specification;450
48.5;5. Sample Application;453
48.6;6. Conclusion;455
48.7;Acknowledgments;455
48.8;References;455
49;From Standard Application Packages to Enterprise Systems - A Matter of Opportunities;456
49.1;1. Historical Review;456
49.2;2. Standard Application Packages;457
49.3;3. Enterprise Systems;457
49.4;4. Opportunities;458
49.4.1;4.1 Function Quality vs. Integration Quality;458
49.4.2;4.2 Customer-Driven Work vs. Vendor-Driven Work;459
49.4.3;4.3 Component View vs. Portfolio View;459
49.4.4;4.4 Expandability vs. Adaptability;460
49.4.5;4.5 Promoting System Concept vs. Controlling System Concept;460
49.5;5. The Connection;461
49.6;References;462
50;The Total Picture - A Framework for Control of IT Investments;464
50.1;1. Introduction;464
50.2;2. Research Method and Project Setting;465
50.3;3. Proposed Framework;466
50.3.1;3.1 The Project Level in the Framework;466
50.3.1.1;3.1.1 Different Types of Benefits;467
50.3.1.2;3.1.2 Principles of the Framework;467
50.3.2;3.2 The Total Picture Level in the Framework;468
50.3.2.1;3.2.1 The Total Picture - from a Cash Flow Perspective;468
50.4;4. Discussion: Applying a Lifetime Perspective and a Total Picture to Control IT Investments;469
50.5;5. Conclusions and Future Research;470
50.6;References;471
51;Design Patterns Application in the ERP Systems Improvements;473
51.1;1. Introduction;473
51.2;2. Review of Business Functionalities Analysis;474
51.3;3. Analysis of Ease of Maintenance and Design Patterns Usage;474
51.3.1;3.1 Analysis of Combined Results;475
51.3.1.1;3.1.1 Design Patterns Familiarity;476
51.4;4. Analysis of Existing Patterns in Dynamics AX;476
51.4.1;4.1 Strategy;476
51.4.1.1;4.1.1 Intent;476
51.4.1.2;4.1.2 Application in Dynamics AX;476
51.4.2;4.2 Iterator;477
51.4.2.1;4.2.1 Intent;477
51.4.2.2;4.2.2 Application in Dynamics AX;477
51.4.3;4.3 Template Method;478
51.4.3.1;4.3.1 Intent;478
51.4.3.2;4.3.2 Application in Dynamics AX;478
51.5;5. Improvement Possibilities for Dynamics AX Using Design Patterns;478
51.5.1;5.1 Software Metrics;478
51.5.2;5.2 Example in Dynamics AX;479
51.6;6. Conclusions;481
51.7;References;481
52;Determinants of Open Source Software Adoption - An Application of TOE Framework;482
52.1;1. Introduction;482
52.2;2. Research on IT Adoption and Implementation;483
52.3;3. Conceptual Model of Open Source Adoption;484
52.4;4. Research Method, Survey Design, and the Sample Description;485
52.5;5. Estimation of the TOE Model;487
52.6;6. Summary;489
52.7;References;489
53;Hybridization of Architectural Styles for Integrated Enterprise Information Systems;491
53.1;1. Introduction;491
53.2;2. Component-Based Integrated Enterprise Information System;492
53.3;3. Service-Oriented Architecture: Characteristics and Open Questions;493
53.4;4. Hybrid Architecture for Integrated Enterprise Information Systems;495
53.4.1;4.1 Components and Services as Architecture Level Concepts;495
53.4.2;4.2 Main Architectural Decisions to Build IEIS;495
53.4.3;4.3 Using SysML for IEIS Architectural Modeling;497
53.5;5. Concluding Remarks;498
53.6;References;498
54;Proposing a Formalised Model for Mindful Information Systems Offshoring;500
54.1;1. Introduction;500
54.2;2. Background and Motivation;501
54.2.1;2.1 Offshoring: The Case of Ireland and Germany;501
54.2.2;2.2 Literature Context;501
54.3;3. Research Framing;502
54.3.1;3.1 Theoretical Considerations;502
54.3.2;3.2 Research Approach;502
54.4;4. Towards a Mindful Offshoring Model;503
54.4.1;4.1 Mindless Offshoring Equation;503
54.4.2;4.2 Mindful Offshoring Equation;503
54.5;5. Analysis and Suggestions;504
54.5.1;5.1 Possible Endogenous Variables;504
54.5.2;5.2 Offshoring Coefficient;504
54.5.3;5.3 Elasticity Analysis of the Equation Parameters;505
54.6;6. Discussion;506
54.6.1;6.1 Assignment of Values to the Parameters;506
54.6.2;6.2 Implications for Theory and Practice;506
54.6.3;6.3 Limitations and Suggestions for Future Work;506
54.7;7. Conclusions;507
54.8;References;507
55;Negotiating a Systems Development Method;509
55.1;1. Introduction;509
55.2;2. Research Design;510
55.2.1;2.1 Theoretical Underpinnings;510
55.2.2;2.2 Case Description and Data Collection;511
55.3;3. The Negotiating Process of Method Tailoring;512
55.3.1;3.1 Negotiation 1 - Basic Principles;512
55.3.2;3.2 Negotiation 2 - Storyboards;513
55.3.3;3.3 Negotiation 3 - Bug Report Template;513
55.3.4;3.4 Negotiation 4 - Standardization of Web Page Template Documentation;515
55.4;4. Reflections on Method Tailoring as Negotiation;515
55.5;5. Conclusion;516
55.6;References;516
56;A Hybrid Peer-to-Peer Solution for Context Distribution in Mobile and Ubiquitous Environments;518
56.1;1. Introduction;518
56.2;2. A Hybrid Peer-to-Peer Based Context Distribution System;519
56.2.1;2.1 A Hybrid Peer-to-Peer Infrastructure for Context Distribution;520
56.2.2;2.2 Context Network and Distribution Service;521
56.2.3;2.3 Scope of Context Distribution;522
56.3;3. Comparison with Related Work;523
56.4;4. Evaluation;524
56.5;5. Conclusions;526
56.6;References;526
57;Rules Transformation Using Formal Concept Approach;528
57.1;1. Introduction;528
57.2;2. Related Works;529
57.3;3. Understanding of Formal Concept Analysis;529
57.4;4. Process of Rule Transformation;530
57.5;5. Storage of Formal Concepts in Formal Context and Experiment Overview;533
57.6;6. Discussions;534
57.7;7. Conclusions;535
57.8;Acknowledgements;535
57.9;References;535
58;Agreements in Virtual Organizations;536
58.1;1. Virtualization;536
58.2;2. Virtual Organizations and Their Development;537
58.3;3. Virtual Organizations’ Management Problems;539
58.4;4. Virtual Organization’s Evaluation by Contracts and Agreements;540
58.5;5. Conclusions;542
58.6;References;542
59;Applying Utility Functions to Adaptation Planning for Home Automation Applications;545
59.1;1. Introduction;545
59.2;2. Motivating Scenario;546
59.3;3. System overview;547
59.3.1;3.1 Device and Service Discovery;547
59.3.2;3.2 Configuration Plans;548
59.3.3;3.3 User Preferences;549
59.3.4;3.4 Utility Functions;549
59.4;4. Evaluation;550
59.4.1;4.1 Case Study Example;550
59.5;5. Related Work;551
59.6;6. Conclusions;552
59.7;Acknowledgments;552
59.8;References;552
60;Current Trends in Testing XMLMSs;554
60.1;1. Introduction;554
60.2;2. Overview of Existing Approaches;555
60.2.1;2.1 XML Data Sets;555
60.2.2;2.2 XML Data Generators;555
60.2.3;2.3 Parsing and Validating XML Data;556
60.2.3.1;2.3.1 XML Conformance Test Suites;556
60.2.3.2;2.3.2 XML Parsers;556
60.2.4;2.4 Querying XML Data;557
60.2.4.1;2.4.1 Analysis of Benchmarking Projects;559
60.2.4.2;2.4.2 Benchmark Repository;559
60.2.5;2.5 Transforming, Updating and Other Operations with XML Data;559
60.3;3. Summary;560
60.4;4. Conclusion;561
60.5;Acknowledgments;561
60.6;References;561
61;Service-Oriented Software Development Value Chain and Process;563
61.1;1. Introduction;563
61.2;2. Service-Oriented Reusable Software Development Process;564
61.3;3. Value Chain Model of Service-Oriented Software Process;565
61.3.1;3.1 Meta-Model of Value Chain;565
61.3.2;3.2 Value Chain-Based Software Development Process;565
61.3.3;3.3 The Establishment of SDVC Based on Different Processes;566
61.4;4. Value Chain Analysis of Software Development Process;569
61.5;5. Related Work;571
61.6;6. Conclusion;571
61.7;Acknowledgments;572
61.8;References;572
62;A Content Markup Language for Data Services;573
62.1;1. Introduction;573
62.2;2. Octapy3 a Distributed and Cooperative Content Management System;574
62.3;3. OCML Specification;577
62.4;4. The Museo Virtuale Test Bed;580
62.5;5. Conclusions;581
62.6;References;581
63;Organizational Learning Literature Visited - Fresh Lenses to Study Practices in ISD Organizations?;582
63.1;1. Introduction;582
63.2;2. Organizational Learning Literature;583
63.2.1;2.1 Concepts and Terminology;583
63.2.2;2.2 Literature in IS Discipline;583
63.2.3;2.3 Literature in Other Disciplines;584
63.2.4;2.4 Classification of Organizational Learning Literature;584
63.3;3. Research Process and Revisited Empirical Data;584
63.4;4. Observations on Empirical Data;586
63.5;5. Discussion;587
63.6;6. Summary and Future Work;588
63.7;References;589
64;Contract Negotiations Supported Through Risk Analysis;591
64.1;1. Introduction;591
64.2;2. Risk Management;592
64.3;3. The Negotiation Process;594
64.4;4. IT Contract Negotiation;595
64.5;5. Case Study and Results;596
64.5.1;5.1 Negotiation Context;596
64.5.2;5.2 Using RisNeg in the Negotiation;596
64.5.3;5.3 Results;598
64.6;6. Conclusions;598
64.7;References;599
65;Instantiating Software Processes: An Industry Approach;600
65.1;1. Introduction;600
65.2;2. Related Work;601
65.3;3. The Siemens Software Processes;602
65.4;4. Standardized and Semi-automated Instantiation of Processes;604
65.4.1;4.1 Implementation of the Approach;605
65.4.2;4.2 Use Case ‘‘Inserting a Milestone’’;606
65.4.3;4.3 Evaluation of the Approach;607
65.5;5. Conclusion;608
65.6;References;608
66;A Language for Modelling Trust in Information Systems;609
66.1;1. Introduction;609
66.2;2. Related Work;610
66.3;3. A Modelling Language for Trust;611
66.3.1;3.1 Modelling Language Concepts;611
66.3.2;3.2 Links/Associations;613
66.3.3;3.3 Modelling Language Graphical Notation;613
66.4;4. Case Study;616
66.5;5. Conclusions and Future Work;617
66.6;Acknowledgements;617
66.7;References;617
67;Modeling the Contribution of Enterprise Architecture Practice to the Achievement of Business Goals;619
67.1;1. Effectiveness of Enterprise Architecture;619
67.2;2. The Architecture Effectiveness Model;620
67.3;3. Three Applications of the AEM Concept;622
67.3.1;3.1 Case 1: A Municipality;622
67.3.2;3.2 Case 2: A University of Professional Education;623
67.3.3;3.3 Case 3: A Financial Institution;624
67.4;4. Discussion;625
67.5;5. Evaluation and Conclusions;626
67.6;Acknowledgment;627
67.7;References;627
68;Organizational Culture and ISD Practices: Comparative Literature Review;629
68.1;1. Introduction;629
68.2;2. Community of Practice and Organizational Culture;630
68.3;3. Overview of Three Communities of Practice;630
68.4;4. Comparative Analysis;631
68.4.1;4.1 Analytic Framework for Comparisons;631
68.4.2;4.2 Business Milieu;631
68.4.3;4.3 Team Efforts;632
68.4.4;4.4 Software Development Approaches;633
68.4.5;4.5 Products and Quality;633
68.5;5. Discussion;634
68.6;6. Conclusions;635
68.7;References;635
69;Metadata to Support Data Warehouse Evolution;637
69.1;1. Introduction;637
69.2;2. Related Work;637
69.3;3. Data Warehouse Evolution Framework;638
69.4;4. Data Warehouse Metadata;638
69.4.1;4.1 Logical Metadata;639
69.4.2;4.2 Physical Metadata;640
69.5;5. Evolution Support;640
69.5.1;5.1 Physical Changes;641
69.5.2;5.2 Logical Changes;642
69.6;6. Conclusions and Future Work;644
69.7;Acknowledgments;644
69.8;References;644
70;The Morning After: What Happens When Outsourcing Relationships End?;646
70.1;1. Introduction;646
70.2;2. Reported Findings on Sourcing Decisions;648
70.2.1;2.1 Related Research;648
70.3;3. Proposed Model;649
70.4;4. Model Applied to Case Study;651
70.5;5. Conclusion and Future Work;652
70.6;References;652
71;Method Engineering: A Formal Description;654
71.1;1. Introduction;654
71.2;2. Research Approach;655
71.3;3. Description of the Method Elements;655
71.3.1;3.1 Method Chains and Alliances;656
71.3.2;3.2 Method Fragments;656
71.3.3;3.3 Method Chunks;657
71.3.4;3.4 Method Components;657
71.4;4. Formal Description of the Concept of Method;657
71.4.1;4.1 Annotation;657
71.5;5. Application of the Formal Description;659
71.6;6. Summary and Outlook;662
71.7;References;663
72;A Methodological Framework for Enterprise Information System Requirements Derivation;664
72.1;1. Introduction;664
72.2;2. Related Works;665
72.3;3. The Proposed Methodological Framework;666
72.4;4. Conclusions;672
72.5;References;672
73;Measuring Communication Heterogeneity Between Multiple Web-Based Agents;673
73.1;1. Introduction;673
73.2;2. Related Works;674
73.3;3. Measuring Heterogeneity;674
73.4;4. Case Studies;676
73.4.1;4.1 Case One. Measuring Communication Heterogeneity with Three Agents;676
73.4.2;4.2 Case Two. Measuring Communication Heterogeneity with Eight Agents;677
73.5;5. Evaluation of Results;679
73.6;6. Conclusions;680
73.7;References;681
74;Requirements Modeling with Agent Programming;682
74.1;1. Introduction;682
74.2;2. Background;683
74.2.1;2.1 The i* Framework;683
74.2.2;2.2 CASO;683
74.3;3. Modeling Softgoals as Preferences in i*;684
74.4;4. A Methodology for Combined Use of the i* and CASO Frameworks;685
74.5;5. Case Study: Meeting Scheduling Process;686
74.5.1;5.1 Building i* Models for Meeting Scheduler;686
74.5.2;5.2 Developing the Initial CASO Model;686
74.5.3;5.3 Validating and Refining the CASO Model by Simulation;688
74.5.4;5.4 Refining i* and CASO Models Based on Validation Results;689
74.6;6. Conclusion;689
74.7;References;689
75;BPMN, Toolsets, and Methodology: A Case Study of Business Process Management in Higher Education;691
75.1;1. Introduction;691
75.2;2. Motivation for This Chapter;692
75.3;3. Background and Related Work;692
75.4;4. Approach Taken;694
75.5;5. Case Study;694
75.5.1;5.1 Experimentation with UML Activity Diagrams and BPEL;695
75.6;6. Results and Evaluation;696
75.7;7. Conclusion;698
75.8;Acknowledgements;699
75.9;References;699
76;Incorporating Spatial Data into Enterprise Applications;700
76.1;1. Introduction;700
76.2;2. Spatial Data Usage in Enterprise Applications;701
76.3;3. Spatial Data Support in Commercial Relational Database Management Systems;701
76.4;4. The Open Geospatial Consortium (OGC);702
76.5;5. Spatial Data Visualization in Enterprise Applications;703
76.6;6. Spatial Extensions (SPEX);704
76.6.1;6.1 SPEX Development Technology;704
76.6.2;6.2 SPEX Visual Components;704
76.6.3;6.3 SPEX Vague Spatial Data Support;706
76.7;7. Conclusion;708
76.8;References;709
77;The Development of Mobile Services - The Impact of Actor Groups in the Standardization Process;710
77.1;1. Introduction;710
77.2;2. A Framework for Showing Standardization Involvement;711
77.3;3. Our Framework and Research Methods;712
77.4;4. Findings - Presentation of the Data;714
77.4.1;4.1 Technological Strength - The Number of Essential IPR;714
77.4.2;4.2 The Depth Metric - Number of Chairs and Editors;714
77.4.3;4.3 The Openness Metric - Number of Proposals Supported;715
77.4.4;4.4 The Efficiency Metric - Two Cases;715
77.4.4.1;4.4.1 Mobile E-mail;715
77.4.4.2;4.4.2 Push to Talk Over Cellular (POC);716
77.4.5;4.5 Summary of Our Metrics;716
77.5;5. General Observation and Discussion;717
77.6;6. Conclusion;718
77.7;References;718
78;Reducing Health Cost: Health Informatics and Knowledge Management as a Business and Communication Tool;719
78.1;1. Introduction;719
78.1.1;1.1 Research Approach;720
78.1.2;1.2 Knowledge Management in the Medical Health Informatics Service of Business;720
78.2;2. Health Informatics and Evidence-Based Medicine;720
78.3;3. The Role of Health Informatics in Knowledge Management Environment;721
78.4;4. Cutting Health Service Costs;722
78.5;5. Information Technology and Information System Use;723
78.5.1;5.1 Strategy;723
78.5.2;5.2 Using Technology;723
78.5.3;5.3 Knowledge Management Culture;723
78.5.4;5.4 Management;723
78.5.5;5.5 Processes;723
78.5.6;5.6 Ongoing Maintenance and Protection;723
78.6;6. Recommendation;724
78.7;7. Summary and Further Research;724
78.8;References;725
79;The Information Architecture of E-Commerce: An Experimental Study on User Performance and Preference;727
79.1;1. Introduction;727
79.2;2. Research Framework;728
79.2.1;2.1 Conceptual Model;728
79.2.2;2.2 Research Questions;729
79.3;3. Research Method;730
79.3.1;3.1 Subjects;730
79.3.2;3.2 Experimental Web sites;730
79.3.3;3.3 Experimental Design and Procedure;731
79.4;4. Research Framework;732
79.4.1;4.1 Experimental Result;732
79.4.2;4.2 Post-Study Result;733
79.5;5. Conclusions;734
79.6;References;734
80;Computer Literacy of Population 50+ - A Case from Slovenia;736
80.1;1. Introduction;736
80.2;2. The CLP Project and the PIG Project;736
80.2.1;2.1 The CLP Project;736
80.2.2;2.2 The PIG Project;738
80.3;3. Conclusions;739
80.4;References;739
81;A Taxonomy of E-Health Standards to Assist System Developers;740
81.1;1. Introduction;740
81.2;2. Background and Evolution of E-Health Standardization;741
81.2.1;2.1 Principal Standards and Stakeholders;741
81.2.2;2.2 E-Health Standardization Problems;742
81.2.3;2.3 Software Development Standards in E-Health;743
81.2.4;2.4 E-Health Standards’ Main Categories;743
81.3;3. The Taxonomy;744
81.3.1;3.1 Taxonomy Domains;744
81.4;4. E-Health Standards Classification;745
81.5;5. Conclusions;745
81.6;References;747
82;Mobile Location-Based Services for Trusted Information in Disaster Management;749
82.1;1. Introduction;749
82.2;2. System Architecture;750
82.3;3. System Security;752
82.4;4. Trust in the System;753
82.5;5. Implemented Prototype;753
82.6;6. Conclusions;754
82.7;Acknowledgments;755
82.8;References;755
83;Resolution of Complexity in ISD Projects;756
83.1;1. Introduction;756
83.2;2. Complexity in ISD Projects;757
83.3;3. A Theoretical Framework for ISD Complexity;757
83.4;4. Research Approach;758
83.5;5. Case Study - Rollout of an Enterprise Project Management Software in a Government Department;759
83.5.1;5.1 Department XYZ;759
83.5.2;5.2 The Third Party - Primavera Australia;760
83.5.3;5.3 The Project;760
83.6;6. Discussion;761
83.6.1;6.1 Addressing Complexity;762
83.7;7. Conclusion;763
83.8;References;763
84;Business Architecture Development at Public Administration - Insights from Government EA Method Engineering Project in Finland;765
84.1;1. Introduction;765
84.2;2. CASE: The GEA Method Engineering Project;766
84.3;3. Research Method;768
84.4;4. Results;768
84.4.1;4.1 E-Government Business Models;768
84.4.2;4.2 Customer-Driven Development;769
84.4.3;4.3 Business Process Modeling;770
84.5;5. Implications;771
84.6;6. Conclusion;772
84.7;Acknowledgments;773
84.8;References;773
85;A Standardization Framework for Electronic Government Service Portals;775
85.1;1. Introduction;775
85.2;2. The Driving Force;776
85.3;3. State of the Art;777
85.4;4. The Greek Standardization Framework;778
85.5;5. Application of the Standardization Framework;780
85.5.1;5.1 The Case of Civil Personnel Selection Portal;780
85.5.2;5.2 The Case of Fireservice Portal;781
85.6;6. Conclusions;782
85.7;References;783
86;Elaborating the WARE Method for eParticipation Requirements;785
86.1;1. Introduction;785
86.2;2. eParticipation;786
86.3;3. Wide Audience Requirement Engineering (WARE);786
86.4;4. Implementing the WARE Method in an eParticipation Project;787
86.5;5. Developing Requirement Design Interface to Support ‘‘Ongoing Activities’’;789
86.6;6. Discussion;791
86.6.1;6.1 Suggested Improvements to the WARE Method;791
86.7;7. Conclusion;792
86.8;References;792
87;Web Tools for Geospatial Data Management;793
87.1;1. Introduction;793
87.2;2. Objectives;794
87.3;3. Methodology;794
87.4;4. Technology Description;795
87.5;5. Developments and Results;796
87.5.1;5.1 Generation of Map Compositions;796
87.5.2;5.2 Example of composition;797
87.5.3;5.3 Integration with Other Web Tools;798
87.5.4;5.4 Examples of Other Tools Integrated into URM Portals;798
87.5.4.1;5.4.1 Metadata Extractor;798
87.5.4.2;5.4.2 Moodle;798
87.5.4.3;5.4.3 Video Lecture;799
87.6;6. Business Benefits;799
87.7;7. Conclusions;799
87.8;References;800
88;Exploring the Role of Method Rationale in the Context of Teaching Information Systems Development Methods;801
88.1;1. Introduction;801
88.2;2. Theoretical Framework;802
88.2.1;2.1 Method rationale;802
88.2.2;2.2 Method Components;803
88.2.2.1;2.2.1 The Internal View;803
88.2.2.2;2.2.2 The External View;803
88.3;3. Research Approach;804
88.4;4. Lectures;804
88.4.1;4.1 G1 Lectures;805
88.4.2;4.2 G2 Lectures;805
88.5;5. Modelling Seminars;805
88.5.1;5.1 G1 Modelling Seminar;806
88.5.2;5.2 G2 Modelling Seminar;806
88.6;6. Interviews;806
88.6.1;6.1 G1 Interviews;807
88.6.2;6.2 G2 Interviews;807
88.7;7. Concluding Discussion;807
88.8;References;808
89;Four Levels of Moral Conflict in ISD;810
89.1;1. Introduction;810
89.2;2. Information Systems Development;811
89.3;3. Four Levels of Moral Conflict in ISD;811
89.3.1;3.1 Intentional Level;812
89.3.2;3.2 Functional Level;812
89.3.3;3.3 Managerial Level;813
89.3.4;3.4 Societal Level;814
89.4;4. Theories Describing the Internal Structure of Moral Conflicts;815
89.4.1;4.1 A Philosophical Theory;815
89.4.2;4.2 Three Normative Theories of Business Ethics;815
89.4.3;4.3 An Exemplary Application of the Theories;816
89.5;5. Discussion;816
89.6;References;817
90;Specification of Learning Content Using Feature Diagrams;819
90.1;1. Introduction;819
90.2;2. Use of Graphical Modeling Languages in Educational Domain;820
90.3;3. Features, Feature Modeling, and Feature Diagram;821
90.4;4. Motivation of Using Feature Diagrams for LO Domain;822
90.5;5. Capabilities and Limitations of Feature Diagrams in Learning Object Domain;823
90.6;6. Case Study: A Learning Object for Teaching Shift Registers;824
90.7;7. Conclusions;826
90.8;References;826
91;Understanding Service-Oriented Architectures in the Classroom: From Web Services to Grid Services;828
91.1;1. Introduction;828
91.2;2. SOA Education;829
91.2.1;2.1 Importance of SOA Education;829
91.2.2;2.2 Requirements of SOA Education;829
91.2.3;2.3 Initiatives for SOA Education;830
91.2.4;2.4 Comments on the Current Content of SOA Education;830
91.3;3. Web Service Education;832
91.3.1;3.1 Importance of Web Services for SOA Education;832
91.3.2;3.2 Initiatives for Web Service Education;832
91.3.3;3.3 Comments on the Current Content of Web Service Education;833
91.4;4. Grid Services in the Context of SOA Education;833
91.5;5. Conclusions;835
91.6;Acknowledgments;835
91.7;References;835
92;Refactoring of Learning Objects for Mobile Learning;836
92.1;1. Introduction;836
92.2;2. Technological and Educational Issues in m-Learning;837
92.2.1;2.1 Technological Constraints of Mobiles;837
92.2.2;2.2 Educational Issues in Using Mobile Devices;838
92.3;3. Refactoring of Learning Objects;838
92.3.1;3.1 Concept of Refactoring in Software Engineering;838
92.3.2;3.2 Learning Content Refactoring Techniques;839
92.3.3;3.3 Framework of LO Refactoring;839
92.4;4. Case Study;841
92.4.1;4.1 Original Learning Object;841
92.4.2;4.2 Refactoring of a LO to a Mobile Device;841
92.5;5. Open Research Issues in LO Refactoring;842
92.6;6. Conclusion and Future Work;843
92.7;References;843
93;Early Orientation Toward Future Profession: A Case Study of Introduction into Information Systems Development for the First-Year Students;845
93.1;1. Introduction;845
93.2;2. Context;846
93.3;3. Previous Experience;847
93.4;4. Conception;848
93.5;5. Implementation of the Conception;850
93.6;6. Evaluation Results;852
93.7;7. Conclusions;854
93.8;References;854
94;Embedding Knowledge Management into Business Logic of E-learning Platform for Obtaining Adaptivity;855
94.1;1. Introduction;855
94.2;2. Methods and Materials;856
94.2.1;2.1 Tesys e-Learning Platform;856
94.2.2;2.2 Concept Maps;857
94.2.3;2.3 Data Filtering;857
94.2.4;2.4 Obtaining Recommendations;858
94.3;3. Analysis Process and Experiments;858
94.4;4. Conclusions and Future Works;860
94.5;References;860
95;Problem-Based Learning in a Programming Context- Planning and Executing a Pilot Survey on Database Access in a Programming Language;862
95.1;1. Introduction;862
95.2;2. The PBL Pilot Survey;863
95.2.1;2.1 History and Related Work;863
95.2.2;2.2 Planning the PBL Pilot Survey;864
95.2.3;2.3 Executing the PBL Pilot Survey;866
95.2.4;2.4 Follow-Up and Evaluation of the PBL Pilot Survey;866
95.3;3. Perspectives on the PBL Pilot Survey;867
95.3.1;3.1 The Tutor Perspective;867
95.3.2;3.2 The Student Perspective;868
95.3.3;3.3 Collected Data;868
95.4;4. Analyses and Discussion;868
95.5;5. Summary and Conclusion;869
95.6;References;869
96;‘‘Learning to Research’’ in a Virtual Learning Environment: A Case Study on the Effectiveness of a Socio-constructivist Learning Design;871
96.1;1. Introduction;871
96.1.1;1.1 The Research Question;872
96.2;2. The Socio-constructivist Learning Model;872
96.3;3. Design and Implementation of the VLE;873
96.4;4. Experiments: Methodology and Results;875
96.4.1;4.1 Methodology and Procedure;875
96.4.2;4.2 Analysis of Results;876
96.5;5. Discussion and Conclusions;876
96.6;Acknowledgements;877
96.7;References;877
97;IS Degrees - Sociotechnical or Technosocial?;879
97.1;1. Introduction;879
97.2;2. Some Key Existing Proposals;880
97.3;3. What Is Different in Our Approach;881
97.4;4. A ‘‘Technosocial’’ IS Curriculum;882
97.5;5. Conclusions and Further Work;883
97.6;Acknowledgements;883
97.7;References;884
98;Teaching Medium-Sized ERP Systems - A Problem-Based Learning Approach;885
98.1;1. Introduction;885
98.2;2. Procedure Model and Description of the Course;886
98.2.1;2.1 [Step 1] Selection of Evaluation Area and Framework;887
98.2.2;2.2 [Step 2] Market Overview;888
98.2.3;2.3 [Step 3a] Identification of Appropriate ERP Manufacturers;888
98.2.4;2.4 [Step 3b] Preparation of Scenario, Evaluation Objectives, and Literature;888
98.2.5;2.5 [Step 4] ERP Evaluations;889
98.2.6;2.6 [Step 5] ERP Presentations;889
98.3;3. System Evaluations and Presentations;890
98.3.1;3.1 General Comparison;890
98.3.2;3.2 Functional Comparison;890
98.3.3;3.3 Technical Comparison;891
98.4;4. Course Evaluation;893
98.4.1;4.1 Students’ Perspective;893
98.4.2;4.2 Manufacturers’ Perspective;894
98.4.3;4.3 Lecturer’s Perspective;894
98.5;References;894
99;Statistical Analysis for Supporting Inter-Institutional Knowledge Flows in the Context of Educational System;896
99.1;1. Introduction;896
99.2;2. Inter-Institutional Model for Education System in Latvia;897
99.3;3. Data Type for supporting Statistical Analysis;898
99.4;4. Data-Gathering Procedure;900
99.5;5. Statistical Methods Overview for Supporting Inter-Institutional Knowledge Flows;900
99.6;6. Statistical Data Application;902
99.6.1;6.1 Forecast Data About First-Year Students’ Knowledge Level and Scope in IT Field;902
99.6.2;6.2 The Forecast and Real Data to Support Knowledge Flows;904
99.7;7. Conclusions and Future Work;904
99.8;Acknowledgments;904
99.9;References;905
100;Using Agile Methods? - Expected Effects;906
100.1;1. Introduction;906
100.2;2. Research Approach;907
100.3;3. Findings;908
100.3.1;3.1 Expected Effects of Traditional Methods;908
100.3.2;3.2 Expected Effects of Agile Methods;909
100.3.3;3.3 Comparison of Effects;910
100.3.3.1;3.3.1 Added Effects;910
100.3.3.2;3.3.2 Lost Effects;911
100.3.3.3;3.3.3 Preserved Effects;911
100.4;4. Conclusions;911
100.5;References;912
101;Finding Categories and Keywords in Web Services;915
101.1;1. Introduction;915
101.2;2. Related Work;916
101.3;3. Existing Web Service Languages;917
101.4;4. Ordinary Documents Versus Web Service Specifications;917
101.4.1;4.1 Structure;917
101.4.2;4.2 Domain;918
101.4.3;4.3 Users;918
101.5;5. Categories and Keywords Derived from Web Services;918
101.5.1;5.1 Useful Tag Information Derived from OWL-S Documents;919
101.5.2;5.2 Information Derived from WSDL Specifications;921
101.6;6. Categories, Keywords, and Types of Users;921
101.7;7. Conclusion and Future Work;922
101.8;References;923
102;MEDNET: Telemedicine via Satellite Combining Improved Access to Health-Care Services with Enhanced Social Cohesion in Rural Peru;924
102.1;1. Introduction: Clinical and Technical Requirements;924
102.1.1;1.1 Medical Situation;925
102.1.2;1.2 Doctors Needs;925
102.1.3;1.3 Health-Care Infrastructure Needs;926
102.2;2. Architecture and Major Components of the System;926
102.2.1;2.1 TeleConsult;926
102.2.2;2.2 Medical Database/Health-Care Records;927
102.2.3;2.3 Satellite Communication/AmerHis;928
102.3;3. Community Engagement;929
102.4;4. Expected Impacts;929
102.5;5. Conclusions - Future Work;930
102.6;Acknowledgement;931
102.7;References;931
103;Why Can’t We Bet on ISD Outcomes: ISD ‘‘Form’’ as a Predictor of Success;932
103.1;1. Introduction;932
103.1.1;1.1 Football as an Allegory for ISD;933
103.1.2;1.2 Historical Context - ‘‘Form’’ or Antecedent Conditions;934
103.2;2. Case 1: Telecoms Corp;935
103.3;3. Case 2: US Insurance Corporation;936
103.4;4. Lessons and Practical Implications;936
103.5;References;938
104;Index;939
