LCG Persistency Framework Project Boundary Conditions and Overall Schedule Torre Wenaus, BNL/CERN.

Slides:



Advertisements
Similar presentations
Identify Problems, Planning Objectives and Constraints.
Advertisements

Project Management 6e..
ESTIMATING Agile/practical project work TDT4290, NTNU, Trondheim Fredrik Bach 02/09/2014.
Financial Systems Needs Assessment Project Update Monthly Research Administrators Meeting March 11, 2010.
Defining the Project Chapter 4.
Rational Unified Process
A Prototyping Lifecycle. The Waterefall Model and Prototyping 4 As early as the 1980’s the classic “Waterfall model” of software development was criticised.
Lecture 2b: Software Project Management CSCI102 - Introduction to Information Technology B ITCS905 - Fundamentals of Information Technology.
SE 555 Software Requirements & Specification Beyond Requirements Based on Weigers Chapter17.
G R I P Governmental Reporting Implementation Process August 30, 2000 Presentation to the Financial Standards Advisory Committee.
Review Questions List and describe the purpose of the four phases of Systems Analysis. The preliminary investigation phase quickly determines whether or.
Iterative development and The Unified process
Systems Engineering Management
Project Management Basics
Defining the Activities. Documents  Goal Statement defines why helps manage expectations  Statement of Work what gets delivered defines scope  Software.
Goal and Scope Where are we going and what path will we be taking?
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
RUP Fundamentals - Instructor Notes
Defining the Project CHAPTER FOUR PowerPoint Presentation by Charlie Cook Copyright © 2014 McGraw-Hill Education. All Rights Reserved.
-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.
Agenda Teams Responsibilities Timeline Homework and next steps.
1 The Initial Report Preparation Guidelines. 2 The Initial Report u Definition of project scope u Project aims and objectives u Initial project plan.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Budget Setting Process For 2015 Budget Draft 0.1 Member Forum Date of Meeting: 27th May 2014.
Blueprint RTAG comments Torre Wenaus, BNL/CERN July 3, 2002.
1 Activities covered by project management Feasibility study Is project technically feasible and worthwhile from a business point of view? Planning Only.
1 Chapter 23 Estimation for Software Projects. 2 Software Project Planning The overall goal of project planning is to establish a pragmatic strategy for.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
Slide 1 Project Management Chapter 4. Slide 2 Objectives ■ Become familiar with estimation. ■ Be able to create a project workplan. ■ Become familiar.
 Management ◦ The activities and tasks undertaken by one or more persons for the purpose of planning and controlling the activities of other in order.
Develop Project Charter
Early Thinking on ARDA in the Applications Area Torre Wenaus, BNL/CERN LCG Applications Area Manager PEB Dec 9, 2003.
J. Scott Hawker p. 1Some material © Rational Corp. Rational Unified Process Overview See and use the RUP Browser on lab machines.
1 / x CMMI Technical Solution Rob Vanden Meersche Dieter Van den Bulcke.
1 Program Release 2008 Update to the Administrative Council August 9, 2007.
Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 3. Defining the System A Use Case Primer Organizing.
Project Management Process
Unit – I Presentation. Unit – 1 (Introduction to Software Project management) Definition:-  Software project management is the art and science of planning.
Project Management Why do projects fail? Technical Reasons
12 March, 2002 LCG Applications Area - Introduction slide 1 LCG Applications Session LCG Launch Workshop March 12, 2002 John Harvey, CERN LHCb Computing.
1 Project Management C13PM Session 2 Project Initiation & Definition Russell Taylor Business Department Staff Workroom
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Establishing Project Scope 1. Factors Affecting Project Scope  The functionality that must be delivered to meet the user’s needs  The resources available.
To RAD or not to RAD? RAD is the relatively new kid on the block. You know the one. The one with all the flashy stuff and is practically the Usain Bolt.
Simulation Project Setup Status Torre Wenaus, BNL/CERN LCG Applications Area Manager PEB Meeting January 28, 2003.
T Project Review MTS [PP] Iteration
Information Sharing for Integrated Care A 5 Step Blueprint.
Collaborating for Quality Quality Assurance (QA) & Quality Control (QC) in the Accelerator Project (ACCSYS) Matthew Conlon ACCSYS QA/QC
12 March, 2002 LCG Applications Area - Introduction slide 1 LCG Applications Session LCG Launch Workshop March 12, 2002 John Harvey, CERN LHCb Computing.
Grid Deployment Technical Working Groups: Middleware selection AAA,security Resource scheduling Operations User Support GDB Grid Deployment Resource planning,
1 Team Skill 4 Managing the scope Noureddine Abbadeni Al-Ain University of Science and Technology College of Engineering and Information Technology Based.
Collaborating for Quality through the Project Quality Plan Matthew Conlon ESS ACCSYS QA/QC Quality Learning & Planning.
What is a Functional Spec?  Defines what the functionality will be NOT how it will be implemented  Describes features of the software product product's.
Chapter 33 Estimation for Software Projects
LCG Applications Area Milestones
Project Management Chapter 3.
Information Sharing for Integrated care A 5 Step Blueprint
WORK BREAKDOWN STRUCTURE
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Information Technology Project Management – Fifth Edition
Software Engineering: A Practitioner’s Approach, 6/e Chapter 23 Estimation for Software Projects copyright © 1996, 2001, 2005 R.S. Pressman & Associates,
Johanna Rothman Know What “Done” Means Chapter 11
Project Management Chapter 11.
Chapter 33 Estimation for Software Projects
Software Engineering: A Practitioner’s Approach, 6/e Chapter 23 Estimation for Software Projects copyright © 1996, 2001, 2005 R.S. Pressman & Associates,
I Datagrid Workshop- Marseille C.Vistoli
Chapter 26 Estimation for Software Projects.
SEAL Project Core Libraries and Services
Presentation transcript:

LCG Persistency Framework Project Boundary Conditions and Overall Schedule Torre Wenaus, BNL/CERN

PSI Colloquium, May Slide 2 Current State of Persistency Framework Schedule

Torre Wenaus, BNL/CERN PSI Colloquium, May Slide 3 This Workshop: Purpose  To address software design, plans and work allocations to meet the September persistency framework prototype milestone.  We do need to focus this workshop on the concrete program to September  We are rushing to an early prototype: this is in my view a good thing  An initial prototype implementation based on initial technology choices and whatever prioritizations are necessary to deliver  Deliver working code and a basic working system, then iterate and build on it  We are serious about building a framework compatible with introducing other implementations in the future  Committed to clean component breakdowns and interfaces able to support future implementations

Torre Wenaus, BNL/CERN PSI Colloquium, May Slide 4 This Workshop: Goals  We need to emerge from this workshop with  An agreed feature set for the September prototype  What will be delivered, what will be deferred  We must focus available effort on what is to be delivered  An agreed component breakdown covering at least the functionality of the September prototype  Identification of the interfaces for the needed components  Draft specifications for as many as possible  Agreement on as many as possible  Agreement on any prioritizations involving deferral past September of certain ‘internal’ interfaces  Agreement on approaches – or at least quick decision processes to settle approaches  E.g. persistent references and navigation

Torre Wenaus, BNL/CERN PSI Colloquium, May Slide 5 Goals (2)  Definition of work packages  With scope covering at least the feature set of the September prototype  With estimates of required effort  Assignment of work packages to active participants  Assessment of whether the scope needed for September is covered  Unassigned work packages?  Inadequate available effort in some work packages?  Timeline  If this workshop fails to settle the specifics of a September prototype – technical, timeline, and work packages allocated to active people – I hold little hope for achieving that milestone!

Torre Wenaus, BNL/CERN PSI Colloquium, May Slide 6 What Next?  Status report to SC2 next week  Within 1-2 weeks…  Small focus meetings in work package teams  Get timelines and deliverables from the work package owners within 1-2 weeks  Persistency Framework workplan to SC2 July 12  Next meeting/workshop…  Status and integration meeting in late August?  Next major workshop end September?  Assess what we have (and have not) done and what we have learned  Take a longer view of the development plan

Torre Wenaus, BNL/CERN PSI Colloquium, May Slide 7 …and enough of the preliminaries!