Logo des Repositoriums

P151 - PRIMIUM - Process Innovation for Enterprise Software

Autor*innen mit den meisten Dokumenten  

Auflistung nach:

Neueste Veröffentlichungen

1 - 10 von 12
  • Konferenzbeitrag
    An environment for modeling workflow components
    (PRIMIUM - Process Innovation for Enterprise Software, 2009) Atkinson, Colin; Stoll, Dietmar
    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.
  • Konferenzbeitrag
    Alignment of software specifications with quality- and business goals in the SIKOSA method
    (PRIMIUM - Process Innovation for Enterprise Software, 2009) Herrmann, Andrea; Weiß, Daniel
    Business-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.
  • Konferenzbeitrag
    Architectural 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, Kevin
    Process-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.
  • Konferenzbeitrag
    Extended privacy definition tool
    (PRIMIUM - Process Innovation for Enterprise Software, 2009) Kähmer, Martin; Gilliot, Maike
    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.
  • Konferenzbeitrag
    On the role of communication, documentation and experience during testing - an exploratory study
    (PRIMIUM - Process Innovation for Enterprise Software, 2009) Illes-Seifert, Timea; Paech, Barbara
    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.
  • Konferenzbeitrag
    Ontology-enabled documentation of service-oriented architectures with ontobrowse semantic wiki
    (PRIMIUM - Process Innovation for Enterprise Software, 2009) Happel, Hans-Jörg; Seedorf, Stefan; Schader, Martin
    Documenting 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.
  • Konferenzbeitrag
    A pragmatic approach to traceability in model-driven development
    (PRIMIUM - Process Innovation for Enterprise Software, 2009) Aleksy, Markus; Hildenbrand, Tobias; Obergfell, Claudia; Schader, Martin; Schwind, Michael
    A 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.
  • Konferenzbeitrag
    New applications for wikis in software engineering
    (PRIMIUM - Process Innovation for Enterprise Software, 2009) Geisser, Michael; Happel, Hans-Jörg; Hildenbrand, Tobias; Korthaus, Axel; Seedorf, Stefan
    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.
  • Konferenzbeitrag
    The emergence of partnership networks in the enterprise application software industry - an SME perspective
    (PRIMIUM - Process Innovation for Enterprise Software, 2009) Arndt Jens-M.; Kude, Thomas; Dibbern, Jens; Heinzl, Armin
    The enterprise application development industry is currently undergoing profound changes. The well established, large system developers (hubs) take the lead in establishing partner networks with much smaller, often young companies (spokes). This paper takes the perspective of these spokes and seeks to understand their motivations for entering into such partner networks. Drawing on research on strategic alliances and product complementarities, a theoretical framework on the determinants of partnering is developed. It is argued that partnering is especially attractive for smaller organizations when it allows them to access capabilities that would otherwise be difficult to obtain. Three broad categories of dynamic capabilities of hub organizations are assumed to act in this role: the capability to innovate architectures, the capability to provide an integrated enterprise application system, and the capability to address broad markets. These are analyzed in eight case studies. The cases represent small and medium sized enterprises (SMEs) that are participating in the partner network of a leading provider of enterprise application systems. The study reveals that while access to market capabilities is a key motivator for all spokes, the other two capabilities do not play an identical role in all cases. Rather, their impact on partnering motivation is contingent upon the type of solution offered by the partner in relation to the large system developer.
  • Konferenzbeitrag
    Bringing developers and users closer together: the open proposal story
    (PRIMIUM - Process Innovation for Enterprise Software, 2009) Rashid, Asarnusch; Wiesenberger, Jan; Meder, David; Baumann, Jan
    Even though end-user participation in requirements engineering (RE) is highly important, it is at present not frequently used. Reasons can be found in the large expenditure of time for organizing and carrying out surveys as well as in the time it takes to understand the users' requirements. This research is supposed to address this problem by presenting the OpenProposal approach for distributed user participation using visual requirement specifications. First experiences made in several case studies show the potential and limits of this approach and outline the possibilities of application.