UML for Java Programmers (häftad)
Format
Häftad (Paperback)
Språk
Engelska
Antal sidor
288
Utgivningsdatum
2003-05-01
Upplaga
1
Förlag
Prentice Hall
Medarbetare
Reed, Ira
Illustratör/Fotograf
illustrations
Illustrationer
illustrations
Dimensioner
20 x 234 x 178 mm
Vikt
560 g
Antal komponenter
1
ISBN
9780131428485
UML for Java Programmers (häftad)

UML for Java Programmers

Häftad Engelska, 2003-05-01
559
Skickas inom 5-8 vardagar.
Fri frakt inom Sverige för privatpersoner.
UML for Java Programmers

Robert C. Martin

All the UML Java developers need to know

You don't use UML in a vacuum: you use it to build software with a specific programming language. If that language is Java, you need UML for Java Programmers. In this book, one of the world's leading object design experts becomes your personal coach on UML 1&2 techniques and best practices for the Java environment.

Robert C. Martin illuminates every UML 1&2 feature and concept directly relevant to writing better Java software--and ignores features irrelevant to Java developers. He explains what problems UML can and can't solve, how Java and UML map to each other, and exactly how and when to apply those mappings.

  • Pragmatic coverage of UML as a working tool for Java developers
  • Shows Java code alongside corresponding UML diagrams
  • Covers every UML diagram relevant to Java programmers, including class, object, sequence, collaboration, and state diagrams
  • Introduces dX, a lightweight, powerfully productive RUP & XP-derived process for successful software modeling
  • Includes a detailed, start-to-finish case study: remote service client, server, sockets, and tests
Visa hela texten

Passar bra ihop

  1. UML for Java Programmers
  2. +
  3. Agile Software Development

De som köpt den här boken har ofta också köpt Agile Software Development av Robert C Martin (häftad).

Köp båda 2 för 1408 kr

Kundrecensioner

Har du läst boken? Sätt ditt betyg »

Bloggat om UML for Java Programmers

Övrig information

ROBERT C. MARTIN is President of Object Mentor Inc., a leading consultancy in object-oriented design, patterns, UML, agile methodologies, and eXtreme programming. He authored the JOLT Award-winning publication Agile Software Development: Principles, Patterns, and Practices (Prentice Hall) and the best-selling Designing Object-Oriented C++ Applications Using the Booch Method (Prentice Hall). He edited Pattern Languages of Program Design 3 (Addison-Wesley), edited More C++ Gems, and co-authored XP in Practice with James Newkirk (Addison-Wesley). A well-known speaker at international developer's events, Martin edited the C++ Report for four years.

Innehållsförteckning



Figures.


Listings.


Forward.


Preface.


1. Overview of UML for Java Programmers.

Diagram Types. Class diagrams. Object diagrams. Sequence diagrams. Collaboration diagrams. State diagrams. Conclusion. Notes.



2. Working with Diagrams.

Why Model? Why build models of software? Why should we build comprehensive designs before coding? Making Effective use of UML. Communicating with others. Road maps. Back-end documentation. What to keep and what to throw away. Iterative Refinement. Behavior first. Check the structure. Envisioning the code. Evolution of diagrams. Minimalism. When and How to Draw Diagrams. When to draw diagrams and when to stop. CASE tools. But what about documentation? And Javadocs? Conclusion.



3. Class Diagrams.

The Basics. Classes. Association. Inheritance. An Example Class Diagram. The Details. Class stereotypes. Abstract classes. Properties. Aggregation. Composition. Multiplicity. Association stereotypes. Inner classes. Anonymous inner classes. Association classes. Association qualifiers. Conclusion. Notes.



4. Sequence Diagrams.

The Basics. Objects, lifelines, messages, and other odds and ends. Creation and destruction. Simple loops. Cases and scenarios. Advanced Concepts. Loops and conditions. Messages that take time. Asynchronous messages. Multiple threads. Active objects. Sending messages to interfaces. Conclusion.



5. Use Cases.

Writing Use Cases. What is a use case? The primary course. Alternate courses. What else? Use Case Diagrams. System boundary diagram. Use case relationships. Conclusion.



6. Principles of OOD.

Design Quality. Design smells. Dependency management. The Single Responsibility Principle (SRP). The Open.Closed Principle (OCP). The Liskov Substitution Principle (LSP). The Dependency Inversion Principle (DIP). The Interface Segregation Principle (ISP). Conclusion. Notes.



7. The Practices: dX.

Iterative Development. The initial exploration. Estimating the features. Spikes. Planning. Planning releases. Planning iterations. The midpoint. Velocity feedback. Organizing the Iterations into Management Phases. What's in an Iteration? Developing in pairs. Acceptance tests. Unit tests. Refactoring. Open office. Continual integration. Conclusion. Notes.



8. Packages.

Java Packages. Packages. Dependencies. Binary Components .jar Files. Principles of Package Design. The Release/Reuse Equivalency Principle (REP). The Common Closure Principle (CCP). The Common Reuse Principle (CRP). The Acyclic Dependencies Principle (ADP). The Stable Dependencies Principle (SDP). The Stable Abstractions Principle (SAP). Conclusion. Notes.



9. Object Diagrams.

A Snapshot in Time. Active O...