Worldwide Protein Data Bank www.wwpdb.org wwPDB Common D&A Project Full Project Team Meeting Rutgers March 16-19, 2010.

Slides:



Advertisements
Similar presentations
CASDA Project Management A presentation to the CASDA Preliminary Design Review IM&T / CASS Dan Miller | CASDA Project Manager 11 March 2014.
Advertisements

Business logic for annotation workflow Tom Oldfield July 21, 2010.
State of Indiana Business One Stop (BOS) Program Roadmap Updated June 6, 2013 RFI ATTACHMENT D.
Test Automation Success: Choosing the Right People & Process
Beta Testing: The Contractor’s Perspective Trns·port User Group Meeting October 2005.
HP Quality Center Overview.
Software Project Management
Project Management Workshop. Nick Cook  Citigroup Corporate and Investment Bank  European Technology Business Office Manager Edinburgh University April.
GAI Proprietary Information
Basic guidelines for the creation of a DW Create corporate sponsors and plan thoroughly Determine a scalable architectural framework for the DW Identify.
Project Management and Communication Represented by: Latifa Jaber Al-Ghafran.
Lecture 2b: Software Project Management CSCI102 - Introduction to Information Technology B ITCS905 - Fundamentals of Information Technology.
NGAO Team Meeting Management Peter Wizinowich May 26, 2009.
1 April 2010 TX SET Timeline Project Conceptualization 11 weeks Market Requirements 12 weeks ERCOT Requirements 12 weeks Conceptual Design 6 weeks Detail.
Software projects Management & Development Alireza Saebi
Planning. SDLC Planning Analysis Design Implementation.
LSU 01/18/2005Project Life Cycle1 The Project Life Cycle Project Management Unit, Lecture 2.
Automating your Business Processes Using Oracle Workflow Therron Hofsetz Logical Apps, Inc.
The BIM Project Execution Planning Procedure
User Interface Mock Up for Sequence Processing Jasmine Young, Jawahar Swaminathan The following interface mock ups take into account the functionalities.
Effective Methods for Software and Systems Integration
Managing Projects using Oracle Project Management (PJT) & SPREADSHEETS Neeraj Garg Vice President, Client Services.
Agenda Teams Responsibilities Timeline Homework and next steps.
30-31 March 2005 Workshop "IMS over Fixed Access" - Washington 1 TISPAN_NGN Project plan Martin Niekus Alain Sultan
Web Trnsport – Beta Testing and Implementation TUG Roundtable Discussion Elizabeth Rodgers Info Tech, Inc. October 9, 2007.
Understand Application Lifecycle Management
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Worldwide Protein Data Bank wwPDB Common D&A Project January 28, 2010 Steering Committee Project Update.
A Project ’ s Tale: Transitioning From SW-CMM to CMMI-SE/SW Warren Scheinin Systems Engineer, NG Mission Systems CMMI Technology Conference & User Group.
CEN th Lecture CEN 4021 Software Engineering II Instructor: Masoud Sadjadi Software Project Planning.
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
Webster Visualize Webster Financial Team Visual Scrumware Joe Andrusyszyn Mark Bryant Brian Hannan Robert Songer.
Using Blackboard for blended learning Delivering the Geography curriculum at Kingston College This talk will give an overview of the assessment features.
OOI CI LCA REVIEW August 2010 Ocean Observatories Initiative OOI Cyberinfrastructure Architecture Overview Michael Meisinger Life Cycle Architecture Review.
Object-oriented Analysis and Design Stages in a Software Project Requirements Writing Analysis Design Implementation System Integration and Testing Maintenance.
© 2012 xtUML.org Bill Chown – Mentor Graphics Model Driven Engineering.
Project Outline City of Mountain View – need image !
Review of Software Process Models Review Class 1 Software Process Models CEN 4021 Class 2 – 01/12.
Data Integration and Management A PDB Perspective.
THE PROJECT LIFE CYCLE PROJECT MANAGEMENT LIFE CYCLE LSU 01/18/2005 PROJECT LIFE CYCLE 1.
Targets for project progress 2015: graduation review – clear documentation and PoC implementation specify general framework and API requirements gap analysis.
Nuclear Standards for Polymeric Piping Aaron Forster, NIST Engineering Laboratory NIST, MS Bureau Drive Gaithersburg, MD (301)
Worldwide Protein Data Bank wwPDB Common D&A Project November 24, 2009 November 24, 2009 Steering Committee Project Update.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
The principles of an object oriented software development process Week 04 1.
Worldwide Protein Data Bank Common D&A Project Sequence Processing Modular Demo May 6, 2010 Project Deliverable.
Lead from the front Texas Nodal 1 Texas Nodal Market Implementation ERCOT Board Of Directors – August 15, 2006 TPTF Meeting August.
EPOS IP Roadmap Massimo Cocco & PDB. EPOS IP project Timeline Implementation Validation Pre-operation.
Requirements Management Overview NIGMS Software Development.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
Nodal Program Update Mike Cleary Sr. VP and Chief Technology Officer.
T Iteration Demo Tikkaajat [PP] Iteration
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
1 Sean Aluoto Anthony Keeley Eric Werner. 2 Project Plan Overview Project Lifecycle model Time line Deliverables Organization plan Risk management Design.
Copyright 2015, Robert W. Hasker. Classic Model Gathering Requirements Specification Scenarios Sequences Design Architecture Class, state models Implementation.
Agenda Leads work – Track Status Admin / Upcoming / Next Steps – RFP Document review – Vendor Question Review – GL Preparation – Orals – Harris.
1 Process activities. 2 Software specification Software design and implementation Software validation Software evolution.
Office 365 Security Assessment Workshop
TechStambha PMP Certification Training
Description of Revision
The Open Group Architecture Framework (TOGAF)
Project Roles and Responsibilities
Software Engineering Lecture #14.
Amendment Invoice Task Force Progress Report
A summary of part 1 of Chapter 7 CEP 812 Kay Paff March 24, 1999
SOFTWARE LIFE-CYCLES Beyond the Waterfall.
Portfolio, Programme and Project
Amendment Invoice Task Force Progress Report
{Project Name} Organizational Chart, Roles and Responsibilities
Presentation transcript:

Worldwide Protein Data Bank wwPDB Common D&A Project Full Project Team Meeting Rutgers March 16-19, 2010

Worldwide Protein Data Bank Common D&A Project March 2010 Project Team Meeting Attendees:

Worldwide Protein Data Bank Common D&A Project March 2010 Project Team Meeting Review of Deliverable Objectives 1Q2010 Deliver production functionality that will provide a significant impact on the annotation workflow. –Implement the chemical and model coordinate sequences issue resolution and integration using the Master Format. –Graphical User Interface for the annotators  Sequence Editor –Build the “GO BACK” functionality architecture  Session management and Tracking infrastructure  WFE/API  WFM

Worldwide Protein Data Bank Common D&A Project March 2010 Project Team Meeting Deliverable Details Master Format. Finalization of Physical Data Exchange Annotator graphical interface for sequence functionality  Extended API Tracking DB creation/support  Extended Work Flow Engine (WFE)  Work Flow Manager (WFM)  Work Flow Manager User Interface (WFM UI)  Integration of this “module” of new functionalities into the existing workflows.

Worldwide Protein Data Bank wwPDB Common Tool Annotation Progress PDBe Sequence Processing Ligand Processing Ligand Processing Release Processing Geometry CK Validation Geometry CK Validation Calculated annotations (Bio Assem) Calculated annotations (Bio Assem) Corrections (water trans, pro- chiral ck) User Interface WFE/API Requirements Design Progress Tracking/ Status wwPDB Common Tool Sequence Processing Ligand Processing Ligand Processing Integration & Release Processing Geometry CK Validation Geometry CK Validation Calculated annotations (Bio Assem) Calculated annotations (Bio Assem) Corrections (water trans, pro- chiral ck) ADIT RCSB Autodep Release Processing Seq. Editor Ligand Processing Ligand Processing Geometry CK Validation Geometry CK Validation Calculated annotations (Bio Assem) Calculated annotations (Bio Assem) Corrections (water trans, pro- chiral ck) CIF - PDB PDB - CIF 4.1, , ,

Worldwide Protein Data Bank Common D&A Project March 2010 Project Team Meeting Goals for this meeting  Take advantage of face to face project team opportunities –Some current Data content/policy issues –Critical path development issues  Complete the design and development plan for the full sequence processing module  Complete the documentation of the Ligand processing module functional and technical requirements and design.  Take the opportunity for Course Correction –Adjust requirements, design and development strategies as needed. –Document lessons learned and adjust plan accordingly  Refine our design and development documentation strategy.

Worldwide Protein Data Bank Common D&A Project March 2010 Project Team Meeting Sequence Processing Current Task List April Objectives  Complete development and testing of Sequence Editor unit – near completion  Complete integration of Sequence Editor unit with existing pipelines – March 31  WFE/APIs instantiated for the full Sequence Processing module against the existing functionality, with preliminary WFM functionality in test, independent of current pipeline. End of April

Worldwide Protein Data Bank Common D&A Project March 2010 Project Team Meeting Functional Requirements: Process Overview With GO BACK functionality Graphical User Interface WFE, WFM

Worldwide Protein Data Bank Common D&A Project March 2010 Project Team Meeting Sequence Processing – the whole megillah  Annotator Team and Tech Team to review the remaining process steps for Sequence Processing –Elaborate on existing process maps – ID process order flexibility –WFM Discussion –Map existing functional software components to workflow components  Identify and resolve software choice issues FASTA vs BLAST  Tech Team – review API and WF implications, granularity?  Tech Team – Design and development plan

Worldwide Protein Data Bank Common D&A Project March 2010 Project Team Meeting Next Target – Ligand Processing With GO BACK functionality

Worldwide Protein Data Bank Common D&A Project March 2010 Project Team Meeting Ligand Processing – Functional Requirements Annotator exchange – experience with and analysis of existing work flows Draft of new TO BE process – Level 1  Annotator Team to elaborate and drill down - Level 2,3  Annotator Team to create decision trees and SIPOCS for all process steps.  Annotators to begin Use Case documentation  Annotator Team to map existing functional software components to the proposed workflow components.  Annotator Team to mock up interfaces for process interactive components

Worldwide Protein Data Bank Common D&A Project March 2010 Project Team Meeting Ligand Processing – Technical Requirements and Design  Tech Team to review the requirements  Review Functional software components  Capture technical requirements  Complete the draft design for the Ligand processing module  Create and initial plan.

Worldwide Protein Data Bank Common D&A Project March 2010 Project Team Meeting Rules of Engagement  Meetings will start at 8:45 AM each day  We will all work to gain the best advantage of our time together – during breaks only.  All discussions will be documented – process maps, tech requirements, design, glossary additions, use cases, CONCERNS.  All documentation will be a Team effort.  Decisions will be made as much as possible by consensus.  If a vote is necessary we agree to adopt the group majority vote.

Worldwide Protein Data Bank Common D&A Project March 2010 Project Team Meeting Next Steps  Complete meeting reports – –Appropriate functional, technical and design documentation –Implement development documentation strategy –Sequence processing delivery plan –Initial Ligand processing development plan  Schedule PI update/review of the project plans – Second week of April target