Business pattern
It is proposed that this article be deleted because of the following concern:
If you can address this concern by improving, copyediting, sourcing, renaming or merging the page, please edit this page and do so. You may remove this message if you improve the article or otherwise object to deletion for any reason. However, please explain why you object to the deletion, either in your edit summary or on the talk page. If this template is removed, it should not be replaced. The article may be deleted if this message remains in place for seven days, i.e., after 11:14 on 28 January. Notify author/project: {{subst:proposed deletion notify|Business pattern|concern=Jargon, no evidence of real notability - list of references confirm nothing}} ~~~~Timestamp: 20120121111402 |
A business pattern is a generic description of rules used by software engineers to create solutions suitable for a given business.
Historically, the business patterns catalog appeared during the nineties with the development of object oriented technologies and the e-business.
[edit] Notes
- Hruby, P., Kiehn, J., Scheller, C. V. (2006). Model-Driven Design Using Business Patterns. Springer. ISBN 3-540-30154-2
- Joshua Kerievsky (2004), Refactoring to Patterns, Addison-Wesley Professional, Boston, ISBN 0-321-21335-1.
- Gregor Hohpe, Bobby Woolf (2004), Enterprise Integration Patterns : Designing, Building, and Deploying Messaging Solutions, Addison-Wesley Professional, Boston, ISBN 0-321-20068-3.
- Martin Fowler (2003), Patterns of Enterprise Application Architecture, Addison-Wesley Professional, Boston, ISBN 0-321-12742-0.
- Mahesh M. Dodani (2003), Pattern Driven Solution Engineering, Journal of Object Technology, 2, 2, 27-33.
- Hans-Erik Eriksson, Magnus Penker (2000), Business Modeling With UML: Business Patterns at Work, John Wiley & Sons, Inc., New York, ISBN 0-471-29551-5.
