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.
Suppose I'm developing library automation software (circulation and acquisitions). I want to help the librarians decide which titles need more copies on the shelves, and which titles could be retired to the basement, based on circulation numbers. What kind of task is this, what is the indicated algorithm, and how would the algorithm be applied to suggest a course of action?
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com