Your email was sent successfully. Check your inbox.

An error occurred while sending the email. Please try again.

Proceed reservation?

Export
Filter
  • Safari Tech Books Online  (4)
  • Fowler, Martin  (1)
  • Boston, Ma. : Addison-Wesley  (2)
  • Reading, MA : Addison-Wesley  (2)
  • Computer software ; Development  (2)
  • Object-oriented programming (Computer science)  (2)
  • COMPUTERS ; Programming ; Object Oriented  (1)
Datasource
Material
Language
Years
Author, Corporation
  • 1
    Online Resource
    Online Resource
    Boston, Ma. : Addison-Wesley | Boston, MA :Safari,
    Language: English
    Pages: xxvii, 334 p. , ill. ; , 24 cm
    DDC: 005.1/17
    Keywords: Computer software ; Development ; Object-oriented methods (Computer science) ; Electronic books ; local
    Abstract: "...I would expect that readers with a basic understanding of object-oriented programming and design would find this book useful, before approaching design patterns completely. Design Patterns Explained complements the existing design patterns texts and may perform a very useful role, fitting between introductory texts such as UML Distilled and the more advanced patterns books." --James Noble Design Patterns Explained: A New Perspective on Object-Oriented Design draws together the principles of object-oriented programming with the power of design patterns to create an environment for robust and reliable software development. Packed with practical and applicable examples, this book teaches you to solve common programming problems with patterns--and explains the advantages of patterns for modern software design. Beginning with a complete overview of the fundamentals of patterns, Design Patterns Explained stresses the importance of analysis and design. The authors clearly demonstrate how patterns can facilitate the overall development process. Throughout the book, key object-oriented design principles are explained, along with the concepts and benefits behind specific patterns. With illustrative examples in C++ and Java, the book demystifies the "whys," "why nots," and "hows" of patterns and explains pattern implementation. Key topics covered include: New perspectives on objects, encapsulation, and inheritance The idea of design patterns, their origins, and how they apply in the discipline of software design Pattern-based, object-oriented software development using the Unified Modeling Language (UML) How to implement critical patterns--Strategy, Observer, Bridge, Decorator, and many more Commonality/Variability Analysis and design patterns, and how they aid in understanding abstract classes From analysis to implementation, Design Patterns Explained allows you to unleash the true potential of patterns and paves the path for improving your overall designs. This book provides newcomers with a genuinely accurate and helpful introduction to object-oriented design patterns. 0201715945B06142001
    Note: Includes bibliographical references (p. 313-321) and index
    Library Location Call Number Volume/Issue/Year Availability
    BibTip Others were also interested in ...
  • 2
    Online Resource
    Online Resource
    Boston, Ma. : Addison-Wesley | Boston, MA :Safari,
    Language: English
    Pages: xiv, 393 p. , ill. ; , 24 cm
    DDC: 005.1/17
    Keywords: Computer software ; Testing ; Object-oriented programming (Computer science) ; Electronic books ; local
    Abstract: A Practical Guide to Testing Object-Oriented Software focuses on the real-world issues that arise in planning and implementing effective testing for object-oriented and component-based software development. It shows how testing object-oriented software differs from testing procedural software and highlights the unique challenges and opportunities inherent in object-oriented software testing. The authors reveal how object-oriented software development allows testing to be integrated into each stage of the process--from defining requirements to system integration--resulting in a smoother development process and a higher end quality. As they follow this process, they describe what to test at each stage as well as offer experienced-based testing techniques. You will find information on such important topics as: Testing analysis and design models, including selecting test cases to guide design inspections Testing components, frameworks, and product lines The testing challenges of inheritance and polymorphism How to devise an effective testing strategy Testing classes, including constructing a test driver and test suites Testing object interactions, covering sampling test cases, off-the-shelf components, protocol testing, and test patterns Testing class hierarchies, featuring subclass test requirements Testing distributed objects, including threads, life cycle testing, and Web server testing Testing systems, with information on stress, life cycle, and performance testing One comprehensive example runs throughout the book to demonstrate testing techniques for each stage of development. In addition, the book highlights important questions that testers should ask when faced with specific testing tasks. The authors acknowledge that testing is often viewed as a necessary evil, and that resources allocated to testing are often limited. With that in mind, they present a valuable repertoire of testing techniques from which you can choose those that fit your budget, schedule, and needs. 0201325640B04062001
    Note: Includes bibliographical references (p. 375-379) and index
    Library Location Call Number Volume/Issue/Year Availability
    BibTip Others were also interested in ...
  • 3
    Online Resource
    Online Resource
    Reading, MA : Addison-Wesley | Boston, MA :Safari,
    Language: English
    Pages: xxi, 190 p. ; , 24 cm
    DDC: 005.1
    Keywords: Computer software ; Development ; eXtreme programming ; Electronic books ; local
    Abstract: Software development projects can be fun, productive, and even daring. Yet they can consistently deliver value to a business and remain under control. Extreme Programming (XP) was conceived and developed to address the specific needs of software development conducted by small teams in the face of vague and changing requirements. This new lightweight methodology challenges many conventional tenets, including the long-held assumption that the cost of changing a piece of software necessarily rises dramatically over the course of time. XP recognizes that projects have to work to achieve this reduction in cost and exploit the savings once they have been earned. Fundamentals of XP include: Distinguishing between the decisions to be made by business interests and those to be made by project stakeholders. Writing unit tests before programming and keeping all of the tests running at all times. Integrating and testing the whole system--several times a day. Producing all software in pairs, two programmers at one screen. Starting projects with a simple design that constantly evolves to add needed flexibility and remove unneeded complexity. Putting a minimal system into production quickly and growing it in whatever directions prove most valuable. Why is XP so controversial? Some sacred cows don't make the cut in XP: Don't force team members to specialize and become analysts, architects, programmers, testers, and integrators--every XP programmer participates in all of these critical activities every day. Don't conduct complete up-front analysis and design--an XP project starts with a quick analysis of the entire system, and XP programmers continue to make analysis and design decisions throughout development. Develop infrastructure and frameworks as you develop your application, not up-front--delivering business value is the heartbeat that drives XP projects. Don't write and maintain implementation documentation--communication in XP projects occurs face-to-face, or through efficient tests and carefully written code. You may love XP, or you may hate it, but Extreme Programming Explained will force you to take a fresh look at how you develop software. 0201616416B04062001
    Library Location Call Number Volume/Issue/Year Availability
    BibTip Others were also interested in ...
  • 4
    Online Resource
    Online Resource
    Reading, MA : Addison-Wesley | Boston, MA :Safari,
    ISBN: 9780133065251 , 0133065251 , 0201485672 , 9780201485677 , 9780133065268 , 013306526X , 9780134757681 , 0134757688 , 0201485672
    Language: English
    Pages: xx1, 431 p. , ill. ; , 25 cm
    Series Statement: The Addison-Wesley object technology series
    Keywords: Software refactoring ; Object-oriented programming (Computer science) ; Electronic books ; local ; Object-oriented programming (Computer science) ; Software refactoring ; COMPUTERS ; Programming ; Object Oriented ; Logiciels ; Refactorisation ; Programmation orientée objet (Informatique)
    Abstract: As the application of object technology--particularly the Java programming language--has become commonplace, a new problem has emerged to confront the software development community. Significant numbers of poorly designed programs have been created by less-experienced developers, resulting in applications that are inefficient and hard to maintain and extend. Increasingly, software system professionals are discovering just how difficult it is to work with these inherited, "non-optimal" applications. For several years, expert-level object programmers have employed a growing collection of techniques to improve the structural integrity and performance of such existing software programs. Referred to as "refactoring," these practices have remained in the domain of experts because no attempt has been made to transcribe the lore into a form that all developers could use. . .until now. In Refactoring: Improving the Design of Existing Code, renowned object technology mentor Martin Fowler breaks new ground, demystifying these master practices and demonstrating how software practitioners can realize the significant benefits of this new process. With proper training a skilled system designer can take a bad design and rework it into well-designed, robust code. In this book, Martin Fowler shows you where opportunities for refactoring typically can be found, and how to go about reworking a bad design into a good one. Each refactoring step is simple--seemingly too simple to be worth doing. Refactoring may involve moving a field from one class to another, or pulling some code out of a method to turn it into its own method, or even pushing some code up or down a hierarchy. While these individual steps may seem elementary, the cumulative effect of such small changes can radically improve the design. Refactoring is a proven way to prevent software decay. In addition to discussing the various techniques of refactoring, the author provides a detailed catalog of more than seventy proven refactorings with helpful pointers that teach you when to apply them; step-by-step instructions for applying each refactoring; and an example illustrating how the refactoring works. The illustrative examples are written in Java, but the ideas are applicable to any object-oriented programming language.
    Note: Includes bibliographical references
    Library Location Call Number Volume/Issue/Year Availability
    BibTip Others were also interested in ...
Close ⊗
This website uses cookies and the analysis tool Matomo. More information can be found here...