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

Slides:



Advertisements
Similar presentations
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Advertisements

Software Development Methodologies 1. A methodology is: A collection of procedures, techniques, principles, and tools that help developers build a computer.
CS 325: Software Engineering January 13, 2015 Introduction Defining Software Engineering SWE vs. CS Software Life-Cycle Software Processes Waterfall Process.
CS3500 Software Engineering Legacy Systems (1) Legacy systems are software (and sometimes hardware) systems that have been developed sometime in the past.
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
Sixth Hour Lecture 10:30 – 11:20 am, September 9 Framework for a Software Management Process – Artifacts of the Process (Part II, Chapter 6 of Royce’ book)
1 CS 501 Spring 2003 CS 501: Software Engineering Lecture 2 Software Processes.
Slide 1 Systems Analysis & Design CS183 Spring Semester 2008 Dr. Jonathan Y. Clark Course Website:
OO Development Process. UML and Process UML standardizes notation, not process –Increase likelihood of widespread acceptance There is significant variability.
Technical Specification / Schedule Department of Computer Science and Engineering Michigan State University Spring 2007 Team : CSE 498, Collaborative Design.
Workshop 1 Methodology 13 January Introduction Method can be defined as a systematic and orderly procedure or process for attaining some objective.
IS 421 Information Systems Management James Nowotarski 16 September 2002.
CS 501: Software Engineering
Chapter 1 The Systems Development Environment
CS 501: Software Engineering
Design Process …and the project.
The Systems Development Environment. Learning Objectives Define information systems analysis and design. Describe the different types of information systems.
CPTE 209 Software Engineering Summary and Review.
Hunt for Molecules, Paris, 2005-Sep-20 Software Development for ALMA Robert LUCAS IRAM Grenoble France.
Tietojärjestelmien peruskurssi Systeemisuunnittelu ja prototyyppimenetelmä Malin Brännback.
Business Driven Technology Unit 5 Transforming Organizations McGraw-Hill/Irwin Copyright © 2013 by The McGraw-Hill Companies, Inc. All rights reserved.
Managing the development and purchase of information systems (Part 1)
© Blackboard, Inc. All rights reserved. Back to the Feature: An Agile, User-centric Software Development Lifecycle Cindy Barry Senior Product Manager Martha.
Twelfth Lecture Hour 10:30 – 11:20 am, Saturday, September 15 Software Management Disciplines Project Organization and Responsibilities (from Part III,
A Development Process Lecture Oo13 Objectory based method.
CAA/CFA Review | Andrea Laruelo | ESTEC | May CFA Development Status CAA/CFA Review ESTEC, May 19 th 2011 European Space AgencyAndrea Laruelo.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Developing Use Cases in a Group Carolyn L. Cukierman Face-to-Face Technology Conference March 27, 2000.
Systems Development AIMS 2710 R. Nakatsu. Overview Why do IT projects succeed and fail? Two philosophies of systems development –Systems Development Life.
Software Engineering Management Lecture 1 The Software Process.
The ALMA Software and Release Management Ruben Soto Software Operations Group & Release Manager Joint ALMA Observatory.
SOFTWARE ENGINEERING MCS-2 LECTURE # 4. PROTOTYPING PROCESS MODEL  A prototype is an early sample, model or release of a product built to test a concept.
Looking Ahead with Blue Mountain RAM Jim Erickson, President Randy Paroda, Director of Product Development September 18, 2013.
Teaching Systems Analysis and Design in a Practical Way: A Collaborative Effort Between Computer Science and Business School by Ken Surendran-CS Chellappa.
Decision Support Systems Development
1 CS 501 Spring 2004 CS 501: Software Engineering Lecture 2 Software Processes.
Chapter 11 Managing Application Development. Agenda Application management framework Application management issues Criteria for development approach Development.
Chapter 8 Workflows of the Process Taken from Walker Royce’s textbook – Software Project Management plus a number of Personal Comments.
1 Software Engineering: A Practitioner’s Approach, 7/e Chapter 2 Process: A Generic View Software Engineering: A Practitioner’s Approach, 7/e Chapter 2.
The principles of an object oriented software development process Week 04 1.
1 Proposal and Observation Handling Ravi Sankrit (User Support Scientist) SSSC May 11, 2011.
Stand Up Comedy Project/Product Management
XXX, Inc. 1 Technical Capabilities  Requirements Engineering  Analysis and Design  Implementation  Quality Assurance  Project Life Cycle  Requirements.
Software Testing Process
Meghe Group of Institutions Department for Technology Enhanced Learning 1.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Design and implementation Chapter 7 – Lecture 1. Design and implementation Software design and implementation is the stage in the software engineering.
Copyright © Curt Hill Software Development Methodology What do you need to know?
Chapter 1: Introduction to Systems Development Systems concepts The information systems infrastructure Top-down information systems development Methodologies.
Software Engineering cosc 4359 Spring 2017.
Introduction To System Analysis and Design
Software Development.
Introduction to Systems Analysis and Design
Software Engineering Management
Applied Operating System Concepts
Fundamentals of Information Systems, Sixth Edition
Observatory Control System
I&T&C Organization Chart
Design and Implementation
Project Management and the Agile Manifesto
Object Oriented Analysis and Design
Introduction To System Analysis and Design PART 2
Software engineering -1
Observatory Control System
Software Development Life Cycle Models
Project Lifecycle and IT Product Life Cycle
What is Software Engineering?
Our Process CMSC 345, Version 1/04.
Presentation transcript:

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

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

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)

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 start 1.Narrative description of the problem 2.Analysis of the text 3.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 Envirom ent/Sky/ Time DB Science tools User ASTRI/MACS - CoreTeam EGSE Infrastru cture/N etworki ng System Engineer

ASTRI Prototype System Architecture

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