1 / 14

Participation Concept eSciDoc Project

Participation Concept eSciDoc Project. Revision History:. Thomas Gruen 05.04.2006 Filename: cpt_participation_process__20060404. Agenda. Approach Time Schedule 2006 Development of Service – Input of Pilots Validation of Concepts Development of Software and Service

idra
Download Presentation

Participation Concept eSciDoc Project

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Participation Concept eSciDoc Project Revision History: Thomas Gruen 05.04.2006 Filename: cpt_participation_process__20060404

  2. Agenda • Approach • Time Schedule 2006 • Development of Service – Input of Pilots • Validation of Concepts • Development of Software and Service • What do we expect from the pilots in the next month

  3. Approach Adv. Board eSciDoc Decision 13/01/2006 Steering Committee Decision 12/2005 • Publication Manager • Scholarly Workbench 1. Usage Scenarios 2. Mapping against requirements 3. Identified Use Cases 5. Functional Design 4. Validation of Requirements with Pilots Priorization      Completed Completed Started Completed Started Develop platform decision Develop high level architecture concept Develop detailed architecture concept    Started Completed Completed

  4. Agenda • Approach • Time Schedule 2006 • Development of Service – Input of Pilots • Validation of Concepts • Development of Software and Service • What do we expect from the pilots in the next month

  5. Framework (SWB) Framework (PM Basic) Publication Management (Basic Functionality) Application Architecture SWB (Showcase) Design Design D D D Build B B B Build T T T Test Test eSciDoc Time Schedule 2006 … Participation Concept and Coordination with Pilots Scholarly Workbench Detailed Specification (Showcase & prod. release) Ramp up Phase 3 months Piloting Planning of the specification phase Planning of the implementation Detailed Specification (Basic & enhanced functionality) Publication Management … Participation Concept and Coordination with Pilots Application Architecture Support Application Architecture Update of Interfaces and Test Preparation Coordination of Interfaces and Develop. Env. Integration Planning of the architecture implementation Joint Testing (SWB & Publication Management) Specify and develop technical architecture Framework

  6. Agenda • Approach • Time Schedule 2006 • Development of Service – Input of Pilots • Validation of Concepts • Development of Software and Service • What do we expect from the pilots in the next month

  7. Service Description Report to eSciDoc Is service tailored to requirements of institute? - validate - Report to Directors Report to eSciDoc Which are the detailed requirements for the most important functionalities? Report to Directors Release Definition Report to eSciDoc Report to Directors Development / Testing How can I improve the prototype? Service Deployment Report to eSciDoc and sInfo How can the service best be integrated into the everyday life of the institute? Report to Directors Can I support other institutes with my experiences as a pilot? Operation Development of Service – Input of Pilots ServiceDevelopment Feedback from Pilots

  8. Agenda • Approach • Time Schedule 2006 • Development of Service – Input of Pilots • Validation of Concepts • Development of Software and Service • What do we expect from the pilots in the next month

  9. Phase 1: Participation for PubMan– Validation of Concepts Validation of Scope of Service and Functionality on the basis of Usage Scenarios and conceptual papers • 26 January 2006 Kick-off Meeting – Objectives: • Validation of Service Description • Create understanding of pilots for fundamental concepts • Present list of features and functionalities • 20-21 February 2006 „Klausurtagung“ - Objectives • Detailed discussion of Usage Scenarios, concepts and functionalities with respective workgroups March 2006 Visit of individual insitutes to discuss and validate USCs and detailed requirements Transition Point • 5-6 April 2006 • Finalizing of Service Description, incl. concepts and features • Final discussion of results • Accept of priorized and extended list of features and functionalities Development Testing …

  10. Agenda • Approach • Time Schedule 2006 • Development of Service – Input of Pilots • Validation of Concepts • Development of Software and Service • What do we expect from the pilots in the next month

  11. Development of Software and Service bases onContinuous Input of Pilots Pilot Institutes Feedback / Testing / Validation / Functional Input • Release 1 • ‘PubMan’ • Release 3 • ‘PubMan’ • Finalizing • Application • Release 2 • ‘PubMan’ • Migration • of eDoc ZIM eSciDoc Project Team Going Live MPS wide! Setting up line organization! Support / Training / Rollout First Yearbook!

  12. Agenda • Approach • Time Schedule 2006 • Development of Service – Input of Pilots • Validation of Concepts • Development of Software and Service • What do we expect from the pilots in the next month

  13. What do we expect from the pilots in the next month • Individual question will be asked by the eSciDoc Team to clarify open issues. • Service description feedback • Voluntary / optional feedback to revised USC is welcomed. • Workgroups to be defined in the next meeting . Next meeting will be : ??.??.???? In Berlin (HH) ?. • We expect the help from the pilots to verify prototypes in the 3 quarter of this year.

  14. Thanks! Any questions?

More Related