TAILIEUCHUNG - Software Engineering For Students: A Programming Approach Part 3

Software Engineering For Students: A Programming Approach Part 3. This fully revised version of Doug Bell's Software Engineering: A Programming Approach continues to use the successful formula of the previous editions. The author's approach is to present the main principles, techniques and tools used in software engineering, one by one, chapter by chapter. This book is a unique introduction to software engineering for all students of computer science and its related disciplines. It is also ideal for practitioners wishing to remain current with new developments in the area | xx Preface Software Engineering and related fields at the college or university level. The book is also aimed at practising software developers in industry and commerce who wish to keep abreast of current ideas in software engineering. What do I need to know The prerequisites for understanding this book are some familiarity with a modern programming language some experience with developing a moderately sized program of a few hundred lines. What is covered in this book This book explains the different principles techniques and tools that are used in software development. These are the mainstream methods that are currently used throughout the industrialized world. This book doesn t present easy answers about the value of these techniques. Indeed it asks the reader to make an assessment of the techniques. This is what the software engineer has to do - now and in the future - choose the appropriate techniques for the project in hand from the multiplicity of techniques that are on offer. Notations UML Unified Modeling Language is used as appropriate within the text as a graphical design notation. Some other graphical notations - flowcharts structure charts and data flow diagrams are also used. Java is used as an illustrative programming language and sometimes also pseudo code program design language . So many chapters Yes but each chapter deals with a separate topic. This is to enable each chapter to focus exclusively and thoroughly on a single idea. How to read this book Because the chapters are independent you do not need to read them in any particular sequence - you can dip into the book at random. But you might choose to read Chapters 1 and 2 first because they set the scene. You might choose to spend one week on each chapter. Preface xxi The organization of this book The chapters are grouped into sections on preliminaries design programming languages verification process models project management review. Several of these sections present a variety of alternative .

152    6    0    12-08-2020
2    5    0    12-08-2020
5    4    0    12-08-2020