Presentation is loading. Please wait.

Presentation is loading. Please wait.

Introductory notes AGENDA 1)Science requirements – Stefano 2)System requirements – Andrea 3)Software requirements/Science cases - Joe/Gino/All 1)Scheduling.

Similar presentations


Presentation on theme: "Introductory notes AGENDA 1)Science requirements – Stefano 2)System requirements – Andrea 3)Software requirements/Science cases - Joe/Gino/All 1)Scheduling."— Presentation transcript:

1 Introductory notes AGENDA 1)Science requirements – Stefano 2)System requirements – Andrea 3)Software requirements/Science cases - Joe/Gino/All 1)Scheduling or Observation preparation 2)ASTRI operations (Execution of the observations) 1)Telescope 2)Camera (calibration, control and DAQ) 3)Environmental/Sky monitoring 4)Safety and Alarm management 5)Archiving (Scientific, Environmental and Engineering Data) 6)Data processing (Quick-look Analysis, Science Tools) 4)Software management plan Joe/Gino/All 5) Development Infrastructure (Dino/Joe?) 6) Next Face-to-Face meeting (When, Where?) GOALS of the meeting: 1.Start to form the ASTRI/Mini-Array Software Team 2.Start to discuss the Software development methodologies and management plan 3.Start to discuss the Development management tools

2 The coffee machine analogy Insert coins Select a coffee flavor, size, sugar ( After a reading of the Machine User Manual) Receive coffee Machine: Prepare coffee User Receive ERROR User

3 The coffee machine analogy Why, What, When, How to observe Receive Data Receive NO DATA User Eventually, User Publish results Mini-Array: Take decisions perform observation get/save data Analyze Data (After a reading of the Instrument Data Analysis Manual) User (After a reading of the Instrument technical handbook)

4 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.

5 Software Development Methodology Useful if the User requirements will not change during the course of the project. Waterfall Methodology

6 Software Development Methodology This iterative development is lighter and more user-centric than 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)

7 Stefano & Andrea talks

8 Software Development Methodology Another view of the iterative development Methodology

9 How to start 1.Narrative description of the problem 2.Analysis of the text 3.Use Cases

10 Use Cases: Request to observe

11 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

12 MACS TCS Camera OCS Envirom ent/Sky/ Time DB Science tools User ASTRI/MACS - CoreTeam EGSE Infrastru cture/N etworki ng System Engineer

13 ASTRI Prototype System Architecture

14 ACS Control-CORBA(ACE/TAO) Data -DDS? Mount Telescope Control System Hardware OPC/UA ACM OPC/UA M2 OPC/UA Observatory Control System Environment/Sk y Monitoring Time Services GUI Instrument Control System Hardware Camera Lid Data Storage Interlocks/ Safety EGSE Solo un esempio Science Analysis


Download ppt "Introductory notes AGENDA 1)Science requirements – Stefano 2)System requirements – Andrea 3)Software requirements/Science cases - Joe/Gino/All 1)Scheduling."

Similar presentations


Ads by Google