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.

Covers material needed for the Advanced Subsidiary (AS) and Advanced Level (A2) qualifications in ICT and is mapped to the AQA syllabuses. (introd.).

This book constitutes the refereed proceedings of the International Conference on Informatics in Secondary Schools - Evolution and Perspectives, ISSEP 2006, held in Vilnius, Lithuania in November 2006. The 29 revised full papers presented were carefully reviewed and selected from 204 submissions. A broad variety of topics related to teaching informatics in secondary schools is addressed.

Computing Concepts for Information Technology explains how computers really work, including how images, sounds, and video are represented by numbers and how chips with millions of transistors process those numbers. Computing Concepts for Information Technology is suitable for people with no prior study of computer systems, although it may be helpful to have experience with a high-level programming language such as Java or Python. Computing Concepts for Information Technology tells a story that begins in the 19th century and shows that the Internet, phones, tablets, and laptops that are so much a part of our lives did not spring fully formed from a Silicon Valley campus. On the inside, computers are all about numbers, and the story continues with numbers and number systems. It reveals the mysteries of binary numbers and explains why computers use a number system different from the one we use every day. One of the reviewers of the book remarked that students of computing should know enough about the digital logic that makes computers work to believe that what’s inside is not little green Martians with calculators, and the book provides a thorough explanation. Input and output, data communications, computer software, and information security are covered at a fundamental level and provide the necessary background for further study. The beginning of the 21st century is an exciting time for those who make, use, and study computers and computer systems, and this book provides the basis for keeping up with the changes that are taking place right now.

PKI (public-key infrastructure) enables the secure exchange of data over otherwise unsecured media, such as the Internet. PKI is the underlying cryptographic security mechanism for digital certificates and certificate directories, which are used to authenticate a message sender. Because PKI is the standard for authenticating commercial electronic transactions,Understanding PKI, Second Edition, provides network and security architects with the tools they need to grasp each phase of the key/certificate life cycle, including generation, publication, deployment, and recovery.