Design/develop SW in C/C++ for airborne RADAR application

Maritime Surveillance mode for high altitude unmanned aircraft (2009-Present)

• Compiled mode requirements within DOORS system. Responsible for the Radar Control/Signal Processing (SP) Software Design. Both Requirements and Software Design were presented to the customer (U.S. Navy) and received approval.

• Developed of SP software that resided on a bank of 35 Mercury PPC signal processors, initially done on Window/Visual Studio environment prior to target hardware migration to greatly reduce development time and cost.

• Worked in collaboration with systems engineering where complex SP algorithms were refined and optimized to operate within strict real-time constraints.

• Integrated SP software to the target platform where it has been successfully flight tested.

Ground Moving Target Indicator (GMTI) mode for Next Generation Jet Fighter/Unmanned Helicopter (2006-2008)

• Designed overall architecture of GMTI SP software to be hosted on both Curtiss-Wright and Mercury platforms (14 signal processors). This design was captured within the Artisan software modeling tool.

• Performed extensive throughput analysis to identify plausible SP graphs. Forecasted memory, fabric IO and CPU processing usage based on mathematical models. This required a thorough understanding of the timing of the Altivec library under various buffer caching paradigms (high speed cache to low speed DRAM).

• Software validated in system integration test phase; delivered on schedule and within budget.

Synthetic Aperture Radar (SAR) mode for Unmanned High Altitude Aircraft (2003-2005)

• Generated design document describing the modifications required to integrate an existing SAR SP application onto a new hardware platform. Implemented and integrated the signal processing modification.

• Implemented modifications to the mode control portion of a SAR application. This required use of the Tornado development environment.

Designed and developed software that implements protocol stacks. This includes ISDN Bri and Pri, SS7, DASS2.

• Designed, developed and tested numerous ISDN variants and features from specification. These included both North American (T1) and European (E1) types, PBX protocols QSIG and DPNSS, Generic Functional Procedures for QSIG (QSIG GF), NFAS/D-Channel Backup, Supplementary Services support, AutoSPID and Autoswitch Detection.

• Responsible for the ISDN portion of SS7 (ISUP) which included design, development, certification testing and training. Member of a small team that developed a Generic Information Element library that converted an ISUP specific Information Element stream into a C structure for customer ease of use. Along with the team, awarded patent (US20030206519) ‘System and method for encoding and decoding messages’.

• Provided customer training on ATM, DASS2/DPNSS and SS7/ISUP; Extensive customer support for the product line.

IPC was an OEM for phone systems(PBX) used on trading floors. I was responsible for designing and implementing software that controlled ISDN connections (basic and primary rate).

• Developed client/server software to transmit data reliably from a UNIX workstation to a VxWorks platform. Built an application layer on top of UDP/IP to obtain TCP/IP reliability with added performance.

• Designed and developed software subsystems to support ISDN, DPNSS, DASS2, QSIG and NET5 protocols to IPC’s PBX phone system. The software provided a seamless interface between the proprietary call processing model and off-the-shelf protocol software. Developed drivers to interface with signaling and voice channel circuitry.

ADP provided realtime feeds (news/financial) to the financial industry. I was responsible for designing/developing the software that interfaced to the various standard communication links(e.g. X.25, Bisync). This software ran on an IBM Real-time Interface Card under a multitasking environment to supply tasks with error free data. Conducted rigorous Certification testing.

Designed and developed software that allowed access to mainframes via terminal emulation from a PC. I was responsible for all aspects of our product (user interface to device driver).