General talk about software patterns

["Mike Beedle" <beedlem AT e-architects.com>]

Never mind, I found him at:

 

http://cba.fiu.edu/web/eg/dsis/batra.htm

 

- Mike

 

---

From: Mike Beedle [mailto:beedlem AT e-architects.com]
Sent: Friday, May 06, 2005 1:43 PM
To: 'patterns-discussion AT cs.uiuc.edu'
Subject: Anyone knows this guy?

 

 

Does anyone knows this guy?  I just go this from ACM:

 

http://www.acm.org/technews/articles/2005-7/0506f.html#item3

 

so I am going to drop him a note making him aware of “Design Patterns”,

 

- Mike

 

"Conceptual Data Modeling Patterns: Representation and Validation"
Journal of Database Management (04/05) Vol. 16, No. 2, P. 84; Batra, Dinesh

Florida International University professor Dinesh Batra defines design patterns in the context of data modeling as descriptions of objects, relationships, and attributes that are customized to address a generalized conceptual or logical database design problem. He examines a number of sources and from them extracts 11 data modeling patterns that are commonly found in business applications. Those patterns are identified as entity event, entity type, generic transaction, discrete transaction, time-based transaction, data warehouse, subsequent transaction, recursive, strict hierarchy, plan, and generalization. Batra validates these patterns by analyzing how often they crop up in three data model sources; one source is aimed at data modeling students and the other two target practitioners for the most part. The author concludes that most of the structures occur frequently enough in the sources to be considered patterns, although some patterns are employed more frequently than others. Type structure and transaction structures (generalization especially) are underrepresented in the academic source, while the plan structure is completely absent. The hierarchy structure is poorly represented in two of the sources, leading Batra to speculate that the hierarchy pattern may need to be renamed. The three sources alternately designate generalization, type, and transaction as the leading pattern.