SUMMARY OF EXPERIENCE: Diverse computer systems software design, project leadership and test experience, including avionics, telephony (Land, Cellular, and VOIP), telecommunications, Defense, office automation, process control, GUI, windowing systems, real time systems, embedded systems and database management. Experience also covers the areas of object-oriented design and programming. Testing experience include white, grey, and black box methodologies. Raytheon IIS Defense 05/17 to Present Work was performed under Agile/SCRUM sprints using CA's Rally Agile toolset. The software configuration management tool used GIT/GITHUB. Software had to ensure all message processing occurred no faster 20Hz rate and no slower than 10Hz rate. In some cases the software had to be tuned to have task run more frequently to meet this rate. Documentation was done using Confluence software to maintain tracking of documentation issues. In an additional project I was responsible for removing compiler warning from code generated by IBM Rational Rhapsody in C++ (RIC) and verify that the code still passes all automated and manual tests. All Rhapsody code was compiled under VxWorks 7.0 using Workbench 4.0. Test scripts for this additional project were written in Python. Developed system requirements Responsibilities included developed system requirements, system dataflow diagrams, tests and documents that conform to military standards MIL-STD-498 and DO-178B for the Embedded Braking Control Applications Unit (BCAU) to be used on the Joint Strike Fighter (JSF). In addition, was a participant in all code reviews. All code had to conform to MISRA standards. Code was developed to run on the TI F2812 DSP and OMAP 3550 using assembly and C++. Test Scripts were written using Perl, and Code Composers' GEL scripting language. All scripts were running using JTAG interface to the DSP. Tests scripts were debugged, dry-ran, and then ran for score. system dataflow diagrams and related documents that conform to military standards MIL-STD-498 for an Embedded Crash Proof Memory Unit also known as a black box to be used on the Joint Strike Fighter (JSF) also known as the F-35. In addition to writing the documents also assisted in developing the software for the black box. Software was developed using Nucleus Embedded Operating environment using C++. Requirements were stored updated and track using DOORS. Testing scripts were written in Tcl/Tk and debugged dry-run and ran for score. The hardware was developed for a FPGA platform. Assisted in developing requirements and embedded software for Embraer Phenom 300 Bleed Air/Anti-Ice system. System communicated with other flight systems using RS-485 ARINC 429 and 615 protocol standards. Software conformed to DO-178B standards. Requirements were stored in Telelogic's DOORS requirement management system. Software was written in C++ using Texas Instruments Code Composer system. System was cross-compiled from a PC with the destination hardware was based on TI C320F2812 DSP. Software processes conformed to the FAA's DO-178B standards and the system was certified to DAL Level B compliance. Assisted in writing requirements and developing the software for Boeing 787 Dreamliner power and engine start subsystem. Embedded software conformed to Boeing power system standards and DO-178B. Requirements were stored in Telelogic's DOORS. Software was written in C using the Smiths Aerospace's ARINC 653-based VxWorks. The system was certified to DAL Level B compliance. Helped port a PalmOS 4.1 application on an embedded hardware handheld scanner to �Clinux PowerPC-based handheld scanner. Software was written in C software was ported into Java. The software was also ported to a Windows CE-based platform using C#. Responsibilities included developing the software foundation to be used for the Boeing 767 tanker and C-130 transport. Embedded software was written in ADA-95 using ARINC 653 version of the Embedded RTOS VxWorks. In addition developed requirements system dataflow diagrams and test scripts for the Northrop-Grumman J-UCAS unmanned airship. These requirements were developed from the customer statement of work and included MIL-STD-1553 TCP/IP Socket Programming MAC/PHY protocols and IEEE-1394 networking and were stored in Telelogic's DOORS. All processes conformed to DO-178B standards and all relative DOD standards. Was responsible for the development of the requirements design specifications and software needed to implement the firewire also known as IEEE-1394 specifications for the Goodrich Smartprobe/Smartport line of products. Embedded software was written in C++ and assembler. All processes conformed to SEAL Level 1 DO-178B standards and all relative DOD standards. The target Embedded hardware was a Texas Instruments based DSP. Requirements were stored in DOORS. Responsibilities included developing requirements design specifications and software for the SmartDeck glass cockpit. Embedded software used OpenGL to draw the instruments used by the pilot. Code was written in C++. UML was designed using Rhapsody. Code was prototyped using Windows XP target used Green Hills Integrity real-time operating system. All code was verified using the target hardware using the Integrity debugger. All processes conformed to DO-178B standards. The system was certified to Level B. Requirements were stored in DOORS.
Description
