Logo des Repositoriums

Auflistung nach Schlagwort "industrial case study"

1 - 2 von 2
  • Konferenzbeitrag
    Component and Connector Views in Practice
    (Software Engineering und Software Management 2018, 2018) Bertram, Vincent; Maoz, Shahar; Ringert, Jan Oliver; Rumpe, Bernhard; von Wenckstern, Michael
    We have presented an experience report of applying Component and Connector (C&C) view verification with an industrial partner, at the MoDELS 2017 conference. C&C views are a means for formal yet intuitive structural specification of C&C models. We report on our experience how C&C views and their verification help to address challenges of traceability and evolution in automotive industry. We analyzed the development process at Daimler AG and evaluated our C&C views verification tool on five Simulink models with more than 7700 subsystems in total and C&C views created for 183 textual requirements provided by Daimler AG. We describe our experience in detail and discuss a list of lessons learned, including, e.g., a missing abstraction concept in C&C models and C&C views that we have identified and added to the views language and tool, that engineers can create graphical C&C views quite easily, and how verification algorithms scale on real-size industry models. Furthermore, we report on the non-negligible technical effort needed to translate Simulink block diagrams to C&C models. We make all materials mentioned and used in our experience electronically available for inspection and further research.
  • Konferenzbeitrag
    Quality Experience
    (Software Engineering und Software Management 2018, 2018) Prechelt, Lutz; Schmeisky, Holger; Zieris, Franz
    This work was presented at the 38th International Conference on Software Engineering (2016). Context: While successful conventional software development regularly employs separate testing staff, there are successful agile teams with as well as without separate testers. Question: How does successful agile development work without separate testers? What are advantages and disadvantages? Method: A case study, based on Grounded Theory evaluation of interviews and direct observation of three agile teams; one having separate testers, two without. All teams perform long-term development of parts of e-business web portals. Results: Teams without testers use a "quality experience" work mode centered around a tight field-use feedback loop, driven by a feeling of responsibility, supported by test automation, resulting in frequent deployments. Conclusion: In the given domain, hand-overs to separate testers appear to hamper the feedback loop more than they contribute to quality, so working without testers is preferred. However, Quality Experience is achievable only with modular architectures and in suitable domains.