Michael Bigontina , 29.07.2014

1. Master’s Thesis Kick-Off PresentationEmpowering Users to Collaboratively Structure Artefact-oriented Requirements Engineering Processes Michael Bigontina, 29.07.2014

2. Agenda • Introduction • Collaborative Knowledge Work • Theoretical Basis of the overall project • General Solution of the overall project • Artefact-oriented Requirements Engineering • Activity-Orientation vs. Artefact-Orientation • AMDiRE (Artefact Model for Domain-independent RE) • Exampleof Tasks andArtefacts • Designtime vs. Runtime • Research Questions • Development • Development approach • Currentstateofwork • Roadmap Michael Bigontina

3. Collaborative Knowledge Work isUbiquitous in Organizations Solving complex problems in communities Planing of an application landscape Development of large software systems Producing new ideas and innovations How can software support processes for collaborative knowledge work? Michael Bigontina Introduction– Artefact-oriented RE – Research Questions – Development - Roadmap

4. Theoretical Basis of the Research Project Involves Three Different Disciplines Knowledge Work Adaptive Case Management Social Principles and Patterns • Adaptive case management is a novel approach to support knowledge-intensive processes. • Solution ideas from ACM: • Essential requirements for ACM support • Emergent design of processes • Evolution of processes with templates • Knowledge work relies on the successful collaboration of different roles. • Facilitating collaboration: • Building successful online communities • Learning from existing communities on the web • Principles and patterns • Literature on knowledge work in organizations provides an understanding of the problem.Description of the problem: • Characteristics of knowledge work • Complex vs. Complicated problems • Roles in knowledge work Michael Bigontina Introduction – Artefact-oriented RE – Research Questions – Development - Roadmap

5. General Solution: Empowering Users toCollaborativelyStructure Knowledge-Intensive Processes Logical and temporal dependencies with CMMN Adding a new task Create a new task for „Neue Idee“ • Goal Orientation • Describewhichgoalsshouldbeachieved • Goals guidethestreamofwork • Replaces traditional processmodel • Emergence • Empowermentandparticipationof end users • Adaptabilityoftemplates at run-time • Continuousimprovementoftemplates • Data Centricity • Data asdriverforknowledgework • Goal-orientedtransformationofdata • Integration ofprocessesanddata • Collaboration • Knowledge creationthroughinteraction • Building a successful online community • Case Templates • Sharing andpreservationofknowledge • Access torecurringbestpracticepatterns Hide completed tasks DARWIN web application Drag and drop of attributes on tasks Attribute types Completed tasks Design Principles Access rights on attributes In-place editing • Flexible stage-gate process for Innovation Management • Development of a future Enterprise Architecturestate • Artefact-oriented Requirements Engineering processes with templates Case Studies Unstructured information New attribute for the template Michael Bigontina Introduction – Artefact-oriented RE – Research Questions – Development - Roadmap

6. Activity-Orientation vs. Artefact-Orientation Rational Unified Process (RUP) Activity-Orientation: Concreteprocesswith a setofmethodsperformed in a particularorder V-Modell XT Artefact-Orientation: Concentration on artefacts, whicharecoupledtomilestones, roles, etc. Source: Johannes Passing - Requirements Engineering in the Rational Unified Process Michael Bigontina Introduction – Artefact-oriented RE – Research Questions – Development - Roadmap

7. AMDiRE – Artefact Model for Domain-independent RE Source: Mendez Fernandez et al. – AMDiRE – Artefact Model for Domain-independent RE Michael Bigontina Introduction – Artefact-oriented RE – Research Questions – Development - Roadmap

8. Exampleof Tasks andArtefacts Source: Mendez Fernandez et al. - Artefact-basedRequirementsEngineering and its Integration into a Process Framework Michael Bigontina Introduction – Artefact-oriented RE – Research Questions – Development - Roadmap

9. Designtime vs. Runtime Designtime Runtime Customisation Approach Stage 1: Initial Project Set-Up • Create Artefacts • AssignRoles • Define Milestones • Set-Up Infrastructure Stage 2: Project-specificExecutionStrategy • Dynamic Content Creation: • Create Content Item • Reflect on Project Parameters • Analyse Possibilities • Document Rationale • Create Content Artefact Type Project Background, Documents, … Based on: Mendez Fernandez et al - A Case Study on the Application of an Artefact-based Requirements Engineering Approach Michael Bigontina Introduction – Artefact-oriented RE – Research Questions – Development - Roadmap

10. Research questions Research Question 1 Research Question 2 Research Question 3 Michael Bigontina Introduction – Artefact-oriented RE – Research Questions – Development - Roadmap

11. Development approach • Namingconventions: • Content Item = Attribute • Artefact = Page • Concept Type = Attribute Value • Milestones = Milestones • Tasks = Tasks Source: Mendez Fernandez et al. - A Meta Model forArtefact-Orientation Michael Bigontina Introduction – Artefact-oriented RE – Research Questions – Development - Roadmap

12. Current State of Work Artefact Content Item Concept Type (e.g. as Text) Concept Item Representation: Text, Number, Boolean, Enum, Date, File ConceptRepresentation: newpage (asforArtefacts) containingconceptsandconceptitems couldbeanotherArtefact Michael Bigontina Introduction – Artefact-oriented RE – Research Questions – Development - Roadmap

13. Roadmap Currentposition 29.07.2014 Michael Bigontina Introduction – Artefact-oriented RE – Research Questions – Development - Roadmap

14. Questions Michael Bigontina