SUMMARY

• 10+ years of experience in Automotive, Avionics Embedded Systems Design, Development, Verification & Validation
• Working as part of GM Global B strategy team involved in System design for Thermal Domain.
• Working as part of GM Global B strategy team involved in System design for Standard Utility Modules (SUM) for SSC (Security Service Co - Ordinator for Functional Safety & Security)
• Good exposure to entire Software Development Life Cycle (SDLC)
• Extensive experience in testing different types of Real time embedded software based on teh criticality level such as Level A, B, C and D in avionics software.
• Expertise in UML base Development using Rational Tools and Generating Code.
• Experience in use of Development Tools - Rhapsody and PathFinder.
• Expertise in use of Requirement Management Tools like DOORS.
• Expertise in use of Configuration management Tools like Serena Dimensions, Rational Synergy and Clear case.
• Expertise in use of Change management Tools like Rational Change and Rational Team Concert (RTC).
• Expertise in performing Functional Verification Procedures (FVP’s), System Testing, Unit and Integration Testing.
• Expertise in performing Code reviews, Requirement and Integration Reviews for safety critical software.
• Experience in use of Verification Tools - RTRT And ARMS
• Worked at Client site in Frankfurt, Germany for about a year performing Unit and Integration Testing.
• Have various skill set that ensures high adoptability to both development and testing environments in Avionics, Automotive, Transportation/Rail, Medical Electronics and similar industries.

TECHNICAL SKILLS

Operating System: Windows XP, MSDOS, Linux, VxWorks.

Languages: C

Design & Testing Tools: Rhapsody, PC-lint, ARMS and RTRT

Configuration and Change Management Tools: Serena Dimensions, Synergy CM, Clear Case And Rational Team Concert and Rational Change

Requirement Management Tool: DOORS

Static Tools: Understanding C++

Protocols: CAN, TCP/IP And LIN

Debugging Tools: Code Composer and PathFinder

Compiler: GCC And Cygwin

PROFESSIONAL EXPERIENCE

Confidential

System Design Engineer

Responsibilities:

• Analyze teh functional requirements of ‘Global B’ project
• High level partitioning of teh features
• Part of functional requirements documented in Subsystem Technical Specifications (SSTS) and provide feedback to requirements authors improve clarity or consistency with established GM requirements strategies. Collaborate with requirements authors and other stakeholders as needed to ensure high quality, executable Subsystem requirements.
• Develop functional partitioning and allocation scenarios comprehending system constraints, cost /resource optimizations, robustness, and implementation complexities.
• Create and maintain teh FPA Model for assigned subsystems using teh Rhapsody tool according to teh established release schedule.
• Defining teh new serial data signals or Modify Existing Signals.
• Provide teh Signal Protection Based on teh ECU Compatibility
• Creation of teh approved signals in teh Rhapsody domain model using teh VB Script
• Modeling teh new feature in Design Model using Rhapsody tool
• Creation of teh new ECU and teh Bus in teh Global-B Architecture Model
• Allocation of sub-functions to teh ECUs
• Deployment of teh new feature’s Software Components in teh appropriate ECUs in teh Global-B Architecture model
• Task completion and updating of work tickets using CM Synergy and RTC.
• Integrate teh modeling work from development context to Product line
• Review of Other domains Modeling Work
• Supported Diagnostic Work for HMI Domain.

Confidential

Verification & Validation Engineer

Responsibilities:

• Develop Software Requirements (SWRD) from System requirements
• Development of code as per teh specified applicable requirements.
• Bug fixing of any errors which occurs during teh development and also after release of teh software.
• Test teh software on teh qualified test stands before releasing to teh testing team to ensure that teh software is working as expected in accordance with teh software requirements.
• System Testing:
• Developed test scripts Based on teh Requirements Using Lab environment
• Executing teh scripts on Test stand in Lab environment.
• Maintaining teh test reports and bug reports.
• Hardware Software Integration Testing (HSIT):
• Developed test scripts Based on teh Requirements Using Lab environment
• Executing teh scripts on Test stand in Lab environment.
• Maintaining teh test reports and bug reports.
• Review of teh Hardware Software integration test Scripts.
• Unit Testing:
• Understanding teh Low Level requirements and develop test cases based on teh Low level Requirements.
• Running test scripts on RTRT and verifying teh results.
• Performing structural coverage analysis.
• Resolving teh hardware and software dependency issues during teh project by interacting with teh customer and relevant technical people.
• Co-ordinate with offshore team and teh onsite team during testing of teh software.
• Acted as Project Quality analyst.
• Peer reviews of teh all deliverables.

Confidential

Verification & Validation Engineer

Responsibilities:

• Derive software requirements from systems specification
• Performed design of teh software based on teh requirements
• Development of real-time embedded software using UML model based tool Rhapsody.
• DOORS configuration of requirements and development of automated solutions for better requirement Management using DXL Scripting language.
• Writing test scripts for Requirement Based Test using Visual Basic, Hardware Software Integration Test using Ashling and configure teh test logs to MKS Source Integrity.
• Development of teh verification tools like Simulator Interface, CAN Communication Test Interface and Verification Test Interface GUI design.
• Worked on CAN Analyzer which is used to receive and transmit CAN messages from/to APUC.
• Teh front end is developed using Visual Basic and Lab View as back end.
• Executing teh test scripts in teh Automated Test Equipment.
• Performed structural coverage analysis and fixing teh gaps in teh code by writing analysis.
• Leading a team of members for teh verification activities.
• Provide assistance during teh maintenance phase of teh software.
• Attended critical FAA Audits and Stages of Involvement (SOI) Audits that are held during each and