Software engineers are increasingly becoming business people; Professional Issues in Software Engineering, 3rd Edition gives them comprehensive coverage of the issues they should know about. While most books look at programs related to software engineering rather than the context in which they are used, this book covers the major developments that have occured in recent years, such as the Internet, Data Protection Act, and changes to the legal status of software engineers. This updated edition of a successful textbook is for undergraduate and graduate students as well as for professionals in software engineering and computer science.

Nowadays software engineers not only have to worry about the technical knowledge needed to do their job, but they are increasingly having to know about the legal, professional and commercial context in which they must work. With the explosion of the Internet and major changes to the field with the introduction of the new Data Protection Act and the legal status of software engineers, it is now essential that they have an appreciation of a wide variety of issues outside the technical. Equally valuable to both students and practitioners, it brings together the expertise and experience of leading academics in software engineering, law, industrial relations, and health and safety, explaining the central principles and issues in each field and shows how they apply to software engineering.

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 book addresses the topic of software design: how to decompose complex software systems into modules (such as classes and methods) that can be implemented relatively independently. The book first introduces the fundamental problem in software design, which is managing complexity. It then discusses philosophical issues about how to approach the software design process and it presents a collection of design principles to apply during software design. The book also introduces a set of red flags that identify design problems. You can apply the ideas in this book to minimize the complexity of large software systems, so that you can write software more quickly and cheaply."--Amazon.

Professional IT practitioners need not only the appropriate technical skills, but also a broad understanding of the context in which they operate. This book provides a unique introduction to: social, legal, financial, organizational and ethical issues in the context of the IT industry; the role of professional codes of conduct and ethics; and key legislation. It is designed to accompany the BCS Professional Examination Core Diploma Module: Professional Issues in Information Systems Practice.

This book is a broad discussion covering the entire software development lifecycle. It uses a comprehensive case study to address each topic and features the following: A description of the development, by the fictional company Homeowner, of the DigitalHome (DH) System, a system with "smart" devices for controlling home lighting, temperature, humidity, small appliance power, and security A set of scenarios that provide a realistic framework for use of the DH System material Just-in-time training: each chapter includes mini tutorials introducing various software engineering topics that are discussed in that chapter and used in the case study A set of case study exercises that provide an opportunity to engage students in software development practice, either individually or in a team environment. Offering a new approach to learning about software engineering theory and practice, the text is specifically designed to: Support teaching software engineering, using a comprehensive case study covering the complete software development lifecycle Offer opportunities for students to actively learn about and engage in software engineering practice Provide a realistic environment to study a wide array of software engineering topics including agile development Software Engineering Practice: A Case Study Approach supports a student-centered, "active" learning style of teaching. The DH case study exercises provide a variety of opportunities for students to engage in realistic activities related to the theory and practice of software engineering. The text uses a fictitious team of software engineers to portray the nature of software engineering and to depict what actual engineers do when practicing software engineering. All the DH case study exercises can be used as team or group exercises in collaborative learning. Many of the exercises have specific goals related to team building and teaming skills. The text also can be used to support the professional development or certification of practicing software engineers. The case study exercises can be integrated with presentations in a workshop or short course for professionals.

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

“Capers Jones has accumulated the most comprehensive data on every aspect of software engineering, and has performed the most scientific analysis on this data. Now, Capers performs yet another invaluable service to our industry, by documenting, for the first time, its long and fascinating history. Capers’ new book is a must-read for every software engineering student and information technology professional.” — From the Foreword by Tony Salvaggio, CEO and president, Computer Aid, Inc. Software engineering is one of the world’s most exciting and important fields. Now, pioneering practitioner Capers Jones has written the definitive history of this world-changing industry. Drawing on several decades as a leading researcher and innovator, he illuminates the field’s broad sweep of progress and its many eras of invention. He assesses the immense impact of software engineering on society, and previews its even more remarkable future. Decade by decade, Jones examines trends, companies, winners, losers, new technologies, productivity/quality issues, methods, tools, languages, risks, and more. He reviews key inventions, estimates industry growth, and addresses “mysteries” such as why programming languages gain and lose popularity. Inspired by Paul Starr’s Pulitzer Prize–winning The Social Transformation of American Medicine, Jones’ new book is a tour de force—and compelling reading for everyone who wants to understand how software became what it is today. COVERAGE INCLUDES • The human need to compute: from ancient times to the modern era • Foundations of computing: Alan Turing, Konrad Zuse, and World War II • Big business, big defense, big systems: IBM, mainframes, and COBOL • A concise history of minicomputers and microcomputers: the birth of Apple and Microsoft • The PC era: DOS, Windows, and the rise of commercial software • Innovations in writing and managing code: structured development, objects, agile, and more • The birth and explosion of the Internet and the World Wide Web • The growing challenges of legacy system maintenance and support • Emerging innovations, from wearables to intelligent agents to quantum computing • Cybercrime, cyberwarfare, and large-scale software failure

For most professions, a code of ethics exists to promote positive behavior among practitioners in order to enrich others within the field as well as the communities they serve. Similar to the medical, law, and business fields, the engineering discipline also instills a code of ethical conduct. Contemporary Ethical Issues in Engineering highlights a modern approach to the topic of engineering ethics and the current moral dilemmas facing practitioners in the field. Focusing on key issues, theoretical foundations, and the best methods for promoting engineering ethics from the pre-practitioner to the managerial level, this timely publication is ideally designed for use by engineering students, active professionals, and academics, as well as researchers in all disciplines of engineering.

Professionalism is arguably more important in some occupations than in others. It is vital in some because of the life and death decisions that must be made, for example in medicine. In others the rapidly changing nature of the occupation makes efficient regulation difficult and so the professional behaviour of the practitioners is central to the good functioning of that occupation. The core idea behind this book is that Information and Communication Technology (ICT) is changing so quickly that professional behaviour of its practitioners is vital because regulation will always lag behind.