© Institut für Wirtschaftsinformatik, Universität des Saarlandes 1999Markus Wittmann 1/9 MARVIN Lisbon Meeting 99 UML combined with eEPC qobject oriented.

Slides:



Advertisements
Similar presentations
Introduction to Object Orientation System Analysis and Design
Advertisements

University of Paderborn Software Engineering Group E. Kindler Handout for the talk given in the eJustice Dialogues at Saarland University. June 6, 2005.
Chapter 26 Legacy Systems.
© Institut für Wirtschaftsinformatik, Universität des Saarlandes MARVIN (CO) MARVIN Kick-Off, Oslo 18./ Presentation WP 3 Clemens Odendahl.
© Institut für Wirtschaftsinformatik, Universität des Saarlandes 1999 Slide 1/14 MARVIN Modelling Workshop Saarbrücken 18 th - 19 th march 1999.
Solutions to Review Questions. 4.1 Define object, class and instance. The UML Glossary gives these definitions: Object: an instance of a class. Class:
D ET N ORSKE V ERITAS DNV - 01/06/ Project Progress between review meeting #2 and #3 Peik Jenssen Copenhagen 25 May 2000.
© Institute for Information Systems (IWi), University of Saarland EC Review Project Review, Lisbon, October 12th 1999 Workpackage 1 Achievements.
1 SWE Introduction to Software Engineering Lecture 13 – System Modeling.
Slide 1 Systems Analysis & Design CS183 Spring Semester 2008 Dr. Jonathan Y. Clark Course Website:
Slide 1 Chapter 7 Structural Modeling. Slide 2 Key Ideas A structural or conceptual model describes the structure of the data that supports the business.
1 SYSTEM and MODULE DESIGN Elements and Definitions.
Lecture 11: Chapter 22 Topics –Object Oriented Modeling –UML –Use case.
© SAP AG Navigation Abstract This material explains how to navigate in SAP systems. It is aimed at students at universities, universities of applied sciences.
1 A Student Guide to Object- Orientated Development Chapter 9 Design.
Data Flow Diagrams "Business process flow" not a Flow Chart.
USE Case Model.
Systems Analysis and Design in a Changing World, Fifth Edition
OO Analysis and Design CMPS OOA/OOD Cursory explanation of OOP emphasizes ▫ Syntax  classes, inheritance, message passing, virtual, static Most.
Chapter 6 The Traditional Approach to Requirements
Systems Analysis and Design in a Changing World, Fifth Edition
Changing Perspective From Structured to Object-oriented.
CHAPTER ONE Problem Solving and the Object- Oriented Paradigm.
Unified Modeling Language, Version 2.0
1 UML Basic Training. UML Basic training2 Agenda  Definitions: requirements, design  Basics of Unified Modeling Language 1.4  SysML.
Slide 1 Structural Modeling Chapter 7. Slide 2 Key Ideas A structural or conceptual model describes the structure of the data that supports the business.
Modeling system requirements. Purpose of Models Models help an analyst clarify and refine a design. Models help simplify the complexity of information.
Slide 1 Systems Analysis and Design with UML Version 2.0, Second Edition Alan Dennis, Barbara Haley Wixom, and David Tegarden Chapter 7: Structural Modeling.
Structural Modeling Chapter 7. Key Ideas A structural or conceptual model describes the structure of the data that supports the business processes in.
Slide 1 Systems Analysis and Design With UML 2.0 An Object-Oriented Approach, Second Edition Chapter 2: Introduction to Object-Oriented Systems Analysis.
Process Description and Quality Guidelines – Two Birds with One Stone European Conference on Quality in Official Statistics Q2014 Rudi Seljak, Tina Steenvoorden.
The Business Choreography Language (BCL) A Domain-Specific Language for Global Choreographies Institute for Software Technology and Interactive Systems.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Slide 1 Systems Analysis and Design With UML 2.0 An Object-Oriented Approach, Second Edition Chapter 2: Introduction to Object-Oriented Systems Analysis.
Slide 1 Systems Analysis and Design With UML 2.0 An Object-Oriented Approach, Second Edition Chapter 2: Introduction to Object-Oriented Systems Analysis.
Short introduction to business process modelling
From Use Cases to Implementation 1. Structural and Behavioral Aspects of Collaborations  Two aspects of Collaborations Structural – specifies the static.
Describing MCM Mission Package Software Interoperability with Architectural Descriptions.
Slide 1 Systems Analysis and Design with UML Version 2.0, Second Edition Alan Dennis, Barbara Haley Wixom, and David Tegarden Chapter 7: Structural Modeling.
Object Oriented Programming and Data Abstraction Earl Huff Rowan University.
Basic Characteristics of Object-Oriented Systems
From Use Cases to Implementation 1. Mapping Requirements Directly to Design and Code  For many, if not most, of our requirements it is relatively easy.
DOMAIN CLASSES – PART 1 BTS430 Systems Analysis and Design using UML.
Introduction to UML.
Agenda Warmup Lesson 4.5 (Program Design & Analysis)
Cmpe 589 Spring 2006.
The Movement To Objects
Systems Analysis and Design
Requirements Engineering Process
Chapter 4 – Requirements Engineering
Levels of testing.
Systems Analysis and Design With UML 2
Unified Modeling Language
Systems Analysis and Design With UML 2
Software Architecture & Design Pattern
Chapter 2 Database Environment Pearson Education © 2009.
Object Oriented Design
Object Oriented Analysis and Design
DATA FLOW DIAGRAM.
Training for developers of X-Road interfaces
Design and Implementation
IMPORTANT NOTICE TO STUDENTS:
Agenda Warmup Lesson 4.5 (Program Design & Analysis)
2.1 Introduction to Object-Oriented Programming
Chapter 2 Database Environment Pearson Education © 2009.
ENERGY 211 / CME 211 Lecture 27 November 21, 2008.
Overview Activities from additional UP disciplines are needed to bring a system into being Implementation Testing Deployment Configuration and change management.
Chapter 2 Database Environment Pearson Education © 2009.
CS 501: Software Engineering
From Use Cases to Implementation
Presentation transcript:

© Institut für Wirtschaftsinformatik, Universität des Saarlandes 1999Markus Wittmann 1/9 MARVIN Lisbon Meeting 99 UML combined with eEPC qobject oriented software development qdifferent tasks of UML and eEPC qwhy the eEPC? qwhat is the eEPC? qan example

© Institut für Wirtschaftsinformatik, Universität des Saarlandes 1999Markus Wittmann 2/9 MARVIN Lisbon Meeting 99 Procedural model for object oriented application development

© Institut für Wirtschaftsinformatik, Universität des Saarlandes 1999Markus Wittmann 3/9 MARVIN Lisbon Meeting 99 Descriptive levels of an information system

© Institut für Wirtschaftsinformatik, Universität des Saarlandes 1999Markus Wittmann 4/9 MARVIN Lisbon Meeting 99 MARVIN UML models mapped to the description levels

© Institut für Wirtschaftsinformatik, Universität des Saarlandes 1999Markus Wittmann 5/9 MARVIN Lisbon Meeting 99 Why the eEPC? qeEPC is a process description modeling method qdescribes the whole process qcan be designed from different points of view qis easy to understand qallows a effective transaction with the end user qis a very common and experienced method

© Institut für Wirtschaftsinformatik, Universität des Saarlandes 1999Markus Wittmann 6/9 MARVIN Lisbon Meeting 99 UML and eEPC to describe the MEIT

© Institut für Wirtschaftsinformatik, Universität des Saarlandes 1999Markus Wittmann 7/9 MARVIN Lisbon Meeting 99 time abstraction level Process Modeling Process Modeling Final (detailed) UML Models Final (detailed) UML Models implementation start Bottom Up UML Modeling Bottom Up UML Modeling Top Down UML Modeling Top Down UML Modeling Further modeling

© Institut für Wirtschaftsinformatik, Universität des Saarlandes 1999Markus Wittmann 8/9 MARVIN Lisbon Meeting 99 Elements of the eEPC Event Process interface Function Organisational unit AND operator Application system type OR operatorDocument XOR operator Application system FileCluster

© Institut für Wirtschaftsinformatik, Universität des Saarlandes 1999Markus Wittmann 9/9 MARVIN Lisbon Meeting 99 an example Request detailed information from ship crew FAX Pager/SMS Check if steel structure is damaged Steel structure is damaged Steel structure is not damaged Request additional information from Class Society ERC is informed MIT ERC

Feedback: Privacy Policy Feedback
Do Not Sell My Personal Information
About project: SlidePlayer Terms of Service

© 2025 SlidePlayer.com. Inc. All rights reserved.