At RE 2009, Patrick Mäder and I gave a mini-tutorial called: ‘How to Select a Requirements Management Tool: Initial Steps’. The gist of this tutorial is described as a chapter in the recent book on ‘Software and Systems Traceability’. We were invited to re-run this tutorial at the upcoming RE 2012.
From the book’s glossary:
Requirements management – The activity concerned with the effective control of information related to stakeholder, system and software requirements and, in particular, the preservation of the integrity of that information for the life of the system and with respect to changes in the system and its environment. Requirements management depends upon requirements traceability as its enabling mechanism.
Requirements management tools – Tools that support requirements management.
At RE 2012, we will highlight the process guide, and then profile one company’s particular experience of evaluating requirements management tools in more detail. Joy Beatty’s team at Seilevel is in the process of undertaking a 3-phase approach to tool evaluation. Remo Ferrari, lead tool researcher for the completed phases 1 and 2 of this study, will join us to share details of Seilevel’s selection criteria and evaluation process. Remo will then discuss 17 popular tools on the market, as assessed according to these criteria. Advice on how to use the guide to build your own criteria and inform your own requirements management tool evaluation process will be provided.
You’ll have to wait until a future RE conference for Joy and the results of phase 3 …
Link to Seilevel’s resources on evaluating requirements management tools.
Download slides from the mini-tutorial.
I will also be participating in the Requirements Engineering Education and Training (REET’12) workshop (co-located with RE’12) and presenting a paper that I really enjoyed writing with my long-term research colleague, Stephen Morris: Case-Based Stories for Traceability Education and Training, by Orlena Gotel and Stephen Morris. Here is the abstract and a taster of our scrumptious story.
Abstract. The purpose of this paper is to disseminate knowledge about proven techniques relevant to software and systems engineering, and in particular to requirements traceability, but derived from another industry and another professional approach. It describes the process of investigating and dealing with an outbreak of a foodborne disease, an established process that depends upon traceability practice at multiple levels and its alignment within two distinct disciplines. We tell a story based upon an outbreak investigation case study to step through the details of this process and to discuss parallels for the practice of traceability in the context of identifying and addressing requirements-borne problems. Not only is this process a model of industrial practice in these other two disciplines, the provision of case study materials based upon past events is also a model industrial practice that makes the details of the process widely accessible for education and training. This paper seeks to encourage the similar use of case studies in requirements engineering education and training, to develop realistically grounded stories that can be used to step through the investigation of a requirements-borne problem, and so to demonstrate and discuss the practice and value of requirements traceability at each step.
Back Story. Your presentation at the International Requirements Engineering Conference was a great success this year, but your flight home is interminable! You feel nauseous and your stomach is cramping. You have had to get up to use the lavatory multiple times and you do not like what you see. You begin to sweat and feel that you have the onset of a low grade fever. By the time you reach home, you are convinced that this is not your usual bout of traveler’s food poisoning. Twenty-four hours later and your stomach pains are severe. You are worried about all that blood you see and you are finding it difficult to quench your thirst. But, as there are still no alerts from your colleagues, you conclude that it must just be you. Researcher that you are, you make your own diagnosis from the web and rush to the doctor’s surgery. Back in the conference city, clinicians have just reported a 300% increase in laboratory reports of E. coli infection over the past month, as compared with the same month in previous years, with the bulk of the cases appearing over the last few days. The Department of Community Health immediately call their newly-appointed epidemiologist: “Dr. Epi, is this a foodborne disease outbreak? What should we do?” Dr. Epi is a recent graduate and this is the first time that she has been posed this question when she holds responsibility. She knows that there are standard ways to conduct an outbreak investigation, so she uses the step-by-step guide of the CDC as her plan, augmented by material from the World Health Organization and numerous course materials. With the mention of E. coli, Dr. Epi knows that she will have to undertake both an epidemiological and environmental (food) investigation in parallel, with the findings of the epidemiological investigation guiding the collection and testing of the environmental samples. The date is October 1st, 2012.
Don’t miss RE’12 in Chicago, 24th–28th September 2012! The IEEE International Requirements Engineering Conference series is the premier international forum for researchers, educators, practitioners and students to present and discuss the latest innovations, trends, experiences and concerns in the field of Requirements Engineering.
I will be presenting a vision paper on day 1 of the main conference: The Quest for Ubiquity: A Roadmap for Software and Systems Traceability Research, by Orlena Gotel, Jane Cleland-Huang, Jane Huffman Hayes, Andrea Zisman, Alexander Egyed, Paul Grünbacher and Giuliano Antoniol. This is the result of an on-going collaboration among members of the Center of Excellence for Software Traceability (CoEST). Here is the abstract of our paper and a preview of the roadmap (I thank my kayaking buddy Mike (Logo) Samuel for drawing me an actual road to use!)
Abstract. Traceability underlies many important software and systems engineering activities, such as change impact analysis and regression testing. Despite important research advances, as in the automated creation and maintenance of trace links, traceability implementation and use is still not pervasive in industry. A community of traceability researchers and practitioners has been collaborating to understand the hurdles to making traceability ubiquitous. Over a series of years, workshops have been held to elicit and enhance research challenges and related tasks to address these shortcomings. A continuing discussion of the community has resulted in the research roadmap of this paper. We present a brief view of the state of the art in traceability, the grand challenge for traceability and future directions for the field.