Generic Concepts for Specifying Relationships

Business patterns: reusable abstract constructs for business specification

“…They may be considered as building blocks from which both complex and complete business specifications, and higher-level, reusable yet still generic "nonelementary business patterns" can be constructed. Some simple nonelementary patterns were shown in (Kilov, Ross, 1994a). A "notification" is a typical example widely used in telecommunications and elsewhere: it results in the creation of an instance of a thing (such as a "traffic violation ticket") only if a triggering condition ("notification criteria") is satisfied for a particular state of a particular instance of a "monitored object".…”

“…(A composition of symmetric relationships, a generic molecular pattern described in (Kilov, Ross, 1994a), can be used to rigorously formulate this invariant}. Note: If the share of interest has not been established (ie it is not yet known to the business), in most cases the only operation that can be applied for this pattern is "establish the share of interest"; this operation involves information the pattern of which was presented above.…”

Testing of Relationships in an OSI Management Information Base

“…This concerns for instance MO attributes referring to other MOs or constraints concerning the joint behavior of MOs [19] in behavior specifications. The representation and management of relationships per se as part of a MIB are like before based on the well known basic OSI management concepts.…”

“…However, MOs arc not isolated from each other but maintain relationships reflecting the interworking and dependencies among the underlying network resources. The importance of relationships has been acknowledged by work on the ISO General Relationship Model (GRM) [18] and other activities [5,3,19]. The GRM is essentially an 'attachment' to the basic information model.…”

Towards Relationship-Based Navigation

“…We depict them using extended Kilov diagrams. In a Kilov diagram [Kilo94a,Kilo94b ], the relationship construct is indicated in a rectangle, as are the participating object classes; the triangle construct "Rel" between them indicates that the classes participate in the indicated relationship. In this paper, we represent each role binding with a Kilov diagram, extending it to also depict the roles which the participant classes play with each other.…”