This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Yay, 2months after uploading I have my score, thankfully its passing! General Considerations(maximum = 58): 51 Documentation(maximum = 20): 20 GUI(maximum = 24): 21 Server(maximum = 53): 49 Everybody likes to see design decisions, but my design is basicly very common. -Used RMI -I chose to implement locking using the Delegation pattern, each Data object gets its own lockmanager object. -used abstractmodel -used swing worker threads -I used the factory pattern to give out remote or local Data objects based on the selection made in the login gui dialog. -booking: The way I chose to implement booking is also via the Delegation pattern.The bookManager class takes care of all the booking for client -mod vs extend: chose to modify the Data class only so that all its public methods were exposed via an interface and to fix the deprecated methods. I then extended the Data class via interface inheritance for both local and remote clients.