摘要 :
In 'The limiting case: sublime or ridiculous?' (Stephenson, 2015) we took half a dozen examples which children at different levels could examine. Here we take six more (continuing the numbering in the previous piece) - and a condi...
展开
In 'The limiting case: sublime or ridiculous?' (Stephenson, 2015) we took half a dozen examples which children at different levels could examine. Here we take six more (continuing the numbering in the previous piece) - and a conditional one as no. 13. The rough levels are respectively:
收起
摘要 :
The case-case study design is a potentially useful tool for infection preventionists during outbreak or cluster investigations. This column clarifies terminology related to case-case, case-control, and case-case-control study desi...
展开
The case-case study design is a potentially useful tool for infection preventionists during outbreak or cluster investigations. This column clarifies terminology related to case-case, case-control, and case-case-control study designs. Examples of practical applications of the case-case study design include determining risk factors for health care-onset versus community-onset infections, or antibiotic-resistant versus antibiotic-susceptible infections. (C) 2019 Association for Professionals in Infection Control and Epidemiology, Inc. Published by Elsevier Inc. All rights reserved.
收起
摘要 :
The Wind Riders of the Lost River Range (WRLRR) is a modular project-based simulated case study. This case study is designed to accompany a hands-on collaborative semester project for a variety of software development courses. The...
展开
The Wind Riders of the Lost River Range (WRLRR) is a modular project-based simulated case study. This case study is designed to accompany a hands-on collaborative semester project for a variety of software development courses. The case can be used in courses like Systems Analysis and Design, Database Design, Software Engineering, and Software Development. The case provides a detailed account of a situation that closely simulates a real-world problem. This challenging experiential learning opportunity reinforces course concepts through their application in a realistic scenario. WRLRR has been developed using the modular design of teaching cases approach. This approach makes it possible to swap modules in and out of the case. This reduces instructor workload by making it unnecessary to develop a new case from scratch for each course iteration. It also discourages students from recycling solutions from previous courses because the case scenario has been altered. Adding or removing modules makes it possible to sufficiently vary the case study to refine the problem being addressed. Macros are provided to automate, and thereby facilitate, the insertion of modules.
收起
摘要 :
Dr. J. K. Suresh, Vice President and Principal Knowledge Manager at Infosys Limited (Infosys), pondered a question that continually needed to be addressed, but never could be truly answered. For a number of years, he had been resp...
展开
Dr. J. K. Suresh, Vice President and Principal Knowledge Manager at Infosys Limited (Infosys), pondered a question that continually needed to be addressed, but never could be truly answered. For a number of years, he had been responsible for overseeing the internal knowledge management (KM) activities of the large, global IT-services company, headquartered in Bangalore, India. The existing system was widely recognized—in case studies, articles and books—for its excellence. But the company, whose revenues for FY 2013 were in excess of $7 billion, was evolving rapidly in its business model. What changes to the KM system, if any, would improve the company’s ability to move its services to the next level?The particular challenge of greatest long term interest was presented by the company’s Products, Platforms, and Solutions (PP&S) operations, seen by many at Infosys as being crucial to the firm’s long term prosperity. Margins on the offshoring of support and routine development activities—the business that had been the bread-and-butter of Infosys as it grew—were becoming narrower, squeezed both by increasing competition and by rising personnel costs in countries like India. An important remedy to this pressure was to develop software products that the company could sell to its customers as part of a larger package, building an asset category that did go home every night. For KM to benefit these PP&S activities, however, a substantially different focus would likely be required. Traditionally, KM at Infosys had been inward focus, facilitating the exchange of code and experience between the company’s employees, currently numbering over 150,000. Where KM could be of greatest help to PP&S, would be in looking outward—e.g., identifying market trends and desirable features, capturing customer experiences, developing sales strategies, finding market niches. Could a system that was designed principally for internal use later be modified for these purposes? Or would it make more sense to build a new system from the ground up? And what might such as system look like?.
收起
摘要 :
A case study is expected to capture the complexity of a single case, which should be a functioning unit, be investigated in its natural context with a multitude of methods, and be contemporary. A case study and, normally, history ...
展开
A case study is expected to capture the complexity of a single case, which should be a functioning unit, be investigated in its natural context with a multitude of methods, and be contemporary. A case study and, normally, history focus on one case, but simultaneously take account of the context, and so encompass many variables and qualities. When a physical artefact is the case the gap between case study and history tends to diminish and case studies often become more or less historical case studies. Case study methodology also bridges the gap between quantitative and qualitative methods in the social sciences. Still the different concepts of validation in quantitative and qualitative research sometimes create confusion when they are combined, as they often are in case studies.
The case might be studied with an intrinsic interest in the case as such, or with an interest in generalising. When a generalisation is based on the deductive principle, the procedure of testing hypothesis is used. A second mode of generalisation is inductive theory-generation, or conceptualisation. The third mode depends on the principle of abduction. Abduction is the process of facing an unexpected fact, applying some rule and, as a result, positing a case that may be. But there are two kinds of abduction: One is when a case is created from a few facts; for instance, historical data or clues. The other is operative when generalisations are made from known cases and applied to an actual problem situation by making appropriate comparisons. This is also called naturalistic generalisation. In a case study, the different modes of generalisation are often combined.
The conclusion is that case studies has the potential for further development through the mastery of the combination on different levels of techniques, methodologies, strategies, or theories, like; the combination of case study and history, which is important when the case is an artefact; the combination of differing quality standards in qualitative and quantitative research, which are difficult to codify; and the combination of different modes of generalisation.
收起
摘要 :
Designed for Discussion: JITE-DC cases offer a detailed perspective on a situation that leads up to a set of decisions or plans that need to be developed by students over the course of their preparation and discussion. They are no...
展开
Designed for Discussion: JITE-DC cases offer a detailed perspective on a situation that leads up to a set of decisions or plans that need to be developed by students over the course of their preparation and discussion. They are not intended to be examples or illustrations about which an instructor can lecture. They are not designed to be in-depth extended word problems that students “solve”. They are built as showcases for specific technologies or techniques of the sort that frequently appear on vendor sites.
收起
摘要 :
John Burger, the founding member of house4hack, despite his passion for social good using practical innovation, was fully aware of the cost of getting people and organizations actively involved in social enterprises. The successfu...
展开
John Burger, the founding member of house4hack, despite his passion for social good using practical innovation, was fully aware of the cost of getting people and organizations actively involved in social enterprises. The successful electrical and electronics engineer with a number of academic (PhD and Masters – cum laude) and corporate accolades (executive in a top firm) had already been at the top of the corporate ladder. But despite the success, his stronger desire to see South Africa become a net producer of IT and technical artifacts rather than a net importer had led him to rethink his entire life strategy. After deep discussions on the merits of free and open source software development with two friends, they decided to start house4hack as a non-profit organization. The main purpose of house4hack was to provide an innovative environment, a hacker space, where members could conceptualise and create innovative technical artifacts which are well suited for the South African and African environment. The emphasis of house4hack was on making available technical equipment and working space so that members had an environment in which they could experiment and develop technical artifacts. An example of a technical artefact that emerged from house4hack is Robohand. Robohand is a mechanically driven artificial hand printed using 3D technology. Robohand has depended exclusively on donations to develop and distribute artificial hands to people who cannot afford them, such as in the war torn areas of South Sudan.It was now three years since house4hack started. The hacker space was exciting, new ideas and opportunities kept emerging at the Tuesday meet ups where members and visitors networked and collaborated on new techniques or technology they had come across. But despite the liveliness, there were some key questions and critical decisions on John’s mind:1.How do we get more people involved in creating artifacts?2.Where do we find seed funding to support house4hack?3.Are we serving Africa well enough with relevant artifacts?4.Am I falling right back into the corporate work lifestyle trap?.
收起
摘要 :
Case-based reasoning systems need to maintain their case base in order to avoid performance degradation. Degradation mainly results from memory swamping or exposure to harmful experiences and so, it becomes vital to keep a compact...
展开
Case-based reasoning systems need to maintain their case base in order to avoid performance degradation. Degradation mainly results from memory swamping or exposure to harmful experiences and so, it becomes vital to keep a compact, competent case base. This paper proposes an adaptive case-based reasoning model that develops the case base during the reasoning cycle by adding and removing cases. The rationale behind this approach is that a case base should develop over time in the same way that a human being evolves her overall knowledge: by incorporating new useful experiences and forgetting invaluable ones. Accordingly, our adaptive case-based reasoning model evolves the case base by using a measure of "case goodness" in different retention and forgetting strategies. This paper presents empirical studies of how the combination of this new goodness measure and our adaptive model improves three different performance measures: classification accuracy, efficiency and case base size.
收起
摘要 :
To my knowledge, no other software engineering language construct as significant as use cases has been adopted so quickly and so widely among practitioners. I believe this is because use cases play a role in so many different aspe...
展开
To my knowledge, no other software engineering language construct as significant as use cases has been adopted so quickly and so widely among practitioners. I believe this is because use cases play a role in so many different aspects of software engineering. Although I first used the term in 1986, I had actually been working on and evolving the concept of use cases since 1967. So many people have asked me how I came up with this concept that I decided to write this article to explain the origins and evolution of use cases. I'll also summarize what they have helped us achieve so far, and then suggest a few improvements for the future.
收起
原文获取