aspose file tools*
The moose likes Testing and the fly likes Cohen book: Design Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » Testing
Bookmark "Cohen book: Design" Watch "Cohen book: Design" New topic
Author

Cohen book: Design

Jeff Langr
author
Ranch Hand

Joined: May 14, 2003
Posts: 762
Greetings Mr Cohen,

I took a look at the Amazon blurb on your new book (congrats!). While the word "Design" is prominently featured in the title, the Amazon review didn't make much note of it. Can you discuss what your book covers with respect to design (and its impacts on/from design)?

thanks,
Jeff


Books: Agile Java, Modern C++ Programming with TDD, Essential Java Style, Agile in a Flash. Contributor, Clean Code.
Frank Cohen
author
Greenhorn

Joined: Apr 17, 2004
Posts: 18
Hi Jeff: Thanks for your interest in Java Testing and Design: From Unit Testing to Automated Web Tests (JTD.)

JTD is the first book to make the case that delivering services � software application functionality delivered over routed networks and open protocols � requires the combined effort of software developers, QA technicians, and IT managers. In my experience those three groups rarely cooperate. It's more like they put up with one another. So, when it's time to make design decisions for a new project or on maintaining an existing service there is rarely group discussion on the best design to use. JTD educates software developers, QA technicians, and IT managers on the available protocols, tools, and techniques to deliver services. For example, choosing tightly coupled n-tier server architectures over loosely-coupled multiple server designs. JTD encourages a build-it-to-be-tested design philosophy. That's the "design" part of Java Testing and Design.

I hope this answered your question. Please let me know.

Thanks.

-Frank


---<br />Frank Cohen, <a href="http://www.PushToTest.com" target="_blank" rel="nofollow">http://www.PushToTest.com</a> phone: 408 374 7426<br />Enterprise test automation solutions to check and monitor Web-enabled <br />applications for functionality, scalability and reliability.
Jeff Langr
author
Ranch Hand

Joined: May 14, 2003
Posts: 762
Thanks Frank!
Kishore Dandu
Ranch Hand

Joined: Jul 10, 2001
Posts: 1934
Frank:

Since you mentioned some insights into multi-network interoperable systems(probably in web context), does the book address or suggest good practises for this interoperability.

I am asking this because lately there is lot of noice about web-services, but with personal experience some requirements does not need this approach(sometimes good old urlconnection suffices for minimum frequency operations).

Let me know.


Kishore
SCJP, blog
Frank Cohen
author
Greenhorn

Joined: Apr 17, 2004
Posts: 18
Hi Kishore: I like simplicity too and sometimes the minimal approach works best. For example, if you are in control of the client/consumer and the service/server then why go through all the trouble of using SOAP when an HTTP Post with some XML in the payload will work just fine. This is the attitude Java Testing and Design takes when discussing architectural and design issues. It assumes that the software developer making protocol, library, and architectural choices is under the normal amount of stress � i.e. lots! - and needs to solve a problem quickly. Java Testing and Design begins with the "Forces at Work Affecting Your Web-Enabled Software." One tenth of it is about technology the rest of this chapter is about human nature.

Java Testing and Design suggests practices for achieving interoperability by describing the protocols and technologies available to software developers, including Java and .NET. It then shows the typical problems that come with each choice, including interoperability and scalability problems. For example, Java developers are regularly told by Sun to use SOAP RPC-encoding. The book shows that choosing SOAP RPC-encoding can lead to a 3000% decrease in throughput over the other encoding styles. Plus, SOAP RPC-encoding does not interoperate with .NET services easily.

-Frank
Alexandru Popescu
Ranch Hand

Joined: Jul 12, 2004
Posts: 995
Originally posted by Frank Cohen:
Java Testing and Design suggests practices for achieving interoperability by describing the protocols and technologies available to software developers, including Java and .NET. It then shows the typical problems that come with each choice, including interoperability and scalability problems.

On what basis/tests are these interoperability/scalability results done?

Java developers are regularly told by Sun to use SOAP RPC-encoding. The book shows that choosing SOAP RPC-encoding can lead to a 3000% decrease in throughput over the other encoding styles. Plus, SOAP RPC-encoding does not interoperate with .NET services easily.

This is quiet easy to understand ;-).

./pope



-Frank[/QB]
[ October 08, 2004: Message edited by: Ali Pope ]

blog - InfoQ.com
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Cohen book: Design