1.
BPMN and Design Patterns for Engineering<br />Social BPM Solutions<br />BPMS2 Workshop, Clermont-Ferrand Aug 29 2011<br />Marco Brambilla, PieroFraternali, Carmen Vaca<br />DipartimentodiElettronica e Informazione<br />Politecnico di Milano<br />Contact:<br />marco.brambilla@polimi.itmarcobrambimarcobrambi<br />

2.
Outline<br /><ul><li>Understanding the goals of social BPM

3.
Representing social BP requirements

4.
Eliciting recurrent solutions: social design patterns

5.
An example

6.
An architecture for the fast prototyping and engineering of SBPM

7.
Conclusions: ongoing & future work (+ demo)</li></li></ul><li>Context and goals<br /><ul><li>EU Funded Project, 2 years

8.
4 SMEs + 2 Universities

9.
Coordinator: Web Models (IT)

10.
Main deliverables

11.
Methodology

12.
Modeling languages

13.
Reusable design patters

14.
Forward engineering architecture

15.
Cases, cases, cases…</li></ul>www.bpm4people.org<br />

16.
The Social BPM Space<br />A continuum from closed to open social BPM, where each organization can find the mix of control & flexibility it needs<br />Process model decided top-down and hard wired, task assignment rigid, communication limited to task input-output<br />ClosedBPM<br />Participatory design<br />Process model resulting from merge of different models (e.g., merger&acquisition), task/flow variants<br />Participatory enactment<br />Actors are fixed, but can communicate with social tools (e.g., follow up a task, tweet on a task status, etc)<br />The community of actors can be (in part) open: e.g., <br />launch a task to be executed in Facebook, find an expert in LinkedIn, vote for alternative flows <br />Social enactment<br />Tasks are executed freely (e.g., in a Wiki-like mode)<br />process constraints are mined and progressively enforced by observing community behaviors<br />Process mining<br />

17.
The contribution of “social” to the BPM lifecycle<br /><ul><li>Weak Ties / Tacit Knowledge exploitation (e.g., team formation)

18.
Knowledgesharing (e.g., self-service technical support)

19.
SocialFeedback (e.g., quality of service monitoring)

20.
Transparency: (e.g., legislation building)

21.
Participation: (e.g., participatory budgeting)

22.
Activitydistribution (e.g., crowd-sourced work)

23.
Decisiondistribution (e.g., social CRM)</li></ul>Social BPMN<br />Socialization <br />design <br />patterns<br />Socialization <br />goals<br />Modeltransformation<br />Participatory & <br />social enactment<br />Social BPM architecture<br />

24.
Overview of the approach<br />General idea:<br />Social BPM Design & Implementation<br />Analyze process improvement requirements<br />Understand SBPM goals<br />Identify communities of reference<br />Analysis & design<br />Understand process socialization patterns<br />Map requirements to goals<br />Identify relevant socialization patterns<br />Refer patterns to goals<br />(Re)design process with social interactions<br />Identify & abstract <br />social platforms to use<br />Automate pattern to application transformation<br />Map process model to <br />application models<br />Deployment<br />Refine <br />application models<br />Map application models<br />into code & deploy<br />

25.
Representing Social BPM requirements<br />Idea: extending BPMN with stereotypes for expressing:<br /><ul><li>The participation of dynamically enrolled actors ( social pools with different roles)

26.
The execution of activities by such actors (social tasks)

27.
Events for controlling the execution of tasks by social actors</li></li></ul><li>Social BPM design patterns<br /><ul><li>As in the tradition of BPM design patterns, they capture reusable solutions to recurrent socialization requirements </li></ul>Dynamic enrollment<br />Poll<br />

28.
Design patterns and goals<br /><ul><li>Socialization goals can be used as drivers for the selection of the social BPM design patterns that are more relevant to a process socialization effort (SBPM by example)</li></li></ul><li>A complete example<br />

29.
Model Driven Engineering of SBPM applications<br /><ul><li>Models are amenable to be transformed into running applications, enabling fast prototyping and early assessment of alternative process socialization strategies directly by the stakeholders

30.
Model-Driven Engineeringis the discipline that supports a generative approach to the creation and maintenance of application from abstract, platform-independent models

31.
Implementation exploited WebRatio (www.webratio.com), an industrial MDE tool that manages app development in three steps:</li></li></ul><li>Models for BPM<br />Two types of models concur to define the application requirements:<br />

32.
Model extensions for Social BPM<br />Process and applications models are extended to incorporate social issues:<br />Pool<br />Vote<br />Follow<br />Lane 1<br />Lane 2<br />

33.
Generative approach and runtime architecture<br />Process layer<br />Presentation layer<br />Visual identity<br />Business layer<br />Servicelayer<br />Datalayer<br />Integrationlayer<br />Standard Java<br />Web application<br />Social Network connection services<br />IBMWebSphere<br />Caucho Resin<br />ApacheTomcat<br />OracleApplicationServer<br />JBoss<br />Application Server<br />

34.
Ongoing and future work<br />Ongoing work: reality check<br /><ul><li>EU Parliament: IT requirement elicitation processes opened to all DGs

35.
NGO: consumers’ claim management and class action organization

36.
PA: participative territory planning

37.
Multinational company: social CRM</li></ul>Future work<br /><ul><li>Complete the implementation of model editor, model transformation, social WebML components

38.
Investigate SNA techniques for social task optimization

39.
Define social process improvement metrics and Social Activity Monitoring concepts</li></li></ul><li>DEMO<br />http://www.bpm4people.org/cms/content/en/demos<br />

40.
Contact:<br />Marco Brambilla<br />marco.brambilla@polimi.itmarcobrambimarcobrambi<br />