PROFESSIONAL SUMMARY:

• 4+ years of experience in the area of Development, System Testing, Verification and Validation of safety critical Embedded System.
• Knowledge on Model based Development and HIL Testing using MATLAB/Simulink/ Real Time Workshop/xPC Target/dSPACE System/Control Desk Software. Very much interested in working in MBD and HIL testing projects.
• Good experience in Avionics System testing, development and execution of LabVIEW system test scripts on integration benches.
• Good experience in identifying and debugging issues at system level and understanding interaction with other avionics Embedded system.
• Experience in writing Software Requirement in DOORS, UML documentation and Software Design document.
• Good knowledge on Embraer Legacy 500, Bombardier C - series and Bombardier Global 7000 system architecture and subsystems.
• Experience in MFC Windows GUI development using MS Visual Studio 2010
• Experience in Perl, Python automation scripting.
• Experience in Integrated Development Environments Analog DSP++, MS Visual Studio, Code Composer Studio
• Knowledge on DO-178B, DO-178C guidelines
• Attended on Model based development tool SCADE Suite
• Knowledge on LabVIEW Data Flow execution modeling.
• Knowledge on Linux Kernel and Device Driver Programming
• A quick learner with talent and attitude to take challenges
• Presented with ‘Live Wire’ Performance for Outstanding contribution at Confidential
• Presented with ‘Spot ’ for valuable contribution to the success of C-Series Software Development support at Confidential

TECHNICAL SKILLS:

Languages: C, C++, VC++

Scripting Languages: Python, Perl, LabVIEW test console scripting, LabVIEW post processing scripting.

Protocols/Standards: Arinc429, TTP, RS-232, RS485, CAN, DO-178B/C

Testing Tools: dSPACE Control system, dSPACE Control desk, NI DIAdem, LabVIEW system console.

Development Tools: Matlab/Simulink/Stateflow R2009a, Visual Studio 2010, LabVIEW, Code composer Studio 3.3, MS Visio 2003Configuration/Reporting Tools: IBM Rational DOORS 8.1, MKS 3.5, Bugzilla, Tortoise SVN

Platforms: MS Windows 7, Linux - Ubuntu

PROFESSIONAL EXPERIENCE:

Confidential, Irvine, California

Tools: DIAdem, DiRT, System Test Console, MKS, DOORS, Ultraedit, TCS ToolProtocol/Standards: A429, TTP, RS-485, DO-178B

Responsibilities:

• Development and testing of Integrated Test Procedures (ITP) as per System Requirements (SysRd) for verification of Flight Control System.
• Develop and test LabVIEW Test Case Scripts (TCS) and LabVIEW Post-Processing Scripts (PPS) as per ITP.
• Debugging and Executing the LabVIEW Test Case Scripts (TCS) on LabVIEW Test Console at Confidential to test different systems for failure.
• Identification of the test scenarios in integration with the other applications of the Flight Control System using DOORS and MKS tools.
• Manual testing and analysis on system test console for errors in system and raising Problem Report (PR)
• Executing the Post Processing Scripts using DiRT (DIAdem Reporting Tool) for plotting the captured data, analyzing the graphical reports for failures and reporting the same to the system development team and/or raising PRs.
• Manual analysis of Failure using DIAdem and problem report.
• Worked on LabVIEW System Test Console.
• Worked on National Instruments DIAdem Tool.
• Worked on MKS as configuration management Tool and Problem reporting.

Confidential

Tools: DOORs, MATLAB Simulink, Rhapsody, MKS, MS Visio 2003Protocol/Standards: RS-485, A429, TTP, DO-178B

Responsibilities:

• Worked on IBM rational DOORS 8.1 to write, manage software requirements and data dictionary, also worked on DOORS object linking mechanism and export of DOORS module as Word/Excel document
• Writing requirements from Simulink models (reverse engineering)
• Manual testing of Model blocks for correct implementation.
• Development of Software Design Document(SWDD) with control flow diagram using Rhapsody and UML flowcharts using MS Visio 2003
• Reviewing requirements against Simulink Models for proper implementation and Tracing
• Requirement Review to meet the Guidelines of DO-178B and to see if the requirements are complete, unambiguous, executable, verifiable and correctly traced
• Conducted sessions on system architecture and system engineering for seniors and fresher’s
• Worked on MKS as configuration management Tool

Confidential

Tools: /Standards: C++, MFC Application, Visual Studio 2010, OOPs

Responsibilities:

• Understanding and analyzing software requirement.
• Designing and architecting the ADCT tool GUI as per requirement using C++.
• MFC Graphical user interface development using visual studio 2010.
• Designing and compiling the solution and fixing the issues.
• Status reporting to the management.
• Regular interaction with the client for upgrading the tool to meet the client requirements.

Confidential

Tools: Code Composer Studio 3.3, Visual DSP++ 5.0, DOORS, MKSProtocol/Standards: Arinc429, TTP, RS-485, SPI-ENG008

Responsibilities:

• Analyzing high level requirement for REU command and monitor lane.
• Delta development of REU Command and Monitor Lane Software code in C for requirement changes.
• Build the code and debugging for compilation and linking errors.
• Flash the image on to the controller (ADSP-21469/ TMS320F28335) and debug for the integration with middleware software.
• Fix the issues and raise problem report.

Confidential

Tools: DIAdem, DiRT, System Test Console, MKS, DOORS, Perl, Python, Ultra editProtocol/Standards: A429, TTP, RS-485, DO-178B

Responsibilities:

• Understand complete system level architecture of EMB 550 MSJ flight.
• Automation using Perl scripting.
• Develop LabVIEW Test Case Scripts (TCS) and LabVIEW Post-Processing Scripts (PPS) as per ITP.
• Debugging and Executing the LabVIEW Test Case Scripts (TCS) on LabVIEW Test Console at Confidential to test different systems for failure.
• Identification of the test scenarios in integration with the other applications of the Flight Control System using DOORS and MKS tools.
• Debugging and Executing Post Processing Scripts using DiRT (DIAdem Reporting Tool), analyzing the graphical reports for failures and reporting the same to the system development team.
• Manual analysis of Failure using DIAdem and problem report to the development team.
• Preparation and Analysis of Reports generated by running Post-Processing Scripts on DIAdem Reporting Tool (DiRT).
• Worked on National Instruments DIAdem Tool.
• Worked on MKS as configuration management Tool.