B-OSL - Object Oriented Specification Language for business ...

B-OSL Object Specification Language for Banking
file:///E:/_pilne/OSL-en/b-osl-en.htm
1 z 6 2013-02-23 09:24
"There's nothing as practical as good theory" (Kurt Lewin)
B-OSL - Object Oriented Specification Language for business - proposal
(banking example)
Copyright by Zygmunt Ryznar
OSL (Object Specification Language) contains business independent standard phrases, dedicated for definition any
objects, and key-words applied in a given business-area and/or in global business environment (UNIVERSE).
B-OSL is a subset of OSL (Object Specification Language) dedicated to define business objects. Object
is independent (self-contained) object having at least its own name, identifier, properties, behaviour and
"history". Object class includes various types of objects (concrete and abstract, existent and
non-existent, real and ideal, independent and dependent).
For banking typical objects are bank, headoffice, branch, customer, deposit-account, loan-accout, account
manager, loan-credit line, product offered by bank, dealer...etc.
Description is related to the main object called SUBJECT (e.g. bank). UNIVERSE, AREA i SUBJECT could be
treated as super-classes (at a top-hierarchy). Business classes within AREA are user-defined, to reflect
SUBJECT behaviour and needs. Specification contains also executive/operational objects, like account
manager, teller etc. and technical infrastructure objects (like servers, databases).
OSL NOTATION
=>
::=
:=
=
:
::
==

B-OSL Object Specification Language for Banking
file:///E:/_pilne/OSL-en/b-osl-en.htm
2 z 6 2013-02-23 09:24
{.....}
(x,y,..)
YYYYYY.UUUUU(XXXXXX)
[name]
(XXXX)
keywords
Environment (ENV)
ENV:=(REGULATIONS, INFRASTRUCTURE)
ENV.REGULATIONS:=(Legal acts, resolutions, decisions ... etc.)
ENV.INFRASTRUCTURE:=( Servers,OperationalSystems, TransactionalDataBases,
DataWarehouses,NetworkManagementSystem, OrganizationalStructureOfCompany )
Object specifications includes elements:
-id
-infoWindow
-dataTable
-typ obiektu ObjectTypes : (eOBJECT
- (ROLE)
- ( OLH -Object Life History )
- (RELATIONS)
-dynamic characteristics(PROCESSses, transactions. events, mode of triggering etc.)
-mode of execution (EXECUTION_MODE:= modeRT ,modeBAT modeOND )
- (DATA_FLOW)
- (CONTROL_FLOW)
Other OSL phrases:
trigger ,
generator ,
agent ,
integrator ,
executor ,
participator ,
owner, stockholder, customer, supplier; partner, employee,
component
performance center )
RELATIONS:=((activated by / activates, activated when/if,

B-OSL Object Specification Language for Banking
file:///E:/_pilne/OSL-en/b-osl-en.htm
3 z 6 2013-02-23 09:24
appearence depends on
assisted by, belongs to /is owned by , built from ,
calls (xxx,yyy)
consists of , contained in/contains, controlled by / controls,derived from,
driven by transaction,driven by product ,driven by banking regulations,
driven by customer, driven by date, driven by schedule,driven by frequency
existence depends on
exists when/in/for, evaluated as critical/most wanted , included in ,
linked to ...by / links, matched/matches
refers to relates to, related by affinity, represented by /
represents , involved in, shared by / shares, used by / uses)
STATE := (active,inactive,dormant,suspended,aborted,idle, lost)
STATUS := (generic, real, virtual)
dOBJECT
iOBJECT
vOBJECT < virtual object e.g. mirror Nostro accounts >.
dOBJECT ::= (EVENT,TRANSACTION,ACTION,PROCESSS)
{CONTROL_FLOW
repetition :=( iteration, single spiral, multiband spiral )
activated .... BY ...with AT WHEN ..
finished AT < > with WHEN ...}
{ DATA FLOW
from ()
to ()
dataGeneration Method
dataEncoding Method
dataCompressing Method
}
{BODY ::= ( Contents, Script, Metadata)

B-OSL Object Specification Language for Banking
file:///E:/_pilne/OSL-en/b-osl-en.htm
4 z 6 2013-02-23 09:24
contents
script
metadata }
Simple example of B-OSL (OSL for banking)
(for illustration purpose only)
infoWindow: =(BankId , BusinessType ,
country, bCurrency, FinancialYear, number of branches, RankingPosition, CurrencyLimits)
dataTables:= (CorrespondentBanks, Branches, Calendar-WorkingDays, bkAccountChart>
id :=BIC
keywords:= (IBAN , ICC , BIC
dataTables:= (LIBOR, OperatingCurrences >,
BUSINESS_MODULES::=(DEPOSITS, LOANS, CIF-INFO, MONEY-MARKET, PAYMENTS, DERIVATES,
SHARES)
keywords:=( BranchNr, CustomerId, AccountNr, Rate, Balance, tunParameter{
)
dataTables := (Product)
procedures:= (NaliczOds, ...)
interest-rate refers to
OperationalObjects ::= [teller, AccountMgr, CustomerMgr, ProductMgr, trader]
{
CLASS ::= ( SUBJECT, PRODUCT, CURRENCY, LIMIT, ACCOUNT,
TRANSACTION,OPERATION,PROCESS,EVENT)

B-OSL Object Specification Language for Banking
file:///E:/_pilne/OSL-en/b-osl-en.htm
5 z 6 2013-02-23 09:24
PRODUCT ::= (ACCOUNT, DERIVATIVES, )
ACCOUNT::= (CURRENT, DEPOSIT, LOAN)
LIMIT ::= (COUNTRY, INDUSTRY, CUSTOMER, CURRENCY)}
{
eOBJECT ::= (CUSTOMER,BANK,ACCOUNT,CURRENCY, DERIVATIVES)
iOBJECT::= (CUSTOMER-POSITION, MONTHLY-BALANCESHEET)
}
{
SUBJECT : (coSUBJECT , prSUBJECT )
BANK: (dmBANK , corBANK )
ACCOUNT: (bsACCOUNT ,nbsACCOUNT
TRANSACTION:
(rtTRANSACTION ,
eodOPERATION )}
eomOPERATION )}
eoyOPERATION )}
eoppOPERATION )}
EVENT: ( in-ev , end-ev , pn-ev , dl-ev )} rv-ev
infoWindow :=(owner, co-owner
MinBalance,actualBalance,HistoryStatement)
Relates to CUSTOMERid
rtTRANSACTION := (Open, Quit, Cash-in, Cash-out, transfer)
eomTRANSACTION:= (printStatement)
tunParameter := (interest-rate, period, ...)
id::= (AccountNr)
exists for prSUBJECT
initiated by FirstPayment
ACCOUNT.CURRENT::infoWindow :=(DebetLimit , repPAYMENTS, StatementType, VisaCardId)
calls ArchEvent(5y,eoy) )

B-OSL Object Specification Language for Banking
file:///E:/_pilne/OSL-en/b-osl-en.htm
6 z 6 2013-02-23 09:24
Concluding remarks
B-OSL specification is a descriptive schema with links to information technology. It could be a good
base for comparative analysis of banking solutions (if all of them are specified in the same notation).
Going further, if the implementation of this language is equipped with computer generator of tables
and graphs, the "image" of business object is more readable.