Explore the latest books of this year!
Bookbot

Allen H. Dutoit

    Inżynieria oprogramowania w ujęciu obiektowym UML, wzorce projektowe i Java
    Object-oriented software engineering
    Rationale management in software engineering
    Object-Oriented Software Engineering Using UML, Patterns, and Java
    • 2013

      Object-Oriented Software Engineering Using UML, Patterns, and Java

      Pearson New International Edition

      • 718 pages
      • 26 hours of reading

      Designed for advanced courses in Software Engineering and Object-Oriented Design, this text serves both junior/senior and graduate students. It is also suitable for short technical or intensive management courses, making it versatile for various educational settings.

      Object-Oriented Software Engineering Using UML, Patterns, and Java
    • 2006

      Thirty years ago, I first entered the dark realm of software engineering, through a prior interest in documentation. In those days, documentation pretty much meant functional specifications. The idea that stakeholders in a system (its implementers, its end-users, its maintainers, and so forth) might want something other than an alphabetic list of function definitions was just taking hold. There was an exciting (to me) vision of stakeholders accessing and contributing to explanations of how and why aspects of a system work as they do, tradeoff analysis of concomitant downsides, and perhaps even accounts of why other possible approaches were not followed. There were many challenges to overcome in achieving this vision. The most formidable is the belief that people do not like to create or use do- mentation. This negative image of documentation is (unfortunately) more than just the bias of a few incorrigible system developers. It is more like a deep truth about human information behavior, about how human beings construe and act towards information. Humans are, by default, active users of information; they want to try things out, and get things done. When documentation is interposed as a prerequisite between people and a desired activity, they try to skip through it, circumvent it, or undermine it. Desi- ing information to suit the needs and interests of its users is an abiding challenge, but we have come a long way from functional specifications as the only answer.

      Rationale management in software engineering
    • 2004

      Object-oriented software engineering

      Using UML, patterns, and Java

      • 734 pages
      • 26 hours of reading
      3.8(63)Add rating

      This thoroughly updated text teaches students or industry R & D practitioners to successfully negotiate the terrain for building and maintaining large, complex software systems. The authors introduce the basic skills needed for a developer to apply software engineering techniques. Next, they focus on methods and technologies that enable developers to specify, design, and implement complex systems. Finally, the authors show how to support the system changes throughout the software life cycle.

      Object-oriented software engineering