Tools for Structured and Object-Oriented Design: An Introduction to Programming Logic, Sixth Edition [Paperback]

Marilyn Bohl (Author), Maria Rynn (Author)

Book Description

Publication Date: October 4, 2002 | ISBN-10: 0130494984 | ISBN-13: 978-0130494986 | Edition: 6

For courses in Problem Solving/Programming Logic and Programming Concepts and Logic. With exceptionally clear explanation of basic programming design principles, this book "really" starts from the beginning and assumes no prior programming knowledge. Using a unique concept-oriented, language-independent approach, it explores the structured design concepts, object-oriented design concepts, and problem-solving tools--through simple language, step-by-step examples, many sample problems, enrichment sections, and exercises. Chapter topics cover an introduction to structured design, SIMPLE SEQUENCE control structure, IFTHENELSE control structure, DOWHILE control structure--counter-controlled loops, DOWHILE control structure--trailer record logic, modularization, CASE control structure, DOUNTIL control structure, introduction to arrays, introduction to object-oriented design, inheritance, other class and object relationships, array applications, master file update processing, and control-break processing. For self-teachers and -learners of computer programming concepts.

Editorial Reviews

From the Publisher

This book uses an easy to follow step-by- step approach to teach the fundamentals of programming logic. --This text refers to an out of print or unavailable edition of this title.

From the Inside Flap

Preface

Tools for Structured Design: An Introduction to Programming Logic, fifth edition, teaches program design in a well thought out, language-independent manner. This text assumes no previous programming background. It can be used as a main text in a programming logic class or as a supplement in any beginning programming class.

Our approach is to start with simple concepts and build upon these concepts as new topics are introduced. We use a sequential, step-by-step approach that introduces, by way of example, only one new concept at a time. Sample problems are included throughout the chapters to illustrate the use of program design tools in practical situations. Enrichment sections are included in many of the chapters to illustrate the program design concepts in Basic and Visual Basic. Exercises are given at the end of each chapter to help you apply what you are learning.

Our objective is to analyze a problem and express its solution in such a way that the computer can be directed to follow the problem-solving procedure. With simple language and frequent examples, this book explains how to understand and how to use important problem-solving tools. We begin with system and program flowcharts. Flowcharting guidelines approved and published by the American National Standards Institute (ANSI) and its international counterpart, the International Standards Organization (ISO), are explained and applied to solution planning. Emphasis is placed on maintaining an overall structure in program design. We show how to use pseudocode as an alternative or supplement to flowcharting in planning the logic of a well-structured program. We analyze techniques of top-down, modular program development by describing how to read and how to develop structure charts that show the hierarchical relationships of modules within a program. We also explain the basic concepts of object-oriented design and event-driven programming and show how to apply these concepts to problem-solving situations.

Upon completion, the solution or program design should be verified using some of the techniques we recommend. The purpose of verification is to detect and eliminate errors as early in program development as possible. Design documentation in flowchart, pseudocode, or another form of design language is also useful in subsequent program coding and program checkout. Much of the necessary documentation is created as an integral part of the program development process.

Enrichment sections are included in many of the chapters to illustrate some of the sample problems in the programming languages Basic and Visual Basic. Basic is used to illustrate how the design of a program can be implemented using a procedural approach. Visual Basic is used to illustrate how the design of a program can be implemented using an event-driven approach. It is important to note that our approach to teaching program design remains language-independent. All program design concepts are covered prior to the enrichment sections in each chapter. The enrichment sections are optional and are included as a supplement to further illustrate some of these concepts.

The fifth edition of this book offers the same pedagogical features as the fourth edition. Each chapter includes objectives and a list of key terms. The fifth edition also includes an index and is supported by an Instructor's Guide. The Instructor's Guide contains the same objectives and key term lists as the textbook as well as suggested teaching strategies. Solutions to all the end-of-chapter exercises are also included. A CD including all the transparency masters in PowerPoint format is available to instructors. In addition, a disk containing the source code for all the Basic and Visual Basic examples included in the enrichment sections of the text is included with the textbook.

The text is organized into three parts as follows:

The first part (Chapters 1 through 10) introduces the theory of structured programming and includes a chapter on each control structure as well as a chapter on array fundamentals. Chapter 10 introduces object-oriented design and programming. These chapters should be covered in sequence.

The second part (Chapters 11 through 13) illustrates several more complex applications, building on material previously introduced. These chapters can be covered in any order after Chapters 1 through 10 are completed.

The final part (Appendices A through C) contains general reference material, including solutions to selected end-of-chapter exercises.

The specific content of each chapter and appendix follows.

Chapter 1 describes the system development life cycle and how program design fits with it. Computer-assisted software engineering (CASE) tools are introduced in this chapter and are referred to throughout the book, where appropriate, to increase your awareness of current tools and trends in the industry. The history of structured programming is also introduced in this chapter. Several nontechnical examples illustrate the basic control structures to give you a sense of what structured programming entails. The concepts of event-driven programming and graphical user interfaces are also introduced in this chapter.

Chapter 2 introduces the SIMPLE SEQUENCE control structure. Chapter 3 introduces the IFTHENELSE control structure and teaches simple, sequential, and nested IFs. Chapter 4 introduces the DOWHILE control structure, focusing on simple counter loops and header record logic. In this edition, the material on counter loops, header record logic, and modularization has been divided into two chapters. Chapter 5 introduces modularization. Chapter 6 focuses on trailer record logic and also includes a discussion of automatic end-of-file processing and multiple-heading logic.

Chapter 7 introduces the CASE control structure. Chapter 8 introduces the DOUNTIL control structure. Chapter 9 introduces one- and two-dimensional arrays with many short, simple examples. Chapter 10 introduces concepts of object-oriented program design. Psuedocode examples are used to illustrate object-oriented design concepts such as classes, data members, methods, encapsulation, driver programs, overloading, inheritance, and polymorphism.

Chapter 11 concentrates on more advanced array applications such as searching (both sequential and binary) and sorting. Chapter 12 illustrates the design of a sequential master file update program. Chapter 13 covers control-break processing.

Appendix A contains ANSI-approved symbols for program flowcharting, and Appendix B summarizes the basic control patterns of structured programming. Appendices A and B should be referred to whenever you are in doubt about which symbols to use in flowcharts. Responses to selected end-of-chapter exercises are provided in Appendix C to help you evaluate your understanding of the material. Acknowledgments

This book would not exist today if it were not for the hard work of many people. We would first like to thank Charles E. Stewart, Publisher, and Kate Linsner, Associate Editor, for all their help in putting this book together. We would also like to thank Janet Bixler for her support and assistance during the production of this manuscript. In addition, the following reviewers provided valuable feedback: Martha Daniels, Durham Technical Community College; Carol Grimm, Palm Beach Community College; Martin Meyers, Truckee Meadows Community College; Jo Ruta, Chattanooga State University; and Zhao Yang, Palm Beach Community College.

Maria Rynn would also like to thank all of her colleagues at Northern Virginia Community College for their continuing support and advice throughout this revision. Finally, she wishes to thank her husband, Tedd, for his constant encouragement, patience, and loving support during this endeavor.

We hope that all who use this book will find that it provides a clear, systematic, and direct approach to problem solving. We welcome your comments and suggestions.

Marilyn Bohl
Maria Rynn --This text refers to an out of print or unavailable edition of this title.

See all Editorial Reviews

Product Details

• Paperback: 416 pages
• Publisher: Prentice Hall; 6 edition (October 4, 2002)
• Language: English
• ISBN-10: 0130494984
• ISBN-13: 978-0130494986
• Product Dimensions: 10.6 x 8.2 x 0.8 inches
• Shipping Weight: 1.8 pounds
• Average Customer Review: 4.1 out of 5 stars  See all reviews (8 customer reviews)
• Amazon Best Sellers Rank: #1,143,184 in Books (See Top 100 in Books)

More About the Author

Discover books, learn about writers, read author blogs, and more.

Customer Reviews

Most Helpful Customer Reviews

9 of 9 people found the following review helpful:

3.0 out of 5 stars Elementary programming book -- overpriced, August 21, 1999

By A Customer

This review is from: Tools for Structured Design: An Introduction to Programming Logic (Textbook Binding)

I was compelled to buy this book for a course that I have to take at a community college to allow me admission to courses that I want to take. Amazon.com describes the book as having over 400 pages. It does not. It has a little over 300 pages, it is paperback, and it costs over $70! If you have absolutely no concept of, or experience with programming, then this book will give you a firm foundation, but at too high a price. Otherwise, skip it.

8 of 8 people found the following review helpful:

4.0 out of 5 stars Will Make You or Break You as a Beginner Programmer, July 13, 2000

By 

Jockomo "Jockomo" (Sacramento, CA USA) - See all my reviews

This review is from: Tools for Structured Design: An Introduction to Programming Logic (Textbook Binding)

I purchased this textbook for a class and found it to be very good in illustrating programs in a language-independent manner. (Flowcharts and pseudocodes are used instead of a specific language.) The exercises in the back of each chapter are helpful, but become tougher and tougher, demanding more time and detail. If you can't handle these exercises perhaps you picked the wrong career! What's the justification for the price tag? (Previously released as an anonymous reader.)

4 of 4 people found the following review helpful:

4.0 out of 5 stars Better then I thought..., February 27, 2003

By 

ender (Lansing, MI USA) - See all my reviews

This review is from: Tools for Structured Design: An Introduction to Programming Logic (5th Edition) (Paperback)

Nice book for those wanting to really do something with any programming language. Although the examples are all in QBasic and Visual Basic, the concepts are applied in pretty much all popular languages today. I found this book to be less boring then I thought it would be when I first looked at it.