 |
Networking and telecommunication OEMs are at the forefront of design complexity. A network element can contain hundreds of thousands or even millions of source lines and employ hundreds of software tasks, all of which contend for a finite amount of memory and CPU time.
To build these massive software systems in the least possible time, OEMs typically opt for parallel development, dividing the work among multiple project teams. Unfortunately, the parallel development paths invariably lead to performance issues at the system integration phase, when, for the first time, subsystems built by the various teams begin competing for system resources. Subsystems that behaved correctly in isolation now respond slowly, if at all. In many cases, these resource-contention problems emerge only during integration and verification testing, when the cost and schedule impact of software recoding is at its highest.
Download this whitepaper and learn more about how to avoid weeks or months of corrective actions resulting in increased costs and negating the time-to-market advantages of parallel development.
|
 |
File Information 
File Information 
Additional Notes