http://dl.gi.de/handle/20.500.12116/23211 2026-07-23T06:20:45Z http://dl.gi.de/handle/20.500.12116/23220 An environment for modeling workflow components Atkinson, Colin; Stoll, Dietmar Heinzl, Armin; Dadam, Peter; Kirn, Stefan; Lockemann, Peter An important goal of workflow engines is to simplify the way in which the interaction of workflows and software components (or services) is described and implemented. The vision of the AristaFlow project is to support a 'plug and play' approach in which workflow designers can describe interactions with components simply by 'dragging' them from a repository and 'dropping' them into appropriate points of a new workflow. However, to support such an approach in a practical and dependable way it is necessary to have semantically rich descriptions of components (or services) which can be used to perform automated compatibility checks and can be easily understood by human workflow designers. This, in turn, requires a modeling environment which supports multiple views on components and allows these to be easily generated and navigated around. In this paper we describe the Integrated Development Environment (IDE) developed in the AristaFlow project to support these requirements. After outlining the characteristics of the 'plug and play' workflow development model, the paper describes one of the main innovations within the IDE -the multi-dimensional navigation over views. 2009-01-01T00:00:00Z http://dl.gi.de/handle/20.500.12116/23222 On the role of communication, documentation and experience during testing - an exploratory study Illes-Seifert, Timea; Paech, Barbara Heinzl, Armin; Dadam, Peter; Kirn, Stefan; Lockemann, Peter Nowadays, the quality of software is becoming more and more a competitive factor. As complete testing is impossible, testers have to make decisions, e.g. to choose which parts of the software have to be tested in which way. For this purpose, testers need a lot of information, such as input documentation which serves as a basis for the derivation of test cases or information on the project status which serves as a basis for planning the testing process. Thus, testers rely on up-todate and complete information in order to make sound decisions. Consequently, the quality of the testing process depends on the quality of the information sources available for the testers. This paper presents the results of an exploratory study conducted during the SIKOSA research project with expert testers of our industry partners in order to identify the most valuable sources of information during testing. Particularly, we conducted interviews in order to investigate which documents are often used by testers, as well as the role of communication and experience. Our results show that defect reports are very valuable. User manuals and problem reports are equally important, because they represent real usage of the software and serve testers as an input for realistic test cases. In addition, our results show the influence of an independent testing team on test process characteristics. 2009-01-01T00:00:00Z http://dl.gi.de/handle/20.500.12116/23223 New applications for wikis in software engineering Geisser, Michael; Happel, Hans-Jörg; Hildenbrand, Tobias; Korthaus, Axel; Seedorf, Stefan Heinzl, Armin; Dadam, Peter; Kirn, Stefan; Lockemann, Peter Within software development, wikis are currently mainly used for brainstorming and documentation purposes or error management and project coordination. This article describes four advanced application scenarios for wiki support in software development processes: Requirements Engineering, Traceability and Rationale Management, Architectural Knowledge Sharing, and Lessons Learned Management in a distributed knowledge infrastructure. Finally, we will give a conclusion by summarizing the main advantages and drawbacks of the presented innovative uses of wikis in software engineering. 2009-01-01T00:00:00Z http://dl.gi.de/handle/20.500.12116/23217 Extended privacy definition tool Kähmer, Martin; Gilliot, Maike Heinzl, Armin; Dadam, Peter; Kirn, Stefan; Lockemann, Peter Eliciting non-functional security requirements within a company was one of the major aspects of the SIKOSA project1. Scenarios, such as that of METRO presented in this paper, show how besides a company's internal requirements, customers' preferences also play an important role. However, conflicts between specific customers' privacy policies and those of a company need to be detected and dealt with. To this end we present a policy language that is able to tackle this comparison problem and two tools: An editor tool allowing users to specify their policies in a user-friendly way and a monitoring tool to evaluate und enforce the policies at runtime. 2009-01-01T00:00:00Z