140 likes | 279 Views
GOALS of the meeting: Start to form the ASTRI/Mini-Array Software Team Start to discuss the Software development methodologies and management plan Start to discuss the Development management tools . Introductory notes. AGENDA Science requirements – Stefano System requirements – Andrea
E N D
GOALS of the meeting: Start to form the ASTRI/Mini-Array Software Team Start to discuss the Software development methodologies and management plan Start to discuss the Development management tools Introductory notes • AGENDA • Science requirements – Stefano • System requirements – Andrea • Software requirements/Science cases - Joe/Gino/All • Scheduling or Observation preparation • ASTRI operations (Execution of the observations) • Telescope • Camera (calibration, control and DAQ) • Environmental/Sky monitoring • Safety and Alarm management • Archiving (Scientific, Environmental and Engineering Data) • Data processing (Quick-look Analysis, Science Tools) • Software management plan Joe/Gino/All • 5) Development Infrastructure (Dino/Joe?) • 6) Next Face-to-Face meeting (When, Where?)
The coffee machine analogy Machine: Prepare coffee User Receive ERROR Insert coins Select a coffee flavor, size, sugar (After a reading of the Machine User Manual) User Receive coffee User
The coffee machine analogy User Receive NO DATA Why, What, When, How to observe (After a reading of the Instrument technical handbook) User User Mini-Array: Take decisions perform observation get/save data Receive Data User Analyze Data (After a reading of the Instrument Data Analysis Manual) Eventually, User Publish results
Mini-Array Control System development Science Team (User) Hardware team Software team Regular Interaction among Science, Hardware and Software teams essential to develop the system because we are operating in a “time-to-market” way.
Software Development Methodology Waterfall Methodology Useful if the User requirements will not change during the course of the project.
Software Development Methodology This iterative development is lighter and more user-centricthan traditional approaches. Agile processes use feedback, rather than planning, as their primary control mechanism. The feedback (by users) is driven by regular tests and releases of the evolving software. This approach could be more appropriate for the Mini-Array (as suggested by Joe)
Software Development Methodology Another view of the iterative development Methodology
How to start • Narrative description of the problem • Analysis of the text • Use Cases
Some consequences of the AGILE approach • In the earlier phase of the project we have to start to select: • Hardware and software (OS, development tools, framework, etc) • Also important is to start: • Database design
ASTRI/MACS - CoreTeam System Engineer DB TCS Science tools Camera MACS User OCS Enviroment/Sky/Time EGSE Infrastructure/Networking
Telescope Control System Instrument Control System Hardware Hardware OPC/UA OPC/UA OPC/UA Lid Mount ACM M2 Camera Interlocks/Safety ACS Data Storage Data -DDS? Control-CORBA(ACE/TAO) EGSE Science Analysis GUI Observatory Control System Environment/Sky Monitoring Time Services Solo un esempio