a model based method for the design of services in collaborative business environments
TRANSCRIPT
IESS 1.1
A model-based method for the design of services in collaborative
business environments Application to construction projects
Daniel Zignale, Sylvain Kubicki, Sophie Ramel, Gilles Halin
2
Summary
➤ Introduction ➤ Context ➤ Objectives
➤ The Dest2Co method ➤ Introduction to the method ➤ Full description
➤ The Dest2Co toolset ➤ Editor and repository
➤ Case study ➤ Application to construction practices
➤ Conclusion ➤ Prospects
Introduction – Method – Toolset – Case study - Conclusion - Prospects
IESS 1.1
Introduction
Introduction
➤ Context of work ➤ A multi-disciplinary study
● Collaboration in construction projects ● Design of business and software services
➤ Two laboratories ● Public Research Center Henri Tudor (CRP HT), Luxembourg ● Research Center in Architecture and Engineering (FRE MAP-
CRAI), Nancy (France)
➤ Objective ➤ A method to propose adapted IT services to support
collaboration in construction projects ● Reconciliating viewpoints ● Fitting domain-specific requirements ● Based on a model-driven approach
4 Introduction – Method – Toolset – Case study - Conclusion - Prospects
IESS 1.1
Dest2Co method and toolset
The Dest2Co method
➤ Introduction ➤ 3 viewpoints to be conciliated [ISO/IEC 4210]
● The Business Requirement View (BRV): business experts ● The Business Solution View (BSV): service architects ● The Technical Solution View (TSV): software architects
➤ Iterative design method ● Reuse services from repository
6 Introduction – Method – Toolset – Case study - Conclusion - Prospects
The Dest2Co method
➤ Background: the Domain Model ➤ The Cooperative Context (CC) of a Construction Project
● Actors: simple actors or groups of actors ● Artifacts: documents or objects ● Activities: business tasks, project phases and project type ● Relations
➤ Issue ● Identify which actors, artifacts and activities are involved in
specific collaborative situations (i.e. construction projects)
7 Introduction – Method – Toolset – Case study - Conclusion - Prospects
The Dest2Co method
➤ First view: The Business Requirements View ➤ Business expert viewpoint ➤ Defining working collaborative practices within collaborative
specific context ● Specific actors working together with a common objective ● Particular artifacts used or produced ● A particular context of activity
➤ Instantiation of BRV Meta-Model ➤ Ex. Sharing design documents
8
Concepts defined in the Domain Model
Introduction – Method – Toolset – Case study - Conclusion - Prospects
The Dest2Co method
➤ The identification of Collaborative Practices ➤ Contact with professionals
● Brainstorming ● Interviews
➤ Analysis of literature ● Scientific studies ● Informal project descriptions
➤ Analysis of sustainable construction guidelines (HQE, BREEAM, MINERGIE, DGNB…)
● Precise requirements and objectives ● Particular actors and documents involved
9 Introduction – Method – Toolset – Case study - Conclusion - Prospects
The Dest2Co method
➤ The identification of Collaborative Practices ➤ 11 generic Collaborative Practices of construction project
● CP1: site choice and assessment ● CP2: designer determination ● CP3: objectives determination ● CP4: budget determination ● CP5: design and reporting ● CP6: contractors determination ● CP7: design assessment and reporting ● CP8: meetings organization and reporting ● CP9: execution preparation and management ● CP10: execution assessment ● CP11: user’s awareness
10 Introduction – Method – Toolset – Case study - Conclusion - Prospects
The Dest2Co method
➤ Second view: the Business Solution View (BSV) ➤ Service architects viewpoint ➤ Decomposition of a Collaborative Practice into a set of
Business Services ● Functional aspect: UML class diagrams, Ecore MM for general
characteristics of services ● Non-functional aspect: quality of services ontology ● Transactional aspect: UML activity diagrams
The actor who calls the service is called “Service consumer” The “Service provider” is responsible of the service realization Other swim lanes correspond to other actors involved
11 Introduction – Method – Toolset – Case study - Conclusion - Prospects
The Dest2Co method
➤ Third view: the Technical Solution View (TSV) ➤ Software architects viewpoint ➤ The Software service Layer: derived from BSV
● From Business Services to Software Services ● From Human roles to systems ● UML + ecore models similar to BSV models
Use OWL-Q for non-functional aspects
➤ The Implemented Service Layer ● Considers implemented and executable services ● Focus on services definition (realization, interface, inputs-outputs) ● Existing standards: BPEL, WSDL, XML schemas
12 Introduction – Method – Toolset – Case study - Conclusion - Prospects
The Dest2Co toolset
➤ Editor ➤ Goal: supporting the encoding of models following the method ➤ Integration of
● existing editors (Papyrus for UML, BPEL designer, part of Protégé for OWL-Q)
● EMF generated and self-defined (for ecore MM) within 3 eclipse perspectives corresponding to the 3 viewpoints
➤ Repository ➤ Goal: foster reuse of services models for the 3 viewpoints ➤ Model database for all kinds of models ➤ Reuse module to be integrated in the editor
Toolset under development
13 Introduction – Method – Toolset – Case study - Conclusion - Prospects
IESS 1.1
Case study
Case study
➤ Illustration and validation of the method and the toolset ➤ From business requirements to adapted services
➤ Focus on 1 Collaborative Practice ➤ Related to design assessment (CP7)
➤ 2 realistic scenarios ➤ 2 specification cases for the CP7 ➤ Deduced from business analysis ➤ Highlight particular situation existing in construction projects
15 Introduction – Method – Toolset – Case study - Conclusion - Prospects
Case study
➤ Business Requirement View ➤ First specification of the CP7 depending on the context
● Instantiation of the Meta-Model
16 Introduction – Method – Toolset – Case study - Conclusion - Prospects
Case study
➤ Business Requirement view ➤ Second specification of the CP7 depending on the context
● Instantiation of the Meta-Model
17 Introduction – Method – Toolset – Case study - Conclusion - Prospects
Case study
➤ Business Requirement View ➤ Dest2Co editor for describing the specification case
18 Introduction – Method – Toolset – Case study - Conclusion - Prospects
Case study
➤ Business Solution View ➤ Decomposition of the CP7 (first specification case) ➤ Transactional aspect of business service
19 Introduction – Method – Toolset – Case study - Conclusion - Prospects
Case study
➤ Technical Solution View: the Software Service Layer ➤ Transposition of the BSV
20 Introduction – Method – Toolset – Case study - Conclusion - Prospects
Case study
➤ Technical Solution View: Implemented Service Layer ➤ Service BPEL (diagram from BPEL designer) ➤ DMS service orchestration
21 Introduction – Method – Toolset – Case study - Conclusion - Prospects
IESS 1.1
Conclusion and prospects
Conclusion
➤ A method and a toolset to design adapted services ➤ From a business analysis
● Business Requirement View ● Business Solution View
➤ To software services definition an reuse ● Technical Solution View
➤ Application to the construction sector ➤ Case study: the assessment of design documents ➤ For validation of the method and toolset
23 Introduction – Method – Toolset – Case study - Conclusion - Prospects
Prospects
➤ Implement semi-automatic transformation between viewpoints ➤ Enable traceability between models
➤ Finish toolset ➤ Validate the approach with professionals
➤ Identify relevant Collaborative Practices specification cases ➤ Identify adapted services according to professionals
24 Introduction – Method – Toolset – Case study - Conclusion - Prospects
IESS 1.1
Thank you for your attention
Questions?