introductory notes agenda 1)science requirements – stefano 2)system requirements – andrea...

Introductory notes

AGENDA1) Science requirements – Stefano2) System requirements – Andrea3) 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 management5) Archiving (Scientific, Environmental and Engineering

Data) 6) Data processing (Quick-look Analysis, Science Tools)

4) Software management plan Joe/Gino/All5) 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 Team2. Start to discuss the Software development

methodologies and management plan3. Start to discuss the Development management

tools

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

User

The coffee machine analogy

Why, What, When, How to observe

Receive Data

Receive NO DATA

User

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

User

(After a reading of the Instrument technical handbook)

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

Useful if the User requirements will not change during the course of the project.

Waterfall Methodology

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)

Stefano & Andrea talks

Software Development Methodology

Another view of the iterative development Methodology

How to start1. Narrative description of the problem2. Analysis of the text3. Use Cases

Use Cases: Request to observe

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

MACS

TCS

Camera

OCS

Enviroment/Sky/Time

DB

Science tools

User

ASTRI/MACS - CoreTeam

EGSEInfrastru

cture/Network

ing

System Engineer

ASTRI Prototype System Architecture

ACS

Control-CORBA(ACE/TAO)Data -DDS?

Mount

Telescope Control SystemHardware

OPC

/UA

ACM

OPC

/UA

M2

OPC

/UA

Observatory Control System

Environment/Sky Monitoring Time ServicesGUI

Instrument Control SystemHardware

Camera Lid

Data Storage

Interlocks/Safety

EGSE

Solo un esempio

Science Analysis