Search

China Reporting is an oral history showing how the China correspondent of the 1930s and 1940s constructed his or her news reality or the network of facts from which their stories were written. How these men and women pooled information and decided upon the legitimacy of particular sources is explored. The influences of competition, language facility (or lack thereof), common personal backgrounds, camaraderie, and changes in American official China policy are also discussed, with special attention paid to the prescriptive, gatekeeping role of editors back home. This is an approach which has often been applied to the domestic journalist. China Reporting is a pioneering effort at using historical perspective to view the foreign correspondent in terms fo the total epistemological context in which he or she operates to produce the news that in turn provides the data base upon which the public and policy makers inevitably draw. This title is part of UC Press's Voices Revived program, which commemorates University of California Press’s mission to seek out and cultivate the brightest minds and give them voice, reach, and impact. Drawing on a backlist dating to 1893, Voices Revived makes high-quality, peer-reviewed scholarship accessible once again using print-on-demand technology. This title was originally published in 1987.

"China Reporting documents the gathering of American journalists, diplomats and China scholars, "old China hands" all, who met in 1982 to discuss their experience in China. In 1982, a group of reporters and diplomats who had been in China between 1930 and 1950 met in Scottsdale, Ariz., to discuss press coverage of events in those years. Among them were John Hersey, John Fairbank and Annalee Jacoby Fadiman. These excerpts from the conference transcript suggest that those attending generally praised what they perceived to be their objectivity and ability to overcome censorship. MacKinnon, who teaches at Arizona State, and Friesen, an engineer, are less laudatory, pointing out that the inability of most Americans in China during that crucial period to speak the language rendered them incapable of discerning popular sentiment."--From Publishers Weekly.

When programmers and system analysts read existing code the understanding of what objective that code is intended to achieve is partial at best. The meaning of the code is not precise. There is a way to proof-read existing code and reveal its original intent. We wrote this book to provide a means to improve the readability, correctness and understanding of the code's purpose. This is especially relevant to system design when multiple new and existing programs are brought together to act in unison. We have accomplished this by using formal methods, and we have demonstrated the practicality of our technique by applying it within a for-profit company. In this book we introduce the basic concepts for designing, using and implementing software integrity assurance mechanisms that can provide fault-free software as well as a dependable approach to understand existing code and to support the integration of new code into existing systems. What we mean by software integrity assurance is not the same as quality assurance, which is traditionally a part of a Master of Software Engineering or Master of Computer Science degree with a Software Engineering emphasis. Software quality assurance encompasses the entire panoply of software development processes, including requirements definition, software design, coding, configuration management, testing and product integration. The use of formal methods is generally absent from the software quality assurance curriculum.Software integrity assurance, as used by us in this book, is more focused on code analysis and elimination of faults that have been introduced during the software development and maintenance phases. Our goal is to educate the reader rather than pretending to provide a magic bullet. We show the reader how to make systems cybersecure by striving to achieve fault-free systems. Our approach emphasizes the importance of using formal methods, and we explain how they form the underpinning of program and system analysis, as opposed to tracing execution paths and relying on what we call operational techniques such as test and evaluation. Software Integrity Assessment, or SIA for short, refers to our unique approach that enables you to assess the integrity of any software program or system. The book is part theory and research and another part textbook. As a first step toward fulfilling the textbook appellation we provide a summary at the end of each chapter. We intend that this summary will help the reader to more readily grasp and understand some of the more abstruse content. The idea is that the items listed in the summaries can easily be converted into exercises for the reader to solve. The intended audience for this book includes software tool designers and developers. It introduces and explains a unique way to think about software produced by others. After reading this book the reader should understand how formal methods can be used to analyze and find faults in existing software programs and systems. To realize the value of the contents to their fullest a tool needs to be developed that automates the processes described here. We have used formal methods wherever possible to facilitate the development of such a tool. Ideally the tool would translate procedural source code from a diverse set of programming languages into the formally defined declarative language we call Dijkstra Guarded Commands or DGC.