Towards an understanding of the causes and effects of software requirements change: two case studies

Changes to software requirements not only pose a risk to the successful delivery of software applications but also provide opportunity for improved usability and value. Increased understanding of the causes and consequences of change can support requirements management and also make progress towards the goal of change anticipation. This paper presents the results of two case studies that address objectives arising from that ultimate goal. The first case study evaluated the potential of a change source taxonomy containing the elements ‘market’, ‘organisation’, ‘vision’, ‘specification’, and ‘solution’ to provide a meaningful basis for change classification and measurement. The second case study investigated whether the requirements attributes of novelty, complexity, and dependency correlated with requirements volatility. While insufficiency of data in the first case study precluded an investigation of changes arising due to the change source of ‘market’, for the remainder of the change sources, results indicate a significant difference in cost, value to the customer and management considerations. Findings show that higher cost and value changes arose more often from ‘organisation’ and ‘vision’ sources; these changes also generally involved the co-operation of more stakeholder groups and were considered to be less controllable than changes arising from the ‘specification’ or ‘solution’ sources. Results from the second case study indicate that only ‘requirements dependency’ is consistently correlated with volatility and that changes coming from each change source affect different groups of requirements. We conclude that the taxonomy can provide a meaningful means of change classification, but that a single requirement attribute is insufficient for change prediction. A theoretical causal account of requirements change is drawn from the implications of the combined results of the two case studies.

Teaching and cognitive outcomes in A-levels and Advanced GNVQ's: Case studies from Science and Business Studies Classrooms

The purpose of the paper is to demonstrate how a research diary methodology, designed to analyse A-level and GNVQ classrooms, can be a powerful tool for examining pedagogy and quality of learning at the level of case study. Two subject areas, science and business studies, are presented as cases. Twelve teachers and thirty-four students were studied over a four-week period in May 1997 and contrasts were drawn between lessons from three A-level physics teachers/three Advanced GNVQ science teachers and two A-level business/economics teachers/four Advanced GNVQ business teachers. Lessons were analysed within a cognitive framework which distinguishes between conceptual and procedural learning and emphasizes the importance of metacognition and epistemological beliefs. Two dimensions of lessons were identified: pedagogical activities (e.g. teacher-led explanation, teacher-led guidance on a task, question/answer sessions, group discussions, working with IT) and cognitive outcomes (e.g. structuring and memorizing facts, understanding concepts and arguments, critical thinking, problem-solving, learning core skills, identifying values). Immediately after each lesson, teachers and students (three per class) completed structured research diaries with respect to the above dimensions. Data from the diaries reveal general and unique features of the lessons. Time-ofyear effects were evident (examinations pending in May), particularly in A-level classrooms. Students in business studies classes reported a wider range of learning activities and greater variety in cognitive outcomes than did students in science classes. Science students self-rating of their ability to manage and direct their own learning was generally low. The phenomenological aspects of the classrooms were consistently linked to teachers' lesson plans and what their teaching objectives were for those particular students at that particular time of the year.

Lean software management case study: Timberline Inc.

This paper is believed to be the first documented account of a full adoption of lean by a software company. Lean techniques were devised by Toyota and other manufacturers over the last 50 years. The techniques are termed lean because they require less resource to produce more product and exceptional quality. Lean ideas have also been successful in service industries and product development. Applying lean to software has been advocated for over 10 years. Timberline, Inc started their lean initiative in Spring 2001 and this paper records their journey, results and lessons learned up to Fall 2003. This case study demonstrates that lean thinking can work successfully for software developers. It also indicates that the extensive lean literature is a valuable source of new ideas for software engineering.