A good book on design patterns?

Hi there. Just wondering if anyone could recommend a good book on design patterns, for someone who's relatively experienced at the nuts and bolts of programming in a few languages, but hasn't really considered design patterns before? Someone recommended Gamma et al's, 'Design patterns: elements of reusable object-oriented software' to me, but it is perhaps a little dated now. Any thoughts?

Surprisingly, no one posted the link to the Sun J2EE Pattern blueprints:
http://java.sun.com/blueprints/corej2eepatterns/index.html
I also liked the O'Reilly publication "J2EE Design Patterns"
They are specific to J2EE architecture, but there's a lot of reuse available even if that's not the architecture you're working with.
Brian

Similar Messages

Good books on Designer 6i

Can anyone recommend a good book on Designer 6i ?
All the books I have come across are for Designer/2000.
thanks

Either this was a difficult question or no one wants to share their favorite books :-)
For now I settled for the German book "Masterkurs Client/Server-Programmierung mit Java: Anwendungen entwickeln mit JDBC, Sockets, XML-RPC, RMI und JMS - Kompakt und praxisnah - Zahlreiche Programmbeispiele und Aufgaben". But I'm still very much interested in other titles on the choices, trade-offs, architecture, when to use web-services, etc.

[BOOK] What's the best book about DESIGN PATTERN

Hi Guys,
by experience, what's the best book for you concerning the Design Pattern in Abap. I mean :
Quality,
Comprehensiveness,
Clearness,
Amount of chapter,
etc.
Thank for advices.
Rachid.

Dear Rachid,
This is rank 1 book, but u have learn online also. So many websites are there. example search: OO Design patterns ZEVOLVING.
Regards,
Abbas.

Recommend design pattern books

Hi
I work at a university and I am looking for some books on design patterns in LabVIEW, preferably for 2009.
I am interested in state machine and master/slave design and perhaps also producer/consumer design pattern.
Can you recommend some books on these techniques.
Simon
LabVIEW 8.6 / 2009 / 2010
Vision Development Module 8.6 / 2009 / 2010
VBAI 3.6 / 2010

The LabVIEW Style Book by Peter Blume has a chapter devoted to discussing patterns in LV. If you want to go generic and not pin yourself to one language, the classic of the subject is Design Patterns by Gamma, Helm, Johnson & Vlissides - that book has been on my shelf ever since I used it as a textbook over a decade ago.
Greg
Certifed LabVIEW Developer

Get instance method and design pattern

Hi All,
1. I New to abap objects and i read the help and some stuff from the forum,
l like to now more about design pattern in abap objects,
2. I saw in some abap class the use of method of GET_INSTANCE i think it's from factory pattern , what is the pros. and cons to use this method ,when i should consider to use it ?
Thanks in Advance
Nina

Hello Nina
A very good introduction into design patterns is the book "Head First: Design Patterns". Here you will find many good reasons why and when to use the factory pattern.
You should use the factory pattern when
- you want to prevent "direct" instantiation (i.e. using a public CONSTRUCTOR method) by the developer
- you want to hide the complexity of instantiation from the user of the class
- the instantiation creates an implementation of an interface and you want to keep control of which implementing class is returned
Regards
Uwe

Finding instance from variable design pattern required

Hello guys,
In my appication I need to get instance of a class from its instance variable.
Let me explain in deep.
I have one class ServerConnection in which I accept connection from client as a SocketChannel..
In the same class I pass this channel variable to new Player construcotr and create one Player class instance.
Now each player has it's own channel.
My problem is that when particular channel closed I have to identify particular Player from so many player..
So how can I identify that instance..
I can do this by comparing socket port but there are so many players instance so it is some burden some.
I need some pattern which can help out me to identify particular player by simply passing Socketchannel as parameter..
Please help me out.

Hello Nina
A very good introduction into design patterns is the book "Head First: Design Patterns". Here you will find many good reasons why and when to use the factory pattern.
You should use the factory pattern when
- you want to prevent "direct" instantiation (i.e. using a public CONSTRUCTOR method) by the developer
- you want to hide the complexity of instantiation from the user of the class
- the instantiation creates an implementation of an interface and you want to keep control of which implementing class is returned
Regards
Uwe

Abstract Factory Design Pattern

Could someone please explain the abstract factory design pattern in simple english. As far as I understand it is used to create a bunch of related objects based on parameter/s provided at runtime.
However, why would one use this compared to an Interface.
I actually am reading a great book on design patterns (Design Pattern by James Cooper) but having a bit of problem really understanding this one.
Cheers

As far as I
understand it is used to create a bunch of related
objects based on parameter/s provided at runtime. There may be variations but as I understand it basically an Abstract Factory defines two interfaces, one is the factory and one is the product. A good example is iterators in Java. The iterator factory is the Iterable interface and the iterator product is the Iterator interface.
ArrayList implements Iterable so it's an iterator factory. If you call the iterator() method of an ArrayList object you'll get an Iterator object. The same applies to TreeSet and many other classes.
The Iterator objects sport the same Interface but they're quite different internally of course (Iterating an array is not the same as iterating a tree) so they're a "family of related products".

Anyone recommends a good book for object oriented programming

I am a college student in computer engineering (Software) and have been programming using Java for over a year. I have become really interested in the design of softwares and the "beauty" of object oriented programming, and thus would like to advance my knowledge about the topic (my university offers an advanced oop class but I would have to wait another 6 months to take it). So my question is, could you recommend me any book that covers the subject of object oriented programming extensively? (I have learned most of the oop I know from "An Introduction to Programming and Object Oriented Design Using Java" by Nino and Hosch.
Thanks in advance

Some years ago I remember cutting my teeth on OOP using an excellent book by Grady Booch. If it's still in print and has been updated, it may be worth a look. Again it was decent. Also consider picking up a book on design patterns. Good luck.
Edit: I found it, it's called "Object-Oriented Analysis and Design with Applications", and it's in its third edition. You can find it here on Amazon.
Edited by: Encephalopathic on Apr 22, 2008 2:48 PM

Suggest good book for J2EE Design Pattern.

Is there any good book for J2EE Design pattern? I know Head First Design Pattern book, but is focuses oncore java. I want to learn in detail with examples J2EE design pattern.
Please suggest good books.
Thanks in advance.
Rahul.

most j2ee patterns are discredited now. they were mostly workarounds for deficiencies in ejb 1 & 2 specs.
"core j2ee patterns" is your best bet, but take it with a grain of salt.
better to learn spring, IMO:
springframework.org
%

Good book on Object Oriented Design?

Can you recommend a good book on Object Oriented Design with lots of practical examples? I already have:
http://www.amazon.com/Design-Patterns-Object-Oriented-Addison-Wesley-Professional/dp/0201633612/ref=sr_1_1?ie=UTF8&qid=1238324375&sr=8-1
But currently I need a book with a more basic approach.

corlettk wrote:
I like Thinking In Java... Also: google for "yawmark's list"TIJ is useless, especially for teaching OO design. It teaches (or tries to) Java as a procedural language.

Books about MVVM, architecture, design patterns for Windows Phone 8.1

Hi,
I'm looking for a book or books (or other resources) that explain how to develop an app with a proper architecture. I mean what each layer (bussines layer, data layer, network access) should do and how should it look like. I'm also looking for a book about
MVVM.
Right now I'm struggling with how to create a layer for network communication - how to separate classes for requests and responses, how to manage requests and create some queue of requests and also to provide some way to cancel them when they are no longer
needed, how to work with servers that use some level of security (cookies, certificates etc.).
Another thing is caching - how to design a short-term cache or a persistant cache (database), what technologies I can use etc.
Last thing that I'm struggling with is also naming. How to name classes in those layers, e.g. to distinguish between classes mapping data from some ORM database, for mapping on JSON in network communication. etc.
I hope you got the idea :)
Thanks.

Currently, I don't find a book about MVVM pattern for Windows Phone 8.1, but I think MSDN and some blogs have some useful samples and conceptions: http://msdn.microsoft.com/en-us/library/windows/apps/jj883732.aspx
http://channel9.msdn.com/Series/Windows-Phone-8-1-Development-for-Absolute-Beginners
And I think your question includes too much scopes, maybe you need to split it into some blocks and get help in the related forum
Best Regards,
Please remember to mark the replies as answers if they help

Is this a good design pattern?

Hi,
I am working with a team to create an application that can acquire data from up to 24 thermcouple channels. We plan to create a wizard to assist the user in setting up the test (specifiying stop conditions, sample rate, channels to sample, output file, and email/text notifications). After the setup, if the user does not cancel out, then the program continues. We have defined parallel loops and their roles, trying to fit into a producer/consumer design pattern. I have attached the main file which shows the structure of the program. We are trying to keep it clean and modular. Before diving into development, we are finalizing a detailed design specification so that different people can work on each of the loops' subvis. I was hoping that people could review the block diagram and offer suggestions for improvement or validate that we have chosen a good method of implementation.
Notes about the block diagram
The plan is for data driven stop conditions to be detected by Event Notifier, handled by the Main UI event, and then the Data Collector is instructed to stop (as well as the Main UI loop). When Data Collector stops, it releases queues, the queue reference becomes invalid, and then the loops with the Dequeue will be stopped.
I am not sure if an additonal event structure should be in the DataCollector to specifically handle the Stop button on the UI because if it is in the Main UI event structure, the DataCollector would not be stopped immediately. This is important to stop quickly because the sample rate could be VERY long. I understand about using an event structure instead of WAIT, but didn't know if there is an efficient way leaving it down in the Main UI event structure....????
Data Collector is the producer, it currently only collects data and passes it on. If the program is going to contain a start collection button, or pause/resume, I need to figure out how to handle this with the Main UI event structure.
Event Notifier consumes data from the Data Collector. It looks at all data and should set a flag if a stop condition is met. The flag will be handled by the Main UI event structure to tell Data Collector to stop. The event notifier also sends a notification to the Email/Text Caller when thresholds have been exceeded warranting a reason for the user to be notified via text or email.
Email/Text Caller waits for notification and then calls a subVI to send an email or text with certain data and channel information. The subVI call is lengthy, so we decided to put this in its own loop instead of a case structure inside the Event Notifier.
Report Generator logs all collected data to a file. A second queue was used, but uses the same data as the first. Is this the correct implementation since two consumers need the same data?
Main UI - handles changing of sample rate, possibly the stop button, possibly start/pause/resume of data collection. Also handles when Event Notifier sets flag for a data driven stop condition, which then should provide a mechanism to stop the Data Collector.
A big question that i have is.... Should the Main UI event structure just be in the Data Collector so that the loop can be stopped immediately? All of the UI events (stop button, start/pause/resume data collection) directly effect the Data Collector. Should the data Collector have a state machine instead?
I feel that the 3 consumer loops (Event notifier, Email/Text Caller, and Report Generator) seem like a good implementation, but i am not confident about the Data Collector and Main UI loops. Should they be combined?
Solved!
Go to Solution.
Attachments:
updatedMain.vi ‏13 KB

A couple of thoughts:
Overall it looks workable- remember to name your queus and notifiers- then you can depop the BD and launch each loop in its own sub-vi without wiring all those queues between loops- Just obtain ref to named queue.
"Data collector" needs a supervisor to control how often the data is collected- I'm thinking a QSM with "init- collect- stop" states. A simple timed loop could produce the "time to acq ticks" under control of the sample rate control. This puts both the DAQ init and cleanup functions within the Data Collector's perview so it aids coehesion and solves the exit without waiting for the loop to iterate.
I'm not a fan of duplicating data- I assume analisys is pretty much just some comparisons- so it is pretty quick- Why not append summary data to the same queue? And make it a single element queue- the report loop can then inspect the queue and look for a summary data "index" - if its greater than the last index written append the darn data to the report? Preview queue works great for these situations.
Do not combine the UI handeler with anything else! Do you see the snag?- hint: here thar be spaghetti. keep the functions seperated for solid scalable and maintainable code.
One last thought: Its getting less popular to stop loops on the error out of a dequeue. First it returns a default element that can cause your listeners some headaches. Second it doesn't let you run cleanup code. Use a stop command <enum> built into the element data as an executive to determine when to stop. We'll try to get the examples updated to show current best practices.
Jeff

Know any good books on OO design in Java?

Can any one recommend a good book on OO design in Java.
I want a book that explains the best practice on method sizes, what to make member varibles or local variables, when to pass parameters, etc...
I have a fair bit of java programming experience, so I don't really want a book for beginners, but one that concentrates on perfecting your OO design skills.
Any recommendations?

Some GREAT online resources...
http://www.patterndepot.com/put/8/JavaPatterns.htm
http://www.objectmentor.com/resources/listArticles?key=author&author=Robert%20C.%20Martin

EJB Design Patterns Book Question

I have been recently reading the EJB Design Patterns book by Floyd Marinesu.
In one of the earlier chapters he says that 'entity beans are transactional creatures, each method call on an entity will require a separate transaction ..'.
Surely this is wrong, if you are using CMT and mark your method transaction attribute as Required then if the calling bean has a transaction the called bean will use that transaction, rather then requiring a separate transaction.
Someone please explain.

Quoted out of context, the statement seems to be incorrect in some cases. IMO, the fact stressed is the "synchronization of the remote entity", which might have been loosely associated with a separate transaction.
Here's the original quote.
Furthermore, since entity beans are transactional creatures, each method call on an entity will require a separate transaction on the server side, requiring synchronization of the remote entity with its underlying data store and maintenance on behalf of the application server.
Maybe Marinescu would answer that better :-)

Any good article on Singleton design pattern recently updated.

Hi,
Can anyone suggest me a good article on Singleton design pattern recently updated..?
Thanks in advance.

Check out the following Singleton Design Pattern Tutorial
http://www.beginner-java-tutorial.com/singleton.html

A good book on design patterns?

Similar Messages

Maybe you are looking for