Presentation is loading. Please wait.

Presentation is loading. Please wait.

Software Engineering for Business Information Systems (sebis) Department of Informatics Technische Universität München, Germany wwwmatthes.in.tum.de Master’s.

Similar presentations


Presentation on theme: "Software Engineering for Business Information Systems (sebis) Department of Informatics Technische Universität München, Germany wwwmatthes.in.tum.de Master’s."— Presentation transcript:

1 Software Engineering for Business Information Systems (sebis) Department of Informatics Technische Universität München, Germany wwwmatthes.in.tum.de Master’s Thesis Kick-Off Presentation Empowering Users to Collaboratively Structure Artefact-oriented Requirements Engineering Processes Michael Bigontina, 29.07.2014

2 Agenda 1.Introduction  Collaborative Knowledge Work  Theoretical Basis of the overall project  General Solution of the overall project 2.Artefact-oriented Requirements Engineering  Activity-Orientation vs. Artefact-Orientation  AMDiRE (Artefact Model for Domain-independent RE)  Example of Tasks and Artefacts  Designtime vs. Runtime 3.Research Questions 4.Development  Development approach  Current state of work 5.Roadmap 29.07.2014 Michael Bigontina 2

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

4 Theoretical Basis of the Research Project Involves Three Different Disciplines 29.07.2014 Michael Bigontina 4 Knowledge Work 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 Adaptive Case Management 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 Social Principles and Patterns 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 Introduction – Artefact-oriented RE – Research Questions – Development - Roadmap

5 Goal Orientation  Describe which goals should be achieved  Goals guide the stream of work  Replaces traditional process model Emergence  Empowerment and participation of end users  Adaptability of templates at run-time  Continuous improvement of templates Data Centricity  Data as driver for knowledge work  Goal-oriented transformation of data  Integration of processes and data Collaboration  Knowledge creation through interaction  Building a successful online community Case Templates  Sharing and preservation of knowledge  Access to recurring best practice patterns General Solution: Empowering Users to Collaboratively Structure Knowledge-Intensive Processes 29.07.2014 Michael Bigontina 5 Create a new task for „Neue Idee“ Logical and temporal dependencies with CMMN Adding a new task Attribute types Drag and drop of attributes on tasks Access rights on attributes Completed tasks Hide completed tasks Unstructured information In-place editing New attribute for the template Design Principles  Flexible stage-gate process for Innovation Management  Development of a future Enterprise Architecture state  Artefact-oriented Requirements Engineering processes with templates Case Studies Introduction – Artefact-oriented RE – Research Questions – Development - Roadmap DARWIN web application

6 Rational Unified Process (RUP) Activity-Orientation vs. Artefact-Orientation 29.07.2014 Michael Bigontina 6 V-Modell XT Source: Johannes Passing - Requirements Engineering in the Rational Unified Process Activity-Orientation: Concrete process with a set of methods performed in a particular order Artefact-Orientation: Concentration on artefacts, which are coupled to milestones, roles, etc. Introduction – Artefact-oriented RE – Research Questions – Development - Roadmap

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

8 Example of Tasks and Artefacts 29.07.2014 Michael Bigontina 8 Source: Mendez Fernandez et al. - Artefact-based Requirements Engineering and its Integration into a Process Framework Introduction – Artefact-oriented RE – Research Questions – Development - Roadmap

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

10 Research questions How can software support artefact- oriented Requirements Engineering? What are characteristics of the process in the generic meta-model for artefact-orientation? How can concrete AMDiRE or BISA Requirements Engineering Processes be supported? 29.07.201410 Research Question 1 Research Question 2 Research Question 3 Introduction – Artefact-oriented RE – Research Questions – Development - Roadmap Michael Bigontina

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

12 Current State of Work 29.07.2014 Michael Bigontina 12 Artefact Content Item Concept Type (e.g. as Text) could be another Artefact Concept Item Representation: Text, Number, Boolean, Enum, Date, File Concept Representation: new page (as for Artefacts) containing concepts and concept items Introduction – Artefact-oriented RE – Research Questions – Development - Roadmap

13 Roadmap 29.07.2014 Michael Bigontina 13 29.07.2014 Current position Introduction – Artefact-oriented RE – Research Questions – Development - Roadmap

14 Questions 29.07.2014 Michael Bigontina 14


Download ppt "Software Engineering for Business Information Systems (sebis) Department of Informatics Technische Universität München, Germany wwwmatthes.in.tum.de Master’s."

Similar presentations


Ads by Google