TOSCA Technical Committee Kick-off December 12, 2011.

Slides:



Advertisements
Similar presentations
Mercury Quality Center 9.0 Training Material
Advertisements

Publication Module using back end interface. Institution Data Entry Add Documents. Edit/Delete Documents that are added but not yet sent to Institution.
Meeting Agenda Preparation and Negative Resolution Scott Orthey.
Michigan Electronic Grants System Plus
Connect Team Connect Team Outside Contrib Outside Contrib Unscheduled Backlog Bugs Feature Requests BA Review Requirement Docs Epic Large Tasks or Features.
TC Admin Open Mic Session Copyright © OASIS 2012 TC Administration Update Report to Members February 8 th / 9 th 2012.
PbD-SE Technical Committee First Meeting December 05, 2012.
OASIS OSLC CCM TC Inaugural Meeting 04 February /04/14OASIS Presentation to OSLC CCM TC.
Copyright © 2005, SAS Institute Inc. All rights reserved. SAS ABM Survey Kit A Sample Usage Scenario: Collecting Numeric Attribute Values.
EvalS Application User Guide version September 17, 2011.
Planning DITA 1.3 Kristen James Eberlein Eberlein Consulting.
1 PER for M Prototype December 14, PER for M Disclaimer.
JIRA Defect Tracking Tool Tool to Record, Track and Resolve Issues, Bugs, Defects, Improvements and New Feature Requests LIGO-G M.
Proposed TC Issues Process Martin Chapman. Purpose An issues driven process helps to 1.Untangle un-conflate problems 2.Narrow focus to solving particular.
OData Technical Committee Kick-off July 26, 2012.
RMsis – v Simplify Requirement Management for JIRA.
TOSCA Technical Committee Kick-off December 12, 2011.
Proposed TOSCA TC Timeline March 1, TC Deliverables Standards Track Work Products – “…is a Work Product produced and approved by a TC in accordance.
Information Management System “ Expert Profile Module" Information Management System “ Expert Profile Module" The Expert Profile module is an integrated.
Aid Management Platform (AMP) Advanced User Training, Module Entering Activities.
For internal use only 1© Nokia Siemens Networks R 255 G 211 B 8 R 255 G 175 B 0 R 127 G 16 B 162 R 163 G 166 B 173 R 137 G 146 B 155 R 175 G 0 B 51 R 52.
Information Management System “Good Practice Module" Information Management System “Good Practice Module" The Good Practice / Success Stories module is.
CMIS4DAM TC Inaugural Meeting 03 December /03/14OASIS Presentation to CMIS4DAM TC.
Management Software For Engineering Project Management
SCA TCs Proposed Issues Process Martin Chapman, Assembly Co-chair Anish Karmarkar, BPEL Co-chair Ashok Malhotra, Policy Co-chair Mike Edwards, Assembly.
Human Resources 1 G-Top Global Workflow Employee View September 2014.
Revised TOSCA TC Timeline Analysis and Candidate September 20, 2012.
Information Management System “Project Module" Information Management System “Project Module" The Project module is an integrated part of System. The back.
Aid Management Platform (AMP) Advanced User Training, Module 1F Entering Activities Tanzania, February 2009.
How to Submit a New Human Ethics Clinical Application.
RMsis – v now with JIRA 5.0 support Simplify Requirement Management for JIRA.
Introduction to Bugzilla. May 12, 2011 What is Bugzilla? Bugzilla is a defect- or issue-tracking system Allows individual or groups of developers effectively.
2012 MEGA eCIP PPT PART 2. Part IV Part V: Federal Requirements.
Note At the 2008/03/12 TC meeting the BPEL4People TC formally adopted the SCA TC issue process for issue resolution. The following slides document v3 of.
2012 TELPAS Online Testing & Data Collection. Disclaimer  These slides have been prepared by the Student Assessment Division of the Texas Education Agency.
Contents Major issue states and transitions Tools.
Legal Citation Markup TC Inaugural Meeting 12 February /12/14OASIS Presentation to LegalCiteM TC.
OASIS VIRTIO TC Inaugural Meeting 30 July /04/13 OASIS Presentation to PKCS 11 TC TC Process Overview TC Process is created by OASIS Board, carried.
Software Testing Lab 1.
Michigan Electronic Grants System Plus
OASIS OSLC CCM TC Inaugural Meeting 04 February 2014
OASIS TC Process Overview
Global Grid Forum GridForge
OCPP TC Inaugural Meeting 07 September 2016
Proposed TC Issues Process
OASIS eTMF TC Inaugural Meeting 16 December 2013
OASIS Overview TC Process
OASIS Overview TC Process
CSAF TC Inaugural Meeting 16 November 2016
SARIF TC Timeline Proposed, approximate.
FFM TC status Thinh Nguyenphu as FFM TC Chair NSN
OASIS OSLC Core TC Inaugural Meeting 12 November 2013
OASIS Overview TC Process & Administration
TC Process Specification Flow
ePerformance Chapter 1. Entering your Performance Notes Step 1 Step 2
OSLC Domains TC Inaugural Meeting 30 September 2016
FFM TC status Thinh Nguyenphu as FFM TC Chair NSN
ARIP TC Inaugural Meeting 22 May 2015
OASIS Overview TC Process
CTI TC Inaugural Meeting 18 June 2015
Legal Citation Markup TC Inaugural Meeting 12 February 2014
OSLC PROMCODE TC Inaugural Meeting 26 March 2014
WS-RX TC Process for Specification Development
WS-RX TC Process for Specification Development
IBOPS TC Inaugural Meeting 23 September 2014
OSLC Automation TC Inaugural Meeting 25 March 2014
COEL TC Inaugural Meeting 15 July 2015
BIOSERV TC Inaugural Meeting 08 July 2015
OASIS VIRTIO TC Inaugural Meeting 30 July 2013
Presentation transcript:

TOSCA Technical Committee Kick-off December 12, 2011

Goal Demonstrate OASIS JIRA installation Show best practices for managing development projects Give TC a place to start 12/12/2011OASIS Presentation to TOSCA TC2

What is JIRA? Issue-tracking system used for bug & issue tracking, project management, etc. Components: Projects – the overall collection of issues. At OASIS, we assign a project at the TC level (e.g. AMQP TC, Energy Interop TC) Issues – the individual atomic entries that the TC enters, tracks, resolves & eventually closes (e.g. ENERGYINTEROP-504, Add Reading Type as optional element in ei:Market) Versions – Identifiers for specific stages of your spec’s lifecycle (e.g. working draft (wd) 07, Committee Specification Draft 02) Components – Sub-sections of a project typically tied to its discrete parts (e.g. Schema, Specs, Models) Status / stages – Indicators of the progress in resolving the issue 12/12/2011OASIS Presentation to TOSCA TC3

What is JIRA? 12/12/2011OASIS Presentation to TOSCA TC4

Organizing Your Project OASIS creates your project at TC level E.g. OASIS Energy Interoperation TC, OASIS AMQP TC Within your project: Use Versions to organize issues by OASIS specification stage Use Components to organize issues the way you organize your specification 12/12/2011OASIS Presentation to TOSCA TC5

Organizing Your Project 12/12/2011OASIS Presentation to TOSCA TC6

How to Get Started Decide what you want to track Public review comments only? Issues raised in committee meetings? Define your terms JIRA status codes are: New, Open, Resolved, Applied, Closed, Deferred Decide what those will mean in your project Decide how you will assign / approve / close E.g. issues aren’t real until they are in JIRA E.g. issues are closed until approved in TC meetings 12/12/2011OASIS Presentation to TOSCA TC7

How to Get Started TC Admin sets up your project & users TC sets up versions and components Versions and components are defined by clicking the “Administer Project” link on the project main page TC members add issues and sub-tasks Issues are entered by clicking the “Create a new issue” link on the project main page Sub-tasks can be created during entry or by converting an issue that was initially entered 12/12/2011OASIS Presentation to TOSCA TC8

12/12/2011OASIS Presentation to TOSCA TC9