Requirements Capture and Specification IACT424/924 Corporate Network Design and Implementation.

Slides:



Advertisements
Similar presentations
M A Wajid Tanveer Infrastructure M A Wajid Tanveer
Advertisements

Cisco 3 - Switches Perrine - Brierley Page 15/10/2015 Module 5 Switches LAN Design LAN Switches.
Network Design and Implementation
High Speed Networks and Internets : Multimedia Transportation and Quality of Service Meejeong Lee.
Design Requirements IACT424/924 Corporate Network Design and Implementation.
Top-Down Network Design Chapter Four Characterizing Network Traffic Copyright 2010 Cisco Press & Priscilla Oppenheimer.
Top-Down Network Design Chapter Four Characterizing Network Traffic Copyright 2010 Cisco Press & Priscilla Oppenheimer.
Network Management Functions
Chapter 21 Successfully Implementing The Information System
Chapter 19: Network Management Business Data Communications, 4e.
Network Management Overview IACT 918 July 2004 Gene Awyzio SITACS University of Wollongong.
© 2005 Prentice Hall7-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
Revision IACT 418 IACT 918 Corporate Network Planning.
Documenting the Existing Network - Starting Points IACT 418 IACT 918 Corporate Network Planning.
LYU9802 Quality of Service in Wired/Wireless Communication Networks: Techniques and Evaluation Supervisor: Dr. Michael R. Lyu Marker: Dr. W.K. Kan Wan.
1 K. Salah Module 1.1: Introduction (cont.) Business Goals and Constraints Analyzing Technical Goals.
Semester 4 - Chapter 3 – WAN Design Routers within WANs are connection points of a network. Routers determine the most appropriate route or path through.
Network Design and Implementation IACT 418/918 Autumn 2005 Gene Awyzio SITACS University of Wollongong.
Architectural Design Establishing the overall structure of a software system Objectives To introduce architectural design and to discuss its importance.
Performance Management (Best Practices) REF: Document ID
 The Open Systems Interconnection model (OSI model) is a product of the Open Systems Interconnection effort at the International Organization for Standardization.
Data Centers and IP PBXs LAN Structures Private Clouds IP PBX Architecture IP PBX Hosting.
 Network Management  Network Administrators Jobs  Reasons for using Network Management Systems  Analysing Network Data  Points that must be taken.
Lecture slides prepared for “Business Data Communications”, 7/e, by William Stallings and Tom Case, Chapter 8 “TCP/IP”.
THE OSI REFERENCE MODEL LES M C LELLAN DEAN WHITTAKER SANDY WORKMAN.
OSI LAYERS(OPEN SYSTEMS INTERCONNECTION ) Betül ŞAHİN
Computer System Lifecycle Chapter 1. Introduction Computer System users, administrators, and designers are all interested in performance evaluation. Whether.
“ Does Cloud Computing Offer a Viable Option for the Control of Statistical Data: How Safe Are Clouds” Federal Committee for Statistical Methodology (FCSM)
Section 11.1 Identify customer requirements Recommend appropriate network topologies Gather data about existing equipment and software Section 11.2 Demonstrate.
The generation, storage, and movement of information are central to managing an enterprise’s business processes As a result, businesses must ensure.
1 WHY NEED NETWORKING? - Access to remote information - Person-to-person communication - Cooperative work online - Resource sharing.
© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Communicating over the Network Network Fundamentals – Chapter 2.
© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public ITE PC v4.0 Chapter 1 1 Connecting to the Network Networking for Home and Small Businesses.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Identifying Application Impacts on Network Design Designing and Supporting Computer.
CIS Network Analysis and Design
THE OSI REFERENCE MODEL Open Systems Interconnection (OSI) International Organization for Standardization( ISO)
Module 10: Monitoring ISA Server Overview Monitoring Overview Configuring Alerts Configuring Session Monitoring Configuring Logging Configuring.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Gathering Network Requirements Designing and Supporting Computer Networks – Chapter.
Unit – I CLIENT / SERVER ARCHITECTURE. Unit Structure  Evolution of Client/Server Architecture  Client/Server Model  Characteristics of Client/Server.
NETWORKING COMPONENTS AN OVERVIEW OF COMMONLY USED HARDWARE Christopher Johnson LTEC 4550.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco PublicITE I Chapter 6 1 Identifying Application Impacts on Network Design Designing and Supporting.
Networking & the Internet. 2 What is a Network? □ A computer network allows computers to communicate with many other computers and to share resources.
1 Version 3.1 Module 1 WANs and Routers. 2 Version 3.1 WANS WAN operates at the physical layer and the data link layer of the OSI reference model. Provide.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Introducing Network Design Concepts Designing and Supporting Computer Networks.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Gathering Network Requirements Designing and Supporting Computer Networks – Chapter.
Cisco 3 - Switch Perrine. J Page 111/6/2015 Chapter 5 At which layer of the 3-layer design component would users with common interests be grouped? 1.Access.
9 Systems Analysis and Design in a Changing World, Fourth Edition.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco PublicITE I Chapter 6 1 Introducing Network Design Concepts Designing and Supporting Computer Networks.
1 © 2003, Cisco Systems, Inc. All rights reserved. CCNA 3 v3.0 Module 8 Virtual LANs Cisco Networking Academy.
Cisco 3 - Switches Perrine - Brierley Page 112/1/2015 Module 5 Switches.
Network design Topic 4 LAN design. Agenda Modular design Hierarchal model Campus network design Design considerations Switch features.
Network design Topic 6 Testing and documentation.
. Large internetworks can consist of the following three distinct components:  Campus networks, which consist of locally connected users in a building.
Network design Topic 2 Existing network infrastructure.
Advanced Computer Networks Lecturer: E EE Eng. Ahmed Hemaid Office: I 114.
Architecture & Cybersecurity – Module 3 ELO-100Identify the features of virtualization. (Figure 3) ELO-060Identify the different components of a cloud.
Chapter 12 The Network Development Life Cycle
Top-Down Network Design Chapter Four Characterizing Network Traffic Copyright 2004 Cisco Press & Priscilla Oppenheimer.
1 Transport Layer: Basics Outline Intro to transport UDP Congestion control basics.
Network Requirements Analysis CPIT 375 Data Network Designing and Evaluation.
Thepul Ginige Lecture-5 Implementation of Information System Part - I Thepul Ginige.
ITEC 275 Computer Networks – Switching, Routing, and WANs Week 12 Chapter 14 Robert D’Andrea Some slides provide by Priscilla Oppenheimer and used with.
Data Network Design and Evaluation Dr Usman Saeed Assistant Professor Faculty of Computing and Information Technology North Jeddah Branch King Abdulaziz.
Chapter 27 Network Management Copyright © The McGraw-Hill Companies, Inc. Permission required for reproduction or display.
Chapter 19: Network Management
Semester 4 - Chapter 3 – WAN Design
Network Management Functions
IS3120 Network Communications Infrastructure
Lecture-5 Implementation of Information System Part - I Thepul Ginige
Requirements Definition
Presentation transcript:

Requirements Capture and Specification IACT424/924 Corporate Network Design and Implementation

Overview Network Services Requirements Analysis Network Requirements User Requirements Application Requirements Host Requirements Determining New Customer Requirements

Definition Requirement That which is required or needed; a want, need That which is called for or demanded; a condition which must be complied with.

Network Services Sets of network capabilities that can be configured and managed within the network Levels of performance and function offered Sets of requirements expected For services to be useful and effective they need to be provisioned end-to-end

Network Services Services need to be Configurable Measurable Verifiable Ensure end users are getting the services they what they requested Accounting

Network Services Services are generally hierarchical General services in the backbone Specific services close to users Network services are derived from the requirements of all entities within the network They describe what is expected by/from each entity

Network Services Network service requirements include User requirements Application requirements Host requirements Network requirements

Network Services Service offerings need to be configured end-to-end Requirements add to each other filtering from user to network In addition to providing performance and function to users they support design and operation of the network

Network Services Mismatches in services can result in network bottlenecks Ethernet FW T1 1.5 Mb/s 200 kb/s 10 Mb/s

Requirements Analysis The identification of bottlenecks like this is one of the primary goals of network design After identifying service requirements the next stage is to quantify what we want from the network To do this we need to analyse and define the requirements of the network

Requirements Analysis Without adequate requirement analysis networks tend to be designed on factors other than users needs Requirement analysis assists in understanding the probable behaviour of the network

Requirements Analysis Payoffs include Objective, informed choices of technologies and services Match of interconnection strategies to networks Networks and components that are properly sized to users and applications Better understanding of of where and how to apply services in the network

Network Requirements Network designers have traditionally focused on providing connectivity between hosts Typically users and applications were not considered Host Network

Network Requirements This view is not complete enough for today’s networks Users and applications need to be considered User Application Host Network User Application Host

User Requirements Users generally have the following requirements Timeliness Interactivity Reliability Quality Adaptability Security Affordability

User Requirements We also need to know how many users are expected to use the system and their locations

Application Requirements Whilst many applications are still ‘best-effort’ users requirements and performance requirements (delay, capacity, reliability) are now being emphasized These requirements lead to a distinction between application that need specific service levels and those that don’t Descriptions of performance requirements for applications will separate specified services from best effort

Types of Specified Service applications Mission Critical Specified reliability Controlled-Rate Specified capacity Real-Time Specified delay

User vs Application Requirements User Service Requirement Timeliness Interactivity Reliability Quality Adaptability Security Affordability User numbers User locations Expected growth Performance Requirement Delay Reliability Capacity

Host Requirements Types of hosts and equipment Generic computing devices Desktop PC’s Interface between application and network Servers Provide service to one or more users Impact on information flow Specialised equipment Supercomputers, mainframe, data gathering equipment Location Dependant

Host Requirements Performance characteristics include Storage performance Processor performance Memory performance (access times) Bus performance

Determining New Customer Requirements Identify business constraints Identify security requirements Identify manageability requirements Determine application requirements Characterise new network traffic Identify performance requirements Create a customer needs specification document

Determining New Customer Requirements Identify business constraints Document budget and available resources Document project timeline Identify staffing requirements such as training or hiring

Determining New Customer Requirements Identify security requirements Appraise security risks and determine how much security will be needed and of what type Determine requirements for for outsiders to access data Determine the authorisation and authentication requirements for Corporate branch offices Mobile users Telecommuters

Determining New Customer Requirements Identify security requirements Identify requirements for authenticating routes received from access routers or other routers Identify requirements for host security Physical security of hosts User accounts Dated software Access rights on data

Determining New Customer Requirements Identify manageability requirements Fault Accounting Configuration Performance Security

Determining New Customer Requirements Determine application requirements Document names and types of new applications Document names and types of new protocols Document the number of users who will be using new applications and protocols Diagram the flow of information when new applications are introduced Identify peak hours of usage for new applications

Determining New Customer Requirements Characterise new network traffic Characterise traffic load Characterise traffic behaviour including Broadcast/multicast behaviour Frame size(s) supported Windowing and Flow control Error recovery mechanisms

Characterising Traffic Loads and Behaviour Approximate sizes of “objects” transferred across networks Type of ObjectSize (MB) message0.01 Spreadsheet0.1 Document1 Still image10 Multimedia Object 100 Database1000

Determining New Customer Requirements Identify performance requirements Response time Accuracy Availability Maximum network utilisation Throughput Efficiency Latency

Determining New Customer Requirements Create a customer needs specification document Record The customers requirements and constraints Characteristics of the existing network

References Teare, D. 1999, Designing Cisco Networks, Cisco Press Indianapolis McCabe, J. 1998, Practical Computer Network Analysis and Design, Morgan Kaufman, San Francisco