Wednesday, August 15, 2007
Universal Data Model for Relationship Development
The PARTY ROLE entity maintains information associated with each role that a PERSON or ORGANIZATION plays, thus providing a more complete profile of each party by identifying all the roles played by each party. Thus, if a person is both an END-USER CUSTOMER and a CONTRACTOR (as I was in the airline example), then it is possible to see a more complete profile of the involved party. In many enterprises, employees purchase products from the enterprise and are not recognized with any special consideration, which could be frustrating. (For example, people can play the role of EMPLOYEE and BILL-TO CUSTOMER at the same time.) Similarly, when evaluating vendor proposals, it may be important to know if one of the organizations that is a SUPPLIER also plays a role as a CUSTOMER, even if it is in another division of the enterprise.
While the PARTY and PARTY ROLE entities maintain information about a single person or organization, the PARTY RELATIONSHIP entity maintains information about two parties within the context of their relationship. This data structure provides the capability to view an integrated profile of all the relationships in which a party is involved. For example, knowing that an organization has a PARTNERSHIP relationship with a part of the enterprise may be important to know when forming an ORG-CUSTOMER RELATIONSHIP (customer relationship between organizations) with another part of the enterprise. Other information related to PARTY RELATIONSHIP is the RELATIONSHIP STATUS (active, inactive, dead, etc.) and the PRIORITY TYPE (high, medium or low).
The EVENT maintains information about any activities, which may occur within the context of relationships. Events may be COMMUNICATION EVENTS such as phone calls, meetings and other contact events, as well as TRANSACTION EVENTS such as orders, shipments, payments and other business transactions. The EVENT ROLE maintains the type of role that each party plays in the event.
SOURCE: dmreview.com/article_sub.cfm?articleId=4820
Tuesday, August 14, 2007
Steps for creating a SOA model
Major steps for creating a SOA model:
1. Definition of the Domain
Monday, August 13, 2007
Tuesday, August 7, 2007
Monday, August 6, 2007
Dependency Injection
Usuall code to access database from Biz Service. Shows dependency of db in bizService.
There 2 types of Dependency - Opaque / Transparent
Opaque below - hard to test...for ex. you want to test without accessing the actual db instead use a fakeDb...its hard in this case.
Transparent
- dependency in case is INVERTED, it is asigned from outside.
- it is passed as a constructor argument
- easy to test...now you can pass a fakeDb object to test
to make it even more easy to test, consider the following change:
Now lets look at various ways to instantiate the object
Sunday, August 5, 2007
ER Notations
ONE throught MANY
ONE and ONLY ONE
- Two dashes it indicates that the first entity can have one and only one of the second
- specifically it cannot have zero,
- and it cannot have more than one
ZERO or ONE
- the first entity can have zero or one of the second, but not more than one
MANY to MANY
SOURCE: http://rapidapplicationdevelopment.blogspot.com/2007/06/entity-relationship-diagram-example.html
Friday, August 3, 2007
PageRank
If a famous doctorX (Recommender) refer (recommends) another doctorY (recommendee) it adds more weight than some unknown 20 people folks refer doctorY
PageRank = a web page is important if pointed to by another important page.
It is a score (PageRank Score) that indicates popularity (aka Popularity Score).