The Case Study Method and The Methodology of Business History

In this brief paper I place the case study method within the methodology of business history and in a broader perspectiveof researching business and management. I also illustrate the sue of case studies as a pedagogical tool and itsimplications for the teaching of MBAs in Latin America.Keywords: Business history, method, case study, MBA, Latin Americ

Re-mining item associations: methodology and a case study in apparel retailing

Association mining is the conventional data mining technique for analyzing market basket data and it reveals the positive and negative associations between items. While being an integral part of transaction data, pricing and time information have not been integrated into market basket analysis in earlier studies. This paper proposes a new approach to mine price, time and domain related attributes through re-mining of association mining results. The underlying factors behind positive and negative relationships can be characterized and described through this second data mining stage. The applicability of the methodology is demonstrated through the analysis of data coming from a large apparel retail chain, and its algorithmic complexity is analyzed in comparison to the existing techniques

A Methodology for Safety Case Development

This paper will outline a safety case methodology that seeks to minimise safety risks and commercial risks by constructing a demonstrable safety case. The safety case ideas presented here were initially developed in an EU-sponsored SHIP project [1] and was then further developed in the UK Nuclear Safety Research Programme (the QUARC Project [2]). Some of these concepts have subsequently been incorporated in safety standards such as MOD Def Stan 00-55, and have also been used to establish specific safety cases for clients. A generalisation of the concepts also appears in Def Stan 00-42 Part 2, in the form of the software reliability case

Designinig Coordination among Human and Software Agents

The goal of this paper is to propose a new methodology for designing coordination between human angents and software agents and, ultimately, among software agents. The methodology is based on two key ideas. The first is that coordination should be designed in steps, according to a precise software engineering methodology, and starting from the specification of early requirements. The second is that coordination should be modeled as dependency between actors. Two actors may depend on one another because they want to achieve goals, acquire resources or execute a plan. The methodology used is based on Tropos, an agent oriented software engineering methodology presented in earlier papers. The methodology is presented with the help of a case study

A methodology for prospective operational design co-ordination

Engineering companies are continually faced with the challenge of how best to utilise their design team given some design project. Decisions regarding how to distribute the project workload amongst the members of the design team are the responsibility of a project manager who, in order to do this, often relies upon previous experience and/or the support of some planning tool. Furthermore, a project manager rarely has the opportunity to assess the capability of the design team against the current work load in order to determine what, if any, alterations couldbe made to the team to facilitate appropriate reductions in project time and cost.This paper proposes a mathematical-based methodology aimed at identifying shortfalls in design teams, which if remedied would result in a more efficient project in terms of time and cost. The methodology provides a means of identifying those skills within the design team,with respect to the outstanding work load, in which improvements would have the greatest influence on reducing time and cost. In addition, the methodology employs a genetic algorithm for the purpose of scheduling tasks to be undertaken by potential design teams. The methodology is applied to two practical case studies provided by engineering industry.The first case study involves the assessment of a multi-disciplined design team consisting of single-skilled engineers. In contrast, the second case study entails the assessment of multiskilled engineers within a multi-disciplined design team. As a result of applying the methodology to the case studies, potential improvement to the design teams are identified and, subsequently, evaluated by observing their effects

Total data quality management: a study of bridging rigor and relevance

Ensuring data quality is of crucial importance to organizations. The Total Data Quality Management (TDQM) theory provides a methodology to ensure data quality. Although well researched, the TDQM methodology is not easy to apply. In the case of Honeywell Emmen, we found that the application of the methodology requires considerable contextual redesign, flexibility in use, and the provision of practical tools. We identified team composition, toolsets, development of obvious actions, the design of phases, steps, and actions, and sessions as vital elements of making an academically rooted methodology applicable. Such an applicable methodology, we name “well articulated”, because it incorporates the existing academic theory and it is made operational. This enables the methodology to be systematically beta tested and made useful for different organizational conditions