Auflistung nach:
Auflistung P239 - Software Engineering & Management 2015 nach Titel
1 - 10 von 114
Treffer pro Seite
Sortieroptionen
- Konferenzbeitrag2nd collaborative workshop on evolution and maintenance of long-living Systems(EML)(Software-engineering and management 2015, 2015) Heinrich, Robert; Jung, Reiner; Konersmann, Marco; Schmieders, Eric
- Konferenzbeitrag8. Arbeitstagung programmiersprachen (ATPS 2015)(Software-engineering and management 2015, 2015) Grelck, Clemens; Widemann, Baltasar Trancón
- KonferenzbeitragAdvances in quantitative software product line analysis(Software-engineering and management 2015, 2015) Dubslaff, ClemensThe quantitative analysis of software is important, e.g., for energy-aware systems having constraints on energy consumption while guaranteeing a certain degree of utility. Analyzing software product lines is challenging due to the possibly exponential number of feature combinations. This paper sketches new approaches using probabilistic model checking for a quantitative analysis of software product lines and the integration of such into the software development process.
- KonferenzbeitragAnalyse der sozialen teamstruktur in softwareprojekten(Software-engineering and management 2015, 2015) Meißner, Johannes; Schulz, Frederik; Rossak, WilhelmUm den organisatorischen Kontext von Softwareentwicklungsprojekten abzubilden, haben wir das Goal-orientierte OrCA-Framework entworfen. Damit lassen sich die Abhängigkeiten zwischen Projektbeteiligten, ihren Beiträgen zur Umsetzung sowie den Ergebnissen ihrer Arbeit modellieren. Durch die Integration von OrCA mit dem Teamrollenkonzept von Belbin reichern wir diese Modelle mit Informationen zu persönlichen und sozialen Charakteristika der Projektbeteiligten an. Diese Arbeit zeigt, wie wir diese Modelle formalisieren, um eine Grundlage für eine automatische Analyse der Qualität der Teamzusammenstellung unter sozialen Aspekten zu schaffen.
- KonferenzbeitragAnalysis strategies for software product lines: A classification and survey(Software-engineering and management 2015, 2015) Thüm, Thomas; Apel, Sven; Kästner, Christian; Schaefer, Ina; Saake, GunterSoftware-product-line engineering enables the efficient development of similar software products. Instead of developing each product from scratch, products are generated from common artifacts. However, the product generation is a challenge for the analysis of correctness properties. Applying traditional analysis techniques, such as type checking and model checking, to each product involves redundant effort and is often not feasible due to the combinatorial explosion of products. Approaches to scale analysis techniques to product lines have been presented in unrelated research
- KonferenzbeitragArchitecture challenges for internal software ecosystems: A large-scale industry case study(Software-engineering and management 2015, 2015) Schultis, Klaus-Benedikt; Elsner, Christoph; Lohmann, DanielThe idea of software ecosystems encourages organizations to open software projects for external businesses, governing the cross-organizational development by architectural and other measures. Even within a single organization, this paradigm can be of high value for large-scale decentralized software projects that involve various internal, yet self-contained organizational units. However, this intra-organizational decentralization causes architecture challenges that must be understood to reason about suitable architectural measures. In our FSE paper, we present an in-depth case study on collaboration and architecture challenges in two of these large-scale software projects at Siemens. We performed a total of 46 hours of semi-structured interviews with 17 leading software architects from all involved organizational units. Our major findings are: (1) three collaboration models on a continuum that ranges from high to low coupling, (2) a classification of architecture challenges, together with (3) a qualitative and quantitative exposure of recurring issues along each collaboration model. We identified compliant software development as the core challenge. It targets cross-cutting regulations and architecture governance to assist and check for compliance. In addition to our study results, we outline a framework along with tool support that allows to manage these regulations and their violations throughout the life cycle. Internal Software Ecosystems We have investigated two large-scale software projects (about 500 and 950 developers) within Siemens [SEL14]. These projects involve a set of internal organizational units that are self-contained profit centers with own business objectives, organizational independent with own product management, and have to a wide extent autonomous processes and software-engineering life cycles. Thus, the view on the organizational structure moves from strict hierarchies towards more decentralized topologies. We define those systems as internal software ecosystems (ISECOs) [SEL14]. ISECOs comprise a keystone organizational unit that provides a platform and multiple client organizational units that build applications upon it. The keystone acts in a creative role but does not have power to direct. Our talk is laid out as follows: First, we outline our study results. Second, we present our current work, a framework that addresses the compliant software development challenge. 114 Case Study Results:
- KonferenzbeitragAufwandsschätzung der softwarewartung und -evolution(Software-engineering and management 2015, 2015) Sneed, Harry M.
- KonferenzbeitragAusführbare spezifikationen im projektalltag - ein erfahrungsbericht(Software-engineering and management 2015, 2015) Nerche, Jens
- KonferenzbeitragAusführbare spezifikationen mit der language workbench MPS(Software-engineering and management 2015, 2015) Nerche, Jens
- KonferenzbeitragAutomated decision support for recurring design decisions considering non-functional requirements(Software-engineering and management 2015, 2015) Busch, AxelPlanning high quality software means more than regarding functionality. Considering non-functional requirements, implementing them and understanding their effects on the software architecture remain often an open question. Therefore, in this paper, we present an approach that provides decision support in a software development process for recurring design decisions in the field of non-functional requirements. The approach defines a design decision model that allows to encapsulate the reasoning of design decisions, make them reusable and use them to enable automated feedback in a decision making process. At the end, this approach increases the developer's productivity by reusing design decisions and therefore allows to implement requirements with lower overhead and to improve the architecture quality by a tool assisted decision support process.