Www.forgentnetworks.com Proposed H.323 Forum Testing Program Support Sanjay Mishra – October 24, 2002.

Slides:



Advertisements
Similar presentations
CATIA V4 Software Deployment Project Proposal
Advertisements

ATC Conference Call January 10, 2008 Thank you for joining the call. We will start the call shortly. Please enter * 6 to mute your line and # 6 to unmute.
U.S. Pretrial Services and Probation Office Northern District of Ohio.
1 SOFTWARE TESTING Przygotował: Marcin Lubawski. 2 Testing Process AnalyseDesignMaintainBuildTestInstal Software testing strategies Verification Validation.
Discover ACP It's Easier than Ever to Hire Temp Labor.
[Insert Project Name] Detailed Design Review (DDR) [Insert Date of DDR] Centers for Medicare & Medicaid Services eXpedited Life Cycle (XLC)
Top-Down Network Design Chapter Fourteen Documenting Your Network Design Copyright 2010 Cisco Press & Priscilla Oppenheimer.
Executive Summary [Date] Background Initiate Review licensing report Introductory meeting Request for deployment information Research Discuss.
Project Bidding Procedures Enhancing Data and Presentation Skills for Engineers EDASPE Writing the RFP Training Courses – July 2004.
Network Design and Implementation
1 Human Resource Management Systems Chapter 6: HRMS Vendors Joseph Y-W. Deng
DoD Information Technology Security Certification and Accreditation Process (DITSCAP) Phase III – Validation Thomas Howard Chris Pierce.
Secure System Administration & Certification DITSCAP Manual (Chapter 6) Phase 4 Post Accreditation Stephen I. Khan Ted Chapman University of Tulsa Department.
8 Systems Analysis and Design in a Changing World, Fifth Edition.
DITSCAP Phase 2 - Verification Pramod Jampala Christopher Swenson.
CSE Senior Design II Test Planning Mike O’Dell Based on an earlier presentation by Mike O’Dell, UTA.
SDLC Phase 2: Selection Dania Bilal IS 582 Spring 2009.
SOFTWARE DEVELOPMENT DOCUMENTATION. INTRODUCTION Documentation can be tied into the entire software development cycle. Unfortunately, documentation is.
National Finance Center’s 2008 Customer Forum EmpowHR 9.0 Billy Dantagnan Teracore.
Documenting Network Design
Effective Methods for Software and Systems Integration
System Software Integration Testing Mars Polar Lander Steven Ford SYSM /05/12.
Web Development Process Description
Chapter 5 IS630. Project Plan 1.Introduction 2.Project Definition Overview 3.Changes Since Project Definition Was Approved 4.Staffing Plan 5.Development.
1 CAPACITY BUILDING AND TRAINING ON PROCUREMENT Session 9 – The World Bank Procedures for IT Procurement September 21, 2005 by Arif Hassan.
RUP Implementation and Testing
Web Trnsport – Beta Testing and Implementation TUG Roundtable Discussion Elizabeth Rodgers Info Tech, Inc. October 9, 2007.
Testing Web to Wireless …and Back March 2001 Presenter: Shirley DeLewis, CQA, CSTE, CPSA.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
ITEC 275 Computer Networks – Switching, Routing, and WANs Week 12 Chapter 14 Robert D’Andrea Some slides provide by Priscilla Oppenheimer and used with.
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Gathering Network Requirements Designing and Supporting Computer Networks – Chapter.
Software Engineering Management Lecture 1 The Software Process.
WebEx Cloud Connected Audio Enterprise
The Macro Design Process The Issues 1. Overview of IP Design 2. Key Features 3. Planning and Specification 4. Macro Design and Verification 5. Soft Macro.
NETE Computer Network Analysis and DesignSlide 1 Documenting Network Design NETE-4635 Computer Network Analysis and Design.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Gathering Network Requirements Designing and Supporting Computer Networks – Chapter.
© 2009 Cisco Systems, Inc. All rights reserved. ROUTE v1.0—1-1 Planning Routing Services Creating an Implementation Plan and Documenting the Implementation.
Software Engineering 1 Object-oriented Analysis and Design Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative.
Software Development A Proposed Process and Methodology.
Network design Topic 6 Testing and documentation.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Preparing the Proposal Designing and Supporting Computer Networks – Chapter 9.
Chapter 12 The Network Development Life Cycle
Chapter 8 Final Construction Final construction in the SDLC Construct and test programs Construct and test the database Obtain additional hardware Prepare.
1 ERCOT Retail Release Overview. 2 How Are Changes Managed? Retail Testing Business Teams Development Teams Release Management Management of: Migration.
Illuminating Britelite’s Internal Services for Success Strategy for Process Improvement.
1 © 2005 Cisco Systems, Inc. All rights reserved. Cisco Unity 4.1 Documentation What you need to know.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
© 2002, Cisco Systems, Inc. All rights reserved..
Project Life Presented by Chuck Ray, PMP ITS Project Manager.
ITEC 275 Computer Networks – Switching, Routing, and WANs Week 12 Chapter 14 Robert D’Andrea Some slides provide by Priscilla Oppenheimer and used with.
Cisco Collaboration Compatibility (IVT) Pricing April 2015.
ITEC 275 Computer Networks – Switching, Routing, and WANs
Systems Analysis and Design in a Changing World, Fifth Edition
Software Engineering Management
Sheridan RFP Proposal for the Purchase of Printers for HMC 1 & 2
Software and Systems Integration
Senior Staff Meeting November 12, 2008
Top-Down Network Design Chapter Fourteen Documenting Your Network Design Copyright 2010 Cisco Press & Priscilla Oppenheimer.
Systems Analysis – ITEC 3155 Evaluating Alternatives for Requirements, Environment, and Implementation.
Manfred Huber Based on an earlier presentation by Mike O’Dell, UTA
Automated Fingerprint Identification System upgrade project
Avatar ICD-10 Upgrade and Enhancements Project
1 Stadium Company Network. The Stadium Company Project Is a sports facility management company that manages a stadium. Stadium Company needs to upgrade.
Chapter 5 IS630.
Preparing the Proposal
Kasy Stinson Water Supply Division
Executive Sponsor: Rick Padilla-State Maintenance Bureau Chief
Executive Sponsor: Tom Church, Cabinet Secretary
NM Department of Homeland Security and Emergency Management
Presentation transcript:

Proposed H.323 Forum Testing Program Support Sanjay Mishra – October 24, 2002

Forgent Labs Overview Combined 35 years of video network design and implementation experience. Fully provisioned test labs in Austin, TX and King of Prussia, PA Extensive inter-operability testing experience –Pre-deployment functionality and performance validation. –Test house for ‘Cisco Verified Interoperable’ program of Cisco AVVID Program Program Active IMTC member

Test Lab Configuration

Test Process Vendor executes NDA with Forgent Networks Vendor provides Forgent with Purchase Order for test fees. Vendor completes Forgent Vendor Questionnaire, providing equipment and contact information, and requested test dates and location. Forgent schedules tests within 2 weeks of requested date. Vendor provides: –Three (3) systems of the same model and hardware/software revision for testing. –Proper shipping containers and documentation for production devices. Documentation includes: User Guide Installation and Configuration Instructions High Level Architecture and Features Summary Application and Release Notes (as applicable) Vendor development test plan describing interoperability with H.323 standards –Current operating system and application software as indicated in the Vendor Questionnaire along with any associated software keys, license certificates, etc. –An on-site technical resource for proper installation verification, if applicable.

Test Process Forgent provides test report documenting specific software and hardware versions, compliance level tested and test results to Vendor within 3 days of completion of testing. Vendor submits test results to H.323 Forum for certification of compliance. Within the scope of the H.323 Forum’s compliance testing program, Forgent will report, but not troubleshoot, any failures encountered during testing. Ad-hoc defect fixes in Forgent labs will not be allowed. Depending on defect severity, Vendor may fix defect and return for a 1-day retest within 30 days of initial test. Forgent Networks can provide consulting services, separate from the testing services, to troubleshoot and diagnose problems and test failures.

Fee Structure Proposed costs for Level 1A and 1B compliance tests are $6,400 each. This corresponds to 4 days of lab time, and breaks down into 3 days for initial testing and 1 day for retesting if problems are encountered in the initial tests. Vendor will be invoiced only $4,800 if no problems are encountered during initial testing. Vendors may also purchase lab time through an annual subscription program. The program will include 9 days of lab time during a 12-month period, and will be priced at $10,080.

Key Milestones MilestoneCurrent Target Completion Date Test process and pricing defined and accepted by H.232 Forum and Forgent Networks TBD Forgent develops Level 1A and Level 1B test plansNov 30, 2002 H.323 Forum defines reference architectureNov 30, 2002 Forgent tests Reference Architecture components for Level 1A and 1B compliance Dec 31, 2002 Testing Program open to all H.323 Forum membersJan 1, 2003