1 reTHINK Deliverables, How To Read reThink deliverables quick starter.

Slides:



Advertisements
Similar presentations
EIDE System Requirements and Specification Documents
Advertisements

EGov-Bus 1st year review Advanced eGovernment Information Service Bus eGov-Bus, FP6-IST STP 1st Formal Review Meeting , Brussels eGov-Bus.
THE CORE PROJECT Jose Jimenez (project manager). What is the Core platform?
Exchange of Performance Assessments EPA Project State, Outlook Urs Hassler – Project leader ETH Zurich
0 DOD/DT/CEDCV – 20 th & 21 st January Paris meeting SAGEM RTD Activities C2-Sense project Paris – 20 & 21 January 2015.
Enabling Access to Sound Archives through Integration, Enrichment and Retrieval WP1. Project Management.
C2-SENSE WP2 Bojan Božić, Gerald Schimak, Refiz Duro C2-SENSE WP2 Meeting Paris
Review meeting 05th December
UNDERSTANDING JAVA APIS FOR MOBILE DEVICES v0.01.
The HITCH project: Cooperation between EuroRec and IHE Pascal Coorevits EuroRec 2010 Annual Conference June 18 th 2010.
“Chapter 9” Managing Object Design Done By: Alia Waled.
Business Area Analysis Focus: Domain View (selected business area) Goals: –Isolate functions and procedures that allow the area to meet its goals –Define.
Page 1 Building Reliable Component-based Systems Chapter 18 - A Framework for Integrating Business Applications Chapter 18 A Framework for Integrating.
Applying the ISO RM-ODP Standard in e-Government B. Meneklis 1, A. Kaliontzoglou 2,3, D. Polemi 1, C. Douligeris 1 1 University of Piraeus, Department.
SWIM and Next Gen Enterprise Architecture Artifacts
1 SWE Introduction to Software Engineering Lecture 11 - Requirements Engineering Processes.
Software Architecture in Practice (3rd Ed) Introduction
What is Business Analysis Planning & Monitoring?
SOA, BPM, BPEL, jBPM.
Initial slides for Layered Service Architecture
CISE Demonstrator Vincent Dijkstra DG Informatics (DIGIT)
WP.5 - DDI-SDMX Integration E.S.S. cross-cutting project on Information Models and Standards Marco Pellegrino, Denis Grofils Eurostat METIS Work Session6-8.
The Preparatory Phase Proposal a first draft to be discussed.
Mantychore Oct 2010 WP 7 Andrew Mackarel. Agenda 1. Scope of the WP 2. Mm distribution 3. The WP plan 4. Objectives 5. Deliverables 6. Deadlines 7. Partners.
Digital Object Architecture
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Requirements Engineering Processes l Processes used to discover, analyse and.
Agenda Context and Vision FI-WARE Architecture
OASIS Week of ebXML Standards Webinars June 4 – June 7, 2007.
Information System Development Courses Figure: ISD Course Structure.
Architectural Design Based on Chapter 11 of the textbook [SE-8] Ian Sommerville, Software Engineering, 8t h Ed., Addison-Wesley, 2006 and on the Ch11 PowerPoint.
SWIM-SUIT Information Models & Services
Enterprise Architecture [Product Name] [Enterprise Architect] [Discipline and Names] To-Be Powerpoint Presentation v
Web Services Standards. Introduction A web service is a type of component that is available on the web and can be incorporated in applications or used.
Lecture 7: Requirements Engineering
SGCC 6.1 Kick-off Project Setup. Introduction Tour de Table –Who’s who –Attendance list, s Scope of CC 6.1.
Chapter 6 Architectural Design.
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
Enterprise Systems Architectures EGN 5621 Enterprise Systems Collaboration (Professional MSEM) Fall, 2012.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 05. Review Software design methods Design Paradigms Typical Design Trade-offs.
Modeling Component-based Software Systems with UML 2.0 George T. Edwards Jaiganesh Balasubramanian Arvind S. Krishna Vanderbilt University Nashville, TN.
Project Methodology May 2, System Development Life Cycle Overview.
INTRODUCTION. 1.1 Why the Internet Protocol Multimedia Subsystem 1.2 Where did it come from?
Logical view –show classes and objects Process view –models the executables Implementation view –Files, configuration and versions Deployment view –Physical.
Jose Jimenez Telefónica I+D Future Network & Mobile Summit 2011 The vision of Future Internet in the FI PPP Core Platform project.
WP2: Domain Model + WP3 TENCC Rob Koper & Hubert Vogten TENCompetence Project Meeting 3-4 July 2006 Kerkrade, The Netherlands.
The FI-WARE Project – Base Platform for Future Service Infrastructures FI-WARE Stefano De Panfilis (Fi-WARE PCC Member) 4 th July 2011 FInES - Samos Summit.
Registries, ebXML and Web Services in short. Registry A mechanism for allowing users to announce, or discover, the availability and state of a resource:
1 Registry Services Overview J. Steven Hughes (Deputy Chair) Principal Computer Scientist NASA/JPL 17 December 2015.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Technical Support to SOA Governance E-Government Conference May 1-2, 2008 John Salasin, Ph.D. DARPA
An organizational structure is a mostly hierarchical concept of subordination of entities that collaborate and contribute to serve one common aim... Organizational.
Stages of design  High level design  High level data structure  Architecture  Low level design-code design  Algorithms  Low level data structures.
Web Services Architecture Presentation for ECE8813 Spring 2003 By: Mohamed Mansour.
Unit – I Presentation. Unit – 1 (Introduction to Software Project management) Definition:-  Software project management is the art and science of planning.
CERES-2012 Deliverables Architecture and system overview 21 November 2011 Updated: 12 February
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 6/6/2016 1/25 IT076IU Software Engineering Project Review 2.
Review of Definitions Software life cycle: –Set of activities and their relationships to each other to support the development of a software system Software.
 The processes used for RE vary widely depending on the application domain, the people involved and the organisation developing the requirements.  However,
© The InfoCitizen Consortium Project Presentation Agent based negotiation for inter- and intra-enterprise coordination employing a European Information.
Nicolas Granier / June 7th
What is an Architecture?
Chapter 1 (pages 4-9); Overview of SDLC
Unified Modeling Language
e-Invoicing – e-Ordering 20/11/2008
Wide Area Workload Management Work Package DATAGRID project
Introduction to Web Services
What is an Architecture?
Web Service Security support in the SSE Toolbox
Presentation transcript:

1 reTHINK Deliverables, How To Read reThink deliverables quick starter

2 reThink Work Breakdown Structure reTHINK Project M9 Review WP8- Management WP1- Use Cases and Business Models WP2- Overall architecture WP3 - Core framework implementation WP3 - Core framework implementation WP5 - Scenario/Service implementation WP6- Integration, End users experimentation WP7- Dissemination activity/Impact management WP4 - Govenance and Security model implementation WP4 - Govenance and Security model implementation

3 reThink deliverables quick starter reThink Deliverables D1.1 Use cases and Sustainable Business models for reTHINK D1.1 Use cases and Sustainable Business models for reTHINK D2.1 Framework architecture definition D4.1 Management and Security features specifications D4.1 Management and Security features specifications D5.1 Service Scenarios Specification D5.1 Service Scenarios Specification D6.1Testbed specification D2.2 Data Models and Interface Specification of the framework D2.2 Data Models and Interface Specification of the framework D3.1 Hyperty Runtime and Hyperty Messaging Node Specification D3.1 Hyperty Runtime and Hyperty Messaging Node Specification ↖ WBS

4 D1.1 Use cases and Sustainable Business models for reTHINK project.eu/bscw/bscw.cgi/d30179/D1.1%20Use%20cases%20and%20Sustaina ble%20Business%20models%20for%20reTHINK.pdf  General Introduction and business trends – Chapter 1 & 2  Description of User scenarios and use cases covering areas like context based social communication, - urban participation for mobile eGovernment in a smart city, user-IoT entity interaction and Content delivery and Use-case prioritization for WP2 and WP5 – Chapter 3  Business Models for most promising use cases – § 3.5  Business processes for Service lifecycle management and business relationships management – Chapter 4 reThink deliverables quick starter ↖List of deliverables

5 D2.1 Framework architecture definition project.eu/bscw/bscw.cgi/d30184/D2.1%20Framework%20Architecture%20D efinition.pdf  This document describes the overall architecture and requirements for the reTHINK project.  Architecture framework (chapter 1-10) – Requirements Chapter 2 – Architecture overview Chapter 5  Extensive study of the state of the Art – Annex A  and use-case – Annex B reThink deliverables quick starter ↖List of deliverables

6 D2.2 Data Models and Interface Specification of the framework project.eu/bscw/bscw.cgi/d30194/D2.2%20Data%20Models%20and%20Interf ace%20Specification%20of%20the%20Framework.pdf  Describes the data models to be used to describe Hyperties and the interfaces for the architecture defined in D2.1.  Requirements – Chapter 3  Specifications of the DataModel – Chapter 5  Interface generic design – Chapter 6 reThink deliverables quick starter ↖List of deliverables

7 D3.1 Hyperty Runtime and Hyperty Messaging Node Specification project.eu/bscw/bscw.cgi/d30198/D3.1%20Hyperty%20Runtime%20and%20 Hyperty%20Messaging%20Node%20Specification-V1.1.pdf  This document describes the technical details and the information needed by developers to start prototyping reTHINK Core Framework, which is comprised of the runtime environment where Hyperties are executed and the messaging nodes used to support messages exchange between Hyperties.  Hyperty Runtime Specification – Chapter 4  Messaging Node Specification – Chapter 5 reThink deliverables quick starter ↖List of deliverables

8 D4.1 Management and Security features specifications project.eu/bscw/bscw.cgi/d30208/D4.1%20Management%20and%20Security %20features%20Specifications.pdf  Provides a detailed specification of the Policy Management, Governance, Identity Management, Graph Connector and the Hyperty Directory service components.  Identity & Trust Management – Chapter 3  Hyperty Registry and Catalogue – Chapter 4  Graph Connector – Chapter 5  Governance & Policy Management – Chapter 6 reThink deliverables quick starter ↖List of deliverables

9 D5.1 Service Scenarios Specification  This document will contain a detailed and systematic description of Service scenarios and Hyperties specified in T5.1 which will be implemented in the next tasks of this WP. reThink deliverables quick starter ↖List of deliverables

10 D6.1 Testbed specification  Defines technical infrastructure and provides manual for using, connecting to the testbed infrastructure. reThink deliverables quick starter ↖List of deliverables