We will now build up a schedule definition introducing the concepts as discussed.

Starting with the base pool of reusable building blocks – dependencies can be added. The building blocks are also expanded to define what is in them (though these are secondary events).

  

Each of these building blocks could be expanded thus:

However in many cases there could be different dependencies for (say) different types of instruments. One solution would be to hard wire this for all the different applicabilities (e.g. instrument, market, time) so have separate schedule for swaps, bonds etc – but would lead to a lot of schedules…..

So to make a single generic definition to work in all cases applicability can be defined. This definition can be expanded as new product come along.

What we have here is a single schedule with generic applicability that can work for all combinations of (in this case)  instrument, market and time. 

So we have covered the schedule, which provides the skeleton of our STP, lets move on to looking at parts of the STP that actually “do things”….

© 2002-2005 Codel Services Ltd

This paper has been prepared by Codel Services Ltd to illustrate how structured business modelling can help your organisation. Codel Services Ltd is an IT Consultancy specialising in business modelling. If you would like further information, please contact us at: Deryck Brailsford, Codel Services Ltd, Dale Hill Cottage, Kirby-Le-Soken, Essex CO13 0EN,United Kingdom. Telephone: +44 (0)1255 862354/Mobile: + 44 (0)7710 435227/e-mail: info@codel-services.com