SUMMARY:

Degreed Electronic Engineer with Requirements Management/Systems/Firmware/Software/Hardware/Test experience in Embedded Product Development. Available for global travel.

TECHNICAL SKILLS:

• System requirements analysis, allocation, and creation System requirements specification development in DOORS for ASPICE Compliance, ISO 26262 Safety, and Verification Requirements Management Process Use Case Development, Sequence Diagrams, UML, SysML System Design Documents (SDD), Interface Control Documents (ICD) Tools: Rational Rose (now Rhapsody), ClearCase, DOORS Classic & DNG, IBM Change/Synergy, Artisan Studio CMM(I) 3, CMMI 5, ASPICE, ISO 26262 Global DOORS Classic and Next Generation Administration - Users, Projects, Maintenance, Classic to DNG Migration Global DOORS Module Template Creation - SW Components, SW Req. Spec., and Control Module Req. Spec. Global DOORS User Help - Use and Network Resolution - 10 International and 1 USA Site 600+ Users
• Software requirements, analysis, allocation, creation, traceability, verification, metrics, and design documents OOA/OOD, C++, UML, Hatley/Pirbhai Structured Techniques C language with 68302/68000 , 68331, 68332, 68HC16, 68HC11, 8x51/251, 80196, 8088, 80CR167, x86, ST9, ARM A8 Assembly language with Motorola 68HC11, 68xxx, Intel 8051, 80196, 8085, Zilog Z8 & Z80 Serial communications: CAN, CAN FD, multidrop RS232/RS422/RS485, SPI, I2C Functional Test/Verification Tools: Rational Rose (now Rhapsody), ClearCase, DOORS, OmTool2, STP, Cadre Teamwork, Select Yourdon, Applied
• Microsystems, Whitesmith, Microtec Research, Intel, Watcom, PVCS, XDB, HP, Pentica, Introl, SDS, BSO
• Tasking, Keil, Nohau, Avocet, Kontron, and ST Microelectronics, Texas Instruments Code Composer, Red Hat Linux, VMware
• Embedded Linux: UBoot customization, kernel customization, bash script modifications for builds
• CPU board design/interface with Intel 80x86, 80196, 8051; Zilog Z-80; Motorola 680x068302, 68HC11; VGA LCD interface; IBM PC interface; CIMBUS; Transducer interface for pressure, position, and speed; various serial interfaces using Orcad (and others) Test for Temperature, Voltage, Vibration, and EMC Schematic narratives for board designs Creation of test procedures documents

WORK HISTORY:

Confidential, Saginaw, MI

Embedded Systems Engineer

Responsibilities:

• Created SysML models representing electric power steering functionality Created initial SW Req. Specs. for Ford, GM, and BMW projects in DOORS Classic supporting ASPICE, Verification, and ISO 26262 Automotive Safety
• Created requirements, verification criteria, and traceability in SW Req. Spec. for serial communication and bootloader in DOORS
• Managed and mentored offshore team for requirements development in DOORS
• Worked with offshore team to close specification issues at all levels of the Engineering V model Used IBM Rational Change for identified SW requirements issues found in SW test prior to production OEM requirements development was performed in a semi-Agile environment (iterative and V)

Confidential, Saginaw, MI

Senior Systems Engineer /Embedded Systems Engineer/DOORS Administration

Responsibilities:

• Classic and DOORS Next Generation embedded requirements development
• Grew User database to 600+ users both domestic/international employees and international contract firms
• Created new users, set permissions, created user groups, created new projects globally with standardized project & template structure
• Provided mentoring and assistance globally to new users of DOORS (3am and 4am starts common) Worked with IT to resolve global network issues involving DOORS and Citrix Created standardized project structure in DOORS Contributor to the corporate Requirements Management Process document - RASIC, Workflow, and Attributes Participant in ASPICE audits for the SW Requirements Specification
• Co-developed Control Module, HW, and SW Req. Spec. templates
• Co-developed common SW Component template to support 6 varieties of SW components
• Co-developed new attributes and types to support ASPICE and quality metrics (part of the Requirements Management Process) Migrated projects to DOORS Change Proposal System - projects in production status
• Created Migration Packages and ReqIF
• Packages for export from DOORS Classic to DNG Training in DOORS Next Generation (see course list on last page of resume)

Confidential

Avionics System Design Engineer

Responsibilities:

• Technical duties included the creation of the System Requirements Document (SRD) based on customer requirements, System Design Document (SDD), and Interface Control Document (ICD). Provided guidance to HW and SW engineers on the creation of requirements and traceability to internal System Requirements in DOORS. All documents were maintained in DOORS.

Confidential

Software Systems Engineer

Responsibilities:

• Developed Use Cases and Software/System Requirements for Embedded Training Live Fire and Simulated Live Fire on the Confidential platforms for the Future Combat Systems (FCS) Program.
• Use Cases along with their respective C++ classes and data structures, and supporting code stubs were developed with BAE Systems for Confidential .
• System of Systems model integration required multi-site interaction along with many others involved in the FCS effort.
• Use Cases were developed in Rational Rose (now Rhapsody) and requirements were managed in DOORS.
• The integrated Use Case products linked in to the Rose and DOORS artifacts under configuration management.
• Red Hat Linux platforms with a VMware virtual machine were used for MS Windows applications.
• All efforts were to CMMI Level 5.

Confidential

Software Systems Engineer

Responsibilities:

• Start up of a new software engineering effort in the Washington DC area for Confidential Suspension and Embedded Training on the Future Combat Systems Program.
• Responsible for the hiring and management of 9 software engineers.
• Site development activities included the procurement and installation of all development hardware and software for multi-site interaction with headquarters.
• Platforms were Red Hat Linux running a VMware virtual machine for Microsoft applications.
• Hiring and site development were successfully accomplished in 3 months time and staff were producing prototype code.
• Additional responsibilities included duties as the Earned Value Management (EVMS) Manager for staff under my direction.
• Weekly reporting to the Defense Contract Management Agency and GDLS HQ was required.
• I was a contributor in several contract bids for product upgrades in the software realm.
• Achieved CMMI Level 5 as an extension of HQ’s previous CMMI Level 3 certification.

Confidential

Software Systems Engineer

Responsibilities:

• Software Engineer for Embedded Training on the Future Combat Systems Program.
• This was a phase of research and work package reviews for contributions to trade studies being developed for embedded training.

Confidential

Core Embedded Systems Engineer & Applications/Product Engineer

Responsibilities:

• This project involved the development of a power sliding door controller and power lift gate controller for a Hyundai/Kia minivan. I wore two hats as the Embedded Systems Engineer and the Applications/Product Engineer. responsibilities included requirements analysis, definition, and management. I wrote the System Design Document (SDD), which included the Interface Control Document (ICD). Also, I co-created the FMEA down to the electronic component level.
• Performed software functional test/verification.
• Requirements and system design documentation were developed with MS Office tools.

Confidential

Core Embedded Systems Engineer & Applications/Product Engineer

Responsibilities:

• Led international controller development for electronic hardware, firmware, mechanical designand test with teams in the USA, Korea, Sweden, India, and Mexico. The teams were a combination of direct employees and subcontractor companies.
• I conducted internal and customer design reviews for all aspects of the controller design. The design review artifacts were placed in Telelogic Change/Synergy.
• SW defects were captured using Telelogic Change/Synergy.
• Developed to CMM Level 3 Std’s. for development process.
• Value Analysis/Value Engineering techniques were employed for product improvement and cost reduction.
• Used ST Microelectronics 92F120/150 and ST Tools.
• My negotiations with ST Microelectronics' VP of Marketing enabled us to acquire all development tools free of charge for our development teams internationally. Savings of $50k.

Confidential

Firmware Engineer

Responsibilities:

• Modified firmware in Pascal, C, and Assembly languages for a multi processor kidney dialysis machine.
• There was no in-house expertise for this specific device and it required locating legacy development tools, creating the development environment, and fixing the anomalies associated with the product. Resolved issues with calibration memory of the Motorola 68000 boards.
• Performed functional test/verification of the machine with the updated calibration memory.

Confidential

Firmware Engineer

Responsibilities:

• Ported heavy duty truck firmware, developed additional firmware for a new medium duty truck Vehicle Electronic Control Unit, and performed functional test/verification/integration of the new code. Firmware development included a proprietary serial link for cluster control, J1587, and CAN/J1939.
• Developed enhanced maintenance features for ease of use in the field by service personnel.
• Used the Siemens/Infineon C167CR MCU, BSO Tasking compiler, Kontron emulator, and proprietary tools for development.
• Required travel to France for customer interface on specification definition concerning system, hardware, and software requirements.

Confidential

Lead Firmware & Applications Engineer

Responsibilities:

• Developed firmware to control a first generation fingerprint sensor IC for commercial applications.
• Other tasks included IC control register definition, development of IC requirements for software development, IC debug to internal layers, and test software.
• Was one of the creative team on the initial version of the IC Programmer's Reference Manual.
• Heavy customer interface and travel.
• Used 80251 MCU & BSO Tasking development tools, Nohau emulator, & PC based documentation tools.

Confidential

Firmware Engineer

Responsibilities:

• Project involved the design, code, functional test/verification, and integration of an existing 8051 based smartcard controller in assembly language.
• Used Avocet and Nohau tools for development.
• Existing code base was created with development tools that were no longer available or maintained.
• This required the purchase of newly released tools, the re-creation of the development environment, and rewriting portions of the original code to retain existing functionality prior to enhancing product features.