This week's book giveaway is in the Design forum.
We're giving away four copies of Building Microservices and have Sam Newman on-line!
See this thread for details.
The moose likes OO, Patterns, UML and Refactoring and the fly likes Design Pattern for Management Documents Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Building Microservices this week in the Design forum!
JavaRanch » Java Forums » Engineering » OO, Patterns, UML and Refactoring
Bookmark "Design Pattern for Management Documents" Watch "Design Pattern for Management Documents" New topic

Design Pattern for Management Documents

Rafael Dipold

Joined: Apr 30, 2013
Posts: 1
A few months ago I met and I implemented a design pattern (just for example) called Actor-Role that represent very types of people (persons and organizations) and the various roles they represent (customer, employee, company, supplier, etc).

I wonder if there is a consensus or pattern which would apply to the management of documents such as Invoice, Order, Payroll, Budget, Quotation, etc.? Once these documents have certain dependencies and common features which can be converted from one type to another (eg Quotation -> Order -> Invoice)

Grateful for any help
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link:
subject: Design Pattern for Management Documents
It's not a secret anymore!