No abstract

Abstract. Continuous stress monitoring may help users better understand their stress patterns and provide physicians with more reliable data for interventions. Previously, studies on mental stress detection were limited to a laboratory environment where participants generally rested in a sedentary position. However, it is impractical to exclude the effects of physical activity while developing a pervasive stress monitoring application for everyday use. The physiological responses caused by mental stress can be masked by variations due to physical activity. We present an activity-aware mental stress detection scheme. Electrocardiogram (ECG), galvanic skin response (GSR), and accelerometer data were gathered from 20 participants across three activities: sitting, standing, and walking. For each activity, we gathered baseline physiological measurements and measurements while users were subjected to mental stressors. The activity information derived from the accelerometer enabled us to achieve 92.4% accuracy of mental stress classification for 10-fold cross validation and 80.9% accuracy for between-subjects classification.

Continuous stress monitoring may help users better understand their stress patterns and provide physicians with more reliable data for interventions. Previously, studies on mental stress detection were limited to a laboratory environment where participants generally rested in a sedentary position. However, it is impractical to exclude the effects of physical activity while developing a pervasive stress monitoring application for everyday use. The physiological responses caused by mental stress can be masked by variations due to physical activity. We present an activity-aware mental stress detection scheme. Electrocardiogram (ECG), galvanic skin response (GSR), and accelerometer data were gathered from 20 participants across three activities: sitting, standing, and walking. For each activity, we gathered baseline physiological measurements and measurements while users were subjected to mental stressors. The activity information derived from the accelerometer enabled us to achieve 92.4% accuracy of mental stress classification for 10-fold cross validation and 80.9% accuracy for between-subjects classification.

Systematic Software reuse is a key business strategy that software managers can employ to dramatically improve their software development processes, to decrease time-to-market and costs, and to improve product quality. Effective reuse requires much more than just code and library technology. We have learned that careful consideration must be given to people, process, and technology. One approach to the systematic integration of these three elements is the concept of the software factory. At Hewlett-Packard Co., we have initiated a multifaceted corporate reuse program to help introduce the best practices of systematic reuse into the company, complemented by multidisciplinary research to investigate and develop better methods for domain-specific, reuse-based software engineering. This essay discusses our experiences. Key aspects include domainspecific kits, busi:-tess modeling, organization design, and technology infrastructure for a flexible software factory. T he phrase software crisis was first used in 1969 to describe the ever-increasing burden and frustration that software development and maintenance have placed on otherwise happy and productive organizations. Since then, managers have been looking for effective strategies to deal with software. Manufacturers of computer systems and instruments, such as Hewlett-Packard Co. and IBM, whose businesses relied mostly on hardware and mechanical engineers, today find that over 70 percent of their research and development engineers are working in the areas of software and firmware. Maintenance and rework account for about 60 to 80 percent of the total software costs. Systems take longer to produce than expected, and software is frequently on the critical path. by M. L. Griss Among the many solutions proposed to address this software crisis, the systematic application of software reuse to prototyping, development, and maintenance is one of the most effective ways to significantly improve the software process, shorten time-to-market, improve software quality and application consistency, and reduce development and maintenance costs. While many companies are developing proprietary software libraries, software reuse is not yet a major force in most corporate software development. We believe that this is largely because effective reuse depends more on socioeconomic than on technical factors at this time,4,5 while most users still concentrate on library or language technology.

No abstract