Tools Interoperability Workshop ICCS 2006. Issues Interchange Problems Solutions –Web services –IS architectures –Common projects –...

Slides:



Advertisements
Similar presentations
Requirements. UC&R: Phase Compliance model –RIF must define a compliance model that will identify required/optional features Default.
Advertisements

Software Engineering 2003 Jyrki Nummenmaa 1 A BASIC OO SOFTWARE DEVELOPMENT PROCESS Earlier, we saw a number of different software lifecycle models.
OBP Research Oy for simpler creation of embedded systems.
Software Engineering Module 1 -Components Teaching unit 3 – Advanced development Ernesto Damiani Free University of Bozen - Bolzano Lesson 3 – Building.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
Software Design & Development Year 12. Structure of the Course Development and Impact of Software Solutions Development and Impact of Software Solutions.
7M701 1 Software Engineering Software Requirements Sommerville, Ian (2001) Software Engineering, 6 th edition: Chapter 5
1 Requirements Analysis and Specification Requirements analysis.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Extended Enterprise Architecture Framework (E2AF)
Software Architecture April-10Confidential Proprietary Master Data Management mainly inspired from Enterprise Master Data Management – An SOA approach.
Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.
Training of master Trainers Workshop 10 – 15 November 2012 e-Services Design and Delivery Module VI Emilio Bugli Innocenti.
New Task Group CRIS Architecture & Development Maximilian Stempfhuber RWTH Aachen University Library
Reuse Standards Dr. Carma McClure Extended Intelligence, Inc. Copyright (c) 1998 by Extended Intelligence, Inc.
Distributed Access to Data Resources: Metadata Experiences from the NESSTAR Project Simon Musgrave Data Archive, University of Essex.
DDI Lifecycle: Moving Forward Outcome of the Recent Workshop in Dagstuhl Joachim Wackerow.
LIGHTNESS Introduction 10th Oct, 2012 Low latency and hIGH Throughput dynamic NEtwork infrastructureS for high performance datacentre interconnectS.
By: Md Rezaul Huda Reza 5Ps for SE Process Project Product People Problem.
CSE 303 – Software Design and Architecture
DIS Helsinki University of Technology Multi-Agent System Enhanced Supervision of Process Automation Teppo Pirttioja 1, Antti Pakonen 2, Ilkka.
Committee of Sponsoring Organizations of The Treadway Commission Formed in 1985 to sponsor the National Commission on Fraudulent Financial Reporting “Internal.
SOFTWARE DESIGN Design Concepts Design is a meaningful engineering representation of something that is to be built It can be traced to a customer’s requirements.
© Mahindra Satyam 2009 Decision Analysis and Resolution QMS Training.
Model-Driven Analysis Frameworks for Embedded Systems George Edwards USC Center for Systems and Software Engineering
Drexel University CS 451 Software Engineering Winter Yuanfang Cai Room 104, University Crossings
BSD Working Group Providers’ forum BSD Panels’ workshop IBSDF study BSD Research.
SOFTWARE ARCHITECT – DESIGN.  Introduction  Architecture Drivers  POS System Architecture  Mapping Between Perspective  Evaluate Architecture  Project.
Schema Interoperability Liam Magee Global Cities Institute RMIT University Melbourne, Australia.
The roots of innovation Future and Emerging Technologies (FET) Future and Emerging Technologies (FET) The roots of innovation Proactive initiative on:
Lecture 7: Requirements Engineering
Commonwealth Certificate for Teacher ICT Integration.
GRAPPLE – Public Event Slide 1 Extending Commercial LMSs with Adaptivity Patrick Pekczynski imc information multimedia communication AG.
Information Systems Engineering. Lecture Outline Information Systems Architecture Information System Architecture components Information Engineering Phases.
Modeling Component-based Software Systems with UML 2.0 George T. Edwards Jaiganesh Balasubramanian Arvind S. Krishna Vanderbilt University Nashville, TN.
SEMANTIC AGENT SYSTEMS Towards a Reference Architecture for Semantic Agent Systems Applied to Symposium Planning Usman Ali.
Accounts Chamber of the Russian Federation Approaches to comprehensive project and program audit in the Accounts Chamber of the Russian Federation.
Rational Unified Process Fundamentals Module 7: Process for e-Business Development Rational Unified Process Fundamentals Module 7: Process for e-Business.
Service Component Registry and Repository (SCRR) April 26, 2007 Lico Galindo 2007 Exchange Network National Meeting.
Requirements Engineering for Web Applications. SR: System Vision Document Written by key stakeholders Written by key stakeholders An executive summary.
A PPARC funded project Common Execution Architecture Paul Harrison IVOA Interoperability Meeting Cambridge MA May 2004.
CSE 303 – Software Design and Architecture
Triple Stores. What is a triple store? A specialized database for RDF triples Can ingest RDF in a variety of formats Supports a query language – SPARQL.
1 Introduction to Design. 2 Outline Basics of design Design approaches.
Developing Product Line Components Jan Bosch Professor of Software Engineering University of Groningen, Netherlands
Week 6: Software Design HNDIT Software Engineering Software Design Learning Outcomes  Understand the activities involved in the Design process.
Mahindra Satyam Confidential Quality Management System Software Defect Prevention.
Architectural Mismatch: Why reuse is so hard? Garlan, Allen, Ockerbloom; 1994.
© Chinese University, CSE Dept. Software Engineering / Topic 3: Software Engineering Principles Your Name: _____________________ Computer Science.
LECTURE 5 Nangwonvuma M/ Byansi D. Components, interfaces and integration Infrastructure, Middleware and Platforms Techniques – Data warehouses, extending.
Triple Stores.
Lecture 9- Design Concepts and Principles
EIN 6133 Enterprise Engineering
FORMAL SYSTEM DEVELOPMENT METHODOLOGIES
Semantic Web - Ontologies
Business Rule Based Configuration Management and Software System Implementation Using Decision Tables Olegas Vasilecas, Aidas Smaizys VGTU, Vilnius, Lithuania.
Enterprise Data Model Enterprise Architecture approach Insights on application for through-life collaboration 2018 – E. Jesson.
Model-Driven Analysis Frameworks for Embedded Systems
Component-Level Design
Lecture 9- Design Concepts and Principles
IDEAS Core Model Concept
MORE ON ARCHITECTURES The main reasons for using an architecture are maintainability and performance. We want to structure the software into reasonably.
Members: Keshava Shiva Sanjeeve Kareena
Partner Implications from Seminar: New Approaches to Capacity Development Break-out Group: Role of Assessment frameworks.
Chapter 5 Architectural Design.
System Reengineering Restructuring or rewriting part or all of a system without changing its functionality Applicable when some (but not all) subsystems.
Triple Stores.
Software Requirements
Architectural Mismatch: Why reuse is so hard?
Software Requirements
Presentation transcript:

Tools Interoperability Workshop ICCS 2006

Issues Interchange Problems Solutions –Web services –IS architectures –Common projects –...

Interchange issues Interoperability –Internal (CG, FCA communities) –External (rest-of-the-world) Standards –De facto –Official Interfaces Efficiency –Theoretical –Experimental Benchmarks

Problems Incomplete functionalities Overlap in functionalities Lack of development capacity

Solutions Web services as inspiration –Conceptual models and techniques Develop IS architectures –What roles do tools play in IS? Do Common projects –How to organize, divide tasks? Open source approaches Better documentation Modular development Requirements analysis –Resulting in scenarios, lists Better configurability –E.g. different layout styles

Solutions Back end infrastructure –Basic CG representations/operations etc –Specialized functionality –Quality criteria: efficiency, reliablity External interoperability –RDF etc. Concentrate on core functionalities Converters, wrappers –Let existing tools interoperate without requiring complete redesign FMF-framework –Possible (implementation of) overall IS architecture? Architectural conceptual models –E.g; modularity

Solutions Use principles from software engineering Types of modules –Sequences of operations –Modular inferencing Implement CGIF –Don’t just talk about it! Common logic –Standardize semantics, not just syntax

Solutions Develoip data-sets for benchmarking Benchmarking –Objects, problems –Internal, external –Data, operations Application frameworks Classification of functionalities Tool assessment –What to evaluate?