McGraw-Hill OnlineMcGraw-Hill Higher EducationLearning Center
Student Centre | Lecturer Centre | Info Centre | HOME

Overview
Table of Contents
Feature Summary
Request Password
Request Lecturer Copy
Buy Book

Jacket
Object-oriented Software Engineering: Practical Software Development using UML and Java
Timothy Lethbridge
Robert Laganiere


Feature Summary

  • Covers the most essential and practical software engineering knowledge in reasonable depth, but is short and simple enough to be absorbed by a second-year student in one academic term
  • Concepts presented are illustrated with implemented examples that readers can build upon
  • Focuses on knowledge and skills that industry most needs students to learn: object orientation, UML, Java, software architecture, user-interface design, and quality assurance
  • Teaches ways of thinking that have been shown to result in better software development: Iterative development, risk management, careful evaluation of alternatives and effective communication
  • Provides an in-depth treatment of key principles that have broad applicability with extensive use of examples and many integrated exercises
  • Based on the following eight themes that are woven together:
    1. Understanding the customer and the user. This theme is discussed in the context of use-cases, requirements and user interface design.
    2. Basing development on solid principles and reusable technology. The book provides reusable software and sets of principles on which readers can base their work.
    3. Visual modelling using UML as the standard.
    4. Evaluation of alternatives in requirements and design. Readers are taught how to make decisions in software engineering.
    5. Object orientation. There is in-depth coverage of analysis, design, as well as implementation using Java. Object-oriented design patterns are also covered.
    6. Iterative development. The book promotes this preferred way to develop software.
    7. Communicating effectively using documentation. The book suggests flexible formats for documentation, and gives guidelines for how to review it.
    8. Risk management in all software engineering activities.