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

Slides:



Advertisements
Similar presentations
Ch:8 Design Concepts S.W Design should have following quality attribute: Functionality Usability Reliability Performance Supportability (extensibility,
Advertisements

A Stepwise Modeling Approach for Individual Media Semantics Annett Mitschick, Klaus Meißner TU Dresden, Department of Computer Science, Multimedia Technology.
Sept-Dec w1d21 Third-Generation Information Architecture CMPT 455/826 - Week 1, Day 2 (based on R. Evernden & E. Evernden)
Service Oriented Architecture Concepts March 27, 2006 Chris Armstrong
Programmierung verteilter Systeme Lab Institut für Informatik Universität Augsburg Universitätsstraße 14, Augsburg Tel.: (+49) 821/ , Fax:
Introduction To System Analysis and Design
Introduction to Software Architecture. What is Software Architecture?  It is the body of methods and techniques that help us to manage the complexities.
Team System and Microsoft Solutions Framework Alan Cameron Wills Architect, MSF
© Copyright Eliyahu Brutman Programming Techniques Course.
Itntroduction to UML, page 1 Introduction to UML.
Software Engineering for Business Information Systems (sebis) Department of Informatics Technische Universität München, Germany wwwmatthes.in.tum.de A.
Community Manager A Dynamic Collaboration Solution on Heterogeneous Environment Hyeonsook Kim  2006 CUS. All rights reserved.
Chapter 1 The Systems Development Environment
Fakultät für Informatik Technische Universität München A Visual Tool for Conflict Resolution in EA Repositories Bachelor’s Thesis kick-off presentation,
* Faculty of Electrical Engineering, Instituto Superior Politécnico José A Echeverría, Marianao, La Habana. Cuba +InfoAsset AG, Munich. Germany # Informatics.
GMD German National Research Center for Information Technology Innovation through Research Jörg M. Haake Applying Collaborative Open Hypermedia.
The Systems Development Environment. Learning Objectives Define information systems analysis and design. Describe the different types of information systems.
Software Engineering Muhammad Fahad Khan
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse.
Software Engineering for Business Information Systems (sebis) Department of Informatics Technische Universität München, Germany wwwmatthes.in.tum.de Design.
Software Engineering for Business Information Systems (sebis) Department of Informatics Technische Universität München, Germany wwwmatthes.in.tum.de Master.
-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.
1 WEB Engineering Introduction to Electronic Commerce COMM1Q.
Software Engineering for Business Information Systems (sebis) Department of Informatics Technische Universität München, Germany wwwmatthes.in.tum.de Master’s.
Software Engineering for Business Information Systems (sebis) Department of Informatics Technische Universität München, Germany wwwmatthes.in.tum.de Data-Parallel.
Educational Template Chapter 21 Knowledge Networks in Nursing Anne Spencer and Pamela Hussey Chapter 17 – Knowledge Networks in Nursing.
Software Engineering for Business Information Systems (sebis) Department of Informatics Technische Universität München, Germany wwwmatthes.in.tum.de Design.
Copyright © 2015 Pearson Education, Inc. Chapter 7: Software Engineering.
Eng. Mohammed Timraz Electronics & Communication Engineer University of Palestine Faculty of Engineering and Urban planning Software Engineering Department.
Software Engineering for Business Information Systems (sebis) Department of Informatics Technische Universität München, Germany wwwmatthes.in.tum.de Design.
Introduction To System Analysis and Design
SOFTWARE DESIGN (SWD) Instructor: Dr. Hany H. Ammar
1 Ontology-based Semantic Annotatoin of Process Template for Reuse Yun Lin, Darijus Strasunskas Depart. Of Computer and Information Science Norwegian Univ.
Adaptive Hypermedia Tutorial System Based on AHA Jing Zhai Dublin City University.
Copyright 2002 Prentice-Hall, Inc. Chapter 2 Object-Oriented Analysis and Design Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey.
Software Architecture and Design Dr. Aldo Dagnino ABB, Inc. US Corporate Research Center October 23 rd, 2003.
1 INTEROP WP1: Knowledge Map Michaël Petit (U. of Namur) January 19 th 2004 Updated description of tasks after INTEROP Kickoff Meeting, Bordeaux.
1 Introduction to Software Engineering Lecture 1.
Illustrations and Answers for TDT4252 exam, June
The Evolution of ICT-Based Learning Environments: Which Perspectives for School of the Future? Reporter: Lee Chun-Yi Advisor: Chen Ming-Puu Bottino, R.
Introduction to Software Engineering. Why SE? Software crisis manifested itself in several ways [1]: ◦ Project running over-time. ◦ Project running over-budget.
Christoph F. Eick University of Houston Organization 1. What are Ontologies? 2. What are they good for? 3. Ontologies and.
1 Technical & Business Writing (ENG-715) Muhammad Bilal Bashir UIIT, Rawalpindi.
Software Engineering for Business Information Systems (sebis) Department of Informatics Technische Universität München, Germany wwwmatthes.in.tum.de A.
Chapter 7 Software Engineering © 2007 Pearson Addison-Wesley. All rights reserved.
Chapter 7: Software Engineering
University of Paderborn - GermanyPresenter: Johannes Magenheim Developing the AGORA Road Map – 9 th WCCE July 27 th – 31 st, 2009 Bento Gonçalves, Brazil.
OASIS DITA for Business Documents Sub-committee Highlights of Work to Date Focus Areas and Future Work Michael Boses Jul
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
Systems Architectures System Integration & Architecture.
Software Engineering for Business Information Systems (sebis) Department of Informatics Technische Universität München, Germany wwwmatthes.in.tum.de Design.
Process 4 Hours.
Chapter 7: Software Engineering
Chapter 7: Software Engineering
Master thesis: Automatic Extraction of Design Decision Relationships from a Task Management System Kick-Off Matthias Ruppel, 8th of May 2017, Munich.
Chapter 1 The Systems Development Environment
The Systems Engineering Context
Some Thoughts about Models in Organisational Efficiency and Agility
1.Introduction to Rational Unified Process (RUP)
Unified Process Source & Courtesy: Jing Zou.
Chapter 1 The Systems Development Environment
Ontology Evolution: A Methodological Overview
Enterprise Data Model Enterprise Architecture approach Insights on application for through-life collaboration 2018 – E. Jesson.
COS 260 DAY 2 Tony Gauvin.
Topic 1: Introduction to the Module and an Overview of Agile
Presented by: Dishant Mittal CS 846
Presentation transcript:

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,

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 Michael Bigontina 2

Collaborative Knowledge Work is Ubiquitous in Organizations 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

Theoretical Basis of the Research Project Involves Three Different Disciplines 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

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 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

Rational Unified Process (RUP) Activity-Orientation vs. Artefact-Orientation 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

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

Example of Tasks and Artefacts 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

Designtime vs. Runtime 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

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? Research Question 1 Research Question 2 Research Question 3 Introduction – Artefact-oriented RE – Research Questions – Development - Roadmap Michael Bigontina

Development approach 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

Current State of Work 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

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

Questions Michael Bigontina 14