| Monday, Aug 20, 2018 |
Tuesday, Aug 21, 2018 |
Wednesday, Aug 22, 2018 |
Thursday, Aug 23, 2018 |
Friday, Aug 24, 2018 |
| Registration | Registration | Registration | Registration | |
| Industry Day | Doctoral Symposium | Research | Research | Research |
| Workshops | Workshops | Industrial Innovation | Industrial Innovation | |
| Tutorials | Tutorials | RE@Next! | RE@Next! | RE@Next! |
| Data Track | ||||
| Poster & Tool Demos | Poster & Tool Demos |
| Monday, August 20, 2018 | ||
7:30-17:30 Registration Location: Hallway next to KC 202 |
||
| Workshops | Tutorials | Industry Day |
9:00-17:30 WS01 - ESPRE 2018 |
9:00-12:00 T04 |
9:00 am-6:00 pm Industry Day |
9:00-17:30 WS03 - RESACS'18 |
9:00-12:00 T06 |
|
9:00-17:30 WS06 - D4RE'18 |
14:00-17:30 T02 Please Note: Participants are required to have "Docker" installed (https://docs.docker.com/). |
|
9:00-17:30 WS09 - MoDRE'18 |
||
9:00-17:30 WS11 - RE4SUSY'18 |
||
9:00-17:30 WS12 - EmpirRE'18 |
||
Workshops
| WS01 - ESPRE 2018 - Monday, Aug 20, 2018
- Room: KC 201 |
|||
| 5th International Workshop on Evolving Security & Privacy Requirements Engineering | |||
| Time | Session | Papers | |
| 9:00-9:30 | Workshop Opening Room: KC 201 |
||
| 9:30-10:30 | Keynote Room: KC 201 |
Yijun Yu |
Dr. Yijun Yu is a Senior Lecturer in Computing at The Open University, UK. He is interested in developing automated, efficient and scalable software techniques and tools to better support human activities in software engineering. He has a vision to improve aviation security through cloud computing and blockchains by live streaming blackboxes, which was featured in interviews with BBC after the missing MH370 flight, and subsequently received a Microsoft Azure and Amazon AWS awards (2017). His research on Requirements-driven Self-Adaptation receives a 10 Year Most Influential Paper award (CASCON’16), 5 Best Paper awards and 3 Distinguished Paper awards at International Conferences (including RE’11). This talk is based on recent joint work with colleagues at The Open University, UK, inspired by his international collaborators from over 10 countries. |
| 10:30-11:00 | Network Break  |
||
| 11:00-12:30 | People and Systems Room: KC 201 |
Towards the Design of Usable Privacy by Design Methodologies Argyri Pattakou, Aikaterini-Georgia Mavroeidi, Christos Kalloniatis, Vasiliki Diamantopoulou and Stefanos Gritzalis (University of the Aegean, Greece) |
|
The Importance of Empathy for Analyzing Privacy Requirements Meira Levy (Shenkar - Engineering. Design. Art, Israel) and Irit Hadar (University of Haifa, Israel) |
|||
Assessing System of Systems Security Risk and Requirements with OASoSIS Duncan Ki-Aries, Shamal Faily, Huseyin Dogan (Bournemouth University, UK) and Christopher Williams (Defence Science & Technology Laboratory, UK) |
|||
| 12:30-14:00 | Lunch | ||
| 14:00-15:30 | Privacy by Design and Lightning Talks Room: KC 201 |
Tool-supporting Data Protection Impact Assessments with CAIRIS Joshua Coles, Shamal Faily and Duncan Ki-Aries (Bournemouth University, UK) |
|
Privacy Consistency Analyzer for Android Applications Sayan Maitra, Bohyun Suh and Sepideh Ghanavati (Texas Tech University, USA) |
|||
| Lightning Talks | |||
| 15:30-16:00 | Network Break |
||
| 16:00-17:00 | Keynote Room: KC 201 |
University of Luxembourg |
Lionel C. Briand is professor in software verification and validation at the SnT centre for Security, Reliability, and Trust, University of Luxembourg, where he is also the vice-director of the centre. He is currently running multiple collaborative research projects with companies in the automotive, satellite, financial, and legal domains. Lionel has held various engineering, academic, and leading research positions in five other countries before that. Lionel was elevated to the grade of IEEE Fellow in 2010 for his work on the testing of object-oriented systems. He was granted the IEEE Computer Society Harlan Mills award and the IEEE Reliability Society engineer-of-the-year award for his work on model-based verification and testing, respectively in 2012 and 2013. He received an ERC Advanced grant in 2016 — on the topic of modelling and testing cyber-physical systems — which is the most prestigious individual research grant in the European Union. His research interests include: software testing and verification, model-driven software development, search-based software engineering, and empirical software engineering. |
| 17:00-17:30 | Wrap-up and Workshop Close | ||
| WS03 - RESACS'18 - Monday, Aug 20, 2018
- Room: KC 305 |
|||
| 4th International Workshop on Requirements Engineering for Self-Adaptive, Collaborative, and Cyber Physical Systems | |||
| Time | Session | Papers | |
| 9:00-9:30 | Workshop Opening Room: KC 305 |
||
| 9:30-10:30 | |||
| 10:30-11:00 | Network Break |
||
| 11:00-12:30 | |||
| 12:30-14:00 | Lunch | ||
| 14:00-15:30 | |||
| 15:30-16:00 | Network Break |
||
| 16:00-17:00 | |||
| 17:00-17:30 | |||
| WS06 - D4RE'18 - Monday, Aug 20, 2018 - Room: KC 301 | |||
| 1st International Workshop on Learning from other Disciplines for Requirements Engineering | |||
| Time | Session | Papers | |
| 9:00-9:30 | Workshop Opening Room: KC 301 |
||
| 9:30-10:30 | |||
| 10:30-11:00 | Network Break |
||
| 11:00-12:30 | |||
| 12:30-14:00 | Lunch | ||
| 14:00-15:30 | |||
| 15:30-16:00 | Network Break |
||
| 16:00-17:00 | |||
| 17:00-17:30 | |||
| WS09 - MoDRE'18 - Monday, Aug 20, 2018 - Room: KC 303 | |||
| 8th International Model-Driven Requirements Engineering Workshop | |||
| Time | Session | Papers | |
| 9:00-9:10 | Workshop Opening Room: KC 303 |
||
| 9:10-10:10 | State-Based Modeling Room: KC 303 |
(Paper #1) (9:10-9:40) |
Modelling and Testing Requirements via Executable Abstract State Machines presented by Chen-Wei Wang (30min including Q/A; discussant: Paper #2) |
(Paper #2) (9:40-10:10) |
A Comparison of the Declarative Modelling Languages B, Dash, and TLA+ (30min including Q/A; discussant: Chen-Wei Wang) |
||
| 10:10-10:30 | Paper #7 | Short Paper on Feature-Based Modeling presented by Anna Perini (20min including Q/A; discussant: Karan Singh Hundal) | |
| 10:30-11:00 | Network Break |
||
| 11:00-11:30 | Elicitation Room: KC 303 |
Paper #5 | Model-Based Development with Distributed Cognition presented by Karan Singh Hundal (30min including Q/A; discussant: Anna Perini) |
| 11:30-12:30 | Keynote Room: KC 303 The Prevalence of Code Over Models: Turning it Around With Transparency |
|
Dr. Julio Cesar Leite is an Associate Professor in the Departamento de Informática at PUC-Rio. He is a founding member of the Brazilian Computer Society, a member of the IFIP 2.9 Working Group, and a holder of the IEEE Requirements Engineering Conference Lifetime Service Award. His research interests are in software requirements engineering with a particular emphasis on improving software transparency. The Requirements Engineering group at PUC-Rio has been developing new requirements techniques for improving transparency within the context of requirements evolution. |
| 12:30-14:00 | Lunch | ||
| 14:00-15:30 | Scenario & Goal-Oriented Modeling Room: KC 303 |
(Paper #3) (14:00-14:30) |
Domain-Specific Software Language for Crisis Management Systems presented by Nadin Bou Khzam (30min including Q/A; discussant: Mounifah Alenazi) |
| (Paper #4) (14:30-15:00) |
Using Obstacle Analysis to Support SysML-Based Model Testing for Cyber Physical Systems presented by Mounifah Alenazi (30min including Q/A; discussant: Paper #6) |
||
| (Paper #6) (15:00-15:30) |
The FOL-based Legal-GRL (FLG) Framework: Towards an Automated Goal Modeling Approach for Regulations (30min including Q/A; discussant: Nadin Bou Khzam) |
||
| 15:30-16:00 | Network Break |
||
| 16:00-17:00 | Short Papers on Goals, Patterns, and Decision Making Room: KC 303 |
(Paper #8) (16:00-16:20) |
Towards Multi-context Goal Modeling and Analysis with the Help of Intents presented by Krzysztof Wnuk (20min including Q/A; discussant: Bert de Brock) |
| (Paper #9) (16:20-16:40) |
Towards pattern-driven requirements engineering: Development patterns for functional requirements presented by Bert de Brock (20min including Q/A; discussant: Paper #10) |
||
| (Paper #10) (16:40-17:00) |
Interacting Decision-making Agents and their Impacts on Assurances: Towards a Taxonomy and Challenges (20min including Q/A; discussant: Krzysztof Wnuk) |
||
| 17:00-17:30 | Group Discussion and Wrap-up | ||
| Workshop Dinner (time and location will be announced at the workshop) | |||
| WS11 - RE4SUSY'18 - Monday, Aug 20, 2018 - Room: KC 302 | |||
| 7th International Workshop on Requirements Engineering for Sustainable Systems | |||
| Time | Session | Papers | |
| 9:00-9:30 | Workshop Opening Room: KC 302 |
||
| 9:30-10:30 | |||
| 10:30-11:00 | Network Break |
||
| 11:00-12:30 | |||
| 12:30-14:00 | Lunch | ||
| 14:00-15:30 | |||
| 15:30-16:00 | Network Break |
||
| 16:00-17:00 | |||
| 17:00-17:30 | |||
| WS12 - EmpiRE'18 - Monday, Aug 20, 2018 - Room: KC 203 | |||
| 7th Workshop on Empirical Requirements Engineering | |||
| Time | Session | Papers | |
| 9:00-9:30 | Workshop Opening Room: KC 203 |
||
| 9:30-10:30 | |||
| 10:30-11:00 | Network Break |
||
| 11:00-12:30 | |||
| 12:30-14:00 | Lunch | ||
| 14:00-15:30 | |||
| 15:30-16:00 | Network Break |
||
| 16:00-17:00 | |||
| 17:00-17:30 | |||
Tutorials
| T04- Half-Day-Tutorial - Aug 20, 2018 - Room: KC 205 |
|||
DT4RE: Design Thinking for Requirements Engineering Room: KC 205 |
|||
| Time | |||
| 9:00-9:30 | Tutorial Opening |
||
| 9:30-10:30 | This tutorial presents Design Thinking as a promising approach to creatively elicit human-centered requirements for software-intensive systems. Specifically, it contributes to Requirements Engineering practices by structuring the fuzzy process of developing creative and innovative ideas. Addressing academics and practitioners alike, the tutorial provides a 3.5 hour hands-on introduction to Design Thinking and links it with the realm of Requirements Engineering. The tutorial should be seen as a forum for the interchange of experience and learnings from combining both approaches and should raise awareness for the importance of human-centered methods and experimentation in early phases of software engineering. After the tutorial, the participants will have access to all materials, templates, and methods on our website for further usage. | Jennifer Hehn, Falk Uebernickel and Daniel Méndez |
|
| 10:30-11:00 | Network Break |
||
| 11:00-12:30 | Tutorial continued | ||
| 12:30-14:00 | Lunch | ||
| T06- Half-Day-Tutorial - Aug 20, 2018 - Room: KC 204 |
|||
Agile Requirements Engineering with User Stories Room: KC 204 |
|||
| Time | |||
| 9:00-9:30 | Tutorial Opening |
||
| 9:30-10:30 | 90% of agile practitioners employ user stories for capturing requirements. Of these, 70% follow a simple template when creating user stories: "As a role, I want to action, so that beneefit". User stories' popularity among practitioners and simple yet strict structure make them ideal candidates for automatic reasoning based on natural language processing. In our research, we have found that circa 50% of real-world user stories contain easily preventable errors that sabotage their potential. To alleviate this problem, the presenters of this tutorial have created methods, theories and tools that support creating better user stories. In this tutorial, you will learn: (1) The basics of creating user stories, and their use in requirements engineering; (2) How to improve user story quality with the Quality User Story Framework and AQUSA tool; and (3) How to generate conceptual models from user stories using the Visual Narrator and the Interactive Narrator tools. Our toolset is demonstrated with results obtained from 20+ software companies employing user stories. At the end of this tutorial you will have the knowledge and resources to start applying user stories in your software development projects. |
Fabiano Dalpiaz and Sjaak Brinkkemper | |
| 10:30-11:00 | Network Break |
||
| 11:00-12:30 | Tutorial continued | ||
| 12:30-14:00 | Lunch | ||
| T02- Half-Day-Tutorial - Aug 20, 2018 - Room: KC 206 |
|||
Reconciling Requirements and Continuous Integration in an Agile Context Room: KC 206 |
|||
| Time | |||
| 14:00-14:30 | Tutorial Opening |
||
| 14:30-15:30 | This tutorial aims at exploring the boundaries between requirements, specifications, stories, scenarios and tests. Revisiting requirements elicitation and bridging the gap between traditional requirements engineering and modern software development (highly based on continuous integration and tests), this tutorial will demonstrate how to operationalize a fully-fledged tool chain going from user stories to automated acceptance testing using open-source tools. This is applicable to industrial practitioners as we will rely on state of the art tools, and link agile requirements to formal requirement engineering methods. We will first focus on the notion of user stories and epics to express user’s requirements, and how to evaluate such requirements based on “definition of ready” and “definition of done” acceptance criteria. We will then demonstrate how such requirements can be tracked in a project management tool, and linked to source code development. At the source code level, we will demonstrate how the stories and the associated acceptance scenarios can be modeled using the Gherkin language, and linked to classical unit tests to automate their validation. Finally, a continuous integration environment will be deployed using Docker to link together the different tools and offer an automated pipeline for software developers, bridging the gap between requirements and code development. Please Note: Participants are required to have "Docker" installed (https://docs.docker.com/). |
Sébastien Mosser and Jean-Michel Bruel | |
| 15:30-16:00 | Network Break |
||
| 16:00-17:30 | Tutorial continued | ||
Industry Day - Room: KC 210
| Monday, Aug 20, 2018 - Room: KC 210 | ||||
| Time | Session | Speaker | Presentation Title | |
| 9:00-9:30 | Opening and Speed Networking |
Chris Carlsson and Prashanth Southekal | ||
| 9:30-10:30 | Keynote |
Travis Stevens Orpyx |
Navigating Requirements Ambiguity and Volatility - One Step at a Time |
|
| 10:30-11:00 | Network Break |
|||
| 11:00-12:00 | RE Tutorial |
Karl Wiegers | Requirements Engineering: Precepts, Practices, and Cosmic Truths |
|
| 12:00-13:00 | Catered Lunch and Networking | |||
| 13:00-13:30 | Industry Presentations 1 | Simon Orrell snowdolphin inc. |
Agility in Requirements in an Increasingly Complex World Summary |
|
| 13:30-14:00 | Industry Presentations 2 | Chris Lambert Cortex |
Minimum Viable Product - How to Stack the Requirements Deck in your Favor Summary |
|
| 14:00-14:30 | Industry Presentations 3 | Shawn Martin Pembina Pipelines |
Requirements Management for Asset Integrity Summary |
|
| 14:30-15.00 | Industry Presentations 4 | Rahul Joshi and Mary Fifield Microsoft |
Microsoft’s Datacenter Community Development Initiative: How Does Shared Value Create Shared Benefits? Gathering Requirements for Community and Business Outcomes Summary |
|
| 15:00-15:30 | Network Break |
|||
| 15:30-15:45 | Survey Results | Xavier Franch | Practitioners' Perception of RE Research Relevance Summary |
|
| 15:45-16:15 | Industry Presentations 5 | Geoffrey Cann | Blockchain in Oil and Gas Summary |
|
| 16:15-16:45 | Industry Presentations 6 | Barb Peace and Lauren Johnston WestJet |
A Picture is Worth a Thousand Words |
|
| 16:45-18:00 | RE Tutorial | Falk Uebernickel, Daniel Mendez and Jennifer Hehn |
Design Thinking for Requirements Engineering Summary |
|
| 18:00 | Cocktails and Dinner | |||
Summary(s)
Keynote Navigating Requirements Ambiguity and Volatility - One Step at a Time
Presenter: |
At its core, the discipline of Engineering is about the application of math and science to solve a problem. Sounds simple right? What could possibly go wrong? To the initiated, everything. The above simple statement does not reflect the hard truth of engineering, which is that often the problem being solved is an ill defined moving end target, or those problems that seem well defined, or similar to previous situations, have nuance that make them unique onto themselves. So how does the unknown, the ill defined and the nuanced manifest itself? It is the missed deadline, the ballooning budget, the failed product, the defective device, and we see it, read about it, experience it everyday. The problem seems easy to solve, doesn’t it? If we write better requirements that took into account reality, or had better project management, or did more upfront planning, all these issues would go away, or at least the vast majority of them. Well, the one thing we can be sure of that our ignorance is infinite and our knowledge is finite, and because of this we need to accept the fact that what we think is the truth will evolve over the course of a project. Therefore, in order to be successful, it is necessary to learn how to deal with these sources of uncertainty, to be adaptable, to manage risk and validate the assumptions, both implicit and explicit, that underly or affect our requirements. I will explore the holistic approach, which involves both culture and process, adopted by Orpyx on their journey to commercialize a first of its kind medical device. |
RE Tutorial Requirements Engineering: Precepts, Practices, and Cosmic Truths
Presenter: |
Software methodologies and fads come and go, but certain facts about requirements are timeless. Regardless of the development strategy or lifecycle used, successful products must be built on a foundation of well-understood, adequately documented, and clearly communicated requirements. This presentation describes some definitions and several foundational principles—cosmic truths—about requirements engineering. Summaries of some key requirement development and management practices also are presented. The goal is to provide a better appreciation for the central issues and the complexities of establishing a solid base of requirements for each project. |
Industry Presentations 1 Agility in Requirements in an Increasingly Complex World
Presenter: |
In this brief talk we’ll look at the difference between ‘complicated' and ‘complex' and what the implications are for system requirements in a world of ever-increasing complexity We’ll also have a look at some examples of requirements in non-software domains where agility is employed to address complexity. |
Industry Presentations 2 Minimum Viable Product - How to Stack the Requirements Deck in your Favor
Presenter: |
Requirements form the basis for a successful implementation in any project. Often any project is faced with conflicting goals, uncertainty and ongoing change that can put its success at risk. What can we do to mitigate risk? How can we ensure faster time to market while producing an effective solution that satisfies the needs of many stakeholders, often with conflicting requirements? How do we ensure value and return on investment sooner in the project cycle while gaining better buy in from the users of a new system or integration? In this discussion, we'll speak to these and other key aspects which impact every project no matter it's scope. |
Industry Presentations 3 Requirements Management for Asset Integrity
Shawn Martin |
One of the major challenges facing the oil and gas industry today is ensuring the safe operation of their ageing assets. There are more than 6,500 platforms in operation around the world and have been in operation beyond their intended lifespan. Hence asset integrity in Oil and Gas is essential to ensure the technical integrity of the assets and compliance to regulatory requirements. In this backdrop, this presentation looks at the asset integrity requirement management efforts undertaken in a leading Canadian energy company where the team worked with diverse stakeholders to deliver an asset integrity program that encompasses processes, systems, regulations, and standards to ensure asset integrity throughout the asset lifecycle. |
Industry Presentations 4 Microsoft’s Datacenter Community Development Initiative: How Does Shared Value Create Shared Benefits? Gathering Requirements for Community and Business Outcomes
Presenters: Rahul Joshi and |
With more than 100 datacenters in small towns and major metropolises, Microsoft’s cloud computing operations span the globe. While the technological innovation promised by cloud computing is already having transformative, positive effects for many people, some communities are concerned about the negative impacts of large datacenter facilities on local natural resources and the relatively few jobs that will be created to offset these costs. As Michael Porter and Mark Kramer posit, healthy societies are necessary for healthy markets, and vice versa. Microsoft has a responsibility to promote to the well-being of communities in which we operate for the mutual benefit of society and the company. But how do we determine what kind of support to provide, and how do we measure the community and business impact? In other words, what kind of requirements should guide our work, and how will we know that we have satisfied them? Our emergent community engagement model draws from Porter and Kramer’s “shared value” framework and research on social cohesion and community leadership. In a panel discussion, we will describe how we developed this model, what we have learned so far, and the possibilities for engaging community stakeholders not only to addresses complex societal issues but to increase their capacity to drive their own solutions and improve our ROI. |
Survey Results Practitioners' Perception of RE Research Relevance
Xavier Franch |
The relevance of Requirements Engineering (RE) research to practitioners is a prerequisite for problem-driven research in the area and key for a long-term dissemination of research results to everyday practice. To better understand how industry practitioners perceive the practical relevance of RE research, we are conducting the RE-Pract project, a collaborative project involving 10 researchers from all over the worlds. We designed and distributed to practitioners a survey asking participants to rate their perceived practical relevance of 418 RE papers, published between 2010 and 2015 at the RE, ICSE, FSE, ESEC/FSE, ESEM and REFSQ conferences. We got 147 answers which we are currently analyzing. The talk will present the first, preliminary results and will show the plan for the next months. |
Industry Presentations 5 Blockchain in Oil and Gas
Presenter: |
Blockchain, also known as distributed ledger technology, is a simple technology construct but with far-reaching impacts, and it is coming quickly to oil and gas. Blockchain combines encryption, distributed computing, decentralized architecture and cloud computing in a novel way to create new business models that do not require trust between counter parties. Blockchain is thus poised to overhaul legacy ways of working in oil and gas that involve assets, ownership, identity, money, contracts and of course, trust. Beyond transformation of business processes (both operational and commercial), blockchain combines with other technologies such as the internet of things, artificial intelligence and automation in more profound ways to create fundamentally different business models. For example, blockchain and artificial intelligence working together on a powered device allows that device to purchase and settle power purchases based not just on load but the price of power. Early use cases of relevance to oil and gas include commodity trading, asset tracking, royalty and venture accounting, but other examples in areas as diverse as shipping, financial transactions, used equipment trading and of course, currency, also underscore the profound possibilities presented by this technology set. |
Industry Presentations 6 A Picture is Worth a Thousand Words
Presenters: WestJet
|
As WestJet prepares to enter the world stage next year with our Dreamliner 787 planes; a business class of service offering and nothing but opportunity in front of us, we are faced with the next level of growth as a company, therefore our processes must grow as well. As a society we are more restless, our attention spans are shorter, we want information in shorter more concise forms. As business analysts, we must respond to these conditions so we can continue enabling change within the organization. Our projects are more complex, there are multiple inter-dependencies and the stakes are higher between success and failure. We must be certain in what we want to do as an organization, and thus spend time on the things that matter and will make a difference to our guest, our people and our bottom line. On projects, we need to be clear on what we are doing; what are we introducing, changing or removing. As business analyst’s our go to tool is the business requirements document. In this new world, we ask ourselves, is this the best way to start? Are we focusing our efforts on eliciting the right requirements, or are we spending unnecessary time waiting, churning, and reworking? Are we representing the information in the most meaningful way? Let us take this opportunity to revisit the toolsets we use as business analyst’s and determine if we can help to improve the quality of information that drives requirements so that the projects are set up for success, and we spend our effort on doing the right things. |
RE Tutorial Design Thinking for Requirements Engineering
Falk Uebernickel, Daniel Mendez and |
Design Thinking is a human-centered problem solving approach that applies rapid prototyping, iterative development cycles, and interdisciplinary teamwork. By structuring the fuzzy process of developing innovative ideas, Design Thinking is a promising approach to creatively elicit human-centered requirements for software-intensive systems. This tutorial provides a hands-on introduction to Design Thinking based on practical examples to foster lively discussions on the potential and challenges in applying Design Thinking in the participants’ own settings. In particular, real project examples from large, (mostly) European enterprises will showcase practices on how to utilize Design Thinking for Requirements Engineering and to integrate it with agile approaches like Scrum on a day-to-day basis. After the tutorial, the participants will have access to all materials, templates, and methods on our website for further usage. |
| Tuesday, August 21, 2018 | ||
7:30-17:30 Registration Location: Hallway next to KC 202 |
||
| Workshops | Tutorials | Doctoral Symposium |
9:00-17:30 WS02 - AffectRE'18 |
9:00-12:00 T01 |
9:00 am-17:30 pm Doctoral Symposium |
9:00-17:30 WS04 - AIRE'18 |
9:00-12:00 T05 |
|
9:00-17:30 WS05 - REET'18 |
14:00-17:30 T03 |
|
9:00-17:30 WS07 - QuaRAP'18 |
||
9:00-17:30 WS10 - EARS'18 |
||
9:00-17:30 WS13 - RE Cares'18 |
||
Workshops
| WS02 - AffectRE'18 - Tuesday, Aug 21, 2018
- Room: KC 206 |
|||
| 1st International Workshop on Affective Computing for Requirements Engineering | |||
| Time | Session | Papers | |
| 9:00-9:30 | Workshop Opening Room: KC 206 |
||
| 9:30-10:30 | |||
| 10:30-11:00 | Network Break |
||
| 11:00-12:30 | |||
| 12:30-14:00 | Lunch | ||
| 14:00-15:30 | |||
| 15:30-16:00 | Network Break |
||
| 16:00-17:00 | |||
| 17:00-17:30 | |||
| WS04 - AIRE'18 - Tuesday, Aug 21, 2018
- Room: KC 201 |
|||
| 5th International Workshop on Artificial Intelligence for Requirements Engineering | |||
| Time | Session | Papers | |
| 9:00-9:30 | Workshop Opening Room: KC 201 |
||
| 9:30-10:30 | |||
| 10:30-11:00 | Network Break |
||
| 11:00-12:30 | |||
| 12:30-14:00 | Lunch | ||
| 14:00-15:30 | |||
| 15:30-16:00 | Network Break |
||
| 16:00-17:00 | |||
| 17:00-17:30 | |||
| WS05 - REET'18 - Tuesday, Aug 21, 2018 - Room: KC 301 | |||
| 8th International Workshop on Requirements Engineering Education and Training | |||
| Time | Session | Papers | |
| 9:00-9:30 | Workshop Opening Room: KC 301 |
||
| 9:30-10:30 | |||
| 10:30-11:00 | Network Break |
||
| 11:00-12:30 | |||
| 12:30-14:00 | Lunch | ||
| 14:00-15:30 | |||
| 15:30-16:00 | Network Break |
||
| 16:00-17:00 | |||
| 17:00-17:30 | |||
| WS07 - QuaRAP'18 - Tuesday, Aug 21, 2018 - Room: KC 305 | |||
| 1st International Workshop on Quality Requirements in Agile Projects | |||
| Time | Session | Papers | |
| 9:00-9:15 | Opening, Introduction of Participants Room: KC 305 |
||
| 9:15-10:0010:10-10:30 | Keynote Practical Lightness: Agility and Quality Requirements in Startup Companies. Daniela Damian |
Daniela Damian |
In this talk I will present from our recent investigation of RE practices in 16 startup companies as they grow and introduce new products and services. Startups present a special -- more extreme -- case of agility in the software process and market penetration. They operate in a dynamic environment, with significant time and market pressures, and rarely have time for systematic requirements analysis. Attention to quality requirements in particular is non-existent at first, when speed of product release takes precedence over its quality. As the startup scales up to deliver to more clients and market segments, quality however becomes top priority in a startup's journey to survival in the market. We found that startups's approach to evolve their requirements practice is of pragmatical lightness, or flexibility, in their evolution towards an "engineering" of requirements. The second part of the talk will discuss the case of data privacy requirements, in light of the recent needed attention to GDPR (General Data Protection Regulation) compliance requirements. A closer look into three of the companies in our study reveals some of the strategies, both technical and process-related, employed by these companies. |
| 10:00-10:30 | Paper Presentation | Definition of the On-Time Delivery Indicator in Rapid Software Development. Martí Manzano, Cristina Gómez, Claudia Ayala, Silverio Martínez-Fernández, Prabhat Ram, Pilar Rodríguez and Marc Oriol |
|
| 10:30-11:00 | Network Break |
||
| 11:00-11:30 | Paper Presentation |
Mining Security Requirements from Common Vulnerabilities and Exposures for Agile Projects. |
|
| 11:30-12:00 | Paper Presentation |
Security Requirements Engineering in the Agile Era: How it Happens in Practice?. |
|
| 12:00-12:30 | Paper Presentation | How do Practitioners Manage Quality Requirements in Rapid Software Development: A Survey. Lidia Lopez Cuesta, Jari Partanen, Pilar Rodríguez and Silverio Martínez-Fernández. |
|
| 12:30-14:00 | Lunch | ||
| 14:00-14:45 | Keynote |
Joerg Doerr Fraunhofer IESE, Germany |
Dealing with quality requirements (QRs) is a challenging task. This holds for traditional software engineering and unfortunately, this also holds for agile approaches. Empirical Studies from a decade ago even showed that it can get worse in agile settings. This keynote starts with highlighting the typical reasons why dealing with QRs is so difficult. It presents proven best practices for handling QRs that worked in traditional settings and discusses which of them work in agile settings and which don't. But this keynote also takes a different angle: the new agile and DevOps settings do not only impose new challenges for QRs, they also offer new opportunities. So how can we make use of them? For this, ideas, concrete approaches and first empirical results for dealing with QRs in very different ways are presented. One facet is deriving them with Crowd-RE approaches like using emoji analysis, usage analysis, or text mining of app reviews/social media information. They promise benefit for so called run-time qualities like usability and performance. But how about the poor development time qualities like maintainability? The keynote will close with a personal perspective on open research challenges. |
| 14:45-15:15 | Open space for attendees' statements (a.k.a. Presentations on-the-fly) | ||
| 15:15-15:30 | Identification of discussion topics | ||
| 15:30-16:00 | Network Break |
||
| 16:00-17:00 | Open discussion in working groups |
||
| 17:00-17:15 | Summary of discussions | ||
| 17:15-17:30 | Conclusions of the workshop. Plans for the future | ||
| WS10 - EARS'18 - Tuesday, Aug 21, 2018 - Room: KC 210 | |||
| 1st International Workshop on Easy Approach to Requirements Syntax | |||
| Time | Session | Papers | |
| 9:00-9:30 | Workshop Opening Room: KC 210 |
||
| 9:30-10:30 | |||
| 10:30-11:00 | Network Break |
||
| 11:00-12:30 | |||
| 12:30-14:00 | Lunch | ||
| 14:00-15:30 | |||
| 15:30-16:00 | Network Break |
||
| 16:00-17:00 | |||
| 17:00-17:30 | |||
| WS13 - RE Cares'18 - Tuesday, Aug 21, 2018 - Room: KC 203 | |||
| RE Cares about giving back to Society: Employing RE Techniques and Hackathon for Alberta | |||
| Time | Session | Papers | |
| 9:00-9:30 | Workshop Opening Room: KC 203 |
||
| 9:30-10:30 | |||
| 10:30-11:00 | Network Break |
||
| 11:00-12:30 | |||
| 12:30-14:00 | Lunch | ||
| 14:00-15:30 | |||
| 15:30-16:00 | Network Break |
||
| 16:00-17:00 | |||
| 17:00-17:30 | |||
Tutorials
| T01- Full-Day-Tutorial Tuesday, Aug 21, 2018 - Room: KC 205 |
|||
Writing Good Requirements Room: KC 203 |
|||
| Time | |||
| 9:00-9:30 | Tutorial Opening |
||
| 9:30-10:30 | Poor requirements practices are widely recognized as one of the top causes of product defects, project delays, and cost overruns. Yet, a practical solution that balances effective results with the everyday pressures of product development can be hard to find. Teams struggle with questions such as “How much detail is enough?”, “When is that detail needed?”, and “What requirements practices are right for my project?” Writing Good Requirements is based on a popular and successful course taught to tens of thousands of students at Intel. It covers effective best practices for specifying requirements that work even for complex, market-driven products. The techniques presented are scalable and have been employed on projects within both agile and traditional methodologies. Rather than presenting a rigid methodology or process, the emphasis is on best practices that can be tailored to a variety of product and project types. The tutorial contains examples from actual requirements documents in original and improved formats. It includes small group exercises and discussions to reinforce the content and techniques through the day. | John Terzakis | |
| 10:30-11:00 | Network Break |
||
| 11:00-12:30 | Tutorial continued | ||
| 12:30-14:00 | Lunch | ||
| 14:00-15:30 | Tutorial continued | ||
| 15:30-16:00 | Network Break |
||
| 16:00-17:30 | Tutorial continued | ||
| T05- Half-Day-Tutorial - Tuesday, Aug 21, 2018 - Room: KC 204 |
|||
Requirements Reuse and Reusability: Product Lines, Cases and Feature‐Similarity Models Room: KC 205 |
|||
| Time | |||
| 9:00-9:30 | Tutorial Opening |
||
| 9:30-10:30 | Several socio-economic trends are increasing personalized customer demands. Suppliers are responding with mass customization but the management of large-scale cost-effective software reuse remains a difficult challenge. Software reuse and reusability range from operational, ad-hoc and short-term to strategic, planned and long-term. Often the focus of attention is just on code or low-level design. This tutorial presents and compares two different requirements-led approaches. The first approach deals with requirements reuse and reusability in the context of product line engineering. The second approach deals with requirements reuse and reusability in the context of case-based reasoning. Both approaches have different key properties and trade-offs between the costs of making software artefacts reusable and the benefits of reusing them. To aid large-scale development we have proposed a Feature-Similarity Model, which draws on both approaches to facilitate discovering requirements relationships using similarity metrics. A Feature-Similarity Model also helps with the evolution of a product line, since new requirements can be introduced first into a case base and then gradually included into a product line representation. | Hermann Kaindl and Mike Mannion | |
| 10:30-11:00 | Network Break |
||
| 11:00-12:30 | Tutorial continued | ||
| 12:30-14:00 | Lunch | ||
| T03- Half-Day-Tutorial - Tuesday, Aug 21, 2018 - Room: KC 206 |
|||
On Tap: Writing Requirements for Molecular Programs Room: KC 204 |
|||
| Time | |||
| 14:00-14:30 | Tutorial Opening |
||
| 14:30-15:30 | Molecular programming uses the computational power of DNA and other biomolecules to create useful nanoscale systems. Molecular program applications being developed include medical sensors that can be absorbed by the body after use, drug capsules that open only when they find diseased cells, and programmable nanoscale robots. This tutorial introduces the model-based language commonly used to write the requirements for molecular programs. This high-level modeling language is mathematically simple, very general, and well documented. Importantly, specifications written in it can be automatically compiled into implementable, detailed design descriptions. Participants will leave knowing how to write the requirements for some small molecular system components, where to go to learn more, and what are some open problems for writing the requirements of large molecular programs. |
Robyn Lutz and Jack H. Lutz | |
| 15:30-16:00 | Network Break |
||
| 16:00-17:30 | Tutorial continued | ||
Doctoral Symposium
| Tuesday, Aug 21, 2018 | ||||
| Time | Session | Speaker | Presentation Title | |
| 9:00-9:30 | ||||
| 9:30-10:30 | ||||
| 10:30-11:00 | Network Break |
|||
| 11:00-12:30 | ||||
| 12:30-14:00 | Lunch | |||
| 14:00-15:30 | ||||
| 15:30-16:00 | Network Break |
|||
| Wednesday, Aug 22, 2018 - Main Conference | |||
| Time | Session | Papers | |
| 7:30-17:30 | Registration |
||
| 8:45-10:30 | Opening and Keynote Room: 203 |
Beyond DevOps: Finding Value through RequirementsThe DevOps movement enables the more frequent delivery of changes to a software system. Adopting DevOps practices is seen as enabling the ability to get more done. But is the more that is getting done actually of value to the end user or to the producing organization? In this talk, I will explore how the ideas of value streams are being applied to software development and how the requirements community is key to enabling an increased focus on the delivery of value. |
|
| 10:30-11:00 | Networking Break |
||
| 11:00-12:30 | Paper 1: RE and Management Room: 301 |
R103: Goal-Oriented Release Planning: A New Life for Goal Models. R87: The Manager Perspective on Requirements Impact on Automotive Systems Development Speed. JF4: A requirements engineering methodology for knowledge management solutions: integrating technical and social aspects. |
|
Paper 2: Evolution and Tracing Room: 303 |
R86: A Qualitative Study on Using GuideGen to Keep Requirements and Acceptance Tests Aligned. R123: Enhancing Automated Requirements Traceability by Resolving Polysemy. R113: Vetting Automatically Generated Traceability Links: What Information is Useful to Human Analysts? |
||
RE@Next 1: Towards Better Requirements Room: 305 |
N186: Assessment of Safety Processes in Requirements Engineering. N202: Software Transparency as a Key Requirement for Self-Driving Cars. N184: Towards Utility-based Prioritization of Requirements in Open Source Environments. |
||
| 12:30-14:00 | Lunch | ||
| 14:00-15:30 | Paper 3: Negotiation and Conflicts Room: 301 |
I196: Tailoring Requirements Negotiation to Sustainability. I17: Requirements Engineering for Consensus-Oriented Written Technical Specifications. JF6: Value-based requirements engineering: method and experience. |
|
Papers 4: Adaptation and Feature Interactions Room: 303 |
I162: Supporting Diagnosis of Requirements Violations in Systems of Systems. JF3: Acon: A learning-based approach to deal with uncertainty in contextual requirements at runtime. R116: Morse: Reducing the Feature Interaction Explosion Problem Using Subject Matter Knowledge as Abstract Requirements. |
||
Panel: RE Cares Room: 305 |
|||
| 15:30-16:00 | Networking Break with Poster Booth |
||
| 16:00-17:30 | Papers 5: Agile RE Room: 301 |
I159: Integrating Requirements Specification and Model-Based Testing in Agile Development. R114: Discovering, Analyzing, and Managing Safety Stories in Agile Projects. R47: Understanding Challenging Situations in Agile Quality Requirements Engineering and their Solution Strategies: Insights from a Case Study. |
|
Papers 6: Mining Product Data Room: 303 |
R128: Mining Android App Description for Permission Requirements Recommendation. R132: Semantic Incompleteness in Privacy Policy Goals. R138: App Review Analysis via Active Learning: Reducing Supervision Effort without Compromising Classification Accuracy. |
||
Posters and Tools Demos Room: 305 |
PTD230 SuSoftPro: Profiling for Sustainability Software. PTD231 Multi-user Input in Determining Answer Sets (MIDAS). PTD233 BloomingLeaf: A Formal Tool for Requirements Evolution over Time. PTD237 FlexiView Experimental Tool: Fair and Detailed Usability Tests for Requirements Modeling Tools. PTD238 piStar Tool – A Pluggable Online Tool for Goal Modeling. PTD239 Dynamic Visual Analytics for Elicitation Meetings with ELICA. PTD240 T-Reqs: Tool Support for Managing Requirements in Large-Scale Agile System Development. |
||
| Thursday, August 23, 2018 | ||||
| Time | Research | Industrial Innovation | RE@Next! | Data Track |
| Registration | ||||
| TBA | TBA | TBA | TBA | |
| Friday, August 24, 2018 | ||||
| Time | Research | Industrial Innovation | RE@Next! | Data Track |
| Registration | ||||
| TBA | TBA | TBA | ||