Corvette Hitachi/INRIA collaboration, 21-22 th of june Hitachi SDL INRIA ECOO.

Slides:



Advertisements
Similar presentations
3 Copyright © 2005, Oracle. All rights reserved. Designing J2EE Applications.
Advertisements

CONCEPTUAL WEB-BASED FRAMEWORK IN AN INTERACTIVE VIRTUAL ENVIRONMENT FOR DISTANCE LEARNING Amal Oraifige, Graham Oakes, Anthony Felton, David Heesom, Kevin.
A SharePoint site is a Web site that provides a central storage and collaboration space for documents, information, and ideas. A SharePoint site is a tool.
Presentation by Prabhjot Singh
Common Portal Definitions AZ-SLDS Program Team July 2011 FOR EXAMPLE USE ONLY.
ARCH-05 Application Prophecy UML 101 Peter Varhol Principal Product Manager.
Ver 1,12/09/2012Kode :CIA-230 Anal-Perc.SistemFASILKOM PERTEMUAN-4 Chapter 4. Use Case Analysis.
Parallel Programming Motivation and terminology – from ACM/IEEE 2013 curricula.
Framework is l Reusable Code, often domain specific (GUI, Net, Web, etc) l expressed as l a set of classes and l the way objects in those classes collaborate.
© Copyright 2011 John Wiley & Sons, Inc.
ARCH-01: Introduction to the OpenEdge™ Reference Architecture Don Sorcinelli Applied Technology Group.
“Chapter 9” Managing Object Design Done By: Alia Waled.
1 SWE Introduction to Software Engineering Lecture 22 – Architectural Design (Chapter 13)
Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 3. Defining the System 4. Managing Scope 5.
Business Process Orchestration
Fall 2007cs4251 Distributed Computing Umar Kalim Dept. of Communication Systems Engineering 31/10/2007.
Designing Your Project Output Achieving your objectives by targeting your audience Ken Peffers UNLV February 2004.
Systems Analysis and Design in a Changing World, 6th Edition 1 Chapter 6.
The Open Grid Service Architecture (OGSA) Standard for Grid Computing Prepared by: Haoliang Robin Yu.
Chapter 1 The Systems Development Environment
Database Administration Chapter 16. Need for Databases  Data is used by different people, in different departments, for different reasons  Interpretation.
Introduction to Computer Technology
Introduction to Databases Transparencies 1. ©Pearson Education 2009 Objectives Common uses of database systems. Meaning of the term database. Meaning.
GMD German National Research Center for Information Technology Innovation through Research Jörg M. Haake Applying Collaborative Open Hypermedia.
Where Agile Business Meets Agile Development DSDM Offshore Steve Messenger Patrick Vermeij.
System design technique  System Development Life Cycle  Prototyping  Rapid Application Development.
Rational Unified Process (Part 1) CS3300 Fall 2015.
Integrating Evaluation into the Design of the Minnesota Demonstration Project Paint Product Stewardship Initiative St. Paul, MN May 1, 2008 Matt Keene,
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 21. Review ANALYSIS PHASE (OBJECT ORIENTED DESIGN) Functional Modeling – Use case Diagram Description.
OBJECT ORIENTED SYSTEM ANALYSIS AND DESIGN. COURSE OUTLINE The world of the Information Systems Analyst Approaches to System Development The Analyst as.
SOFTWARE SYSTEMS DEVELOPMENT 4: System Design. Simplified view on software product development process 2 Product Planning System Design Project Planning.
WSMX Execution Semantics Executable Software Specification Eyal Oren DERI
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
1/9 May 2001 GSDI 5 Panel / IGN-F GSDI Business Plan Some thoughts on development issues.
ARCH-2: UML From Design to Implementation using UML Frank Beusenberg Senior Technical Consultant.
1 Incorporating Data Mining Applications into Clinical Guidelines Reza Sherafat Dr. Kamran Sartipi Department of Computing and Software McMaster University,
TAL7011 – Lecture 4 UML for Architecture Modeling.
9 Systems Analysis and Design in a Changing World, Fourth Edition.
Chapter 7 The Object-Oriented Approach to Requirements.
Chapter 3 Strategic Information Systems Planning.
BPEL Business Process Engineering Language A technology used to build programs in SOA architecture.
MODEL-BASED SOFTWARE ARCHITECTURES.  Models of software are used in an increasing number of projects to handle the complexity of application domains.
SQL Based Knowledge Representation And Knowledge Editor UMAIR ABDULLAH AFTAB AHMED MOHAMMAD JAMIL SAWAR (Presented by Lei Jiang)
CISB113 Fundamentals of Information Systems IS Development.
A Mediated Approach towards Web Service Choreography Michael Stollberg, Dumitru Roman, Juan Miguel Gomez DERI – Digital Enterprise Research Institute
Slide 1 Service-centric Software Engineering. Slide 2 Objectives To explain the notion of a reusable service, based on web service standards, that provides.
Department of Computer Science 1 CSS 496 Business Process Re-engineering for BS(CS) Chapter 2: Workflow Management Khurram Shahzad
UML - Development Process 1 Software Development Process Using UML.
Investigating and Improving a COTS-based Software Development Process Morisio, Seaman, Parra, Basili, Kraft, Condon icse 2000.
 Project Team: Suzana Vaserman David Fleish Moran Zafir Tzvika Stein  Academic adviser: Dr. Mayer Goldberg  Technical adviser: Mr. Guy Wiener.
LECTURE 5 Nangwonvuma M/ Byansi D. Components, interfaces and integration Infrastructure, Middleware and Platforms Techniques – Data warehouses, extending.
Final Review Systems Analysis and Design in a Changing World, 4th Edition 1 Final Review u Chapters 1-6, 8-10, 13, 14, 15 u Multiple choice, short answer,
Empowering the Knowledge Worker End-User Software Engineering in Knowledge Management Witold Staniszkis The 17th International.
Computer Systems Architecture Edited by Original lecture by Ian Sunley Areas: Computer users Basic topics What is a computer?
Information Systems Development
Component and Deployment Diagrams
Haiku vs. Rap: Comparing and Contrasting Structure
Systems Analysis and Design 5th Edition Chapter 4. Use Case Analysis
Systems Analysis and Design 5th Edition Chapter 4. Use Case Analysis
Recall The Team Skills Analyzing the Problem (with 5 steps)
Systems Analysis and Design 5th Edition Chapter 4. Use Case Analysis
Chapter 13 Logical Architecture.
Service-centric Software Engineering
Tiers vs. Layers.
Chapter 13 Logical Architecture.
Analysis models and design models
Item 7.11 SDMX Progress report
Marketing Experiments I
Software Development Process Using UML Recap
Presentation transcript:

Corvette Hitachi/INRIA collaboration, th of june Hitachi SDL INRIA ECOO

Corvette Hitachi/INRIA collaboration, th of june Objectives Collaborative workflow to coordinate a virtual team Definition of a new workflow model to support cooperative interactions Extend Hitachi SDL WorkCoordinator with INRIA ECOO transaction technology

Corvette Hitachi/INRIA collaboration, th of june Collaborative Workflow AB A B A and B work alternatively on the document. Order of interactions is predefined. A and B work simultaneously on the document. They interact when they want in a non predefined way.

Corvette Hitachi/INRIA collaboration, th of june Architecture Modeling Coordination Production Communication Tokyo Workspace Nancy Workspace Internet, WEB, WEBDAV Workflow System Process logic Collaboration Rules Collaborative Process Modeling

Corvette Hitachi/INRIA collaboration, th of june Contributing technology (1) WorkCoordinator

Corvette Hitachi/INRIA collaboration, th of june Contributing technology (2) Motu

Corvette Hitachi/INRIA collaboration, th of june Contributing technology (3) Motu (cooperation model) COO-transactions provide for consistency

Corvette Hitachi/INRIA collaboration, th of june Design decisions WorkCoordinator code is frizzed In “paper” process book, traditional (competitive) and cooperative processes are described in the same way => use WorkCordinator process model to model cooperative workflow Additional decisions : one work item per activity...

Corvette Hitachi/INRIA collaboration, th of june Competitive vs. Cooperative Process Interpretation Competitive Interpretation Cooperative Interpretation Process Model Edit Review_1 Modify Review _2 Edit Review_1 Modify Review _2 Edit Review Modify Review

Corvette Hitachi/INRIA collaboration, th of june Design architecture Modeling Coordination Production Communication Tokyo Workspace Nancy Workspace Internet, WEB, WEBDAV Workflow System Process logic Collaboration Rules Collaborative Process Modeling Workcoordinator Motu

Corvette Hitachi/INRIA collaboration, th of june Implementation architecture

Corvette Hitachi/INRIA collaboration, th of june Achievement Success –cooperation between parallel activities good separation between control flow and data flow Limitations : –no cooperation between succeeding activities an activity cannot start its execution before the preceding one has completed problem of group termination But we know how to surpass limitations

Corvette Hitachi/INRIA collaboration, th of june Conclusion Demonstration of technical feasibility –Corvette, Motu A component based approach for the development of workflow systems Applicability –designed with potential users –however, there is a need for usage analysis (experiments forecasted)

Corvette Hitachi/INRIA collaboration, th of june Component based WFMS ABT EXCACT SUS INITERRTAANT WFT ABT DEP GRO TER SUS ACS RTC 1 2 in wft up_to_date ? Process logic Transaction management 1 : a in wft 2 : a in wft and up_to_date 1 : postconditions fulfilled & up_to_date 2 : not_up_to_date 2 1 completed

Corvette Hitachi/INRIA collaboration, th of june More about Corvette