EOSCpilot All Hands Meeting 8 March 2018 Pisa

Slides:



Advertisements
Similar presentations
Nov. 14, 2007 Systems Engineering ä System ä A set or arrangement of things so related as to form a unity or organic whole. ä A set of facts, principles,
Advertisements

Page 1, CBSE graduate course Component-Based Software Engineering Building reliable component-based systems Assignments for the CBSE group.
Roles and Responsibilities Jahangheer Shaik. Service Specification Specification requires development of three inter-related documents CIM, PIM and PSM.
Ron Kratzke, Vitech Corporation MBSE for System Testing Managing the development of system testing using the principles of Model.
Based on D. Galin, and R. Patton.  According to D. Galin  Software quality assurance is:  A systematic, planned set of actions necessary to provide.
BMAN Integrative Team Project Week 2 Professor Linda A Macaulay.
Lecture 7: Requirements Engineering
An Introduction to Software Engineering. Communication Systems.
 Before software can be engineered, the system must be understood.  The overall objective of the system must be determined, the role of the system elements.
CONTENTS OF THE SRS REPORT. Software Requirements Specification (SRS) template The SRS document describes recommended approaches for the specification.
Session 1 What Is the UML? Written by Thomas A. Pender Published by Wiley Publishing, Inc. October 5, 2011 Presented by Kang-Pyo Lee.
Getting Ready for the NOCTI test April 30, Study checklist #1 Analyze Programming Problems and Flowchart Solutions Study Checklist.
 System Requirement Specification and System Planning.
1 Week 3 Software Engineering Spring Term 2016 Marymount University School of Business Administration Professor Suydam.
Research & Innovation Preparatory Phase and Early Phase Support under the WP * of Horizon 2020 Harry Tuinder Research Infrastructure Unit DG Research,
Scope of Systems Requirements: Definition o f Requirements Not to define the full system Not to define the full system Describe or define the essential.
EGI Foundation (Session Chair)
overview of activities on High Performance Computing
Types and Characteristics of Requirements
ICT22 – 2016: Technologies for Learning and Skills ICT24 – 2016: Gaming and gamification Francesca Borrelli DG CONNECT, European Commission BRUXELLES.
EOSC Services for Scientists
Services for EOSC management
Panel discussion on Principles of Engagement
Classifications of Software Requirements
EOSC MODEL Pasquale Pagano CNR - ISTI
Chapter 4 – Requirements Engineering
School of Business Administration
Chapter 4 Requirements Engineering (1/3)
Chapter 4 – Requirements Engineering
Chapter 5 – Requirements Engineering
This project is co-funded by the European Union
EOSCpilot Service Pilots Face to Face with SDs and RPs
Defining EOSC Rules of Engagement Damien Lecarpentier (CSC)
Exploitation and Sustainability updates
Skills & Capabilities (EOSCPilot WP7) Interaction with RDA
ASSET - Automotive Software cyber SEcuriTy
Wrap-up & discussion EOSC Governance Development Forum workshop:
Online Shopping APP.
Project Overview and EOSC Governance
Systems Analysis and Design: What is it?
European Open Science Cloud All Hands Meeting Pisa 8-9 March 2018
EOSCpilot Skills Landscape & Framework
EOSC Governance Development Forum
The Design Process.
Software Requirements
WP2 Governance Per Öster
EOSCpilot All Hands Meeting 9 March 2018, Pisa
FP7 SCIENTIFIC NEGOTIATIONS Astrid Kaemena European Commission
WP5.2 Report & outlook Jan Bot, SURF
EOSCpilot All Hands Meeting 8 March 2018 Pisa
EOSCpilot All Hands Meeting 8 March 2018 Pisa
EOSCpilot All-hands meeting Pisa, March 8th-9th 2018
EOSC Overall Architecture Donatella Castelli CNR-ISTI
European Open Science Cloud All Hands Meeting Pisa 8-9 March 2018
6.2 data interoperability Rafael C Jimenez ELIXIR
Verification Concepts for SysmL v2
Skill gaps and planning for training pilots
European Open Science Cloud All Hands Meeting Pisa 8-9 March 2018
Brian Matthews STFC EOSCpilot Brian Matthews STFC
MANAGING THE DEVELOPMENT AND PURCHASE OF INFORMATION SYSTEMS
EOSCpilot All Hands Meeting, Pisa, 8-9 March, 2018
EOSCpilot All Hands Meeting 9 March 2018, Pisa
Requirements Document
Verification Concepts for SysmL v2
Subject Name: SOFTWARE ENGINEERING Subject Code:10IS51
How to make training materials discoverable
Skills Framework FAIR 4S DI4R18 Lisbon
UML  UML stands for Unified Modeling Language. It is a standard which is mainly used for creating object- oriented, meaningful documentation models for.
From Use Cases to Implementation
ACSC 155 System Analysis and Design 4. Systems Design
Presentation transcript:

EOSCpilot All Hands Meeting 8 March 2018 Pisa WP4 – Science Demonstrators Session on Functional and non-functional requirements

WP4 Science Demonstrators From DoA: Science Demonstrators will be used - to drive and prioritise the integration of the EOSC services - to meet the functional and non-functional needs of researchers - to ensure that the proposed technical governance structures provide the control needed by researchers. Together, these Science Demonstrators will help drive the development of the EOSC ecosystem and its associated infrastructure. www.eoscpilot.eu The European Open Science Cloud for Research pilot project is funded by the European Commission, DG Research & Innovation under contract no. 739563

Functional requirements (From Wikipedia) In Software engineering and systems engineering, a functional requirement defines a function of a system or its component. A function is described as a set of inputs, the behavior, and outputs. Functional requirements may be calculations, technical details, data manipulation and processing and other specific functionality that define what a system is supposed to accomplish.[1] Behavioral requirements describing all the cases where the system uses the functional requirements are captured in use cases. Functional requirements are supported by non-functional requirements (also known as quality requirements), which impose constraints www.eoscpilot.eu The European Open Science Cloud for Research pilot project is funded by the European Commission, DG Research & Innovation under contract no. 739563

Non-functional requirements (From Wikipedia) In systems engineering and requirements engineering, a non-functional requirement (NFR) is a requirement that specifies criteria that can be used to judge the operation of a system, rather than specific behaviors. …… Non-functional requirements are in the form of "system shall be <requirement>", an overall property of the system as a whole or of a particular aspect and not a specific function. …. Non-functional requirements are often called "quality attributes" of a system. Other terms for non-functional requirements are "qualities", "quality goals", "quality of service requirements", "constraints" and "non-behavioral requirements". … Qualities—that is non-functional requirements— …… www.eoscpilot.eu The European Open Science Cloud for Research pilot project is funded by the European Commission, DG Research & Innovation under contract no. 739563