Industry TrackHave you alredy planned your professional qualification activities for 2019? REFSQ 2019 is an excellent qualification option if you are working as a professional Requirements Engineer, Requirements Manager, Requirements Engineering Coach, Business Analyst, ... Compared to previous years we will expand the industry activities.
Industry KeynoteWednesday morning, 20th of March 2019
Jet Propulsion Laboratory, California Institute of Technology
Requirements Analysis and Verification for the Thirty Meter Telescope with OpenMBEE and the OpenSE Cookbook
This talk focuses on leveraging the Executable System Engineering Method (ESEM) which automates requirements verification (e.g. power and mass budget margins and duration analysis of operational modes) using executable SysML models. It demonstrates how the ESEM is applied in conjunction with OpenMBEE (an open source Model Based Engineering Environment) to create key engineering products (e.g. operational concept document) and specify, analyze, and verify requirements of the Alignment and Phasing System (APS) and the Narrow Field Infrared Adaptive Optics System (NFIRAOS) within the Thirty Meter Telescope (TMT) project. TMT is under development by the TMT International Observatory (TIO).
Robert Karban is a Project Systems Engineer in the Systems Engineering and Formulation Division at NASA/JPL. Robert leads the team providing the Systems Environment (based on OpenMBEE) to JPL users, and applies modeling on the Thirty Meter Telescope project. Prior to that, he developed control and instrumentation systems for large telescopes at the European Southern Observatory (ESO), applying model driven technology, and for particle accelerators at the European Organization for Nuclear Research (CERN). Robert is a Challenge team lead of INCOSE's MBSE Initiative, an OMG certified SysML professional, and co-chair of the OMG's revision task force for SysML. He started his career at Siemens Medical Devices developing System Software and received is M.S. in Computer Science from the Technical University of Vienna/Austria.
Industry TalksWednesday, 20th of March 2019
Like every year the industry track will feature a set of high-quality invited presentations. This year presentations will mainly focus on challenges, i.e. topics that require new attention in industrial RE.
A pragmatic view from a practical perspective
What is a requirement engineer expected to deliver in context of software development within a large corporation? This contribution addresses the intersection of requirements engineering and design. From a practical point of view there are three main areas where requirements can originate from. These are business, technology and people. Requirements engineering is indisputably strong in eliciting and articulating requirements. However, these three areas of origin are not equally accounted for in the process of engineering requirements.
Within Deutsche Bahn Group we therefore elaborated and discussed several problem hypotheses relating to the requirements process. We identified 13 critical issues and for each one a golden rule. We also compared the existing practice of requirements engineering with the established human centered design practice in context of an internal IT provider. Here again the fact came to light clearly that requirements themselves do not create a solution. A conceptional design is required to mediate the transformation from requirements to a solution. Here we see in the context of agile development some stumbling blocks that should be encountered.
When we talk about design, we realize that design is a frayed term. In light of contemporary trends towards digital transformation we find that the purpose of design requires some re-shaping. Design problems can be referred to as “wicked problems” according to Horst Rittel. To tackle wicked design problems an integrated mindset of design and engineering is very useful. Equally important is the practice of design as a craft as well as design as a mindset. Several examples from inside Deutsche Bahn are described to illustrate such an integrated mindset. Returning to the intersection of requirements engineering and design it seems that from a practical perspective it is time for a new integrated approach that can be located in the emerging discourse of “digital design”. A discourse that has been started by the German Association for IT, Telecommunications and New Media and picked up the International Requirements Engineering Board, as well as the German Usability Professionals Association.
David Gilbert has worked in various operational and strategic Digital Design roles since 2007. Until 2015, he worked for various design agencies such as Scholz & Volkmer, Pixelpark, Mutabor or SinnerSchrader. The projects he has worked in have received over 25 international and national design awards. - Since 2015 he is working in the IT department of the Deutsche Bahn Group, where he holds the role of Chief Architect User Experience at the intersection of classic system-oriented and user-oriented software conception. From 2011 - 2016, he was a lecturer in UX Design at the RheinMain University of Applied Sciences, and has published various contributions to the topics of strategic UX design and digital design. He is a member of the IREB working group "Digital Design", deputy chairman of the Bitkom "Digital Design" working group as well as he is a member of the "Designforum Digital Experience" of the German Design Council.
Requirements collection and business process optimization for the development of an information system to replace a legacy system.
The Volkswagen Group operates an approximately 15-year-old back-end IT system, which shows symptoms of a legacy system (outdated process and IT documentation, error-prone, time-consuming maintenance, etc.) and that has to be replaced by a successor system. The presentation will first of all present the initial situation and the special challenges in the context of very large and over years grown legacy systems. In the second part of the presentation, the approach is presented in which (a) the requirements of the users and interface partners on the successor system and (b) the actually practiced as-is process were recorded with the help of interviews. In the third part, we discuss how the recorded requirements had been evaluated against the business process vision, possibly detailed, grouped and prioritized. In conclusion, problems and positive findings of the applied approach are summarized. In particular, we note that many pseudo-requirements had been captured and sometimes even implemented, and that some core requirements can only be captured based on acquired domain knowledge and target business process vision and not through interviews.
Bosch Software Innovations GmbH