DOCSLIB.ORG

Software Testing Techniques in Software Development Life Cycle

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Software Testing Techniques in Software Development Life Cycle D.Meenakshi et al, / (IJCSIT) International Journal of Computer Science and Information Technologies, Vol. 5 (3) , 2014, 3729-3731 Software Testing Techniques in Software Development Life Cycle D.Meenakshi , J. Swami Naik , M.Raghavendra Reddy Computer Science Department, G.Pulla Reddy Engineering College Kurnool,AndhraPradesh, India Abstract: Software testing provides a means to minimize by the user. [Verification: Are we building the product errors, cut maintenance and decrease overall software costs. right?] Different software development and testing methodologies, 2. Error Detection: Testing makes an attempt to go tools, and techniques have emerged to enhance software things wrong and to determine if things happen when quality. At each and every phase of software development life they shouldn‟t or things don‟t happen when they cycle testing is performed with different tools and techniques. One of the major problems within software testing area is how should. to get a suitable set of cases to test a software system. The 3. Validation looks at the system correctness – i.e. is software should assure maximum effectiveness with the least defined as checking that what has been specified is hat possible number of test cases. At present there are many the user actually wanted. [Validation: Are we building testing techniques available for generating test cases. the right prduct?] Keywords: Software Testing, Level of Testing, Testing The purpose of testing is verification, validation and error Technique, Testing Process detection in order to detect problems – and the purpose of finding those problems is to get them set. Most generic I. INTRODUCTION Software problems are : Inadequate software performance, Software testing is as getting on as the hills in the the past Data searches that yields incorrect results. Incorrect data digital computers. Testing the software is the only means entry & unsuccessful data edits, wrong coding / for assessing the quqlity of software . in view of the fact implementation of business rules, Incorrect calculation, that testing typically consumes 40 - 50% of effort in ineffective data edits, Incorrect processing of data devolopment, and requires more effort for systems that relationship, Incorrect or inadequate interfaces with other require more reliability, it is an important t part of the programs, Inadequate performance and security controls, software engineering. Contemporary software systems Incorrect file handling, insufficient support of business must be more reliable and correct. Automatic methods are needs, Unreliable results or performance, Confusing or used for ensuring software correctness which range from misleading data, Software usability by end users & static techniques, such as (software) model checking or Obsolete Software, Inconsistent processing. static analysis, to dynamic techniques , such as testing. All these testing techniques have strengths and weaknesses: Terminology: model checking (with abstraction) is automatic, exhaustive, Mistake – A manual action done which produce an but may suffer from scalability issues. Static analysis, on incorrect result. the other hand, scales to very large programs but may give Fault [or Defect] – An incorrect step, process, or too many fake warnings, while testing alone may miss data definition in a program. significant errors, since it is intrinsically incomplete. Failure – The lack of ability of a system or Software Testing: component to execute its Required function within Software testing is not only error detection; Testing the precise Performance requirement. software means operating the programs under controlled Error – The variation between a computed, conditions, to (1) checks whether it behaves “as specified”; observed, or Metric or condition and the (2) to detect errors, and (3) to validate that what has been true,specified, or theoretically correct value or specified is what the user actually wants. condition. Specification – A document that specifies in a Verifica Error Validation complete, accurate, confirmable manner, the tion Detection requirements, design, performance, or other feature of a system or component, and often the Procedures for determining whether these Activities in software testing provisions have been Satisfied. We observe errors, which can often be connected with failures. But 1. Verification is defined as checking or testing of items, the decisive cause of the fault is often very hard to including software, for conformance and reliability by find. evaluating the results against requirements specified www.ijcsit.com 3729 D.Meenakshi et al, / (IJCSIT) International Journal of Computer Science and Information Technologies, Vol. 5 (3) , 2014, 3729-3731 II. OBJECTIVES : To verify if the system is “Fit for function”. A good test case is one that has a probability of To confirm if the system meets the requirements detecting an error. and be executed successfully in the Intended A superior test is not redundant. environment. A successful test is one that uncovers a yet Executing a program with the intention of finding undiscovered error. an error. A good test supposed to be “best of breed”. To check if the method does what it is predictable to do. Testing type Specification Scope Opacity Who do it? Low level design Actual Unit Classes White box programmer code Low level and high level Integration Multiple classes White and Black box programmer design Function High level design Whole product Black box Independent test group Whole product in System Requirement analysis Black box Independent test group environment Whole product in Acceptance Requirement analysis Black box Customer environment Whole product in Beta Adhoc Black box Customer environment Whole product in Independent test group Regression Changed software White and Black box environment programmer `III. SOFTWARE TESTING LIFECYCLE – PHASES Testing Cycle starts with the study of user‟s Requirement requirements. study Understanding of the requirements is very essential for testing the product Component Identification Design Test Specification Design Test Specification Review Test Execution Construction Code Review , Test execution and evaluation Performance and simulation Testing Test Closure Deployment Test summary report ,Project De-brief , Project Documentation Test Process Analysis Analysis done on the reports and improving the application‟s performance by implementing new technology and additional IV LEVELS OF TESTING: Unit testing: The initial level of testing. Tests done on particular methods or components. Requires information about internal program design and code. Test wll be done by Programmers (not by testers). www.ijcsit.com 3730 D.Meenakshi et al, / (IJCSIT) International Journal of Computer Science and Information Technologies, Vol. 5 (3) , 2014, 3729-3731 To test the function of a program or unit of Acceptance testing: code such as a program or module,To test To check whether the software meets customers internal logic,To verify internal design,To requirements or not. test path & conditions coverage,To test Beta testing: exception conditions & error handling,To test Testing the software under the customers environment. Objectives the function of a program or unit of code such Regression testing: as a program or module,To test internal Testing done to the software after making the changes or logic,To verify internal design,To test path & enhancements conditions coverage,To test exception conditions & error handling V. TEST PLAN When After modules are coded Purpose of preparing a Test Plan Who Developer Validate the acceptability of a software product. Internal Application Design,Master Test Help the people outside the test group to Input Plan,Unit Test Plan understand „why‟ and „how‟ of product Output Unit Test Report validation. White Box testing techniques,Test Coverage A Test Plan should be thorough enough (Overall Methods techniques coverage of test to be conducted) Debug,Re-structure,Code Scope Tools Analyzers,Path/statement coverage tools The areas to be tested by the QA team. Specify the areas which are out of scope (screens, Incremental Integration Testing database, mainframe processes etc). It is done based on design and Continuous testing Test Approach of an application as and when a new functionality Details on how the testing is to be performed. is added. Any specific strategy is to be followed for testing Application’s functionality aspects are required to (including configuration management). be independent enough to work separately before completion of development. VI. CONCLUSION : Done by programmers or testers. Testing can show the presence of faults in a system; it Top-down integration: cannot prove that there are no remaining faults. Component Develop the skeleton of the system and integrates developers are dependable for component testing; system it with components. testing is the responsibility of a separate team. Integration Bottom-up integration testing is testing increments of the system; release testing Integrate infrastructure components then add involves testing a system to be released to a customer. Use functional components. experience and guidelines to design test cases in defect To simplify error localization, systems should be testing. Interface testing is designed to discover defects in incrementally integrated the interfaces of composite components. Equivalence partitioning is a way of discovering test cases - all cases in To technically verify proper interfaces a partition
Load more

Recommended publications
  • Software Development Career Pathway
    Career Exploration Guide Software Development Career Pathway Information Technology Career Cluster For more information about NYC Career and Technical Education, visit: www.cte.nyc Summer 2018 Getting Started What is software? What Types of Software Can You Develop? Computers and other smart devices are made up of Software includes operating systems—like Windows, Web applications are websites that allow users to contact management system, and PeopleSoft, a hardware and software. Hardware includes all of the Apple, and Google Android—and the applications check email, share documents, and shop online, human resources information system. physical parts of a device, like the power supply, that run on them— like word processors and games. among other things. Users access them with a Mobile applications are programs that can be data storage, and microprocessors. Software contains Software applications can be run directly from a connection to the Internet through a web browser accessed directly through mobile devices like smart instructions that are stored and run by the hardware. device or through a connection to the Internet. like Firefox, Chrome, or Safari. Web browsers are phones and tablets. Many mobile applications have Other names for software are programs or applications. the platforms people use to find, retrieve, and web-based counterparts. display information online. Web browsers are applications too. Desktop applications are programs that are stored on and accessed from a computer or laptop, like Enterprise software are off-the-shelf applications What is Software Development? word processors and spreadsheets. that are customized to the needs of businesses. Popular examples include Salesforce, a customer Software development is the design and creation of Quality Testers test the application to make sure software and is usually done by a team of people.
    [Show full text]
  • Object Oriented Programming
    No. 52 March-A pril'1990 $3.95 T H E M TEe H CAL J 0 URN A L COPIA Object Oriented Programming First it was BASIC, then it was structures, now it's objects. C++ afi<;ionados feel, of course, that objects are so powerful, so encompassing that anything could be so defined. I hope they're not placing bets, because if they are, money's no object. C++ 2.0 page 8 An objective view of the newest C++. Training A Neural Network Now that you have a neural network what do you do with it? Part two of a fascinating series. Debugging C page 21 Pointers Using MEM Keep C fro111 (C)rashing your system. An AT Keyboard Interface Use an AT keyboard with your latest project. And More ... Understanding Logic Families EPROM Programming Speeding Up Your AT Keyboard ((CHAOS MADE TO ORDER~ Explore the Magnificent and Infinite World of Fractals with FRAC LS™ AN ELECTRONIC KALEIDOSCOPE OF NATURES GEOMETRYTM With FracTools, you can modify and play with any of the included images, or easily create new ones by marking a region in an existing image or entering the coordinates directly. Filter out areas of the display, change colors in any area, and animate the fractal to create gorgeous and mesmerizing images. Special effects include Strobe, Kaleidoscope, Stained Glass, Horizontal, Vertical and Diagonal Panning, and Mouse Movies. The most spectacular application is the creation of self-running Slide Shows. Include any PCX file from any of the popular "paint" programs. FracTools also includes a Slide Show Programming Language, to bring a higher degree of control to your shows.
    [Show full text]
  • 2015 State of the Software Supply Chain Report: HIDDEN SPEED BUMPS on the ROAD to “CONTINUOUS”
    2015 State of the Software Supply Chain Report: HIDDEN SPEED BUMPS ON THE ROAD TO “CONTINUOUS” Foreword by Gene Kim, Gareth Rushgrove, John Willis, Jez Humble, and Nigel Simpson RESEARCH REPORT TABLE OF CONTENTS Foreword . 3 Introduction . 5 Why All Modern Software Development Relies on a Software Supply Chain . 6 SUPPLIERS: Open Source Projects . 7 Public Repositories (The Warehouses) . 8 Choosing the Best Suppliers (Sourcing) . .. 9 PARTS: Open Source Components . 12 Repository Management (Local Warehouses) . 15 MANUFACTURERS: Assembled Software Development . 19 Technical Debt: Assembly Line Inefficiencies . .. 21 FINISHED GOODS: Software Applications . 22 The Volume of Elective Re-work and Risk . 22 Software Bill of Materials . 23 Quality Controls: OWASP, PCI, FS-ISAC, U .S . Congress . 23 Lessons Learned from Traditional Manufacturing Supply Chains . 25 Automation: How To Improve Software Supply Chains . 26 Appendix . 28 Figure 1: The Volume and Size of the Global Software Supply Chain Figure 2: Target Benchmarks for Software Supply Chain Practices - Quality Control Figure 3: Target Benchmarks for Software Supply Chain Practices - Efficient Distribution Figure 4: Analysis of Components Used within Applications Figure 5: Multiple Versions of Parts Often Downloaded by the Largest Development Teams Figure 6: Volume of Defective Parts Used Figure 7: Comparison of Impact of Supply Chain Complexity on Prius versus Volt Figure 8: Efficient Sourcing Practices By Manufacturers 2015 State of the Software Supply Chain Report: Hidden Speed Bumps on the Road to “Continuous” Page 2 FOREWORD Gene Kim, Co-author of “The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win” and upcoming “DevOps Cookbook” “Anyone who believes, as I do, that we can learn valuable lessons from manufacturing and supply chains on how to better manage technology work will love this report .
    [Show full text]
  • College of Fine and Applied Arts Annual Meeting 5:00P.M.; Tuesday, April 5, 2011 Temple Buell Architecture Gallery, Architecture Building
    COLLEGE OF FINE AND APPLIED ARTS ANNUAL MEETING 5:00P.M.; TUESDAY, APRIL 5, 2011 TEMPLE BUELL ARCHITECTURE GALLERY, ARCHITECTURE BUILDING AGENDA 1. Welcome: Robert Graves, Dean 2. Approval of April 5, 2010 draft Annual Meeting Minutes (ATTACHMENT A) 3. Administrative Reports and Dean’s Report 4. Action Items – need motion to approve (ATTACHMENT B) Nominations for Standing Committees a. Courses and Curricula b. Elections and Credentials c. Library 5. Unit Reports 6. Academic Professional Award for Excellence and Faculty Awards for Excellence (ATTACHMENT C) 7. College Summary Data (Available on FAA Web site after meeting) a. Sabbatical Requests (ATTACHMENT D) b. Dean’s Special Grant Awards (ATTACHMENT E) c. Creative Research Awards (ATTACHMENT F) d. Student Scholarships/Enrollment (ATTACHMENT G) e. Kate Neal Kinley Memorial Fellowship (ATTACHMENT H) f. Retirements (ATTACHMENT I) g. Notable Achievements (ATTACHMENT J) h. College Committee Reports (ATTACHMENT K) 8. Other Business and Open Discussion 9. Adjournment Please join your colleagues for refreshments and conversation after the meeting in the Temple Buell Architecture Gallery, Architecture Building ATTACHMENT A ANNUAL MEETING MINUTES COLLEGE OF FINE AND APPLIED ARTS 5:00P.M.; MONDAY, APRIL 5, 2010 FESTIVAL FOYER, KRANNERT CENTER FOR THE PERFORMING ARTS 1. Welcome: Robert Graves, Dean Dean Robert Graves described the difficulties that the College faced in AY 2009-2010. Even during the past five years, when the economy was in better shape than it is now, it had become increasingly clear that the College did not have funds or personnel sufficient to accomplish comfortably all the activities it currently undertakes. In view of these challenges, the College leadership began a process of re- examination in an effort to find economies of scale, explore new collaborations, and spur creative thinking and cooperation.
    [Show full text]
  • Secure Database Development
    Secure Database Development Jan Jurjens (1) and Eduardo B. Fernandez (2) (1) Computing Department, The Open University, Milton Keynes, MK7 8LA GB http://www.jurjens.de/jan (2) Dept. of Computer Science, Florida Atlantic University, Boca Raton, FL 33431, USA http://www.cse.fau.edu/~ed Synonyms Secure DBMS development, secure database design DEFINITION This entry considers how to build secure database system software. In particular, it describes how to build a general-purpose database management system where security is an important design parameter. For the database community the words secure database design may refer to the schema design to produce a database for a specific application with some level of security properties. There is a large amount of literature on this latter subject and a related section in this encyclopedia (Database security). This section concentrates mostly on how to build the software of a DBMS such that it exhibits security properties, which is called secure database development. Both approaches are contrasted so that the reader can decide which one of these problems applies to her specific case but more space is dedicated to the general secure database development problem. HISTORICAL BACKGROUND While there is a large number of papers on security models including authorization and other security aspects of databases [2, 4, 6], there is little work on how to implement a secure Database Management System (DBMS). It is true that many proposals for secure multilevel databases include details of implementation but most of them are ad hoc architectures that cannot be generalized to databases using different models or even to other multilevel databases with different requirements.
    [Show full text]
  • Chapter 3 Software Design
    CHAPTER 3 SOFTWARE DESIGN Guy Tremblay Département d’informatique Université du Québec à Montréal C.P. 8888, Succ. Centre-Ville Montréal, Québec, Canada, H3C 3P8 [email protected] Table of Contents references” with a reasonably limited number of entries. Satisfying this requirement meant, sadly, that not all 1. Introduction..................................................................1 interesting references could be included in the recom- 2. Definition of Software Design .....................................1 mended references list, thus the list of further readings. 3. Breakdown of Topics for Software Design..................2 2. DEFINITION OF SOFTWARE DESIGN 4. Breakdown Rationale...................................................7 According to the IEEE definition [IEE90], design is both 5. Matrix of Topics vs. Reference Material .....................8 “the process of defining the architecture, components, 6. Recommended References for Software Design........10 interfaces, and other characteristics of a system or component” and “the result of [that] process”. Viewed as a Appendix A – List of Further Readings.............................13 process, software design is the activity, within the software development life cycle, where software requirements are Appendix B – References Used to Write and Justify the analyzed in order to produce a description of the internal Knowledge Area Description ....................................16 structure and organization of the system that will serve as the basis for its construction. More precisely, a software design (the result) must describe the architecture of the 1. INTRODUCTION system, that is, how the system is decomposed and This chapter presents a description of the Software Design organized into components and must describe the interfaces knowledge area for the Guide to the SWEBOK (Stone Man between these components. It must also describe these version).
    [Show full text]
  • Software Development Life Cycle (SDLC)
    Software Development Life Cycle (SDLC) • Architecture of Software Development Life Cycle Pipelines, on page 1 • Management VPC SDLC Pipeline, on page 3 • Customer VPC SDLC Pipeline, on page 4 • Code Analysis Reporting, on page 5 Architecture of Software Development Life Cycle Pipelines There are two Cisco SD-WAN for government Software Development Life Cycle (SDLC) pipelines: • Cisco vOrchestrator and Cisco vMonitor SDLC pipeline: The SDLC pipeline used to develop and deploy control components in the Amazon management VPC. • Cisco SD-WAN controllers and Cisco vManage SDLC pipeline: The SDLC pipeline used to develop and deploy control components in the Amazon customer VPC. Software Development Life Cycle (SDLC) 1 Software Development Life Cycle (SDLC) Architecture of Software Development Life Cycle Pipelines Figure 1: Cisco vOrchestrator and Cisco vMonitor SDLC pipeline Figure 2: Cisco SD-WAN Continuous Integration and Continuous Delivery Pipeline Software Development Life Cycle (SDLC) 2 Software Development Life Cycle (SDLC) Management VPC SDLC Pipeline Management VPC SDLC Pipeline Before the images are built and deployed to Cisco SD-WAN for government, the code is first analyzed. After analysis, the code is pushed to a development server in the Cisco DMZ network. The management VPC SDLC pipeline does the following: Checks for Regressions and Analysis of Code To check for regressions and analyze code, Cisco has created the following automated pipeline: 1. Jenkins pulls the code locally from Cisco's Git server. 2. Jenkins (open-source automation tool) securely copies the code to the development server using the scp (secure copy) utility. 3. On the development server, robot regressions are triggered.
    [Show full text]
  • Software Development a Practical Approach!
    Software Development A Practical Approach! Hans-Petter Halvorsen https://www.halvorsen.blog https://halvorsen.blog Software Development A Practical Approach! Hans-Petter Halvorsen Software Development A Practical Approach! Hans-Petter Halvorsen Copyright © 2020 ISBN: 978-82-691106-0-9 Publisher Identifier: 978-82-691106 https://halvorsen.blog ii Preface The main goal with this document: • To give you an overview of what software engineering is • To take you beyond programming to engineering software What is Software Development? It is a complex process to develop modern and professional software today. This document tries to give a brief overview of Software Development. This document tries to focus on a practical approach regarding Software Development. So why do we need System Engineering? Here are some key factors: • Understand Customer Requirements o What does the customer needs (because they may not know it!) o Transform Customer requirements into working software • Planning o How do we reach our goals? o Will we finish within deadline? o Resources o What can go wrong? • Implementation o What kind of platforms and architecture should be used? o Split your work into manageable pieces iii • Quality and Performance o Make sure the software fulfills the customers’ needs We will learn how to build good (i.e. high quality) software, which includes: • Requirements Specification • Technical Design • Good User Experience (UX) • Improved Code Quality and Implementation • Testing • System Documentation • User Documentation • etc. You will find additional resources on this web page: http://www.halvorsen.blog/documents/programming/software_engineering/ iv Information about the author: Hans-Petter Halvorsen The author currently works at the University of South-Eastern Norway.
    [Show full text]
  • A Perspective on the Future of Middleware-Based Software Engineering
    A Perspective on the Future of Middleware-based Software Engineering Valerie Issarny Mauro Caporuscio Nikolaos Georgantas INRIA-Rocquencourt INRIA-Rocquencourt INRIA-Rocquencourt Domaine de Voluceau Domaine de Voluceau Domaine de Voluceau 78153 Le Chesnay, France. 78153 Le Chesnay, France. 78153 Le Chesnay, France. [email protected] [email protected] [email protected] Abstract • An interaction paradigm and semantics for achieving coordination. Middleware is a software layer that stands between the networked operating system and the application and pro- • A transport/session protocol for achieving communi- vides well known reusable solutions to frequently encoun- cation. tered problems like heterogeneity, interoperability, security, dependability. Further, with networks becoming increas- • A naming/discovery protocol, naming/description con- ingly pervasive, middleware appears as a major building vention, registry structure, and matching relation for block for the development of future software systems. Start- publishing and discovering the resources available in ing with the impact of pervasive networking on comput- the given network. ing models, manifested by now common grid and ubiqui- tous computing, this paper surveys related challenges for the middleware and related impact on the software de- velopment. Indeed, future applications will need to cope with advanced non-functional properties such as context- awareness and mobility, for which adequate middleware support must be devised together with accompanying soft- ware development notations, methods and tools. This leads us to introduce our view on next generation middleware, considering both technological advances in the network- ing area but also the need for closer integration with software engineering best practices, to ultimately suggest middleware-based software processes.
    [Show full text]
  • Linux Installation and Getting Started
    Linux Installation and Getting Started Copyright c 1992–1996 Matt Welsh Version 2.3, 22 February 1996. This book is an installation and new-user guide for the Linux system, meant for UNIX novices and gurus alike. Contained herein is information on how to obtain Linux, installation of the software, a beginning tutorial for new UNIX users, and an introduction to system administration. It is meant to be general enough to be applicable to any distribution of the Linux software. This book is freely distributable; you may copy and redistribute it under certain conditions. Please see the copyright and distribution statement on page xiii. Contents Preface ix Audience ............................................... ix Organization.............................................. x Acknowledgments . x CreditsandLegalese ......................................... xii Documentation Conventions . xiv 1 Introduction to Linux 1 1.1 About This Book ........................................ 1 1.2 A Brief History of Linux .................................... 2 1.3 System Features ......................................... 4 1.4 Software Features ........................................ 5 1.4.1 Basic commands and utilities ............................. 6 1.4.2 Text processing and word processing ......................... 7 1.4.3 Programming languages and utilities .......................... 9 1.4.4 The X Window System ................................. 10 1.4.5 Networking ....................................... 11 1.4.6 Telecommunications and BBS software .......................
    [Show full text]
  • Middleware Technologies
    A. Zeeshan A middleware approach towards Web (Grid) Services 06 January 2006 A Middleware road towards Web (Grid) Services Zeeshan Ahmed Department of Intelligent Software Systems and Computer Science, Blekinge Institute of Technology, Box 520, S-372 25 Ronneby, Sweden [email protected] In Student Workshop on Architectures and Research in Middleware Blekinge Institute of Information Technology (BIT 2006), 06.01.2006, Romney Sweden A. Zeeshan A middleware approach towards Web (Grid) Services 06 January 2006 ABSTRACT: 2. MIDDLEWARE TECHNOLOGIES (MDLW TECH) Middleware technologies is a very big field, containing a strong already done research as well as the currently This is one of the new and hottest topics in the field of running research to confirm already done research’s the computer science which encompasses of many results and the to have some new solution by theoretical technologies to connects computer systems and provide a as well as the experimental (practical) way. This protocol to interact with each other to share the document has been produced by Zeeshan Ahmed information between them. The term Middleware carries (Student: Connectivity Software Technologies Blekinge the meaning to mediate between two or more already Institute of Technologies). This describes the research existing separate software applications to exchange the already done in the field of middleware technologies data. including Web Services, Grid Computing, Grid Services and Open Grid Service Infrastructure & Architecture. Middleware technologies reside inside complex, This document concludes with the overview of Web distributed and online application by hiding their self in (Grid) Service, Chain of Web (Grid) Services and the the form operating system, database and network details, necessary security issue.
    [Show full text]
  • A Debate on Teaching Computing Science
    Teaching Computing Science t the ACM Computer Science Conference last Strategic Defense Initiative. William Scherlis is February, Edsger Dijkstra gave an invited talk known for his articulate advocacy of formal methods called “On the Cruelty of Really Teaching in computer science. M. H. van Emden is known for Computing Science.” He challenged some of his contributions in programming languages and the basic assumptions on which our curricula philosophical insights into science. Jacques Cohen Aare based and provoked a lot of discussion. The edi- is known for his work with programming languages tors of Comwunications received several recommenda- and logic programming and is a member of the Edi- tions to publish his talk in these pages. His comments torial Panel of this magazine. Richard Hamming brought into the foreground some of the background received the Turing Award in 1968 and is well known of controversy that surrounds the issue of what be- for his work in communications and coding theory. longs in the core of a computer science curriculum. Richard M. Karp received the Turing Award in 1985 To give full airing to the controversy, we invited and is known for his contributions in the design of Dijkstra to engage in a debate with selected col- algorithms. Terry Winograd is well known for his leagues, each of whom would contribute a short early work in artificial intelligence and recent work critique of his position, with Dijkstra himself making in the principles of design. a closing statement. He graciously accepted this offer. I am grateful to these people for participating in We invited people from a variety of specialties, this debate and to Professor Dijkstra for creating the backgrounds, and interpretations to provide their opening.
    [Show full text]