Software Organisation

Do we need a software process?

• T/DAQ reorganisation will create an Online Software group, with overall responsibility for all online software including coordination of subdetector software
• The Backend DAQ will become an Open Source project with a model for collaborative software development
• One person responsible for each identified component
• Typical components might be the run controller for a subdetector or perhaps the database schema for the subdetectors data, etc
• Software process: requirements and high level design, detailed design, coding, test strategy, user guide. Produce deliverables, then iterate and refine
• Coding conventions? Not much in DAQ -1: some inconsistencies even within packages. But old ATLAS software process defined conventions. Some uniformity seems desirable