Industrial Presentations

Confirmed presentations (last update: 20th May 2010)

Benoit Cardinael, Escent:
Requirements Engineering in Capital Markets Projects (preliminary title) (Details)

Robert Darimont, Respect-IT:
Goal Orientation: Lessons Learnt from 10 Years of Use (Details)

Christof Ebert, Vector Consulting Services:
Requirements Engineering for Safe and Secure Software-Intensive Systems (Details)

Dirk Fritsch, QA Systems:
A SCRUM project with RM Tool support (Details)

Rainer Grau, Zühlke Engineering:
The Real Reasons Why Requirements Engineering Trainings Fail (Details)

Frank Houdek, Daimler:
Challenges in Automotive Requirements Engineering (Details)

Hans-Bernd Kittlaus, InnoTivum:
Software-as-a-Service - How do requirements differ from traditional software products? (Details)

Robert Neher, Polarion Software:
Why do I need an integrated tool landscape in my application lifecycle? (Details)

Barbara Paech, International Requirements Engineering Board (IREB):
International Understanding in RE: What you need to know about the “Certified Professional for Requirements Engineering” certification (Details)

Andreas Schreiber, Deutsches Zentrum fuer Luft- und Raumfahrt e.V. (DLR):
The World of Requirements in Germany’s Research Center for Aaeronautics and Space (Details)

Christian Schuderer, Siemens:
Requirements Engineering in Plant Automation – A Practice Report (Details)

Markus Voelter:
Using Domain Specific Languages in Requirements Engineering (Details)

Detailed information

Benoit Cardinael, Escent:
Requirements Engineering in Capital Markets Projects (preliminary title)

Abstract:

During this talk, we will review specific challenges faced by requirements engineers active in the capital markets domain, such as cross-border mergers and exponentially increasing complexity. We will explain how the recent financial crisis has exacerbated those challenges with new regulations, increased offshoring and high pressure on costs. We will also demonstrate why the industry’s defensive reaction has made the situation even worse. Then, based on our field experience as consultants in various countries and cultures, we will discuss mitigating actions to overcome these challenges. We will conclude by expressing why we believe that professionalisation of the requirements engineering business, backed by internationally recognized certifications such as the IREB Certified Professional for Requirements Engineering, will become a pre-requisite and a key success factor in the coming years.

Biographie:

Benoit Cardinael is co-founder of escent, a Belgian-based company providing since 2006 business consultancy services to the Capital Markets industry. Benoit has worked as requirement engineer, functional architect, methodologist or project lead on international delivery projects for large customers in London, New-York, Paris, Luxembourg and Brussels. He took part in various projects such as securities front to back office systems integration, in-house financial software developments or treasury management package customization. He started his career in 1996 at EDS Global Securities Industry Group, joined the Capital Markets Company then SWIFT before founding escent.

Robert Darimont, Respect-IT:
Goal Orientation: Lessons Learnt from 10 Years of Use

Abstract:

Mastering requirements engineering is recognised as a key and challenging step for IT project success. Goal-driven requirements engineering aim at eliciting, modelling, and formalizing the problem to solve mainly in terms of goals to achieve and of agents responsible for the achievement of those goals. The talk will review 10 years of use of goal orientation on industrial projects in various areas (aeronautics, health care, services, …). The talk will also explain how goal orientation works, what are the outputs, the pros & cons, and the current trends.

Biographie:

Dr Ir Robert Darimont is CEO of Respect-IT, a Belgian company providing services in Requirements Engineering and commercialising the Objectiver software tool. He graduated and received a PhD in requirements engineering from the University of Louvain (B).

Christof Ebert, Vector Consulting Services:
Requirements Engineering for Safe and Secure Software-Intensive Systems

Abstract:

Software-intensive systems almost by nature pose safety related risks, such as in automotive, aerospace, automation, railways or medical applications. More recently, open interfaces, standardized platforms and a variety of heterogeneous networks also drive security risks, which can easily turn to safety hazards. It is only a question of time before the resulting security vulnerabilities of such embedded systems are systematically identified and exploited at the harm and expense of users and manufacturers. This article provides experience and guidance how safety and information security can be successfully achieved in software-intensive systems based upon a systematic requirements engineering (RE) perspective. Our experiences from automotive, transport and automation applications show that success depends a thorough understanding and handling of safety and security requirements and their interaction with functional requirements. Four RE-related levers are addressed: safety / security requirements elicitation, analysis, design, and validation. We will show for each of these levers how safety and security are analyzed and implemented. Only a disciplined requirements engineering will ensure that software-intensive systems effectively and sustainably meet the safety and security expectations their users rely upon and thus our society depends upon.

Biography:

Dr. Christof Ebert is managing director at Vector Consulting Services. He is helping clients worldwide to improve product development and product strategy and to manage organizational changes. Prior to that, he held engineering and management positions for fifteen years in telecommunication, IT, transportation and aerospace. An internationally renowned keynote speaker, SEI certified CMMI Instructor, area editor of the Software Engineering Body of Knowledge and steering chair of the IEEE conference series on Global Software Engineering, he authored several books and teaches at the University of Stuttgart.
Contact him at christof.ebert@vector.com

Dirk Fritsch, QA Systems:
A SCRUM project with RM Tool support

Abstract:

“In consequence of continuously shorter product cycles and constantly decreasing project times agile methods find more and more their way into almost all development sectors and lines of business.
Compared to the application of the traditional and classical procedure models the use of agile methods and the therewith associated shorter iterations defines the course of project more purposefully. But the basic principles of the traditional and classical methods (for example the complete documentation of a project) are often disregarded in the practical experience because of new agile concept, although they still determine the quality of a project.
At this point the example of the use of the RM & E Tools IRQA in a SCRUM project should show, in which way traditional and classical tools can support agile practices, particularly in the area of documentation.”

Biography:

“Dirk Fritsch has long-time experience as Consultant and Coach for Requirements Engineering / Management and Business Process Modelling in international projects.
He is involved in studies at various universities in the area of Requirements Gathering for improvement of established RE/RM tools.”

Rainer Grau, Zühlke Engineering:
The Real Reasons Why Requirements Engineering Trainings Fail

Abstract:

Since 20 or even more years defects in requirements engineering regulary pop up as root cause of project failures. The natural correcting action is to improve the process and to train the team. That is what organizations do – at least these organizations that identify this root cause. Nevertheless within a regular period of five to six years the quality of the outcome of the discipline requirements engineering once again drops terrifiying to a very deep base line. This talk reflects on more then five years experience in education of very small to very large companies in all different domains in the discipline of Requirements Engineering. The talk collects and presents exemplary scenarios why education and training effort trickles away like drops in the desert. The talk will stimulate organizations to commit to changes eliminating root causes that turn education into waste.

Biography:

Rainer Grau is traveler in the software industry since 20 year. Starting as Software Engineer his journey passed architecture, project management, requirements engineering and software processes. Parallel with his engagement in many customer projects he was and is active as adjunct professor in the postgraduate education. In 2004 he joined Zühlke Technology Group as manager of the International Education Centre. Since 2008 Rainer Grau is vice president of the International Requirements Engineering Board, responsible for the certification “Certified Professional for Requirements Engineering”.

Frank Houdek, Daimler:
Challenges in Automotive Requirements Engineering

Abstract:

Specifications play an important role in the automotive development process as many components are not developed or produced by the OEM but by numerous suppliers. Thus, specifications are essential to define what an OEM needs and to base testing activities on.
Traditionally, strong emphasis lies on specifications of individual components. In the last years, more attention is given on functionalities on vehicle level, especially as functionality is more and more distributed across many components within one vehicle. For instance, exterior lighting is distributed across up to 20 electronic control units (ECUs).
The presentation summarizes recent challenges in automotive software engineering, like handling cross-component functionalities, reuse across car-models, co-cooperation with suppliers and hand-over specification to testing. Additionally, the presentation provides also insights in challenges when introducing new requirements engineering technologies in automotive environments.

Hans-Bernd Kittlaus, InnoTivum:
Software-as-a-Service – How do requirements differ from traditional software products?

Abstract:

Software as a Service (SaaS), the software component of Cloud Computing, is gaining increasing acceptance as a new delivery model for software. All the major vendors from Microsoft to SAP are embracing it. But it is much more than just a new delivery model for an existing software license product. With SaaS, the vendor assumes additional responsibilities, e.g. for hosting or data security. Additional requirements come from multi-tenancy, finer-grained levels of usage-based pricing, and changing customer expectations. This presentation looks at which requirements a software vendor or a corporate IT organization that intends to offer SaaS needs to address, and how they differ from traditional software license products.

Biography:

Hans-Bernd Kittlaus is the owner and CEO of InnoTivum Consulting (www.innotivum.de). Before he was Director of SIZ GmbH, Bonn, Germany (German Savings Banks Organization) and Head of Software Product Management and Development units of IBM. He provides management and consulting to both software vendors and corporate IT organizations focussed on the cooperation and alignment of business and IT, in particular software product management, SaaS, customer relationship management (CRM), business process management (BPM), and Change Management. He has published numerous articles and books, a.o. “Software Product Management and Pricing – Key Success Factors for All Software Organizations”, Springer, 2009, and “SaaS – wie können KMU profitieren?” in Wirtschaftinformatik & Management 02.2010. He is Diplom-Informatiker and certified PRINCE2 Practitioner, member of ACM, GI and ISPMB (International Software Product Management Board).

Robert Neher, Polarion Software:
Why do I need an integrated tool landscape in my application lifecycle?

Abstract:

Looking into most of application and product development a plenty of tools have been acquired for each discipline
- Requirement management, interaction with customers
- Test cases, validation, verification
- Test planning, regression
- Bug tracking, defect/issue management
- Release management
- Project and task management
- Version- and configuration management
- Support tickets, customer portals
- Etc.
Development organization spend a fortune to implement traceability to perform impact analysis (what happens when?). This ends up in consumption of resources which slows down innovation speed.
This contribution

Biography:

Diplom-Ingenieur Elektrotechnik
…
1998-2000 Object International, Mgr. Sales
2000-2003 TogetherSoft Corp., Business Development EMEA
2003-2004 Borland Corp., Business Development Manager EMEA
2004-today Polarion Software, VP Sales & Business Development

Barbara Paech, International Requirements Engineering Board (IREB):
International Understanding in RE: What you need to know about the “Certified Professional for Requirements Engineering” certification

Abstract:

Companies become more and more aware of the fact that requirements engineering (RE) is a good and important concept for succeeding with projects. However, there are many different approaches to requirements engineering, often leading to the question whether the developer really understands what the analyst has specified, especially in the case of distributed projects. It is the objective of the International Requirements Engineering Board (IREB) e.V., established in 2007, to achieve standardization in requirements engineering, leading to an international common understanding.
The IREB consists of leading RE experts from business, consulting, research and science.
They share the objective to improve and standardize education and training in requirements engineering, resulting in requirements engineers worldwide speaking a “common language”. Therefore, they developed a curriculum and the “Certified Professional for Requirements Engineering” (CPRE) certificate which has already been issued to more than 2,500 people worldwide.
This talk covers the IREB e.V. itself, the CPRE certification, training opportunities, examination procedure and exam questions. It also points out the difference to other certifications, namely “Business Analyst”, “IIBA” and “BABOK”.
Also covered by the talk:
- IREB e.V. background information, history and objectives
- Internal cooperation of the IREB members
- Curriculum content and certification levels
- Internationality: worldwide availability of certification and examination; countries with CPRE standard being active.
- Some statistics
- Demonstration of example exam questions
- Future development and CPRE Advanced Level

Biography:

Barbara Paech holds the chair „Software Engineering“ at the University of Heidelberg. Till October 2003 she was department head at the Fraunhofer Institute Experimental Software Engineering. Her teaching and research focuses on methods and processes to ensure quality of software with adequate effort. Since many years she is particularly active in the area of requirements and rational engineering. She has headed several industrial, national and international research and transfer projects. She is spokeswoman of the section “Software Engineering” in the German Computer Science Society and member of the International Requirements Engineering Board.

Andreas Schreiber, Deutsches Zentrum fuer Luft- und Raumfahrt e.V. (DLR):
The World of Requirements in Germany’s Research Center for Aaeronautics and Space

Abstract:

The development of software is a core activity at most DLR institutes. About a quarter of DLR’s manpower is assigned to it. Projects range from small software tools developed by students to large long-term cooperations with other research centers, academia, and industry. The kind of developed software is very also different. There are many small scripts with a limited lifetime (e.g., for prototyping) as well as large systems or critical real-time software. Furthermore, in most cases the software is developed by engineers or natural scientist who do not have any education in software engineering. The talk outlines the current status of software engineering at DLR with focus on requirements engineering. With examples from very different development projects, some of the used tools and methodologies for requirements engineering will be described. Also, the efforts for DLR-internal standardization and some of the research topics related to requirements management will be presented.

Biography:

Andreas Schreiber is scientist and head of the Department for Distributed Systems and Component Software of the German Aerospace Center’s (DLR) Simulation and Software Technology division. He received a degree in industrial mathematics from Technical University Clausthal. His research fields include distributed computing, Grid Computing, modern software architectures, user interfaces, and software engineering.

Christian Schuderer, Siemens:
Requirements Engineering in Plant Automation – A Practice Report

Abstract:

Requirements Engineering in Plant Automation is a two fold activity. One task has to deal with portfolio driven planning of products designed for reuse, the other task is to transform customer requirements into plant solution considering the previously defined products. Main differentiators and basic concepts will be shown as well as examples from substantial implementations in real plant projects.

Biography:

Dipl. Ing. Christian Schuderer is Senior Consultant in the domain of Systems Engineering within Corporate Technology Division of Siemens AG. The focus of his work is on development and application of standardized solutions in the field of plant engineering.

Markus Voelter:
Using Domain Specific Languages in Requirements Engineering

Abstract:

An important part of Requirements Engineering is capturing precisely what a software system is supposed to do.
The challenge is to express these requirements precisely, without predetermining the way the system is designed or implemented. The use of natural language or “picture drawing” modeling languages leads to ambiguity and inconsistencies.
Domain Specific Languages offer a way to solve this dilemma: they are built specifically to precisely represent information for a given domain. In this talk we present a couple of examples of how we have used DSLs for RE. Examples are based on various tools, including Eclipse and JetBrains MPS.

Biography:

Markus Völter works as an independent researcher, consultant and coach for itemis AG in Stuttgart, Germany. His focus is on software architecture, model-driven software development and domain specific languages as well as on product line engineering. Markus also regularly writes (articles, patterns, books) and speaks (trainings, conferences) on those subjects. Contact him via voelter at acm dot org or www.voelter.de.