Improving Mathematics Problem Solving Through Written Explanations

In this action research study of two classrooms of 7th grade mathematics, I investigated how requiring written explanations of problem solving would affect students ability to problem solve, their ability to write good explanations, and how it would affect their attitudes toward mathematics and problem solving. I studied a regular 7th grade mathematics class and a lower ability 7th grade class to see if there would be any difference in what was gained by each group or any group. I discovered that there were no large gains made in the short time period of my action research. Some gains were made in ability to problem solve by my lower ability students over the 7 weeks that they did a weekly problem solving assignment. Some individual students felt that the writing had helped them in their problem solving because they needed to think and write each step. As a result of this research I plan to continue implementing writing in my classroom over the entire school year requiring a little more from students each time we problem solve and write.

Designing Software Product Lines for Testability

Software product line (SPL) engineering offers several advantages in the development of families of software products such as reduced costs, high quality and a short time to market. A software product line is a set of software intensive systems, each of which shares a common core set of functionalities, but also differs from the other products through customization tailored to fit the needs of individual groups of customers. The differences between products within the family are well-understood and organized into a feature model that represents the variability of the SPL. Products can then be built by generating and composing features described in the feature model. Testing of software product lines has become a bottleneck in the SPL development lifecycle, since many of the techniques used in their testing have been borrowed from traditional software testing and do not directly take advantage of the similarities between products. This limits the overall gains that can be achieved in SPL engineering. Recent work proposed by both industry and the research community for improving SPL testing has begun to consider this problem, but there is still a need for better testing techniques that are tailored to SPL development. In this thesis, I make two primary contributions to software product line testing. First I propose a new definition for testability of SPLs that is based on the ability to re-use test cases between products without a loss of fault detection effectiveness. I build on this idea to identify elements of the feature model that contribute positively and/or negatively towards SPL testability. Second, I provide a graph based testing approach called the FIG Basis Path method that selects products and features for testing based on a feature dependency graph. This method should increase our ability to re-use results of test cases across successive products in the family and reduce testing effort. I report the results of a case study involving several non-trivial SPLs and show that for these objects, the FIG Basis Path method is as effective as testing all products, but requires us to test no more than 24% of the products in the SPL.