DOCSLIB.ORG

Algorithms (One of the Following) L Buy the Book -  Introduction to Algorithms, Thomas H

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Algorithms (One of the Following) L Buy the Book -  Introduction to Algorithms, Thomas H Level 9 Reading List [ladder home page] [ladder overview] [reading list] [pyramid] Required reading Recommended Reading Appropriate Optional Reading The top list is a recommendation by category. Detailed book descriptions follow the summary table. R Algorithms (one of the following) L Buy the book - Introduction to Algorithms, Thomas H. Cormen, et al Buy the book - Data Structures and Algorithms, Aho, Hopcraft, and Ullman Buy the book - Algorithms in C++, Robert Sedgewick Buy vol.1 Buy vol.2 - The Art of Computer Programming (vols. 1-3), Donald Knuth Buy vol.3 Construction Practices Buy the book A Code Complete, Steve McConnell Buy the book A Programming Pearls, Jon Bentley Buy the book - Practice of Programming, Brian Kernighan and Rob Pike Buy the book - Writing Solid Code, Steve Maguire Buy the Book - Programming on Purpose: Essays on Software Design, P. J. Plauger Buy the book - Programmers at Work, Susan Lammers Software Development Overview Buy the book. A 201 Principles of Software Development, Alan M. Davis Get the article A "The Humble Programmer," Edsger Dijkstra "Software Engineering Programmes are not Computer Science Programmes," David Get the article A Parnas Get the article A "They Write the Right Stuff ," Charles Fishman Buy the book - Software Engineering, Ian Sommerville Buy the book - Software Engineering: A Practitioner's Approach, Roger Pressman Professional Ethics Get the code A Software Engineering Code of Ethics and Professional Practice, ACM/IEEE-CS Periodicals Subscribe - Software Development Subscribe - IEEE Software Algorithms Introduction to Algorithms, Thomas H. Cormen, et al. This comprehensive book contains an exhaustive discussion of specific algorithms, algorithm analysis, and algorithm design (though not as exhaustive as Knuth's seven volume series). Data Structures and Algorithms, Aho, Hopcraft, and Ullman. This book is focused as a textbook introduction to data structures. It contains excellent discussions of arrays, records, pointers, lists, and trees. It also covers the fundamental algorithmic topics of searching and sorting. Algorithms in C++, Robert Sedgewick. This is a good choice if you want a book whose examples are in C++. The Art of Computer Programming, Donald Knuth. These are the touch stone books in the field, though they certainly are not light reading. These are the first three volumes of a series that was originally intended to be seven volumes. They can be somewhat intimidating. Aside from the English description of the algorithms, they're described in mathematical notation or MIX, an assembly language for the imaginary MIX computer. Nevertheless, they contain exhaustive details on a huge number of topics, and if you have an intense interest in a particular algorithm, you won't find a better reference. Construction Practices Code Complete, Steve McConnell. McConnell's book is an exhaustive compendium of all the detailed software- construction level practices that make the difference between readable, maintainable, extendible programs and disorganized mish-mashes that become unworkable after initial construction. Programming Pearls, Jon Bentley. This book provides terrific insight into the functioning of the expert programmer's mind. In each essay, Bentley walks the reader through the thought processes he uses to solve detailed programming problems. Along the way he introduces the concepts of Big-O notation, approaches to performance tuning, back-of-the-envelope calculations, and many other topics. Reading this book thoughtfully is like working through an apprenticeship with a master programmer. Practice of Programming, Brian Kernighan and Rob Pike. This book is written by two C/Unix gurus and contains a good, solid discussion of key code-level and design level issues. Chapter 4, on interface design, covers a topic that doesn't get much coverage in other books. Writing Solid Code, Steve Maguire. This book describes key software-construction practices used at Microsoft. It explains how to minimize defects by using compiler warnings, protecting your code with assertion statements, fortifying subsystems with integrity checks, designing unambiguous function interfaces, checking code in a debugger, and avoiding risky programming practices. Programming on Purpose: Essays on Software Design, P. J. Plauger. This is a refreshing collection of essays that were originally published in Computer Language magazine. Plauger is a master designer and takes up a variety of topics having as much to do with being a designer as with design in the abstract. What makes the essays refreshing is that Plauger ranges freely over the entire landscape of design topics rather than restricting himself to a discussion of any one design style. The result is uniquely insightful and thought provoking. Programmers at Work, Susan Lammers. This book contains interesting interviews with many of the pioneers of personal computing, including Bill Gates, Gary Kildall, Dan Bricklin, and others. Software Development Overview 201 Principles of Software Development, Alan M. Davis. 201 Principles provides an easy-to-read introduction to the critical issues in software development. Davis’s book prepares you to recognize key issues when other books discuss them and when they crop up on your own projects. "The Humble Programmer," Dijkstra, Edsger. This classic paper helped begin the inquiry into how much computer programming depends on programmers' mental abilities. Dijkstra has persistently trumpeted the message that the essential task of programming is mastering the enormous complexity of computer science. He argues that programming is the only activity in which humans have to master nine orders of magnitude difference between the lowest level of detail and the highest. This paper would be interesting reading solely for its historical value, but many of its themes sound fresh 20 years later. It also gives a good sense of what it was like to be a programmer in the early days of computer science. "Software Engineering Programmes are not Computer Science Programmes," David Parnas. This exceptional article describes the contents of the Software Engineering program at McMaster University. The premise of the article is that it is easiest to understand a software engineering curriculum by comparing it to a computer science curriculum. Periodicals Software Development. This magazine focuses on programming issues, less on tips for specific environments than the general issues you face as a professional programmer. The quality of the articles is quite good. It also includes product reviews. IEEE Software. This magazine focuses on software topics and is published bimonthly. It's a good source of information on software-development methods and other leading-edge software topics. It publishes many articles by researchers and makes an earnest attempt to print research on practical topics which are of use to professional programmers. It isn't always as practical as I (SteveMcC) would like it to be, but, in my opinion, it's still the most valuable magazine a programmer can subscribe to. [This review was written in 1992.] Copyright © 1999 Construx Software Builders, Inc. Level 10 Reading List [ladder home page] [ladder overview] [reading list] [pyramid] Required reading Recommended Reading Appropriate Optional Reading The top list is a recommendation by category. Detailed book descriptions follow the summary table. R Construction Practices L Buy the book - Software Implementation, Michael Marcotty User Interface Design Buy the book A The Design of Everyday Things, Donald A. Norman Designing the User Interface: Strategies for Effective Human-Computer Interaction, Buy the book A Ben Shneiderman Buy the book A Usability Engineering, Jakob Nielsen Buy the book - The Elements of Friendly Software Design, Paul Heckel Buy the book - About Face: The Essentials of User Interface Design, Alan Cooper Buy the book - The Art of Human-Computer Interface Design, Brenda Laurel, ed Database Design "A Simple Guide to Five Normal Forms in Relational Database Theory," William Get the article A Kent Get the article A "Process Driven Data Design," Frank Sweet Get the article A "The Power of Stored Procedures," David McGoveran Buy the book - Fundamentals of Database Systems, Ramez Elmasri and Shamkant B. Navathe Software Functional Design Buy the book I Object Oriented Analysis and Design, Grady Booch Buy the book I Design Patterns, Erich Gamma, et al. Structured Design, Edward Yourdon and Larry Constantine (or see Meilir Page- Buy the book I Jones's book instead) Practical Guide to Structured Systems Design, Meilir Page-Jones, (or see Yourdon Buy the book A and Constantine's book instead) Buy the book A Software Creativity, Robert L. Glass "A Rational Design Process: How and Why to Fake It," David Parnas and Paul Get the article A Clements Get the article A "On the Criteria to Be Used in Decomposing Systems into Modules," David L. Parnas Get the article A "Designing Software for Ease of Extension and Contraction," David L. Parnas "The Modular Structure of Complex Systems," David Lorge Parnas, Paul C. Get the article A Clements, and David M. Weiss Pattern Oriented Software Architecture : A System of Patterns, Frank Buschmann, et Buy the book - al. Buy the Book - Programming on Purpose: Essays on Software Design, P. J. Plauger Software Architecture : Perspectives on an Emerging Discipline Buy the book - by Mary Shaw and David Garlan Get the article - "Structured Design," W. Stevens, G. Myers, and L. Constantine
Load more

Recommended publications
  • PMR 5020 Modelagem Do Projeto De Sistemas Aula 2: Sistemas E Seu Processo De Projeto Prof
    PMR 5020 Modelagem do Projeto de Sistemas Aula 2: Sistemas e seu processo de projeto Prof. José Reinaldo Silva [email protected] PMR5020 Escola Politécnica da USP 1 O Design Mecatrônico (Mechatronic Design) Sistema de informação Sistema Mecânico Artefato Mecatrônico Sistema de controle Sistema Eletrônico Prof. José Reinaldo Silva PMR5020 Escola Politécnica da USP 2 O noso artefato alvo… Sistemas Não tem fronteiras óbvias Não tem um “corpo” material Geralmente acoplado Prof. José Reinaldo Silva PMR5020 Escola Politécnica da USP 3 Um sistema é um conjunto de objetos distinguíveis – não necessariamente homogêneo – que trabalham em conjunto para atingir um objetivo coletivo. Eventualmente cada um dos elementos constituintes pode ser também um sistema menor do que o sistema que o contém. Assim a definição é recursiva e convergente. Existem uma (ou mais) categorias de elemento constituinte tal que não vale a pena imergir nos detalhes internos deste, isto é, a precisão dos detalhes não contribui em nada seja para o funcionamento do sistema, seja para entender a sua funcionalidade. Prof. José Reinaldo Silva PMR5020 Escola Politécnica da USP 4 Teoria de sistemas Proposta em 1940 por Ludwig von Bartalanffy Em busca da unificação da ciência X reducionismo Prof. José Reinaldo Silva PMR5020 Escola Politécnica da USP 5 Sistema: uma definição holônica Um sistema é definido pelo par ordenado S=(A, R) onde A é um conjunto de elementos constituintes (objetos) relevantes A e R o conjunto R de relações definidas entre estes objetos. Eventual- mente um elemento de A tem as mesmas características do sistema e é chamado de sub-sistema de S.
    [Show full text]
  • Chapter 1: Introduction
    Just Enough Structured Analysis Chapter 1: Introduction “The beginnings and endings of all human undertakings are untidy, the building of a house, the writing of a novel, the demolition of a bridge, and, eminently, the finish of a voyage.” — John Galsworthy Over the River, 1933 www.yourdon.com ©2006 Ed Yourdon - rev. 051406 In this chapter, you will learn: 1. Why systems analysis is interesting; 2. Why systems analysis is more difficult than programming; and 3. Why it is important to be familiar with systems analysis. Chances are that you groaned when you first picked up this book, seeing how heavy and thick it was. The prospect of reading such a long, technical book is enough to make anyone gloomy; fortunately, just as long journeys take place one day at a time, and ultimately one step at a time, so long books get read one chapter at a time, and ultimately one sentence at a time. 1.1 Why is systems analysis interesting? Long books are often dull; fortunately, the subject matter of this book — systems analysis — is interesting. In fact, systems analysis is more interesting than anything I know, with the possible exception of sex and some rare vintages of Australian wine. Without a doubt, it is more interesting than computer programming (not that programming is dull) because it involves studying the interactions of people, and disparate groups of people, and computers and organizations. As Tom DeMarco said in his delightful book, Structured Analysis and Systems Specification (DeMarco, 1978), [systems] analysis is frustrating, full of complex interpersonal relationships, indefinite, and difficult.
    [Show full text]
  • Users, Roles, and Personas (PDF)
    Constantine & Lockwood, Ltd. PREPRINT Users, Roles, and Personas Larry Constantine, IDSA Chief Scientist, Constantine & Lockwood, Ltd. You cannot think outside the box when you are trying to represent a box. Brian Hayes To do effective design you need to understand your users and their needs. While no credible school of thought in design would take serious exception, opinions vary considerably on how best to gain that understanding and how to record and communicate it once you do. Models of one form or another are the medium for the message in most design methods. Models function as intermediaries between the often ambiguous, overwhelmingly complex reality of actual users and the more narrowly focused and specific needs of designers. In usage-centered design (see sidebar, “Users or Usage”), user roles capture and carry the essential understanding about users. User roles, one of the three core models of usage-centered design, are close cousins of personas but differ in a number of ways of potential significance to designers. In an attempt to sound a counterpoint to complement the main themes of the book, this chapter introduces user roles in the context of usage-centered design and explores the relationships between user roles and personas. Compared to typical personas as presented in this book and elsewhere, user roles are a more compact and concise representation that is more finely focused on issues with direct relevance for visual and interaction design. For these reasons, user role models can also be simpler and faster to develop. Although roles and personas can complement each other, user role models may also, under some circumstances and for some purposes, offer distinct advantages for designers.
    [Show full text]
  • Contents U U U
    Contents u u u ACM Awards Reception and Banquet, June 2018 .................................................. 2 Introduction ......................................................................................................................... 3 A.M. Turing Award .............................................................................................................. 4 ACM Prize in Computing ................................................................................................. 5 ACM Charles P. “Chuck” Thacker Breakthrough in Computing Award ............. 6 ACM – AAAI Allen Newell Award .................................................................................. 7 Software System Award ................................................................................................... 8 Grace Murray Hopper Award ......................................................................................... 9 Paris Kanellakis Theory and Practice Award ...........................................................10 Karl V. Karlstrom Outstanding Educator Award .....................................................11 Eugene L. Lawler Award for Humanitarian Contributions within Computer Science and Informatics ..........................................................12 Distinguished Service Award .......................................................................................13 ACM Athena Lecturer Award ........................................................................................14 Outstanding Contribution
    [Show full text]
  • Survey of Pen-And-Paper Computing
    Human-Computer Interaction Series Editors-in-chief John Karat Jean Vanderdonckt, Université Catholique de Louvain, Belgium Editorial Board Gaëlle Calvary, LIG-University of Grenoble 1, France John Carroll, Penn State University, USA. Gilbert Cockton, Northumbria University, Newcastle, UK Larry Constantine, University of Madeira, Portugal Steven Feiner, Columbia University, USA Peter Forbrig, Universität Rostock, Germany Elizabeth Furtado, University of Fortaleza, Brazil Hans Gellersen, Lancaster University, UK Robert Jacob, Tufts University, USA Hilary Johnson, University of Bath, UK Dianne Murray, Putting People Before Computers, UK Kumiyo Nakakoji, University of Tokyo, Japan Philippe Palanque, Université Paul Sabatier, France Oscar Pastor, University of Valencia, Spain Fabio Pianesi, Istituto Trentino di Cultura, Italy Costin Pribeanu, National Institute for Research & Development in Informatics, Romania Gerd Szwillus, Universität Paderborn, Germany Manfred Tscheligi, Center for Usability Research and Engineering, Austria Gerrit van der Veer, Vrije Universiteit Amsterdam, The Netherlands Shumin Zhai, IBM Almaden Research Center, USA Thomas Ziegert, SAP Research CEC Darmstadt,Germany Human-computer interaction is a multidisciplinary field focused on human aspects of the de- velopment of computer technology. As computer-based technology becomes increasingly per- vasive – not just in developed countries, but worldwide – the need to take a human-centered approach in the design and development of this technology becomes ever more important. For roughly 30 years now, researchers and practitioners in computational and behavioral sciences have worked to identify theory and practice that influences the direction of these technologies, and this diverse work makes up the field of human-computer interaction. Broadly speaking it includes the study of what technology might be able to do for people and how people might interact with the technology.
    [Show full text]
  • From Customer Value Constellation to Service Experience Blueprinting
    Journal of Service Research 000(00) 1-21 ª The Author(s) 2011 Multilevel Service Design: Reprints and permission: sagepub.com/journalsPermissions.nav From Customer Value Constellation DOI: 10.1177/1094670511401901 to Service Experience Blueprinting http://jsr.sagepub.com Lia Patrı´cio1, Raymond P. Fisk2, Joa˜o Falca˜o e Cunha1, and Larry Constantine3 Abstract The proliferation of complex service systems raises new challenges for service design and requires new methods. Multilevel Service Design (MSD) is presented as a new interdisciplinary method for designing complex service systems. MSD synthesizes contributions from new service development, interaction design, and the emerging field of service design. MSD enables integrated development of service offerings at three hierarchical levels: (a) Designing the firm’s service concept with the customer value constellation of service offerings for the value constellation experience; (b) Designing the firm’s service system, comprising its architecture and navigation, for the service experience; and (c) Designing each service encounter with the Service Experience Blueprint for the service encounter experience. Applications of the MSD method are described for designing a new retail grocery service and for redesigning a bank service. MSD contributes an interdisciplinary service design method that accommodates the cocreative nature of customer experiences and enables experience integration from the design of the service concept through the design of the service system and service encounter. Keywords service system design, customer experience, value constellation, blueprint, technology-enabled multi-interface services Introduction cocreate value (Maglio et al. 2009). For example, customers can cocreate value by combining service offerings from multi- The rapid evolution of service systems raises new challenges ple firms, such as credit and insurance in the case of a home for service design.
    [Show full text]
  • CALIFORNIA STATE UNIVERSITY, NORTHRIDGE the EVOLUTION of SOFTWARE DESIGN IDEAS a Thesis Submitted in Partial Satisfaction Of
    CALIFORNIA STATE UNIVERSITY, NORTHRIDGE THE EVOLUTION OF SOFTWARE DESIGN IDEAS A thesis submitted in partial satisfaction of the requirements for the degree of Master of Science in Computer Science by David J. Koepke May 1985 The thesis of David J. Koepke is approved: Professor Diane Schwartz Professor Russell '1:1;;'{t;Chair California State University, Northridge 11 ACKNOWLEDGEMENTS I would like to express my sincere gratitude to Professor Russ Abbott for all the enlightening conversations, suggestions, and generous extended use of his software design books and articles. I would also like to thank Pat Morales for her vital assistance in typing and revising this thesis, typing and distributing the inquiry letters, and her moral support throughout this project. A special thanks to Larry Constantine, Edsger Dijkstra, C.A.R. Hoare, James Emery and Donald Knuth for their responses to my questions on the history of software design. iii TABLE OF CONTENTS Page List of Figures ..................................... vii Abstract . Vlll Chapter 1 INTRODUCTION . 1 1.1 Overview of Thesis . 3 1.2 Previous Historical Texts 4 1.3 Historical Errors . 4 1.4 Design Influences of the Past 6 Chapter 2 ABSTRACTION 9 2.1 Early Abstraction 10 2.2 Top-Down Design/Stepwise Refinement 14 2.3 Levels of Abstraction . 20 2.4 Program Families 22 2.5 Abstract Data Types 24 2.6 Summary 32 Chapter 3 MODULARITY 34 3.1 Early Modularity 35 3.2 Information Hiding ..•.....• 42 3.3 Object-Oriented Programming 46 3.4 Summary ................................ 53 iv Chapter 4 STRUCTURED PROGRAMMING 54 4.1 Genesis of Structured Programming .
    [Show full text]