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)).

The purpose of the Guide to the Software Engineering Body of Knowledge is to provide a validated classification of the bounds of the software engineering discipline and topical access that will support this discipline. The Body of Knowledge is subdivided into ten software engineering Knowledge Areas (KA) that differentiate among the various important concepts, allowing readers to find their way quickly to subjects of interest. Upon finding a subject, readers are referred to key papers or book chapters. Emphases on engineering practice lead the Guide toward a strong relationship with the normative literature. The normative literature is validated by consensus formed among practitioners and is concentrated in standards and related documents. The two major standards bodies for software engineering (IEEE Computer Society Software and Systems Engineering Standards Committee and ISO/IEC JTC1/SC7) are represented in the project.

The ultimate reference on wireless technology—now updated and revised Fully updated to incorporate the latest developments and standards in the field, A Guide to the Wireless Engineering Body of Knowledge, Second Edition provides industry professionals with a one-stop reference to everything they need to design, implement, operate, secure, and troubleshoot wireless networks. Written by a group of international experts, the book offers an unmatched breadth of coverage and a unique focus on real-world engineering issues. The authors draw upon extensive experience in all areas of the technology to explore topics with proven practical applications, highlighting emerging areas such as Long Term Evolution (LTE) in wireless networks. The new edition is thoroughly revised for clarity, reviews wireless engineering fundamentals, and features numerous references for further study. Based on the areas of expertise covered in the IEEE Wireless Communication Engineering Technologies (WCET) exam, this book explains: Wireless access technologies, including the latest in mobile cellular technology Core network and service architecture, including important protocols and solutions Network management and security, from operations process models to key security issues Radio engineering and antennas, with specifics on radio frequency propagation and wireless link design Facilities infrastructure, from lightning protection to surveillance systems With this trusted reference at their side, wireless practitioners will get up to speed on advances and best practices in the field and acquire the common technical language and tools needed for working in different parts of the world.

This handbook contains information and guidance that supports all of the topics of the 2016 version of the CSQE Body of Knowledge (BoK) upon which ASQ's Certified Software Quality Engineer/(CSQE) exam is based. Armed with the knowledge presented in this handbook to complement the required years of actual work experience, qualified software quality practitioners may feel confident they have taken appropriate steps in preparation for the ASQ CSQE exam. However, the goals for this handbook go well beyond it being a CSQE exam preparation guide. Its author designed this handbook not only to help the software quality engineers, but as a resource for software development practitioners, project managers, organizational managers, other quality practitioners, and other professionals who need to understand the aspects of software quality that impact their work. It can also be used to benchmark their (or their organization's) understanding and application of software quality principles and practices against what is considered a cross-industry good practice baseline. After all, taking stock of strengths and weaknesses, software engineers can develop proactive strategies to leverage software quality as a competitive advantage. New software quality engineers can use this handbook to gain an understanding of their chosen profession. Experienced software quality engineers can use this handbook as a reference source when performing their daily work. It is also hoped that trainers and educators will use this handbook to help propagate software quality engineering knowledge to future software practitioners and managers. Finally, this handbook strives to establish a common vocabulary that software quality engineers, and others in their organizations can use to communicate about software and quality. Thus increasing the professionalism of the industry and eliminating the wastes that can result from ambiguity and misunderstandings.

Software Engineering: Architecture-driven Software Development is the first comprehensive guide to the underlying skills embodied in the IEEE's Software Engineering Body of Knowledge (SWEBOK) standard. Standards expert Richard Schmidt explains the traditional software engineering practices recognized for developing projects for government or corporate systems. Software engineering education often lacks standardization, with many institutions focusing on implementation rather than design as it impacts product architecture. Many graduates join the workforce with incomplete skills, leading to software projects that either fail outright or run woefully over budget and behind schedule. Additionally, software engineers need to understand system engineering and architecture-the hardware and peripherals their programs will run on. This issue will only grow in importance as more programs leverage parallel computing, requiring an understanding of the parallel capabilities of processors and hardware. This book gives both software developers and system engineers key insights into how their skillsets support and complement each other. With a focus on these key knowledge areas, Software Engineering offers a set of best practices that can be applied to any industry or domain involved in developing software products.

A detailed and thorough reference on the discipline and practice of systems engineering The objective of the International Council on Systems Engineering (INCOSE) Systems Engineering Handbook is to describe key process activities performed by systems engineers and other engineering professionals throughout the life cycle of a system. The book covers a wide range of fundamental system concepts that broaden the thinking of the systems engineering practitioner, such as system thinking, system science, life cycle management, specialty engineering, system of systems, and agile and iterative methods. This book also defines the discipline and practice of systems engineering for students and practicing professionals alike, providing an authoritative reference that is acknowledged worldwide. The latest edition of the INCOSE Systems Engineering Handbook: Is consistent with ISO/IEC/IEEE 15288:2015 Systems and software engineering—System life cycle processes and the Guide to the Systems Engineering Body of Knowledge (SEBoK) Has been updated to include the latest concepts of the INCOSE working groups Is the body of knowledge for the INCOSE Certification Process This book is ideal for any engineering professional who has an interest in or needs to apply systems engineering practices. This includes the experienced systems engineer who needs a convenient reference, a product engineer or engineer in another discipline who needs to perform systems engineering, a new systems engineer, or anyone interested in learning more about systems engineering.

Computer Architecture/Software Engineering