1. Software Engineering for Business Information Systems (sebis) Department of Informatics Technische Universität München, Germany wwwmatthes.in.tum.de Master’s Thesis Final Presentation Leveraging Artefact-Oriented Requirements Engineering through a Software System for Knowledge-Intensive Processes Michael Bigontina, 01.12.2014

2. Agenda 1.Introduction  Artefact-Orientation  Research Questions 2.Software Support  Requirements for Software Support  Mapping to Darwin  Coverage of Requirements 3.Evaluation  Overview of Demos  Screenshots 4.Results and Outlook 01.12.2014 Michael Bigontina 2

3. Artefact-Orientation 01.12.2014 Michael Bigontina 3 Rational Unified Process (RUP) V-Modell XT Sources: Passing - Requirements Engineering in the Rational Unified Process; V-Modell XT 1.4 Dokumentation 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 – Software Support – Evaluation – Results and Outlook

4. Current Situation 01.12.2014 Michael Bigontina 4 Generally Word or Excel documents are used to store created artefacts Drawbacks: Tasks are missing and consequently no explicit assignment of work to users Collaboration in one document not possible Only basic progress information and no visualization Resulting documents are vast and complicated to manage Solution: Use software to manage the artefact- oriented Requirements Engineering process Source for template contents: Besner - Evaluation of an Artefact-based Requirements Engineering Approach Introduction – Software Support – Evaluation – Results and Outlook

5. Research Questions 01.12.2014 Michael Bigontina 5 How can software support artefact- oriented Requirements Engineering? How can the process in the generic meta-model for artefact-orientation be represented? How can concrete AMDiRE or BISA Requirements Engineering Processes be supported? Research Question 1 Research Question 2 Research Question 3 Deliverable: 32 requirements Deliverable: Mappings based on process characteristics Deliverable: Process support features Introduction – Software Support – Evaluation – Results and Outlook

6. Requirements for Software Support 6 Artfact Model (1 Requirement) Artefact Structure (6 Requirements) Artefact Content (5 Requirements) Generic Role Model (2 Requirements) Artefact Abstraction Model (4 Requirements) Generic Process Model (5 Requirements) Extended Generic Process Model (5 Requirements) Lifecycle (4 Requirements) Existence of a process A process consists of tasks Tasks are related to the creation of artefact content Tasks have input and output represented by artefacts Existence of milestones Representation of artefacts Representation of content items Hierarchic structuring of artefacts Dependencies between content items Artefacts have a specific type Relationship between content items and their content 01.12.2014 Introduction – Software Support – Evaluation – Results and Outlook Michael Bigontina

7. ATM example 01.12.20147 Requirements Engineer Business Analyst Domain Experts Employees Installation of new ATMs for the ABC-bank Create Stakeholder Model Create Context Specification Define Project Scope Define business case 100% 60% June 14‘October 14‘September 14‘August 14‘Juli 14‘ 77% Data Logic Context Specification Template Source (Word/Excel icons): http://office.microsoft.com/ 100% 90% TODAY 70% TODAY 70% Michael Bigontina Introduction – Software Support – Evaluation – Results and Outlook

8. ATM example 01.12.2014 Michael Bigontina 8 Requirements Engineer Business Analyst Domain Experts Employees Installation of new ATMs for the ABC-bank Create Stakeholder Model Create Context Specification Define Project Scope Define business case 100% 60% June 14‘October 14‘September 14‘August 14‘Juli 14‘ 77% Data Logic Context Specification Template Source (Word/Excel icons): http://office.microsoft.com/ 100% 90% 70% Create Domain Model 0% TODAY Introduction – Software Support – Evaluation – Results and Outlook

9. Meta Model for Artefact-Orientation 01.12.2014 Michael Bigontina 9 Source: Méndez Fernández et al. – A Meta Model for Artefact-Orientation Introduction – Software Support – Evaluation – Results and Outlook

10. Lifecycle of Artefact-Oriented Models 01.12.2014 Michael Bigontina 10 Lifecycle 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 Based on: Méndez Fernández et al. – A Case Study on the Application of an Artefact-based Requirements Engineering Approach Reflect on Project Situation Introduction – Software Support – Evaluation – Results and Outlook

11. Mapping the Meta Model 01.12.2014 Michael Bigontina 11 Introduction – Software Support – Evaluation – Results and Outlook

12. Mapping the Process 01.12.2014 Michael Bigontina 12 Introduction – Software Support – Evaluation – Results and Outlook

13. Mapping the Lifecycle 01.12.2014 Michael Bigontina 13 Introduction – Software Support – Evaluation – Results and Outlook

14. Coverage of Requirements 01.12.2014 Michael Bigontina 14 1 Req.6 Req.5 Req.2 Req.4 Req.5 Req. 4 Req. in % Separation of tasks into steps excluded on purpose Assigning roles to activities excluded on purpose Not in focus of thesis No generic concepts and concept items available Introduction – Software Support – Evaluation – Results and Outlook

15. AMDiRE (Artefact Model for Domain- independent Requirements Engineering) Domain-independent model Implementation of artefact structure to show general mapping Representation of artefact structure Evaluation Three demo implementations based on the meta model for artefact-orientation: 01.12.2014 Michael Bigontina 15 BISA Model (Business Information Systems‘ Analysis) Well-elaborated model with lots of artefacts and content items Also well-described artefact-content Implementation of artefact structure Examplary implementation of artefact content Representation of generic artefact content ATM scenario based on AMDiRE Concrete scenario regarding the installation of new ATMs for a bank Artefact structure as in AMDiRE demo Artefact content partly structured using pages and partly using file uploads Representation of concrete artefact content Description Goal Demo Introduction – Software Support – Evaluation – Results and Outlook

16. Evaluation: ATM demo 01.12.2014 Michael Bigontina 16 Sources (content on pages): Besner - Evaluation of an Artefact-based Requirements Engineering Approach; Méndez Fernández et al. - AMDiRE: Artefact Model for Domain-independent Requirements Engineering Introduction – Software Support – Evaluation – Results and Outlook

17. Results Research Question 1: How can software support artefact-oriented Requirements Engineering? By fulfilling the described requirements and thus providing the concepts needed. Research Question 2: How can the process in the generic meta-model for artefact-orientation be represented? The process is underspecified in the meta model and requires tailoring. The process is generally defined during design time. Artefact structure, artefact content and the lifecycle are needed to support execution. Thus, a mapping of these elements is required to represent the process. Research Question 3: How can concrete AMDiRE or BISA Requirements Engineering Processes be supported? By allowing to structure processes and restrict the execution using entry and exit conditions. By supporting a process execution covering all levels of hierarchy in the artefact model. By providing well-elaborated features for executing the process. 01.12.2014 Michael Bigontina 17 Introduction – Software Support – Evaluation – Results and Outlook

18. Outlook 01.12.2014 Michael Bigontina 18 Extend the visualization and analysis features Provide further features for creating and editing of artefact content (e.g. a UML diagram editor) Extend the expertise feature for tasks Conduct further research: Analyse the user interaction with the implemented models (e.g. regarding the structuring of artefact content) Possible extensions for artefact-oriented models: Tracking of progress Metadata for tasks Introduction – Software Support – Evaluation – Results and Outlook

19. Questions 01.12.2014 Michael Bigontina 19 Thank you for your attention!