A highly readable text designed for beginning and intermediate C programmers. While focusing on the programming language, the book emphasises stylistic issues and software engineering principles so as to develop programs that are readable, maintainable, portable, and efficient. The software engineering techniques discussed throughout the text are illustrated in a C interpreter, whose source listing is provided on diskette, and highlighted "bug alerts" offer tips on the common errors made by novice programmers. Can be used as the primary course textbook or as the main reference by programmers intent on learning C.

The author starts with the premise that C is an excellent language for software engineering projects. The book con- centrates on programming style,particularly readability, maintainability, and portability. Documents the proposed ANSI Standard, which is expected to be ratified in 1987. This book is designed as a text for both beginner and inter- mediate-level programmers.

Market_Desc: · Programmers· Software Engineers· Requirements Engineers· Software Quality Engineers Special Features: · Offers detailed coverage of software measures. Exposes students to quantitative methods of identifying important features of software products and processes· Complete Case Study. Through an air traffic control study, students can trace the application of methods and practices in each chapter· Problems. A broad range of problems and references follow each chapter· Glossary of technical terms and acronyms facilitate review of basic ideas· Example code given in C++ and Java· References to related web pages make it easier for students to expand horizons About The Book: This book is the first comprehensive study of a quantitative approach to software engineering, outlining prescribed software design practices and measures necessary to assess software quality, cost, and reliability. It also introduces Computational Intelligence, which can be applied to the development of software systems.

This book describes the C programming language and software engineering prin ciples of program construction. The book is intended primarily as a textbook for beginning and intermediate C programmers. It does not assume previous knowl edge of C, nor of any high-level language, though it does assume that the reader has some familiarity with computers. While not essential, knowledge of another programming language will certainly help in mastering C. Although the subject matter of this book is the C language, the emphasis is on software engineering-making programs readable, maintainable, portable, and efficient. One of our main goals is to impress upon readers that there is a huge difference between programs that merely work, and programs that are well engi neered, just as there is a huge difference between a log thrown over a river and a well-engineered bridge. The book is organized linearly so that each chapter builds on information provided in the previous chapters. Consequently, the book will be most effective if chapters are read sequentially. Readers with some experience in C, however, may find it more useful to consult the table of contents and index to find sections of particular interest.

Today’s software engineer must be able to employ more than one kind of software process, ranging from agile methodologies to the waterfall process, from highly integrated tool suites to refactoring and loosely coupled tool sets. Braude and Bernstein’s thorough coverage of software engineering perfects the reader’s ability to efficiently create reliable software systems, designed to meet the needs of a variety of customers. Topical highlights . . . • Process: concentrates on how applications are planned and developed • Design: teaches software engineering primarily as a requirements-to-design activity • Programming and agile methods: encourages software engineering as a code-oriented activity • Theory and principles: focuses on foundations • Hands-on projects and case studies: utilizes active team or individual project examples to facilitate understanding theory, principles, and practice In addition to knowledge of the tools and techniques available to software engineers, readers will grasp the ability to interact with customers, participate in multiple software processes, and express requirements clearly in a variety of ways. They will have the ability to create designs flexible enough for complex, changing environments, and deliver the proper products.

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

This text is written with a business school orientation, stressing the how to and heavily employing CASE technology throughout. The courses for which this text is appropriate include software engineering, advanced systems analysis, advanced topics in information systems, and IS project development. Software engineer should be familiar with alternatives, trade-offs and pitfalls of methodologies, technologies, domains, project life cycles, techniques, tools CASE environments, methods for user involvement in application development, software, design, trade-offs for the public domain and project personnel skills. This book discusses much of what should be the ideal software engineer's project related knowledge in order to facilitate and speed the process of novices becoming experts. The goal of this book is to discuss project planning, project life cycles, methodologies, technologies, techniques, tools, languages, testing, ancillary technologies (e.g. database) and CASE. For each topic, alternatives, benefits and disadvantages are discussed.