Defining and tracking requirements for New Communities Fernando Aguilar aguilarf@ifca.unican.es

Introduction - Objectives Requirements gathering: Clients need to express what they really want. Designers must link the real requirements with the solutions. Importance of the “man in the middle”. Developers need to understand and address the problems correctly.

Introduction - Objectives We have a complete set of services and resources (INDIGO – EGI). We have people that knows those solutions. We have Research Communities with problems and requirements to solve them. We have people that understand those problems. Let’s make some bridges! Understand Community Requirements Identify priorities in dev. Bridge communication gaps. RC Expert IT Expert

How we did in INDIGO? Requirement Collection Co-Design Interactions Researchers to describe Case Studies, User stories, group into common Requirements Understand how INDIGO services will match communities requirements Confirm with developers to address requirements in design Identify communities Champions Share activities inside INDIGO (with ICT people) Advanced research activities (postdoc+ level) Different Technical/Scientific background/interest Using Tool for communication, i.e. OpenProject Record Case Studies, User Stories, Requirements Track INDIGO developments Communicate with ICT Co-Design Interactions Integration Testing Explore all INDIGO service components Help to prepare integration solutions Setup Testbeds: Realistic resources where demos can be built

INDIGO-DataCloud RIA-653549 INDIGO Architecture Enhanced features in IaaS PaaS SaaS 2nd release ElectricIndigo Data Center Solutions Data Solutions Automated Solutions High-level User Oriented Solutions AAI Services INDIGO-DataCloud RIA-653549 5

INDIGO-DataCloud Solutions for Earth Sciences Matching requirements – INDIGO components INDIGO-DataCloud Solutions for Earth Sciences

Configuration Database Training Infrastructure Federated Data Manager EGI Services Compute Storage Data Security Operations Training Design Phases Cloud Compute Data Transfer Configuration Database Discovery Online Storage Attribute Management FitSM Alpha Cloud ContainerCompute Content Distribution Service Monitoring Beta Archive Storage Training Infrastructure IdP Proxy High Throughput Compute Federated Data Manager Production Helpdesk Retired Data Hub

What we need? Description Problem workflow Community: understand how you work, roles, technical skills. Case study: your goals, objectives, what you expect. Problem workflow Different components needed by the system. User interaction. Different steps. Requirements for every step. Interaction with other systems. Interaction between components.

What we need? User Stories Data Requirements Shows what user expect exactly from the system. Try to be as “atomic” as possible. Data Requirements Type of data Size How do you use your data Help us to understand how you manage and what solutions you need.

Architecture Do you have any previous architecture? How your problem can be matched with INDIGO solutions? We will try to find out which INDIGO groups can help you. Let’s see the next example

Architecture

Thank you! Fernando Aguilar aguilarf@ifca.unican.es