Using Valuation-Based Decision Making to Increase the Efficiency of China\u27s Patent Subsidy Strategies

[Excerpt] “The Chinese government has grown concerned that its patent fee subsidy programs have not funded the most deserving patents, and thus they no longer wish to spend public resources to promote low-value patents. Instead, the government would prefer subsidy programs that encourage the most deserving patents. The Patent Strategy reflects this desire, as the fourth strategic focus of the Patent Strategy recognizes the need to “[o]ptimize [China’s] patent subsidy policy and further define the orientation to enhance patent quality.”19 This Article explains how a disciplined and transparent valuation-based decision making process can help the Chinese government design patent fee subsidy programs that allocate funds more consistently to deserving patents. In addition, this Article offers the outline of a practical valuation model the Chinese government could use to filter patent fee subsidy requests.

Improving Prolog programs: Refactoring for Prolog

Refactoring is an established technique from the object-oriented (OO) programming community to restructure code: it aims at improving software readability, maintainability and extensibility. Although refactoring is not tied to the OO-paradigm in particular, its ideas have not been applied to Logic Programming until now. This paper applies the ideas of refactoring to Prolog programs. A catalogue is presented listing refactorings classified according to scope. Some of the refactorings have been adapted from the OO-paradigm, while others have been specifically designed for Prolog. The discrepancy between intended and operational semantics in Prolog is also addressed by some of the refactorings. In addition, ViPReSS, a semi-automatic refactoring browser, is discussed and the experience with applying ViPReSS to a large Prolog legacy system is reported. The main conclusion is that refactoring is both a viable technique in Prolog and a rather desirable one.Comment: To appear in Theory and Practice of Logic Programming (TPLP

Cost-Benefit Analysis Applied to Personnel/Human Resource Management Decisions

[Excerpt] Every model for improving quality in manufacturing or service emphasizes the need to understand customer or client needs, measure achievements in terms of those needs, and use measurements to adjust processes so that the needs are better met. For many clients of the personnel functions, such as line managers and shareholders, meeting their needs means demonstrating competitive return on investment. In a very real sense, the resources used to support human resource programs/processes could also be used to buy new equipment, pay stock dividends, or purchase raw materials. Thus, the results of personnel investments must produce enough value to justify shifting the resources from these other purposes. Cost-benefit analysis provides a framework and system for understanding what information best reflects the needs of clients, and how to organize and use that information so that progress toward meeting client needs is clearly evident. Cost-benefit analysis shifts the focus away from simply improving personnel processes and toward improving personnel business outcomes

A heuristic-based approach to code-smell detection

Encapsulation and data hiding are central tenets of the object oriented paradigm. Deciding what data and behaviour to form into a class and where to draw the line between its public and private details can make the difference between a class that is an understandable, flexible and reusable abstraction and one which is not. This decision is a difficult one and may easily result in poor encapsulation which can then have serious implications for a number of system qualities. It is often hard to identify such encapsulation problems within large software systems until they cause a maintenance problem (which is usually too late) and attempting to perform such analysis manually can also be tedious and error prone. Two of the common encapsulation problems that can arise as a consequence of this decomposition process are data classes and god classes. Typically, these two problems occur together – data classes are lacking in functionality that has typically been sucked into an over-complicated and domineering god class. This paper describes the architecture of a tool which automatically detects data and god classes that has been developed as a plug-in for the Eclipse IDE. The technique has been evaluated in a controlled study on two large open source systems which compare the tool results to similar work by Marinescu, who employs a metrics-based approach to detecting such features. The study provides some valuable insights into the strengths and weaknesses of the two approache

Fuzzy memoization for floating-point multimedia applications

Instruction memoization is a promising technique to reduce the power consumption and increase the performance of future low-end/mobile multimedia systems. Power and performance efficiency can be improved by reusing instances of an already executed operation. Unfortunately, this technique may not always be worth the effort due to the power consumption and area impact of the tables required to leverage an adequate level of reuse. In this paper, we introduce and evaluate a novel way of understanding multimedia floating-point operations based on the fuzzy computation paradigm: performance and power consumption can be improved at the cost of small precision losses in computation. By exploiting this implicit characteristic of multimedia applications, we propose a new technique called tolerant memoization. This technique expands the capabilities of classic memoization by associating entries with similar inputs to the same output. We evaluate this new technique by measuring the effect of tolerant memoization for floating-point operations in a low-power multimedia processor and discuss the trade-offs between performance and quality of the media outputs. We report energy improvements of 12 percent for a set of key multimedia applications with small LUT of 6 Kbytes, compared to 3 percent obtained using previously proposed techniques.Peer ReviewedPostprint (published version

Improving Prolog Programs: Refactoring for Prolog

Refactoring is an established technique from the OO-community to restructure code: it aims at improving software readability, maintainability and extensibility. Although refactoring is not tied to the OO-paradigm in particular, its ideas have not been applied to Logic Programming until now. This paper applies the ideas of refactoring to Prolog programs. A catalogue is presented listing refactorings classified according to scope. Some of the refactorings have been adapted from the OO-paradigm, while others have been specifically designed for Prolog. Also the discrepancy between intended and operational semantics in Prolog is addressed by some of the refactorings. In addition, ViPReSS, a semi-automatic refactoring browser, is discussed and the experience with applying \vipress to a large Prolog legacy system is reported. Our main conclusion is that refactoring is not only a viable technique in Prolog but also a rather desirable one.Comment: To appear in ICLP 200