Definition of a Description Language for Business Service Decomposition
Lam-Son Lê, Aditya Ghose, Evan MorrisonSchool of Computer Science and Software EngineeringUniversity of Wollongong (UoW)Australia
1. Definition of a Description Language
for Business Service Decomposition
Lam-Son Lê, Aditya Ghose, Evan Morrison
School of Computer Science and Software Engineering
University of Wollongong (UoW)
Australia
Slide 1 IESS 1.0, Geneva, Feb 2010 BSDL, UoW – funded by
2. Outline
• Services - An introduction
• Representation Spectrum of Services
• BSDL - Contribution
• Related Work & Future Work
Slide 2 IESS 1.0, Geneva, Feb 2010 BSDL, UoW – funded by
3. Context
• IT & business operated by services
– BMS
– ITIL
• Services at various perspectives:
universal, IT-enabling, business
• Services & Strategy correlation
Slide 3 IESS 1.0, Geneva, Feb 2010 BSDL, UoW – funded by
4. Example
Pre-construction clearance
Cost: 300’000
Schedule: 6 months
Penalty: 10 % deduction
on cost for every week
late
Lighting Facility Bridge Construction Pillars construction
Cost: 150’000 Cost: 2’000’000 Cost: 350’000
Schedule: 3 months Schedule: 28 months Schedule: 5 months
Penalty: 9% deduction on Penalty: 6 % deduction on Penalty: 8 % deduction on
cost for every week late cost for every month late cost for every week late
Span construction
Cost: 600’000
Schedule: 4 months
Penalty: 12 % deduction
on cost for every week
late
Slide 4 IESS 1.0, Geneva, Feb 2010 BSDL, UoW – funded by
5. To describe business services
1. Provider and Requester (Customer)
2. Capabilities
3. Non-functional Properties
4. Decomposition
5. Distribution of (2) and (3)
Slide 5 IESS 1.0, Geneva, Feb 2010 BSDL, UoW – funded by
6. Representation Continuum
<wsag:ServiceDescriptionTerm
wsag:Name=„EcoInf" <message
wsag:ServiceName=„Eco Calc"> name="GetLastTr">
<usdl:ServiceDescription> </message> <portType
<usdl:ServiceName>Eco ame="StockQuotePortType"
Calculator</usdl:ServiceName> >
Net work of web services
Business strategy Goal-oriented Internet of generic services and their interaction
requirements
SML GRL BSDL USDL BPMN BPEL4WS WSDL
Business services and Execution of web services
service decomposition Business processes
Slide 6 IESS 1.0, Geneva, Feb 2010 BSDL, UoW – funded by
7. Existing Work on Business Services
• Description of Service Capabilities
and Properties
– (DSCP) http://service-description.com/
– Capabilities
– Non-functional Properties
– Language (meta-)presented in ORM
Slide 7 IESS 1.0, Geneva, Feb 2010 BSDL, UoW – funded by
8. BSDL
• Is based on DSCP
• More concepts added to address
– Service decomposition
– Additional non-functional properties
• Meta-modelled in UML – good input for
tool implementation in Eclipse
• Formalized in Alloy
Slide 8 IESS 1.0, Geneva, Feb 2010 BSDL, UoW – funded by
9. BSDL: Meta-model
Rule Description
Acyclic There must be no cycle along
the decomposition
hierarchy of business
services.
Mutual For each business service, all
properties and
capabilities declared in it
must take it as their sole
service.
Uniqueness The set of parameters of two
different signatures must
be different.
Same An obligation and
service corresponding penalties
must be of the same
business service.
Slide 9 IESS 1.0, Geneva, Feb 2010 BSDL, UoW – funded by
11. Alloy as Formalization Language
• Alloy language
– Is a declarative modeling language based on
1st order logic and set theory
– Has OO syntax
• Benefits of using Alloy
– Building blocks & well-formedness rules
formalized together
– Alloy Analyzer tool enables:
• consistency checking
• visualization an instance model
Slide 11 IESS 1.0, Geneva, Feb 2010 BSDL, UoW – funded by
12. Formalized in Alloy
sig Decomposition {
decomposedService: one BusinessService,
constituentServices: some BusinessService
}
fact acyclic {
all e: seamHierarchicalElement | e not in
(e.^components + e.^parent)
}
constituentServices
Business Service 1..*
1 decomposedService
Decomposition sig Subcontracting extends Decomposition { }
Subcontracting
Slide 12 IESS 1.0, Geneva, Feb 2010 BSDL, UoW – funded by
13. Well-formedness rules in Alloy
sig Decomposition {
decomposedService: one BusinessService,
constituentServices: some BusinessService
}
fact acyclic {
all bs: BusinessService |
bs not in bs.^(~decomposedService.constituentServices) and
bs not in bs.^(~constituentServices.decomposedService)
}
sig Subcontracting extends Decomposition { }
Slide 13 IESS 1.0, Geneva, Feb 2010 BSDL, UoW – funded by
17. Related Work
• SLA@SOI
• WSDL
• DSCP
• USDL
• SML
Slide 17 IESS 1.0, Geneva, Feb 2010 BSDL, UoW – funded by
18. Conclusion
• Services from a business perspective
• DSCP defines business services, service
capability and non-functional properties
• More concepts needed
• BSDL addresses
– service decomposition
– schedule, penalty…
• BSDL defined using UML and Alloy
Slide 18 IESS 1.0, Geneva, Feb 2010 BSDL, UoW – funded by
19. Future work
• Improvement of BSDL
– Decomposition of Capabilities
– Distribution of Non-Functional Properties
• Strategic alignment of business services
• Evaluation
– Case-studies with CRC industrial partners
– Toolkit
Slide 19 IESS 1.0, Geneva, Feb 2010 BSDL, UoW – funded by