P151 - PRIMIUM - Process Innovation for Enterprise Software
Autor*innen mit den meisten Dokumenten
Auflistung nach:
Neueste Veröffentlichungen
- KonferenzbeitragExtended privacy definition tool(PRIMIUM - Process Innovation for Enterprise Software, 2009) Kähmer, Martin; Gilliot, MaikeEliciting 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.
- KonferenzbeitragOn the role of communication, documentation and experience during testing - an exploratory study(PRIMIUM - Process Innovation for Enterprise Software, 2009) Illes-Seifert, Timea; Paech, BarbaraNowadays, 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.
- KonferenzbeitragArchitectural principles and components of adaptive process management technology(PRIMIUM - Process Innovation for Enterprise Software, 2009) Reichert, Manfred; Dadam, Peter; Rinderle-Ma, Stefanie; Jurisch, Martin; Kreher, Ulrich; Göser, KevinProcess-aware information systems (PAIS) must not freeze business processes, but should enable authorized users to deviate from the implemented workflows on-the-fly and to dynamically evolve them over time. While there has been a lot of work on the theoretical foundations of dynamic process changes, there is still a lack of implemented PAIS providing this dynamics. Designing the architecture of such adaptive PAIS, however, constitutes a big challenge due to the high complexity coming with dynamic changes. Besides this, performance, robustness, security and usability of the PAIS must not be affected by the added flexibility. In the AristaFlow project we follow a holistic approach to master this complexity. Based on a conceptual framework for adaptive process management, we have designed a sophisticated architecture for next generation process management technology. This paper discusses major design goals and basic architectural principles, gives insights into selected system components, and shows how change support features can be realized in an integrated and efficient manner.
- KonferenzbeitragAlignment of software specifications with quality- and business goals in the SIKOSA method(PRIMIUM - Process Innovation for Enterprise Software, 2009) Herrmann, Andrea; Weiß, DanielBusiness-IT alignment for software specifications means that the specifications have to be aligned with business goals. In the SIKOSA research project, we developed the SIKOSA method which supports the integrated assurance of quality during the whole software development process. In this work, we present these aspects of the SIKOSA method, which especially align specification decisions to quality goals and thus indirectly to business goals. Such goals play a role in the following activities: the derivation of software requirements from quality goals, the prioritization of these software requirements, and the definition of decision criteria for architectural design decisions. The results of all three activities influence architectural decisions.
- KonferenzbeitragAn environment for modeling workflow components(PRIMIUM - Process Innovation for Enterprise Software, 2009) Atkinson, Colin; Stoll, DietmarAn 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.
- KonferenzbeitragOntology-enabled documentation of service-oriented architectures with ontobrowse semantic wiki(PRIMIUM - Process Innovation for Enterprise Software, 2009) Happel, Hans-Jörg; Seedorf, Stefan; Schader, MartinDocumenting and maintaining an enterprise-wide service-oriented architecture (SOA) causes a substantial management effort, which should be addressed by intelligent, scalable solutions. A particular challenge is that business experts, developers, and software architects take different perspectives on a SOA, each favoring various description formats and sources, which leads towards a scattering of architectural information. Ontobrowse Semantic Wiki specifically addresses these issues by providing an ontology-based integration and documentation platform for architectural information. In this paper, we identify key issues arising from documentation and maintenance of a SOA by introducing the case of an insurance company. We give a detailed description of the Ontobrowse approach and its implementation, and explain how ontologies, artifact mappings, and architectural rules are created to support the Enterprise SOA case.
- KonferenzbeitragA pragmatic approach to traceability in model-driven development(PRIMIUM - Process Innovation for Enterprise Software, 2009) Aleksy, Markus; Hildenbrand, Tobias; Obergfell, Claudia; Schader, Martin; Schwind, MichaelA common problem in model-driven software development (MDSD) processes is the tracing of requirements across different phases of the software development life cycle and multiple levels of abstraction down to the code level. Because debugging at the model level is not feasible yet, unwanted or unexpected behavior of the executable system needs to be analyzed at the code level at run-time and in a feedback loop must be traced back to and handled at the model level. Thus, traceability is a very important success factor and quality criterion in software engineering and maintenance and especially when developing high-quality model-driven infrastructures. In this paper, we present the conceptual design and prototypical implementation of a lightweight traceability approach which supports tracing requirements across different models and levels of abstraction. While providing support for representing different types of traceability links between design models and implementation details, our approach can easily be integrated into existing MDSD projects without increasing their complexity.
- KonferenzbeitragNew applications for wikis in software engineering(PRIMIUM - Process Innovation for Enterprise Software, 2009) Geisser, Michael; Happel, Hans-Jörg; Hildenbrand, Tobias; Korthaus, Axel; Seedorf, StefanWithin 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.
- KonferenzbeitragA visual approach to traceability and rationale management in distributed collaborative software development(PRIMIUM - Process Innovation for Enterprise Software, 2009) Hildenbrand, T.; Heinzl, A.; Geisser, M.; Klimpke, L.; Acker, T.Traceability and rationale management are utmost critical, especially in distributed collaborative software development projects, due to a lack of mutual workplace awareness and informal coordination among the participating stakeholders. Therefore, this paper presents the rationale behind and implementation of a conceptional design for a novel approach to traceability and rationale management in distributed settings. In doing so, an innovative solution for extracting, visualizing, and analyzing the relationships between requirements and other key artifacts as well as responsible stakeholders is designed based on business needs within the software industry. Thus, the main objective of this paper is to instantiate the underlying conceptual considerations and methodological guidelines with the help of a comprehensive tool infrastructure particularly adapted to distributed settings.
- Editiertes Buch