Beruflich Dokumente
Kultur Dokumente
Maria Stergiou
Computing Laboratory, University of Kent,
Canterbury, Kent, CT2 7NF, UNITEDKINGDOM
Email: M.Stergiou@ukc.ac.uk
and
Leslie Johnson
Computing Laboratory, University of Kent,
Canterbury, Kent, CT2 7NF, UNITED KINGDOM
Email: L.Johnson@ukc.ac.uk
yes
Produce Invoice
Invoice matches no
...
delivery note?
Document (a)
Controls
yes
Mechanisms
CLASS: INVOICE
IDEF0 (c)
Invoice Number
Invoice Customer CustomerNumber
CustomerName
One-to-many
Date Data
Amount
...
Entity Attributes
Customer …...
Object Oriented
Software Engineering (d)
Entity-Attribute-Relationship (e)
Figure 1 Alternative representations of Invoicing (as a process, activity, function, entity, etc.)
Figure 2 displays possible events that could take One may think that there is no need for an in-
place when a (written) business rule is depth analysis of all possible scenarios because
implemented. In this case, the person dealing they rarely occur. This could be true. However,
with the invoicing cross checks that the entries when they do occur, the possible cost they carry
on the invoice match the entries on the delivery with them may outweigh any benefit from
note signed by the customer. But there may be ignoring them in the first place. In the above
cases where the delivery note is misplaced or lost example, in the case of Employee A, s/he has
and cannot be retrieved from the files. Or, if it is already lost significant time in investigating the
found, its entries may not match the entries on problem that the rest of his/her work may be
the customer order. It is also possible that even if delayed. Or, in the case of Employee B, a
it is found and matches the customer order, it customer may become annoyed if sent invoices
does not carry the customer signature. for goods that were never delivered. Whenever
“Before we send the invoice to a customer, we cross check that the entries on the invoice
match the entries on the delivery note signed by the customer …”
BUT
(5) (6)
BUSINESS IT
Better RequirementsGathering
(RAD, JAD, etc.)
Better &NewTechnologies
(Networks, Telecomms , etc.)
Wearenot happy Better &NewM ethods
(IE, SSM , SSADM , etc.)
“Letsdothethingswedo
better / faster / cheaper” “Wearegettingbetter in automating ”
Better &NewTechnologies
(EDI, Groupware, Workflow, etc.)
Weare still not happy Better &NewM ethods
(UseCases, O-O, UM L, etc.)
“Nowwhat?” “???????”
exercise. case, unwritten business rules will be ignored by
choice and not by accident.