Company logo of Crocus Information LtdCrocus Information Ltd

Business Requirements Analysis consultancy to blue chip companies

Event Catalogue, Feasibility Study stage (slide 26)

The developing logical data structure diagram for the Acme Fashion case study's Feasibility Study phase, s24
case study home | previous | next

Event Catalogue table

The business events for Acme Fashion Supplies are documented in the table below. An event is when something happens in the real world that a business process or process chain has to react to.

The event catalogue ('catalog' for our American friends :D) has been derived from the top-level dataflow diagram and the analysis / meetings that went with it.

When the more detailed investigation is carried out and the top level decomposed, expect more to be added. Don't be surprised if a number of processes feature in the handling of each event as you decompose your initial dataflow diagram. You're quite likely to have find a process that's common to more than one business event.

Ref Short Name Description and effects Handled by process(es) Volumes
Ev01 Details of new customer received from Accounts A customer's application has to be approved by the Accounts Department. This establishes their initial credit limit. Accounts will have opened a new file for them in the Customer Master File. Sales then phone the new customer using the info from Accounts and take their first order. If an order was included with their application, this will have been passed on to sales with the other details from Accounts. Process 1, Sell Product and Take Order.
3 to 5 per week, a few tens per week during peak periods.
Ev02 Customer order received Customer orders arrive by phone, in the post and from the travelling sales team. The order details are recorded in the master sales spreadsheet and a printout from it makes up the sales order, despatch and delivery notes. Process 1, Sell Product and Take Order. Approx 25 orders per day, rising to 50 at peak times.
Ev03 Order filled After each order is filled, the Goods Out staff member updates the number in stock on the stock master file. If the new stock level is below the minimum stock holding level, they tick the re-order box. Process 3, Control Stock Approx 25 per day, rising to 50 at peak times.
Ev04 Delivery received from supplier Deliveries that are received from suppliers are accompanied by a delivery note. As Goods In staff check in the stock they tick each item on the delivery note. They then update the number in stock in C2 Stock Master File and pass the delivery notes to Stock Control.
Process 4, Receive Goods Into Stock Up to 5 times per day
Ev05 Order placed with supplier Goods Out staff tick those stock items in C2 Stock Master File that reach their minimum stock holding level as they fill orders throughout the day. The stock manager trawls the stock master file at regular inetrvals throughout the day, raising purchase orders for those ticked. As he does so, he erases the pencilled tick and inserts the purchase order number. He may phone a supplier first to ensure they have the stock to cover the order. The completed supplier orders are posted at lunchtime and in the evening post.
Emergency orders can be faxed through
Process 3, Control Stock 3 or 4 per average day
Ev06 Courier collects parcels for delivery to customer The courier collects parcels for delivery to customers four times a day. The Goods Out staff member who deals with the courier signs a collection receipt for the number of parcels in the load. S/he keeps the pink copy and files it in the dispatch log. Process 2, Fill and Dispatch Orders 4 times per day
Ev07 Goods returned by customer Customers are allowed to return unsold goods. They must use one of our pre-printed returns notes, pre-numberd. Goods are checked into stock as long as they are in original condition. As they are checked in, the staff member ticks off (or amends it to take into account rejects) the items on the returns note. They then update C2 Stock Master File to include the returned stock. Process 4 Receive Goods Into Stock Around 15 to 20 per day
Ev08 List of unfilled Customer orders received from the Stock Room The previous day's dispatch notes, for those orders that couldn't be filled completely, are passed to Sales at the start of each day.
Sales phones the customer to confirm whether the items should be put on back order and then updates their master sales s/sheet with the outcome. They file the dispatch notes (also updated with the outcome) for priority attention as new stock is delivered (also known as 'back orders').
Process 1 Sell Product and Take Order
Ev09 Back order cancellation received Sometimes, especially if items have been on back order for a long time, the customer will write in or phone to cancel the back order. Whoever takes the call updates the master sales s/sheet, finds the dispatch note that corresponds to the cancelled back order and hand-writes the item(s) cancelled. Process 1 Sell Product and Take Order 10 or 20 times per week.

All below are still to be completed

It's good practice to have a separate table to hold those you know about but are still working on. A side effect is it let's you easily report on progress to the project manager or BA team leader.

Ref Short Name Description and effects Handled by process(es) Volumes
Ev10 New advertising campaign planned New advertising campaign planned
Ev11 Credit limit list received from Accounts Credit limit list received from Accounts
Ev12 Stock levels received from Stock Control. Stock levels received from Stock Control.
Rcvd by Sales.
Ev13 Dispatch notes received from Goods Out. Dispatch notes received from Goods Out.
Rcvd by Control Stock.
E14 Delivery and returns notes received from Goods In Delivery and returns notes received from Goods In
Process 3, Control Stock
Ev15 Customer order received from Sales. Customer order received from Sales.
Rcvd by Goods Out - Fill and Dispatch Orders.
Ev16 Delivery received from supplier. Delivery received from supplier.

Go to Top
briefing / case study quiz | dataflow diagram notation quiz | exercises on modelling process and data