70 likes | 180 Views
ALMA Integrated Computing Team Coordination & Planning Meeting #3 Socorro, 17-19 June 2014. New AM organization and improving the acceptance procedure Masao Saito (JAO AM) Daniel Espada (JAO Interim Deputy AM). Acceptance Management Organization. 2013.12 – 2014.4 AM: Masao Saito
E N D
ALMA Integrated Computing TeamCoordination & Planning Meeting #3 Socorro, 17-19 June 2014 New AM organization and improving the acceptance procedure Masao Saito (JAO AM) Daniel Espada (JAO Interim Deputy AM)
Acceptance Management Organization • 2013.12 – 2014.4 • AM: Masao Saito • Deputy AM: Itziar de Gregorio • 2014.5 – 2014.6 • AM: Masao Saito • Interim Deputy AM: Daniel Espada • 2014.7 – 2014.8 • Interim AM: Daniel Espada
Acceptance Since CPM#2 • Cycle 2 started on time thanks to all of you!! • Acceptance Procedure is established. • TRR/ACRV held on Friday 11 am (CLT)
Improvement Efforts since CPM#2 • Integrated Acceptance Calendar: Our Foundation • Schedule, Scope is clearer than before. • Better requirements deadline is given • BUT, IT IS NOT EASY TO UNDERSTAND AT A FIRST LOOK • Acceptance wiki: Focal point of each acceptance • Better organized, documents, structures etc. • SSG wiki: • Clear responsibility for each subsystem scientist in each subsystem • AM-RM meeting/regular contact • Less miscommunication between ICT and JAO science • SEQM meeting • Better quality control for the overall process
New things in the acceptance after CPM#2 • Robust process • After TRR, the software is tested internally before going public. After ACRV, the software goes public (e.g. source catalogue) • ARC deployment • Invite ARC contacts to TRR to share deployment info. • Kanban • Very successful to track status of ICT-tickets. • Pipeline Heuristics (originally not in the JAO acceptance) • AM accepts the software with SciOPS approval • New Subsystem • Dashboard (Stuartt), Integrated Reporting (Lars)
Acceptance Status • Bugs are well followed in Kanban if labeled correctly.
Remaining Issues • Too many PRTSIR tickets assigned to software • New procedure is underway • Science Portal Requirement • ToO triger etc. needed every cycle start. • Pipeline infrastructure • Pipeline developer team proposed a reasonable procedure. • ARC deployment • Detailed Procedure is needed. Separate discussion.