Offshoring manufacturing: Implications for engineering jobs and education: A survey and case study

One result of globalization is the rapid growth of offshoring, i.e., the outsourcing of functions and jobs to offshore locations. In the USA, offshoring has progressed to the point where it already affects everyday lives, from the cars we drive (of which a large portion of the work and components are outsourced) to computers (which are typically manufactured offshore and shipped back to the USA), to electronic diagnostics (where calls are answered overseas). This phenomenon has implications on our lives and on the jobs that engineers and scientists will assume both now and in the future. Further, it is something that all highly developed and even some lesser-developed countries must face. Consequently, the growth of outsourcing will have a major impact on the educational objectives of engineering programs and the resultant engineering curricula worldwide.

This paper presents recent data on product and job offshore migrations and discusses the various dimensions of this phenomenon. In addition to the potential loss of engineering and other high-end technical jobs, sociological and cultural aspects, intellectual property issues, strategic planning concerns, and macro-economic issues are presented. For example, the effects of offshoring on the societal fabric of the countries that are recipients of manufacturing and service center outsourcing, such as China and India, are significant, rapid, and controversial. Offshoring has also begun to change the way that engineering programs in these countries educate their students. In addition, intellectual property issues create a major risk to companies considering outsourcing to certain less-developed countries. These issues can be broadly categorized into: the robustness and strength of intellectual property laws, and the degree to which these laws are implemented and enforced. Further, such factors as currency fluctuations and geo-political conditions can substantially impact outsourcing decisions and profitability.

The phenomenon of offshoring, which is now affecting engineering careers, will play a major role in shaping engineering education worldwide. The next generation of engineers will need to possess the ability to work seamlessly across cultures, have outstanding communication skills and be familiar with the principles of project management, logistics, and systems integration. Some educational models that begin to address these requirements will be presented.     

Analyzing the relationships between inspections and testing to provide a software testing focus

ContextQuality assurance effort, especially testing effort, is frequently a major cost factor during software development. Consequently, one major goal is often to reduce testing effort. One promising way to improve the effectiveness and efficiency of software quality assurance is the use of data from early defect detection activities to provide a software testing focus. Studies indicate that using a combination of early defect data and other product data to focus testing activities outperforms the use of other product data only. One of the key challenges is that the use of data from early defect detection activities (such as inspections) to focus testing requires a thorough understanding of the relationships between these early defect detection activities and testing. An aggravating factor is that these relationships are highly context-specific and need to be evaluated for concrete environments.ObjectiveThe underlying goal of this paper is to help companies get a better understanding of these relationships for their own environment, and to provide them with a methodology for finding relationships in their own environments.MethodThis article compares three different strategies for evaluating assumed relationships between inspections and testing. We compare a confidence counter, different quality classes, and the F-measure including precision and recall.ResultsOne result of this case-study-based comparison is that evaluations based on the aggregated F-measures are more suitable for industry environments than evaluations based on a confidence counter. Moreover, they provide more detailed insights about the validity of the relationships.ConclusionWe have confirmed that inspection results are suitable data for controlling testing activities. Evaluated knowledge about relationships between inspections and testing can be used in the integrated inspection and testing approach In²Test to focus testing activities. Product data can be used in addition. However, the assumptions have to be evaluated in each new context.     

Guidelines for conducting and reporting case study research in software engineering

Case study is a suitable research methodology for software engineering research since it studies contemporary phenomena in its natural context. However, the understanding of what constitutes a case study varies, and hence the quality of the resulting studies. This paper aims at providing an introduction to case study methodology and guidelines for researchers conducting case studies and readers studying reports of such studies. The content is based on the authors’ own experience from conducting and reading case studies. The terminology and guidelines are compiled from different methodology handbooks in other research domains, in particular social science and information systems, and adapted to the needs in software engineering. We present recommended practices for software engineering case studies as well as empirically derived and evaluated checklists for researchers and readers of case study research.     

Usage and usefulness of technical software documentation: An industrial case study

ContextSoftware documentation is an integral part of any software development process. However, software practitioners are often concerned about the value, degree of usage and usefulness of documentation during development and maintenance.ObjectiveMotivated by the needs of NovAtel Inc. (NovAtel), a world-leading company developing software systems in support of global navigation satellite systems, and based on the results of a former systematic mapping study, we aimed at better understanding of the usage and the usefulness of various technical documents during software development and maintenance.MethodWe utilized the results of a former systematic mapping study and performed an industrial case study at NovAtel. From the joint definition of the analysis goals, the research method incorporates qualitative and quantitative analysis of 55 documents (design, test and process related) and 1630 of their revisions. In addition, we conducted a survey on the usage and usefulness of documents. A total of 25 staff members from the industrial partner, all having a medium to high level of experience, participated in the survey.ResultsIn the context of the case study, a number of findings were derived. They include that (1) technical documentation was consulted least frequently for maintenance purpose and most frequently as an information source for development, (2) source code was considered most frequently as the preferred information source during software maintenance, (3) there is no significant difference between the usage of various documentation types during both development and maintenance, and (4) initial hypotheses stating that up-to-date information, accuracy and preciseness have the highest impact on usefulness of technical documentation.ConclusionsIt is concluded that the usage of documentation differs for various purposes and it depends on the type of the information needs as well as the tasks to be completed (e.g., development and maintenance). The results have been confirmed to be helpful for the company under study, and the firm is currently implementing some of the recommendations given.     

Developing a knowledge-based perspective on coordination: The case of global software projects

We have attempted to bring together two areas which are challenging for both IS research and practice: forms of coordination and management of knowledge in the context of global, virtual software development projects. We developed a more comprehensive, knowledge-based model of how coordination can be achieved, and\illustrated the heuristic and explanatory power of the model when applied to global software projects experiencing different degrees of success. We first reviewed the literature on coordination and determined what is known about coordination of knowledge in global software projects. From this we developed a new, distinctive knowledge-based model of coordination, which was then employed to analyze two case studies of global software projects, at SAP and Baan, to illustrate the utility of the model.     

From ICT coordination to ICT integration: a longitudinal case study

This study utilizes a school‐improvement perspective to examine the role of curriculum coordination in the integration of information and communication technologies (ICT) into primary schools. The nature and impact of this role is examined in seven primary schools in Australia. These seven schools were drawn from a longitudinal intervention that provided additional ICT‐related resources and personnel to the schools. An instrument, referred to as the Learning Outcomes and Pedagogy Attributes (LOPA) measure, was developed and charted for the seven schools over the 4‐year data collection period. The changes in LOPA score over time were then analysed in terms of the conditions at the school with regard to curriculum ICT coordination. The study concludes that the coordinator role and school leadership in general, play critical but varying roles in the complex process of ICT integration into schools. Success appeared to be associated with the support provided for the role, the extent to which the role was connected to school leadership, personal leadership characteristics of those in the role and the strategies employed within the role.     

Characteristics of software ecosystems for Federated Embedded Systems: A case study

ContextTraditionally, Embedded Systems (ES) are tightly linked to physical products, and closed both for communication to the surrounding world and to additions or modifications by third parties. New technical solutions are however emerging that allow addition of plug-in software, as well as external communication for both software installation and data exchange. These mechanisms in combination will allow for the construction of Federated Embedded Systems (FES). Expected benefits include the possibility of third-party actors developing add-on functionality; a shorter time to market for new functions; and the ability to upgrade existing products in the field. This will however require not only new technical solutions, but also a transformation of the software ecosystems for ES.ObjectiveThis paper aims at providing an initial characterization of the mechanisms that need to be present to make a FES ecosystem successful. This includes identification of the actors, the possible business models, the effects on product development processes, methods and tools, as well as on the product architecture.MethodThe research was carried out as an explorative case study based on interviews with 15 senior staff members at 9 companies related to ES that represent different roles in a future ecosystem for FES. The interview data was analyzed and the findings were mapped according to the Business Model Canvas (BMC).ResultsThe findings from the study describe the main characteristics of a FES ecosystem, and identify the challenges for future research and practice.ConclusionsThe case study indicates that new actors exist in the FES ecosystem compared to a traditional supply chain, and that their roles and relations are redefined. The business models include new revenue streams and services, but also create the need for trade-offs between, e.g., openness and dependability in the architecture, as well as new ways of working.     

Psychological evaluation and design of work tasks: two examples

Abstract

Practical experience with flexible production automation has provoked rising demands for human oriented job design. Prospective evaluation of work tasks based on status-quo analyses with the psychological instrument VERA, developed for the assessment of the available scope of action in fulfilling the task, has led to design proposals concerning technical and organizational aspects as well as questions of training and retraining. Procedure and results are shown by presenting two case studies dealing with a small flexible manufacturing system and a planned ‘production island’.     

Using aspects for testing of embedded software: experiences from two industrial case studies

Aspect-oriented software testing is emerging as an important alternative to conventional procedural and object-oriented testing techniques. This paper reports experiences from two case studies where aspects were used for the testing of embedded software in the context of an industrial application. In the first study, we used code-level aspects for testing non-functional properties. The methodology we used for deriving test aspect code was based on translating high-level requirements into test objectives, which were then implemented using test aspects in AspectC++. In the second study, we used high-level visual scenario-based models for the test specification, test generation, and aspect-based test execution. To specify scenario-based tests, we used a UML2-compliant variant of live sequence charts. To automatically generate test code from the models, a modified version of the S2A Compiler, outputting AspectC++ code, was used. Finally, to examine the results of the tests, we used the Tracer, a prototype tool for model-based trace visualization and exploration. The results of the two case studies show that aspects offer benefits over conventional techniques in the context of testing embedded software; these benefits are discussed in detail. Finally, towards the end of the paper, we also discuss the lessons learned, including the technological and other barriers to the future successful use of aspects in the testing of embedded software in industry.     

Successfully completing case study research: combining rigour, relevance and pragmatism

The organizational and social issues associated with the development, implementation and use of computer-based information systems have increasingly attracted the attention of information systems researchers. Interest in qualitative research methods such as action research, case study research and ethnography, which focus on understanding social phenomena in their natural setting, has consequently grown. Case study research is the most widely used qualitative research method in information systems research, and is well suited to understanding the interactions between information technology-related innovations and organizational contexts. Although case study research is useful as a means of studying information systems development and use in the field, there can be practical difficulties associated with attempting to undertake case studies as a rigorous and effective method of research. This paper addresses a number of these difficulties and offers some practical guidelines for successfully completing case study research. The paper focuses on the pragmatics of conducting case study research, and draws from the discussion at a panel session conducted by the authors at the 8th Australasian Conference on Information Systems, September 1997 (ACIS 97), from the authors' practical experiences, and from the case study research literature.     

ICT and learning: Lessons from Australian classrooms

Research into Information and Communication Technologies (ICT) in schools is well into its third decade but there is still a pressing need to better understand how computer-based technologies are influencing learning opportunities, and how the local conditions of schooling impact on teachers’ attempts to integrate these technologies in their classrooms. In this article, we provide some insight into these questions through our research in six diverse public schools in the state of New South Wales (NSW), Australia. We observed classrooms and conducted interviews with teachers and other key stakeholders, such as principals and technology coordinators about the integration of ICT. Our goal was to describe and examine the ways in which teachers, in a range of settings, are utilising ICT in their classroom practices to mediate student’s learning experiences Our findings indicate that ICT is largely being integrated in ways that support and supplement existing classroom practices. From our observations, we believe that successful integration of ICT requires fundamental shifts in the core activities of schools. These shifts include new teaching. The cases described in this article suggest some ways in which these shifts may be initiated and sustained.     

The role of experience in night work: Lessons from two ergonomic studies

The purpose of this article is to analyze some connections between experience, health and work, especially in the field of night work. As a result of the baby boom, the proportion of elderly workers is steadily increasing, while at the same time many workers are reaching retirement age and being replaced by younger people. And, in the same time, there is an overall gradual increase in shift work and night work. To our knowledge, worker experience has not been extensively studied in this context. This was our focus in studying work activity in two very different situations, in a hospital and in a steel industry.In these two studies we observed that the experienced workers endeavor to plan ahead, especially at night. They do this to limit fatigue and to avoid emergencies and ensure that work is stress-free and as far as possible under control. But experience not only brings workers to plan ahead, it also enables them to do so, thanks to the resources it confers: gaining familiarity with tasks and acquiring the ability to identify critical situations, gaining knowledge about themselves and awareness of situations that cause difficulty; and gaining a better overview of the collective aspects of their work and of ways to share tasks or obtain assistance.They are able to undertake these strategies thanks to specific skills and capacities they have built along their professional career, which notably leads them to find the best trade-off between several goals, possibly contradictory.Such experience is especially valuable at night, when the worker is tired, and when there are fewer supervisors present. This experience can only be gained, however, if the work environment fosters its acquisition and provides an opportunity to make use of it, especially during the night shift and especially with respect to planning tasks ahead of time.     

Structural elements of coordination mechanisms in collaborative planning processes and their assessment through maturity models: Application to a ceramic tile company

Maturity is defined as a measure to evaluate the capabilities of an organization in regards to a certain discipline. The Collaborative Planning Process is a very complex process and Coordination mechanisms are especially relevant in this field to align the plans of the supply chain members. The objective of this paper is to develop a maturity model and a methodology to perform assessment for the Structural Elements of Coordination Mechanisms in the Collaborative Planning Process. Structural elements are specified in order to characterize coordination mechanisms in a collaborative planning context and they have been defined as key areas to be assessed by the maturity model. The identified structural elements are: number of decision-makers, collaboration level, interdependence relationships nature, interdependence relationships type, number of coordination mechanisms, information exchanged, information processing, decision sequence characteristics and stopping criteria. Structural elements are assessed using the scheme of five levels: Initial, Repeatable, Defined, Managed and Optimized. This proposal has been applied to a ceramic tile company and the results are also reported.     

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.     

The influencing causes of software unavailability: A case study from industry

Software unavailability can lead to disastrous consequences ranging from delays and cancellation to a loss of millions of dollars of technology. However, research on the causes that can make systems unavailable is still little. The aim of this paper is to investigate such causes in an industrial context using 2 qualitative approaches ((a) interview and (b) retrospective analysis) using archival data and records from a student information system. As a result, connectivity, human, hardware, storage, and software were found to be the important categories of causes for the unavailability. Besides, the critical lessons to be learned that relate to activities of software management and software business are also discussed. This includes vendor support, systems documentation, health check process, licensing, and software updating or upgrading. To strengthen the claim that our findings are promising, we compare our main findings with those of a previous study. This study can generally assist software engineering people including engineers, developers, project managers, vendors. Additionally, this paper dis cusses the threats to the study's validity and suggests open problems for future research.     

Effort, co-operation and co-ordination in an open source software project: GNOME

Abstract This paper presents results from research into open source projects from a software engineering perspective. The research methodology employed relies on public data retrieved from the CVS repository of the GNOME project and relevant discussion groups. This methodology is described, and results concerning the special characteristics of open source software development are given. These data are used for a first approach to estimating the total effort to be expended.     

Development of a knowledge management initiative and system: A case study

As knowledge emerges as the primary strategic resource in the 21st century, many firms in the manufacturing and service sectors alike are beginning to introduce and implement Knowledge Management (KM). Organisations can certainly benefit from its application for enhanced decision support, efficiency and innovation, thus helping them to realise their strategic mission. However, KM is an emerging paradigm, and not many organisations have a clear idea of how to proceed with it. This paper presents the results of a case study conducted in one company in the United Kingdom (UK), the major aim being to identify how it has developed a KM initiative and system. Hopefully, the information extracted from this study will be beneficial to other organisations that are attempting to implement KM or to those that are in the throes of adopting it.     

Individual and group-based learning from complex cognitive tasks: Effects on retention and transfer efficiency

The effects of individual versus group learning (in triads) on efficiency of retention and transfer test performance in the domain of biology (heredity) among 70 high-school students were investigated. Applying cognitive load theory, the limitations of the working memory capacity at the individual level were considered an important reason to assign complex learning tasks to groups rather than to individuals. It was hypothesized that groups will have more processing capacity available for relating the information elements to each other and by doing so for constructing higher quality cognitive schemata than individuals if the high cognitive load imposed by complex learning tasks could be shared among group members. In contrast, it was expected that individuals who learn from carrying out the same complex tasks would need all available processing capacity for remembering the interrelated information elements, and, consequently, would not be able to allocate resources to working with them. This interaction hypothesis was confirmed by the data on efficiency of retention and transfer test performance; there was a favorable relationship between mental effort and retention test performance for the individual learners as opposed to a favorable relationship between transfer test performance and mental effort for the students who learned in groups.     

An approach to analyzing and planning post-merger IS integration: Insights from two field studies

Information systems (IS) integration is among the most challenging tasks in corporate mergers and acquisitions (M&As). In this paper we propose and illustrate the use of an approach to analyzing and planning post-merger IS integration that extends general theory for IS planning, considering the specific characteristics of the M&A context. We highlight that planning effectiveness is possible to achieve in fundamentally different ways, dependent on the characteristics of the merger or acquisition at hand.

Approximate Common Knowledge and Co-ordination: Recent Lessons from Game Theory

The importance of the notion of common knowledge in sustaining cooperative outcomes in strategic situations is well appreciated. However, the systematic analysis of the extent to which small departures from common knowledge affect equilibrium in games has only recently been attempted.We review the main themes in this literature, in particular, the notion of common p-belief. We outline both the analytical issues raised, and the potential applicability of such ideas to game theory, computer science and the philosophy of language.