home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.object
- Path: sparky!uunet!walter!porthos!dancer!haim
- From: haim@dancer.cc.bellcore.com (kilov,haim)
- Subject: Re: Constraint Management / Consistency Checking
- Organization: Bellcore, Livingston, NJ
- Date: Thu, 12 Nov 92 15:47:37 GMT
- Message-ID: <1992Nov12.154737.26597@porthos.cc.bellcore.com>
- References: <2930569391.0.p00058@psilink.com>
- Sender: netnews@porthos.cc.bellcore.com (USENET System Software)
- Lines: 21
-
- In response to Ron Schultz's question:
- that has a stated rule that for a
- particular checking account, that is only a credit card account for the same
- customer can be used to provide overdraft protection for the checking
- account. I am looking for a means to centrally locate these "rules" or
- constraints so that if the rule changes, I can change it in one location
- --
-
- These rules (constraints) are the preconditions for the corresponding
- operations. Certainly, the same operation may be reused more than once,
- but it has to be specified (i.e., its pre- and postconditions should be
- stated) only once. The particular operation here is "attempt overdraft
- protection". This stuff can be formulated, e.g., in Z (see Pamela Zave and
- Michael Jackson. Techniques for partial specifiction and specification of
- switching systems. Lecture Notes in Computer Science, Springer Verlag,
- Vol. 551 (1991), pp. 511-525).
-
- Hope this helps.
-
- -Haim Kilov
- haim@bcr.cc.bellcore.com
-