Software Systems Engineering Resume Profile
3.00/5 (Submit Your Rating)
EXPERIENCE
Confidential
- As a software systems engineering contractor, I provided DO-178B level B system software certification of flight controls inclusive of development and review of functional requirements high and low level , requirement based test procedures, discrepancy reporting, and debugging of tests for root cause analysis for the built-in-test BIT , electronic-flight-instrument-system EFIS , Aircraft Model ACM and Flight Plan Management FPM components of the legacy 737 flight management system FMS . The automated tests were validated to assure commercial aircraft safety of flight SOF for FAA certification. This legacy system had a pSOS processor running Ada source code.
Confidential
- As an independent contract engineer I performed software requirements allocation, design definition, test planning, and root cause analysis. I wrote clear, concise and testable requirements in support of DO-178B, Level C structural coverage testing for GPS products of real time embedded applications written in C and Ada. I also provided strong writing skills necessary to produce documentation required for security certification evaluation. Tools that were used to support this effort were C, Ada, Understand, Python, DOORS, Clearcase and PREP.
Confidential
- As the Functional Software Manager for the software development, requirements and test personnel of ATDC, I arranged training, provided affordability measures such as knowledge transfer and removal of repeatability, performed personnel reviews, approved time, created charts for discrepancy accounting, interviewed potential engineering employees, and created work instructions in an EVMS environment.
- As a software engineer I created automated software system tests for a top secret autonomous unmanned aerial vehicle UAV in an AS9100 Quality Assurance environment. My expertise was provided in the area of engines FADECS , propulsion, electrical, and zeroization verification and validation. Other prerequisites of the efforts were performing requirements and code analysis verification in a VxWorks environment, and creating test methodology designs. Utilized XML, DOORS and Understand for C/C to reverse engineer the UAV embedded code to perform code analyses. Worked with numerous bus traffic types, e.g., MIL-STD-1553, ARINC 429, RS-422, RS-485, IEEE-1394. Developed QSA javascript and C code, provided C and QSA code reviews, and reviewed/revised Python scripts for the embedded systems.
Confidential
- As a systems engineer contractor, I architected DODAF style UML Sequence Diagrams based on customer interface control documents ICD s requirements and system control documents SCD s. Edited ICDs for ARINC 429 parameters and performed real time embedded systems and software development activities per RTCA/DO178B and DO278 level B software development guidelines. Evaluated C code for sequences and fault codes by using the Understand for C/C engineering tool. Exported requirements from the DOORS requirement tool environment to perform requirements analysis. Created the ARINC 429 Verification Plan for both nominal and off-nominal robustness testing.
Confidential
- As a software engineer I created software system test scripts for a space based electro-optical infrared EOIR system and airworthiness certification of autonomous unmanned aerial vehicles UAVs . My expertise was provided in the area of guidance, navigation and controls GN C , operational modes ground flight , autonomous steering modes, and the integrated sensor suite SAR EOIR verification and validation in an AS9100 CMMI level 3 environment. Other prerequisites of the efforts were performing requirements and C code analysis verification in a VxWorks environment, and creating test methodology designs using DO-178B as a guide. Worked with numerous bus traffic types, e.g., MIL-STD-1553, ARINC 429, RS-422.
Confidential
- As an independent contractor with NASA SCA/DFRC , I created the System Design Document and Software Test Plan Procedure STP PR for the Radar Information Processing System RIPS at Edwards AFB. Designed WinRunner automated tests to validate the RIPS C code in a Windows 2000 environment, and designed a Post Processing Analyzer in Perl for little endian to big endian conversion of radar geodetic data from serial links. Provided software quality assurance SQA audits of the autonomous X-37, AAW F-18 and X-ACT avionic vehicles as an SEPG function to attain an SEI CMMI level 3 rating. Used Rational Rose, VISIO, Understand for C and ClearQuest to reverse engineer and create UML diagrams of RIPS.
- As a lead software integration test engineer for the Instrument Command Control ICC Payload on the Space Infrared Telescope Facility SIRTF autonomous observatory with NASA LMMS/JPL , I worked on testing aspects associated with spacecraft command and telemetry links, command and telemetry formats, RS-422 data processing and acquisition, and processing and control aspects associated with real-time systems. Prepared Perl scripts for data parsing, Tcl scripts to generate command sequences, used Matlab models as test environments and manipulated the VxWorks/Tornado IDE to host the code in the target processor.
- As a lead for software integration on the UAV X-33 Reusable Launch Vehicle for NASA LMSW/DFRC , I authored Software Test Plans STPs and Procedures STPRs in a MIL-STD-1553, C, VxWorks/Tornado, UNIX Sun Solaris and SGI IRIX and PowerPC environment. I validated the X-33 vehicle's electrical system, mission computer and vehicle health monitor with logic and protocol analyzers verifying the accuracy of the MIL-STD-1553 messages.
- As a lead software test engineer for NASA ITSS/JPL , I evaluated Perl 5 and Tcl Expect scripting interpreters for database and cross platform verification and validation. Designed the System and Integration Test Plan for the Shuttle Radar Topography Mission SRTM . Structured tests for a FDDI network running TCP/IP. The network's design was for separate logical ring configurations, one for control and the other for data. The controller IPC node was housed on a Sun running Solaris and the other nodes were on an SGI running IRIX
