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.

In the Guide to the Software Engineering Body of Knowledge (SWEBOK(R) Guide), the IEEE Computer Society establishes a baseline for the body of knowledge for the field of software engineering, and the work supports the Society's responsibility to promote the advancement of both theory and practice in this field. It should be noted that the Guide does not purport to define the body of knowledge but rather to serve as a compendium and guide to the knowledge that has been developing and evolving over the past four decades. Now in Version 3.0, the Guide's 15 knowledge areas summarize generally accepted topics and list references for detailed information. The editors for Version 3.0 of the SWEBOK(R) Guide are Pierre Bourque (Ecole de technologie superieure (ETS), Universite du Quebec) and Richard E. (Dick) Fairley (Software and Systems Engineering Associates (S2EA)).

This tutorial book presents an augmented selection of the material presented at the Software Engineering Education and Training Track at the International Conference on Software Engineering, ICSE 2005, held in St. Louis, MO, USA in May 2005. The 12 tutorial lectures presented cover software engineering education, state of the art and practice: creativity and rigor, challenges for industries and academia, as well as future directions.

Over the past decade, software engineering has developed into a highly respected field. Though computing and software engineering education continues to emerge as a prominent interest area of study, few books specifically focus on software engineering education itself. Software Engineering: Effective Teaching and Learning Approaches and Practices presents the latest developments in software engineering education, drawing contributions from over 20 software engineering educators from around the globe. Encompassing areas such as student assessment and learning, innovative teaching methods, and educational technology, this much-needed book greatly enhances libraries with its unique research content.

This book identifies challenges and opportunities in the development and implementation of software that contain significant statistical content. While emphasizing the relevance of using rigorous statistical and probabilistic techniques in software engineering contexts, it presents opportunities for further research in the statistical sciences and their applications to software engineering. It is intended to motivate and attract new researchers from statistics and the mathematical sciences to attack relevant and pressing problems in the software engineering setting. It describes the "big picture," as this approach provides the context in which statistical methods must be developed. The book's survey nature is directed at the mathematical sciences audience, but software engineers should also find the statistical emphasis refreshing and stimulating. It is hoped that the book will have the effect of seeding the field of statistical software engineering by its indication of opportunities where statistical thinking can help to increase understanding, productivity, and quality of software and software production.

This tutorial book presents an augmented selection of the material presented at the Software Engineering Education and Training Track at the International Conference on Software Engineering, ICSE 2005, held in St. Louis, MO, USA in May 2005. The 12 tutorial lectures presented cover software engineering education, state of the art and practice: creativity and rigor, challenges for industries and academia, as well as future directions.

An industry insider explains why there is so much bad software—and why academia doesn't teach programmers what industry wants them to know. Why is software so prone to bugs? So vulnerable to viruses? Why are software products so often delayed, or even canceled? Is software development really hard, or are software developers just not that good at it? In The Problem with Software, Adam Barr examines the proliferation of bad software, explains what causes it, and offers some suggestions on how to improve the situation. For one thing, Barr points out, academia doesn't teach programmers what they actually need to know to do their jobs: how to work in a team to create code that works reliably and can be maintained by somebody other than the original authors. As the size and complexity of commercial software have grown, the gap between academic computer science and industry has widened. It's an open secret that there is little engineering in software engineering, which continues to rely not on codified scientific knowledge but on intuition and experience. Barr, who worked as a programmer for more than twenty years, describes how the industry has evolved, from the era of mainframes and Fortran to today's embrace of the cloud. He explains bugs and why software has so many of them, and why today's interconnected computers offer fertile ground for viruses and worms. The difference between good and bad software can be a single line of code, and Barr includes code to illustrate the consequences of seemingly inconsequential choices by programmers. Looking to the future, Barr writes that the best prospect for improving software engineering is the move to the cloud. When software is a service and not a product, companies will have more incentive to make it good rather than “good enough to ship."

This book constitutes invited papers from the First International Workshop on Frontiers in Software Engineering Education, FISEE 2019, which took place during November 11-13, 2019, at the Château de Villebrumier, France. The 25 papers included in this volume were considerably enhanced after the conference and during two different peer-review phases. The contributions cover a wide range of problems in teaching software engineering and are organized in the following sections: Course experience; lessons learnt; curriculum and course design; competitions and workshops; empirical studies, tools and automation; globalization of education; and learning by doing. The final part "TOOLS Workshop: Artificial and Natural Tools (ANT)" contains submissions presented at a different, but related, workshop run at Innopolis University (Russia) in the context of the TOOLS 2019 conference. FISEE 2019 is part of a series of scientific events held at the new LASER center in Villebrumier near Montauban and Toulouse, France.

This volume constitutes the proceedings of the 8th Conference on Software Engineering Education, SEI CSEE 1995, held in New Orleans, Louisiana, USA in March/April 1995. The volume presents 25 carefully selected full papers by researchers, educators, trainers and managers from the relevant academic, industrial and governmental communities; in addition there are abstracts of keynote speeches, panels, and tutorials. The topics covered include curriculum issues: Goals - what should we be teaching.- Process issues.- Software engineering in special domains.- Requirements and designs.- People, management, and leadership skills.- Technology issues.- Education and training - needs and trends.

Today, software engineers need to know not only how to program effectively but also how to develop proper engineering practices to make their codebase sustainable and healthy. This book emphasizes this difference between programming and software engineering. How can software engineers manage a living codebase that evolves and responds to changing requirements and demands over the length of its life? Based on their experience at Google, software engineers Titus Winters and Hyrum Wright, along with technical writer Tom Manshreck, present a candid and insightful look at how some of the world’s leading practitioners construct and maintain software. This book covers Google’s unique engineering culture, processes, and tools and how these aspects contribute to the effectiveness of an engineering organization. You’ll explore three fundamental principles that software organizations should keep in mind when designing, architecting, writing, and maintaining code: How time affects the sustainability of software and how to make your code resilient over time How scale affects the viability of software practices within an engineering organization What trade-offs a typical engineer needs to make when evaluating design and development decisions