Backend System Requirements

Slides:



Advertisements
Similar presentations
This Area Will Not Be Seen Alliance Access Alliance Access.
Advertisements

T.Sharon-A.Frank 1 Multimedia Quality of Service (QoS)
EE 4272Spring, 2003 Protocols & Architecture A Protocol Architecture is the layered structure of hardware & software that supports the exchange of data.
1 Simulation Modeling and Analysis Verification and Validation.
16: Distributed Systems1 DISTRIBUTED SYSTEM STRUCTURES NETWORK OPERATING SYSTEMS The users are aware of the physical structure of the network. Each site.
Implementation/Acceptance Testing / 1 Implementation and Acceptance Testing Physical Implementation Criteria: 1. Data availability 2. Data reliability.
Error Checking continued. Network Layers in Action Each layer in the OSI Model will add header information that pertains to that specific protocol. On.
©2008 Pearson Prentice Hall Project Management Systems Analysis and Design, 7e Kendall & Kendall CH#3.
Department of Electronic Engineering City University of Hong Kong EE3900 Computer Networks Introduction Slide 1 A Communications Model Source: generates.
14-15 May,2002 EVLA Correlator Backend Functional Design Tom Morgan 1 Backend Preliminary Functional Design.
Systems Development Lifecycle Testing and Documentation.
Overall Data Processing Architecture Review EVLA Monitor and Control Interfaces July , 2002EVLA Data Processing PDR Bill Sahr.
1 Network Layer Lecture 13 Imran Ahmed University of Management & Technology.
CERN – European Organization for Nuclear Research Administrative Support - Internet Development Services CET and the quest for optimal implementation and.
14 June, 2004 EVLA Overall Design Subsystems II Tom Morgan 1 EVLA Overall Software Design Final Internal Review Subsystems II by Tom Morgan.
CSC 600 Internetworking with TCP/IP Unit 5: IP, IP Routing, and ICMP (ch. 7, ch. 8, ch. 9, ch. 10) Dr. Cheer-Sun Yang Spring 2001.
18-19 July, 2002Correlator Backend System OverviewTom Morgan 1 Correlator Backend System Overview Tom Morgan, NRAO.
TCP OVER ADHOC NETWORK. TCP Basics TCP (Transmission Control Protocol) was designed to provide reliable end-to-end delivery of data over unreliable networks.
Protocol Layering Chapter 11.
Chapter 12 The Network Development Life Cycle
Virtual Circuit Networks Frame Relays. Background Frame Relay is a Virtual Circuit WAN that was designed in late 80s and early 90s. Prior to Frame Relays.
Tackling I/O Issues 1 David Race 16 March 2010.
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
LonWorks Introduction Hwayoung Chae.
CCNA 2 Router and Routing Basics Module 8 TCP/IP Suite Error and Control Messages.
CS509 Computer Networks Lecture 1 Dr. Nermin Hamza.
System SOFTWARE.
AMHS (ATS Message Handling System)
Chapter 19: Network Management
Deterministic Communication with SpaceWire
Software Overview Sonja Vrcic
Software Specification and Configuration Management
Non Functional Requirements (NFRs)
CS408/533 Computer Networks Text: William Stallings Data and Computer Communications, 6th edition Chapter 1 - Introduction.
THE OSI MODEL By: Omari Dasent.
DSS Front End Software Review
Advanced Computer Networks
Transport layer.
ISO/OSI Model and Collision Domain
Layered Architectures
Telemedicine.
Understand the OSI Model Part 2
CT1303 LAN Rehab AlFallaj.
Internet Protocol: Connectionless Datagram Delivery
Chapter 13 & 14 Software Testing Strategies and Techniques
Working of Script integrated with SiteScope
Real-time Software Design
Capability reporting Francesco Schillirò INAF- OACT
18-WAN Technologies and Dynamic routing
TASK 4 Guideline.
Correlator – Backend System Overview
Transport Layer Unit 5.
Architecture of Parallel Computers CSC / ECE 506 Summer 2006 Scalable Programming Models Lecture 11 6/19/2006 Dr Steve Hunter.
Chapter 3: Open Systems Interconnection (OSI) Model
VCI Overview Sonja Vrcic
Software Development Process
Distributed Systems Bina Ramamurthy 11/30/2018 B.Ramamurthy.
ECE 544 Project3 Team member: BIAO LI, BO QU, XIAO ZHANG 1 1.
OSI Model The Seven Layers
Training Module Introduction to the TB9100/P25 CG/P25 TAG Customer Service Software (CSS) Describes Release 3.95 for Trunked TB9100 and P25 TAG Release.
Net 323 D: Networks Protocols
Software System Testing
Types of Specification
Distributed Systems Bina Ramamurthy 4/22/2019 B.Ramamurthy.
Requirements Definition
Chapter-5 Traffic Engineering.
OSI Reference Model Unit II
OSI Model 7 Layers 7. Application Layer 6. Presentation Layer
Error Checking continued
Presentation transcript:

Backend System Requirements System Requirements Specification EVLA Correlator Backend Project Document A25251N0000 Revision 2.0 May 10, 2002 14-15 May, 2002 Backend System Requirements

Backend System Requirements Assumptions Correlator Handles Packetization of Lag Frames Lag Frames Will Not Necessarily Arrive in Lag Set Order Lag Frame Delivery a One-Time Shot Lag Set Length Always Power of 2 Timely Delivery of Indirect Data e2e Capable of Handling Output Rates and Volumes 14-15 May, 2002 Backend System Requirements

Backend System Requirements Constraints Critical Component in the Astronomical Data Path Operations Performed Shall be Reversible Performance Limits Set by Technology and Budget 14-15 May, 2002 Backend System Requirements

Backend System Requirements Input Data Lag Frames State Counts Data Valids Meta-data Observational Mode Data Processing Parameters Status Requests 14-15 May, 2002 Backend System Requirements

Backend System Requirements Output Data Formatted Observational Output Status Reports Error Reports Warning Reports Failure Reports Recovery Reports 14-15 May, 2002 Backend System Requirements

Backend System Requirements Correlator Interface Receive Lag Frame Data Packets All Backend Processors Have Paths to All Correlator Outputs Sufficient Bandwidth to Meet Performance Requirement All Frames For Same Baseline Routed to Same BE Processor 14-15 May, 2002 Backend System Requirements

Monitor & Control Interface Receive Non-Lag Frame Data Receive Status and Queries Send Query Responses and Internally Generated Messages 14-15 May, 2002 Backend System Requirements

Backend System Requirements End-to-End Interface Transfer Formatted Data All Backend Processors Have a Path to the e2e System Sufficient Bandwidth to Meet Performance Requirement 14-15 May, 2002 Backend System Requirements

Backend System Requirements Data Processing Lag Set Assembly Normalization Coarse Quantization Correction Time Stamp Adjustment Interference Removal/Reduction Windowing Fourier Transform Integration Output Formatting 14-15 May, 2002 Backend System Requirements

Internal Monitor and Control No User Interface of Its Own Respond to Outside Queries Selectable Internal Test Modes Self Monitoring Self Recovery Problem Reporting 14-15 May, 2002 Backend System Requirements

Backend System Requirements Performance Maximum Aggregate Input Rate of 1.6 Gbytes/sec Maximum Aggregate Output Rate of 25 Mbytes/sec 14-15 May, 2002 Backend System Requirements

Backend System Requirements Reliability Detect and Recover From Processor Failures Detect and Recover From Process Failures Detect and Recover From Internal Network Failures No Total System Reboots Between Maintenance Windows (Goal) 14-15 May, 2002 Backend System Requirements

Backend System Requirements Scalability Total System Extensible to Higher Rates of Input, Output, and Data Processing Hardware Extensible in a Manner That is Transparent to Software and Vice Versa Upgrades Meet Seamlessly With Unchanged Components 14-15 May, 2002 Backend System Requirements