|
| Panels |
| |
| Transforming the Requirements Engineering Classroom Experience |
| Moderator: Didar Zowghi - University of Technology, Sydney, Australia |
| Panelists: Jane Cleland-Huang, Don Gause, Olly Gotel, Zhi Jin, Pete Sawyer |
Although, as a community we have developed extensive curriculum plans and have identified skill sets that requirements engineers need to develop, we have spent little time engaging in the discussion of how requirements principles and practices can best be taught. This panel asks the question of how we can improve requirements engineering education and training programs by transforming the learning process into one that actively engages students as they seek to acquire knowledge and learn critical skills. |
| |
| Requirements Engineering - Industry Needs |
| Moderator: Ann Hickey - University of Colorado, USA |
| Panelists: Alan Davis, Christof Ebert, Martin S. Feather, Suzanne Robertson, Frank Houdek, Sarah Gregory, Gert Bikker |
Requirements engineering (RE) is the discipline within systems and software engineering that bridges the entire life cycle and thus significantly influences the success or failure of a product or project. From a business perspective, it is what makes the difference between a winning product and a mere set of features. Therefore, good requirements engineering practices in industry are critical to succeed – and survive – in ever-changing markets. The goal of this panel is to address the often perceived theory-practice gap between academia and industry by delivering insights into concrete industry demands/needs for improvements in RE, identifying potential solutions to those needs, and challenging academia and industry to address unmet needs. |
| |
| How to Combine Requirements Engineering and Interaction Design? |
| Moderator: Hermann Kaindl - Vienna University of Technology, Austria |
| Panelists: Larry Constantine, Oscar Pastor, Alistair Sutcliffe, Didar Zowghi |
|
In this panel, we propose to figure out how require-ments engineering and interaction design can be usefully combined. In particular, some people argue that scenar-ios / use cases should be concrete, as in story-telling. Others argue for use of “essential” use cases as a meth-odological approach to interaction and user-interface design. Somewhat in the middle, it is argued that use cases should help acquiring the requirements in the first place. What should the practitioner believe and, in par-ticular, do, in order to develop useful and usable software and systems?
Software development and interaction design require different skills and different methods and are typically done by different people. Still, scenario-based design is proposed for several activities relevant for both tasks, such as requirements elicitation, software design, and interaction design. Symbolic modeling in this spirit is actually common to various fields.
However, scenario-based approaches vary, especially with regard to their use, e.g., employing abstract use cases or integrating scenarios with functions and goals in a systematic design process. So, the key issue to be raised at the panel is how to combine different approaches, e.g., in scenario-based development, so that the interaction design as well as the development of the user interface and of the software internally result in an overall useful and useable system.
|
|
|
|
