NetBeans 6 delivers great updates to the Matisse GUI builder. Spend a few minutes with Roman Strobl and get an expert briefing on what's new and what has changed. (sponsored)
In this, the third and final installation of Andres' Introduction to Groovy series, you learn about how Groovy handles variable numbers of arguments, named parameters, currying, and more about Groovy operators. Including, some new operators.
Swing Fuse (actually just Fuse), is a framework designed to make it easier to create your own custom desktop components. In this article, Daniel Spiewak shows you how to get started and provides sample source code you can download.
Willam Louth shows how he uses JXInsight Probes to investigate probable performance issues with code bases that he is not familiar with. He also highlights possible pitfalls in creating a benchmark, as well as in the analysis of results.
The introduction to the book starts with an interesting phrase "The difference between "theory" and "practice" is that in theory there is no difference between theory and practice, but in practice there is." The authors like to apply this statement to UML modeling, and continue later saying, in theory, everything in UML is useful, but in practice, a whole lot of people and projects need to know how to drive an OO software design from use cases.
The sample chapter includes a 4-step process for creating a sequence diagram; the example design is a Java/Spring Framework web-app.
The OOAD process that we cover focuses on the area that lies in between use cases and code. Its emphasis is on what needs to happen at that point in the life cycle where you’re starting out: you have a start on some use cases, and now you need to do good analysis and design. In the book, we also illustrate how to take the design through to unit tests and source code, and show how to keep your UML model and Java code in sync ready for the next bout of development.
Meera -- to answer the question in your review about why the chapter on testing wasn't presented before the Coding chapter..... It was one of those cases where we didn't want to introduce too many new concepts all at once. In the Coding chapter, we talk about how to create your entity classes from the detailed design for the example use cases. However if we'd talked about how to create tests for those classes before talking about creating them, it wouldn't have made a huge amount of sense (lots of forward-references). Hopefully this way, it all flows much more clearly.
We definitely favour the test-first approach though (i.e. write the tests before writing the code), although the process is flexible enough that you can pretty much "take it or leave it" and still benefit hugely from the main OOAD process that we cover.
Hi Matt,
Thanks for your response on my review. I now understand why the tests weren't written before the coding chapter. As a reviewer and a programmer, I guess I was looking at a completely different perspective.
Kudos to both of you for giving the community such a good book.
Book Review-Use Case Driven Object Modeling with UML-Theory and Practice
At 1:17 PM on Mar 28, 2007, Meera Subbarao wrote:
Fresh Jobs for Developers Post a job opportunity
Read on for Meera's full review.
2 replies so far (
Post your own)
Sample chapter download
Thanks for the nice review!You can download a sample chapter from the book here:
http://www.apress.com/book/bookDisplay.html?bID=10210
The sample chapter includes a 4-step process for creating a sequence diagram; the example design is a Java/Spring Framework web-app.
The OOAD process that we cover focuses on the area that lies in between use cases and code. Its emphasis is on what needs to happen at that point in the life cycle where you’re starting out: you have a start on some use cases, and now you need to do good analysis and design. In the book, we also illustrate how to take the design through to unit tests and source code, and show how to keep your UML model and Java code in sync ready for the next bout of development.
Meera -- to answer the question in your review about why the chapter on testing wasn't presented before the Coding chapter..... It was one of those cases where we didn't want to introduce too many new concepts all at once. In the Coding chapter, we talk about how to create your entity classes from the detailed design for the example use cases. However if we'd talked about how to create tests for those classes before talking about creating them, it wouldn't have made a huge amount of sense (lots of forward-references). Hopefully this way, it all flows much more clearly.
We definitely favour the test-first approach though (i.e. write the tests before writing the code), although the process is flexible enough that you can pretty much "take it or leave it" and still benefit hugely from the main OOAD process that we cover.
Agile Development with the ICONIX Process: A core subset of agile UML techniques.
Extreme Programming Refactored: The other side.
Re: Sample chapter download
Hi Matt,Thanks for your response on my review. I now understand why the tests weren't written before the coding chapter. As a reviewer and a programmer, I guess I was looking at a completely different perspective.
Kudos to both of you for giving the community such a good book.