The primary aim for this book is to gather and collate articles which represent the best and latest thinking in the domain of technology transfer, from research, academia and practice around the world. We envisage that the book will, as a result of this, represent an important source of knowledge in this domain to students (undergraduate and postgraduate), researchers, practitioners and consultants, chiefly in the software engineering and IT/industries, but also in management and other organisational and social disciplines. An important aspect of the book is the role that reflective practitioners (and not just academics) play. They will be involved in the production, and evaluation of contributions, as well as in the design and delivery of conference events, upon which of course, the book will be based.

This book was written primarily for all those DTP users and programmers who want to keep up with the rapid development of electronic publishing, particular those who wish to develop new systems for the output of typefaces. In this volume, various formats are presented, their properties discussed and production requirements analyzed. Appendices provide readers additional information, largely on digital formats for typeface storage.

An effective systems development and design process is far easier to explain than it is to implement. A framework is needed that organizes the life cycle activities that form the process. This framework is Configuration Management (CM). Software Configuration Management discusses the framework from a standards viewpoint, using the original

This volume combines the proceedings of the 1987 SEI Conference on Software Engineering Education, held in Monroeville, Pennsylvania on April 30 and May 1, 1987, with the set of papers that formed the basis for that conference. The conference was sponsored by the Software Engineering Institute (SEI) of Carnegie-Mellon University. SEI is a federally-funded research and development center established by the United States Department of Defense to improve the state of software technology. The Education Division of SEI is charged with improving the state of software engineering education. This is the third volume on software engineering education to be pub lished by Springer-Verlag. The first (Software Engineering Education: Needs and Objectives, edited by Tony Wasserman and Peter Freeman) was published in 1976. That volume documented a workshop in which educa tors and industrialists explored needs and objectives in software engineering education. The second volume (Software Engineering Education: The Educational Needs of the Software Community, edited by Norm Gibbs and Richard Fairley) was published in 1986. The 1986 volume contained the proceedings of a limited attendance workshop held at SEI and sponsored by SEI and Wang Institute. In contrast to the 1986 Workshop, which was limited in attendance to 35 participants, the 1987 Conference attracted approximately 180 participants.

Strategic Defense Initiative examines developments in the technologies currently being researched under SDI. The OTA does not repeat the work of its earlier reports but gives special attention to filling in gaps in those reports and to describing technical progress made in the intervening period. The report also presents information on the prospects for functional survival against preemptive attack of alternative ballistic missile defense system architectures now being considered under the SDI. Finally, it analyzes the feasibility of developing reliable software to perform the battle management tasks required by such system architectures.

It. is well known that t.he introduction of a new technology in one organization not always produces the intended benefits (Levine, 1994). In many cases, either the receivers do not reach the intended level of use or simply the technology is rejected because it does not match with the expectations (true or false) and the accepted psychological effort to use it. The case of formal methods is a paradigmatic example of continual failures. The published cases with problems or failures only constitute the visible part of a large iceberg of adoption cases. It. is difficult to get companies to openly express the problems they had; however, from the experience of the author, failure cases are very common and they include any type of company. Many reasons to explain the failures (and in some cases the successes) could be postulated; however, the experiences are not structured enough and it is difficult to extract from them useful guidelines for avoiding future problems. Generally speaking, there is a trend to find the root of the problems in the technol ogy itself and in its adequacy with the preexistent technological context. Technocratic technology transfer models describe the problems in terms of these aspects. Although it is true that those factors limit the probability of success, there is another source of explanations linked to the individuals and working teams and how they perceive the technology.

This is the first handbook to cover comprehensively both software engineering and knowledge engineering - two important fields that have become interwoven in recent years. Over 60 international experts have contributed to the book. Each chapter has been written in such a way that a practitioner of software engineering and knowledge engineering can easily understand and obtain useful information. Each chapter covers one topic and can be read independently of other chapters, providing both a general survey of the topic and an in-depth exposition of the state of the art. Practitioners will find this handbook useful when looking for solutions to practical problems. Researchers can use it for quick access to the background, current trends and most important references regarding a certain topic.The handbook consists of two volumes. Volume One covers the basic principles and applications of software engineering and knowledge engineering.Volume Two will cover the basic principles and applications of visual and multimedia software engineering, knowledge engineering, data mining for software knowledge, and emerging topics in software engineering and knowledge engineering.

Computer Aided Software Engineering (CASE) tools typically support individual users in the automation of a set of tasks within a software development process. Such tools have helped organizations in their efforts to develop better software within budget and time constraints. However, many organizations are failing to take full advantage of CASE technology as they struggle to make coordinated use of collections of tools, often obtained at different times from different vendors. This book provides an in-depth analysis of the CASE tool integration problem, and describes practical approaches that can be used with current CASE technology to help your organization take greater advantage of integrated CASE.

This well structured book discusses lifecycle optimization of software projects for crisis management by means of software engineering methods and tools. Its outcomes are based on lessons learned from the software engineering crisis which started in the 1960s. The book presents a systematic approach to overcome the crisis in software engineering depends which not only depends on technology-related but also on human-related factors. It proposes an adaptive methodology for software product development, which optimizes the software product lifecycle in order to avoid “local” crises of software production. The general lifecycle pattern and its stages are discussed, and their impact on the time and budget of the software product development is analyzed. The book identifies key advantages and disadvantages for various models selected and concludes that there is no “silver bullet”, or universal model, which suits all software products equally well. It approaches software architecture in terms of process, data and system perspectives and proposes an incremental methodology for crisis-agile development of large-scale, distributed heterogeneous applications. The book introduces a number of specialized approaches which are widely used in industry but are often ignored in general writings because of their vendor-specificity. In doing so, the book builds a helpful bridge from academic conceptions of software engineering to the world of software engineering practice. With its systematic coverage of different software engineering methodologies and the presented rich systems engineering examples the book will be beneficial for a broader audience.

Focus on masters' level education in software engineering. Topics discussed include: software engineering principles, current software engineering curricula, experiences with ex- isting courses, and the future of software engineering edu- cation.