tellabs presentation

Uploaded from authorPOINTLite
Views:
 
Category: Entertainment
     
 

Presentation Description

No description available.

Comments

Presentation Transcript

Unit Test Script Generator (UTG): 

Unit Test Script Generator (UTG) Requirements

Just Who Is Tellabs Anyway?: 

Just Who Is Tellabs Anyway? Started in 1975 by six people at a kitchen table Began by selling echo cancellers Moved into the digital cross connect market Today, 6,000+ employees worldwide Over $1,600,000,000 in 1998 net sales

Telecommunications Crash Course: 

Telecommunications Crash Course 1 DS0 = 1 Phone Call 64 kb/s 1 DS1 => 24 DS0s 1.544 Mb/s 1 DS3 => 28 DS1s 672 DS0s 44.73 Mb/s 1 STS-1E => 1 DS3 672 DS0s 51.840 Mb/s OC1 => STS-1E 51.840 Mb/s OC3 => 2016 DS0s 155.520 Mb/s OC12 => 8064 DS0s 622.08 Mb/s OC48 => 32256 DS0s 2488.320 Mb/s OC192 => 129024 DS0s 9953.28 Mb/s

Digital Cross Connects The TITAN Family: 

Digital Cross Connects The TITAN Family TITAN 5500 Cross Connects at DS3/DS1 Level Max 2048 DS3s 57,344 DS1s 1,376,256 DS0s TITAN 532L Cross Connects at DS1/DS0 Level Max 256 DS3s 7,168 DS1s 172,032 DS0s

What Does A TITAN Do?: 

What Does A TITAN Do? Transports, routes information for: Connect Long Distance Hubs 911 Services FAA radar traffic Cellular networks ATM networks Lotto networks

Intro to the Tellabs Development Environment: 

Intro to the Tellabs Development Environment Software is compiled in the SUN environment Target hardware processors are all Motorola 68000 / Power PC based Software is uploaded from the SUN to the TITAN using an external SCSI link

CS 406/407 Project Goals: 

CS 406/407 Project Goals Provide complete life cycle experience for students Provide a useful tool to aid in the development process

The Zen of Requirements: 

The Zen of Requirements Requirements are driven by a product not vice versa Requirements change at the most inconvenient times There are few wrong answers but some are more right than others

Software Lifecycle: 

Software Lifecycle High Level Design Low Level Design Code SWIT Testing Unit Testing

What is Unit Testing?: 

What is Unit Testing? Function level testing. Goal is to execute every line of code. A unit test executes 1 block of code. Not done on target hardware.

Why Unit Test?: 

Why Unit Test? First line of defense. Eliminate simple coding mistakes. Simplest way to test all code. A good process requires this.

Who will the UTG benefit?: 

Who will the UTG benefit? Software development groups.

Virtues of a Programmer: 

Virtues of a Programmer Laziness Hubris Impatience

Unit Test Scripts Violate All Three Virtues: 

Unit Test Scripts Violate All Three Virtues

Laziness: 

Laziness Over 9000 functions. Over 3000 existing unit test scripts. Unit tests require a lot of effort to write.

Hubris: 

Hubris We don’t write buggy code! Not a lot of bugs are found at this stage. Time spent unit testing is time spent not coding.

Impatience: 

Impatience Obvious! Trivial! Boring!

Fundamental Requirements: 

Fundamental Requirements Must be easier. Must be more accurate. Must be more consistent.

Basic Requirements: 

Basic Requirements Given a C function, identify all code blocks. Be able to read existing scripts. Provide the ability to edit entire tests. Insert/Delete/Cut/Copy/Paste/Edit.

More Requirements: 

More Requirements Show the relationship between tests and code blocks. The UTG should attempt to guess at the test summary.

External Requirements: 

External Requirements Must be supported on Solaris 2.6. Perl 5 and C are the recommended languages. GUI must be provided.

Unit Test Script Form: 

Unit Test Script Form Header Code Block definitions Test Summary Optional Sections Tests Script Conclusion (Pass/Fail section)

Unit Test Form: 

Unit Test Form Test #). Summary (same as in summary section). Input section. parameter/local variable values. Expected output Section. Subsequent functions called. Return value of function.

The UTG does not …: 

The UTG does not … Perform any run-time analysis. Run Unit Tests