Nov. 24th 2011
Contribution to IS Contribution to IS modellingmodelling
Mounia FREDJ
AlQualsadi team
2
OutlineOutlineContextOverview of research activitiesConclusion
3
AlQualsadi teamAlQualsadi Research Axis
Axis 1 - EA Governance : Which models for IT Strategy, Governance, Maturity & Alignment ?
Axis 2 - EA Integration : How to insure interoperability and integration of Portals/Processes/Services/Components ?
Axis 3 - EA Quality : How to achieve specification, verification/validation, and engineering of EA models of a certain quality ?
Axis 4 - EA Applied to ICT4D : How to apply EA approaches in citizen-centricprojects ?
Axis 5 - Applied Maths Methods for EA : Which math methods to formalise, simulate, and explain EA governance, integration, and quality ?
4
ContextContextEnterprise IS : complexity, heterogeneity and evolutivity
ProblemDifficulties to capitalize and spread out the good practices in IS engineering
⇒ to face the problems of capitalization, adaptation and evolutionof enterprise IS
Approaches ?Reuse
• reducing the development cost• gain of time• improving quality
Integration
5
ApproachApproach reusereuse
Reuse
Reusethrough MDA
Reusethrough patterns
approach
P-Sigma Formalism
2 systems of patterns
(RE and egov)
6
OutlineOutlineContextOverview of research activities
1 : Reuse• Patterns oriented approach
1. P-Sigma Formalism2. Systems of patterns (RE and e-gov)
• MDA Approach
2 : Adaptation3 : Components retrieval4 : Model Integration
Conclusion
7
1. 1. ReuseReuse : patterns: patterns--orientedoriented approachapproachA widely chosen vector of reuse : pattern
Generic solution to a recurrent problem in a contextRepresented by {problem, context, solution}
⇒ best-practices « know » and « know-how »
Product Pattern / Process Patternproduct oriented problem, model oriented solutionprocess oriented problem, a process oriented solution
Problematic : many formalisms for patterns representationNeed of a common formalism
Collaboration with LIG- Grenoble, France
8
1. 1. ReuseReuse : main goals of one : main goals of one formalismformalismStandardization of product and process patterns representation : A patterns system must integrate product and process patterns and therefore must offer a unique formalism to combine expression of model and process solutions.
Better formalization of the pattern’s selection interface : Contrary to the existing representation formalisms, where the items allowingpattern’s selection are not explicit, P-Sigma distinguishes five items helping to select patterns.
Patterns system organization : P-Sigma formalism aims to makeexplicit the different relations among patterns. The Relation part enablesto organize a patterns system thanks to clear relations: uses, requires, alternative, refines, etc.
9
1. 1. ReuseReuse : P: P--SIGMA SIGMA FormalismFormalism
StrenghtProblem
Identifier
Classification
Context
Approach
Model
Consequence
Appl. case
Activities DiagClasses Diag.Sequence Diag. Classes Diag.
Seq Diag.
Uses
Requires
AlternativeRefines
P-SIGMA
Formalism
inte
rfac
ere
alizat
ion
relation
10
1. 1. ReuseReuse : patterns for : patterns for RequirementsRequirements Engineering (RE)Engineering (RE)
Problematic : to define patterns to help the requirementsanalyze (regardless of the domain)
Idea : to identify the recurrent problems and to propose reusablecomponents as a solution
Proposition of a patterns systems (RequirementsDiagnosis)Goal : to guide analysts to identify requirementsComposition : 10 patternsbsynthetic : Diagnosisbrefinement : ContextElement, Goal, Requirementbguidance : PlanDiagnosis, JustifyRequirement, DocumentDiagnosis …The analyst can choose the components he considers relevant to his
application and adapt them to his context
Collaboration with EMI – SIR, Rabat, Morocco
11
1. 1. ReuseReuse : System of patterns for the e: System of patterns for the e--govgov
Traditional services
E-gov solutions
Citizen oriented Services
Co-supervision with SIR-EMI – Thesis of H. Ouchetto
12
1. 1. ReuseReuse : System of patterns for the e: System of patterns for the e--govgov
GoalTo contribute to the emergence of a common referentiel for the AdministrationTo provide process patterns for the design of an e-gov portal
Approach : a comparative study of international architectures
⇒ To identify generic and specific needs of a e-gov architecture
System of patterns for an e-gov portal4 process patterns The information design of an egov portal, its creation, the content management and publication
13
OutlineOutlineContextOverview of research activities
1 : Reuse• Patterns oriented approach
1. P-Sigma Formalism2. Systems of patterns (RE and e-gov)
• MDA approach2 : Adaptation3 : Components retrieval4 : Model Integration
Conclusion
14
1. 1. ReuseReuse : MDA : MDA approachapproachGoal : to re-use the business model
Model Driven Architecture (MDA) approach of the OMGObjective of MDA
• Separation of concerns (business functionality of an IS and itsimplementation technique)
Principle :• Business : PIM (Platform Independent Model)• Implementation : PSM (Platform Specific Model).• Transition from PIM-to-PSM : transformation
Problem of the MDALack of the plateform explicit representationLack of a transformation process PIM-to-PSM
Co-supervision ENSIAS-Nantes – A. Belangour thesis
15
1. 1. ReuseReuse : Proposition of an : Proposition of an implementationimplementation
A based Y cycle approachDescription of the targeted PDM platform(Platform Description Model)The PIM and the PDM constitute the 2 branches of the Y cyclePSM = "merging" the PIM and the PDM
Need of a meta-model describing the targeted PDM platform : PDMM (Platform Description Meta Model)
⇒ Choice of .Neta design decision model : DDM (Design DecisionModel) conform to a DDMM (Design DecisionMeta-Model)
Business Target Platform
Implementation of the business model in the target platform
PSM
DDM
PDMPIM
merging
16
OutlineOutlineContextOverview of research activities
1 : Reuse• Patterns oriented approach
1. P-Sigma Formalism2. Systems of patterns (RE and e-gov)
• MDA approach2 : Adaptation
Variability for the Business Components (BC)Variability in SOA
3 : Components retrieval4 : Model Integration
Conclusion
17
2. Adaptation : 2. Adaptation : VariabilityVariability for the BCfor the BC
Concepts Concepts
Concepts
Business domain 1 : Ex. Hotel Business domain 2 : Ex. car rental company
Business domain 3 : Ex. Library
ReusableConcepts
Abstraction Business domain 4 : Ex. DVD rental
A : ClientB : BookingC : Resource
Reuse
ClientBookingRoom
Business domain Business domain
Business domain
ClientBookingCar
MemberBookingBook
ClientBookingDVD
Business domain
Business Components (BC)Business Components (BC)
‐ Represent an active concept of a business domain‐ Used to define :
an entity : client, member, …a process : hotel management, car rental management, library management,…
18
Design For reuse Design By reuse
2. Adaptation : a 2. Adaptation : a completecomplete methodmethod for the BC for the BC design and usedesign and use
BC system
Maintenance
Produces Uses
Validates
BC engineer IS engineer
Produces
Model of BCP1)Process oriented2) Design range for functionalrequirements3)Supporting variability4)A complete solution (4 views)
++
Methodological guides
1) BCP specification2) Reuse of BCP
Co-tutelle LIG – FSR - R. Saidi thesis
19
Dynamical view specification
Spécification de la vue Structurelle
Organization
Documentation / Classification
Bibliothèque de CMP
BCP supporting variability
Functional view specification
Identification of the variability
Business VariabilityExtension of activities diagram of
UML 2
Variabilité FonctionnelleExtension du diagramme de cas
d’utilisation d’UML 2
Dynamical VariabilitySeq. Diagram UML 2
Structural VariabilityExtension of the Symphony
model
Business view Specification
OrganisationalCMP
Description du CMP
PMi
PM1
PMn
PMPreliminary study
Traduction rules
Construction rules
2. Adaptation : BCP engineering2. Adaptation : BCP engineering19
ImplementedBCP
20
OutlineOutlineContextOverview of research activities
1 : Reuse• Patterns oriented approach
1. P-Sigma Formalism2. Systems of patterns (RE and e-gov)
• MDA approach2 : Adaptation
Variability for the Business Components (BC)Variability in SOA
3 : Components retrieval4 : Model Integration
Conclusion
21
Axe : Axe : VariabilityVariability in SOA in SOA The context of SOA
Mastering the complexityThe reuse of componentsSeparation of concernsImproving the flexibility
Importance of adaptability factorAims to propose systems that fullfill need changes, executionconditions, clients and use context
ProblematicManagement of the variability for adaptable and evolutive services
Co-supervision at ENSIAS - B. Chakir Thesis
22
OutlineOutlineContextOverview of research activities
1. Reuse• Patterns oriented approach
1. P-Sigma Formalism2. Systems of patterns (RE and e-gov)
• MDA approach2. Adaptation
Variability for the Business Components (BC)Variability in SOA
3. Components retrievalUser profile modelGlobal process
4 : Model IntegrationConclusion
23
3. Components 3. Components retrievalretrievalExisting tools for components retrieval
Not very many services to facilitate the retrieval of componentsDedicated to experts
The problemHow can we find relevant components according to the user profile ?
Objective⇒ System components retrieval
• Modelize the user profile• Taken into account in the process of retrieval
ConstraintsHeterogeneity of the reusable componentsAbstraction levelsComponents providers
Co-supervision with SIR-EMI - H. Ouchetto thesis
24
3. Components 3. Components retrievalretrieval : global : global processprocess
Request
Descriptive components
DB User model Ontology of the
domain
Treatment of the request
Optimization of the results
Reformulation of the request
Presentation and memorization of
results
25
4. Model 4. Model IntegrationIntegrationContext : Collaborative design / enterprise evolution
Problematic :Integration of IS models
It will be presented in the session
Co-supervision with FSR - S. Benabdellah thesis
26
Conclusion
Main activitiesCapitalization of IS engineering and business engineering
Proposition of a method for the design and the use of Business Components (BC) supporting variability
Components retrieval (user-oriented)
Definition of integration mecanisms (semantic)
27
My research within AlQualsadi axes
Axis 1 - EA Governance
Axis 5 - AppliedMaths Methods for
EA
Axis 4 - EA Applied to ICT4D
Axis 3 - EA Quality
Enterprise Architecture
Axis 2 - EA Integration
syntactic/semanticinteroperability,
model integration,
reuse, adaptation, MDE, MDA, meta-modeling
Models for IT Strategy, Governance, Maturity &
Alignment ? BPM
BPM
e-Gov (appl. domain), BP patterns for egov
28
Thank youFor your attention