Trying to connect WBSs with people and phases Relevant questions to my work: How the realistic NGAO strategies will/should affect the work in progress?

Slides:

Advertisements

Similar presentations

Work Breakdown Structures

Advertisements

Write Your Project Title Here VU Logo Here Group Members Introduction Write your group members introduction here with names and VU Id.

NGAO Construction Project Cost Estimation: Initial Thoughts Richard Dekany NGAO Team Meeting #12 December 13, 2007.

Sixth Hour Lecture 10:30 – 11:20 am, September 9 Framework for a Software Management Process – Artifacts of the Process (Part II, Chapter 6 of Royce’ book)

Using UML, Patterns, and Java Object-Oriented Software Engineering Royce’s Methodology Chapter 16, Royce’ Methodology.

Science Group: Status, Plans, and Issues Claire Max Liz McGrath August 19, 2008.

NGAO Controls Team Meeting August 29, 2008 Erik Johansson.

NGAO System Design Review Response Peter Wizinowich, Rich Dekany, Don Gavel, Claire Max for NGAO Team SSC Meeting June 18, 2008.

Build to Cost Meeting: Goals, Agenda & New Directions Peter Wizinowich NGAO Team Meeting September 11-12, 2008.

1 NGAO Instrumentation Studies Overview By Sean Adkins November 14, 2006.

NGAO Control Systems Group Status, Plans & Issues NGAO Team Meeting August 19, 2008 Erik Johansson Jimmy Johnson, Doug Morrison, Ed Wetherell.

Observing Operations Concept Document Elizabeth McGrath NGAO PD Team Meeting #6 March 19, 2009.

NGAO System Design: AO System (WBS 3.2) & Laser Facility (WBS 3.3) Design Inputs & Outputs Peter Wizinowich NGAO Team Meeting #9 August 24, 2007.

Managing the Information Technology Resource Jerry N. Luftman

Science Operations Update NGAO - Meeting 11 D. Le Mignant, E. McGrath & C. Max W. M. Keck Observatory 11/05/2007.

Build to Cost Directions & Guidelines Peter Wizinowich SSC Meeting November 3, 2008.

NGAO Meeting #3 Introduction NGAO Meeting #3 Peter Wizinowich December 13, 2006.

Planning “Science Operations” tasks for the PD phase NGAO PD Phase D. Le Mignant W. M. Keck Observatory 08/19/2008.

WBS & AO Controls Jason Chin, Don Gavel, Erik Johansson, Mark Reinig Design Meeting (Team meeting #10) Sept 17 th, 2007.

NGAO Management Update Peter Wizinowich NGAO Meeting #11 November 5, 2007.

Science Operations Replan NGAO - Meeting 6 D. Le Mignant W. M. Keck Observatory 04/25/2007.

NGAO System Design Phase Management Report - Replan NGAO Meeting #6 Peter Wizinowich April 25, 2007.

Science Operations Plan NGAO - Meeting 10 D. Le Mignant W. M. Keck Observatory 09/17/2007.

NGAO interface control documents: Christopher Neyman W. M. Keck Observatory Keck NGAO PD phase Meeting #6 March 19, 2007 Videoconference.

1 Jul 2005CSE403, Summer'05, Section 02 Section 02: Life Cycle Architecture Review Valentin Razmov.

NGAO Team Meeting Management Peter Wizinowich May 26, 2009.

NGAO System Design Phase System & Functional Requirements Documents NGAO Meeting #6 Peter Wizinowich April 25, 2007.

Design Team Report: AO Operational Tools (aka Acquisition and Diagnostics) Christopher Neyman W. M. Keck Observatory (for the Operational tools team) Keck.

Encouraging “System Level” Thinking Christopher Neyman, Erik Johansson, David Le Mignant W. M. Keck Observatory Viswa Velur California Institute of Technology.

System Architecture WBS 3.1 Mid-Year Replan Richard Dekany NGAO Team Meeting #6 April 25-26, 2007 UCSC.

Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.

Software engineering Olli Alm Lecture 2: requirements, modelling & representation.

Project Management Methodology (PMM)

NGAO Instrumentation Preliminary Design Phase Planning September 2008 Sean Adkins.

Functional Requirements for NGAO Christopher Neyman W. M. Keck Observatory NGAO Team Meeting #9 August 24, 2007.

Trying to connect WBSs with people and phases Relevant questions to my work: How the re 8 -planning will affect the work in progress? Priorities to capture.

Design Team Report: AO Operational Tools (aka Acquisition and Diagnostics) Christopher Neyman W. M. Keck Observatory (for the Operational tools team) Keck.

Software projects Management & Development Alireza Saebi

Task Analysis is Part of Planning Once we have completed planning on the deliverables and contents of the deliverables, we need to plan out “how to accomplish”

Task Analysis is Part of Planning Once we have completed our plan on what to deliver and the contents of deliverables (via requirements), we need to: plan.

Basel Accord IITRANSITIONSERVICES Business Integration Support FCM Management Limited Paris New York Toronto.

® IBM Software Group © 2006 IBM Corporation PRJ480 Mastering the Management of Iterative Development v2 Module 3: Phase Management - Inception.

How to integrate the parts of your project to achieve success.

RUP Requirements RUP Artifacts and Deliverables

Typical Software Documents with an emphasis on writing proposals.

Current Situation and CI Requirements OOI Cyberinfrastructure Integrated Observatory Management Workshop San Diego May 28-29, 2008.

1 REQUIREMENT ENGINEERING Chapter 7. 2 REQUIREMENT ENGINEERING Definition Establishing what the customer requires from a software system. OR It helps.

CEN th Lecture CEN 4021 Software Engineering II Instructor: Masoud Sadjadi Software Project Planning.

Centro de Estudos e Sistemas Avançados do Recife PMBOK - Chapter 4 Project Integration Management.

Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.

Testing Workflow In the Unified Process and Agile/Scrum processes.

OOI CI LCA REVIEW August 2010 Ocean Observatories Initiative OOI Cyberinfrastructure Architecture Overview Michael Meisinger Life Cycle Architecture Review.

Doug Tody E2E Perspective EVLA Advisory Committee Meeting December 14-15, 2004 EVLA Software E2E Perspective.

Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava

Capacity Building Committee Architecture and Data Committee Meeting Seattle – July 2006.

Rational Unified Process Fundamentals Module 3: Disciplines I.

11/24/2015Dr. SASTRY-PROJ SOFTWARE PROJECT MANAGEMENT By Dr. M V S PERI SASTRY. B.E,Ph.D.

Project Task Planning 1 Concepts and Definitions Work Breakdown Structures.

1 Technology Infusion of the Software Developer’s Assistant (SDA) into the MOD Software Development Process NASA/JSC/MOD/Brian O’Hagan 2008 Software Assurance.

Lecture 14 22/10/15. The Object-Oriented Analysis and Design  Process of progressively developing representation of a system component (or object) through.

EO Dataset Preservation Workflow Data Stewardship Interest Group WGISS-37 Meeting Cocoa Beach (Florida-US) - April 14-18, 2014.

State of Georgia Release Management Training

Unit – I Presentation. Unit – 1 (Introduction to Software Project management) Definition:-  Software project management is the art and science of planning.

Software Production ( ) Lecture 3: Dr. Samer Odeh Hanna (PhD) office: 318.

1 1. Systems and Software Development 1.1 The Systems Life Cycle.

SOFTWARE PROJECT MANAGEMENT

IT-301 Project Management I: Unit 4: Cost Management.

Architecture Concept Documents

IEEE Std 1074: Standard for Software Lifecycle

Web Service Security support in the SSE Toolbox

Presentation transcript:

Trying to connect WBSs with people and phases Relevant questions to my work: How the realistic NGAO strategies will/should affect the work in progress? –How much planning is needed before Sept meeting? –Should we de-scope nearly all science ops if we can’t fund science instrument SD & PD. W/o instruments, this effort looks obsolete to me. Assuming we keep the current NGAO plan: –Priorities to capture observing scenarios? –What are the complementarities between some of the deliverables? –What are the overlap between some of the WBS? (see slides)

Trying to connect WBSs with people and phases Some whishes: -A realistic plan for science instruments to be built with our science community.. -Agreement on outlines & leads for main documents to be produced according to current plans -Agree on leads for the WBS (focus on need for overlap/coordination) -Flow diagram of activities with identified leads, e.g. OOCD??

NGAO sequences definitions document OOCD document: Example observations Planning User Observatory Observing User Observatory Post-observing Uses cases planning tools acquisition sequences calibrations sequences observing sequences Observing support and technical operations operation procedures WBS 3.2 WBS 3.4.4: Science observing planning and execution User Interfaces design WBS WBS WBS (new?) science requirements WBS 3.1 Re-planning Phased approach? (New) performance budgets WBS users inputs documentactivityWBS name WBS 3.1.2

NGAO sequences definitions document OCR document: Observing scenarios Planning User Observatory Observing User Observatory Post-observing Uses cases planning tools acquisition sequences calibrations sequences observing sequences Observing support and technical operations operation procedures WBS 3.2 WBS 3.4.4: WBS 3.1.2: Science observing planning and execution MCS sequences WBS WBS WBS User Interfaces WBS WBS WBS documentactivityWBS name Where should we document the sequence definitions? What is the difference between OCR and the NGAO SDD?

NGAO sequences definitions document OCR document: Observing scenarios Planning User Observatory Observing User Observatory Post-observing Uses cases planning tools acquisition sequences calibrations sequences observing sequences Observing support and technical operations operation procedures WBS 3.2 WBS 3.4.4: MCS sequences WBS WBS WBS User Interfaces WBS WBS WBS NGAO software architecture document WBS External ICD WBS 3.5 Internal ICD WBS 3.6 ?? documentactivityWBS name

NGAO sequences definitions document WBS 3.4.4: MCS sequences WBS WBS WBS User Interfaces WBS WBS WBS NGAO software architecture document WBS External ICD WBS 3.5 Internal ICD WBS 3.6 documentactivityWBS name MCS infrastructure document WBS 6.1.1: UI infrastructure document WBS 6.2.1: Data server infrastructure WBS 6.4.1: Should some of these be captured in the ICD?