Welcome To The Future

 Mr. Weber has turned his attention to cybersecurity after accomplishing over 15 years of software experience. Worked with the development team to implement secure coding practices and standards for the database data collection application. Implemented security measures, such as encryption and access controls, to protect sensitive data stored and processed by the application. Worked on improving the security of the interface with Xilinx FPGA memory locations and implemented security best practices, such as input validation, error handling, and secure coding practices. Conducted code reviews and adhered to security recommendations to ensure the software development process adheres to secure coding standards and practices. Conducted security testing and analysis on the developed test software application to ensure it meets security standards and requirements, such as penetration testing, vulnerability assessment, and threat modeling. Worked with the security team, corroborate with the security team, and analysis on the real-time control development using C/C++ and TCP/IP to ensure it meets security standards and requirements, such as penetration testing, vulnerability assessment, and threat modeling. Conducted code reviews and provided security recommendations to ensure the software development process adheres to secure standards.

Advance Test Software Engineer

  6/2021 to 9/2022 

Primary technologies: C#, C++, VB Test and Develop software for Honeywell  

Software Engineer, 9/2019 to 6/2021

Primary technologies: C#, VB

Debugged and Develop software for Night Vision Technology

Substitute Teacher, 8/2016 to Present

Primary technologies: Math, Art, Science, History, Multimedia, Music, and Special Education.

Software Engineer, 8/2013 to 4/2014

Primary technologies: C/C++.

Debugged and tested software for Locomotives

Systems Engineer, General Dynamics Land Systems  Sep 1998 – May 2006

** EDUCATION **

Masterschool Boot Camp ofr Cybersecurity.

   Oakland University, Rochester, Michigan; Master of Science in Computer Science and Engineering.

   The University of Akron, Akron, Ohio; Bachelor of Science in Electrical Engineering.

   Attended training for Diversity,

 Peer Review Process

   Seminars on Navigation; Software, 

Hardware modeling and design tool (Statemate)

   VxWorks 6.9 and Workbench 3.3

   C Programming Course with HOTT

   PLC Course from Atech 

   Teaching License in Computer Technology

   Tutor qualifications in Math, 

Computers, and Engineering
  C#, PHP, OOP, SQL-T Lynda.com

** TECHNICAL SKILLS **
 

Situation 1:

Situation: Obtained a new Main Control Unit from the vendor (Germany) and it had to be qualified by Joy Global before being excepted and deployed in the field.

Task: Develop a qualifying Test for the Main Control Unit or the Central Control Unit (CCU) and verify the unit’s capability/functionality.

Actions:

• Read and      understand the unit's manufacturing requirements.
• Developed a      plan for types of tests needed for qualification using Company      qualification standards.
• Create a test      for the unit’s requirements.
• Determined the      tools to test the unit: VxWorks, C++, PC, TCP/IP,
• Developed      architecture (software and hardware) documents.
• Fabricated a      CAN selector test box.
• Developed      software code via a document plan.
• Tested the unit      per documented plan and stored results metrics in the Caliber repository.
• Retained all      documentation in the Caliber repository.

Results: The unit was tested and qualified on time and within budget per company standards: vibration, temperature, and functionality.  The unit was able to be excepted and deployed in the field.

Situation 3:

Situation: new requirements were given for the Unit Under Test (UUT).

Task: Upgrade existing application lab bench software written in CVI/LabWindow (ANSI C) to comply with UUT's new requirement.

Actions:

• Read and      understand old and new requirements.
• Work with the      team to develop solutions.
• Modified code      to comply with new requirements.
• Tested the      changes.
• Document the      change.
• Review changes      with the team.
• run telemetry,      memory, and video mapping tests on the unit under UUT.

Results:  The lab bench was qualified and put to work in the lab.

Situation 4:

Situation: The locomotive software version needs updates to fix known bugs: TCP/IP location problem, Display problem, and function definition implementation.

Task: find and correct locomotive software bugs written in C++ on Linux RTOS QNX.

Actions:

• Read and      understand the trouble report.
• Download the      latest version of the code from the Perforce repository.
• Review code,      run code, and observe code behavior.
• Talk to subject      experts in the company about the problem and possible solutions.
• Determine the      problem and implement the solution.
• Test solution.
• Upload to      repository

Results:  The code was modified and tested and loaded into a repository for others the include in their projects.

Situation 5:

CAN Microprocessor Current Control Transformer (MCT) Top Tester. This included hardware and software solutions to be developed by two interns. I oversaw scheduling and overseeing the test unit's production from start to finish. The software was written in C#, and the hardware used a Peripheral Interface Controller (PIC) microcontroller. The purpose of the software was to test UUT functionality in the manufacturing facility. The software exercises the CAN Bus and the display on the unit. The unit had several modes of operation in which was displayed of the unit. The PIC controller the CAN Bus address selections on the UUT. The software monitored the voltage and current and displayed it to the user performing the test

Situation: Obtained a new Main Control Unit from the vendor (Germany) and it had to be qualified by Joy Global before being excepted and deployed in the field.

Task: Develop a qualifying Test for the CAN Microprocessor Current Control Transformer (MCT) Top Tester and verify the unit’s capability/functionality.

Actions:

• Read and      understand the unit's manufacturing requirements.
• Developed a      plan for types of tests needed for qualification using Company qualification      standards.
• Create a test      for the unit’s requirements.
• Determined the      tools to test the unit: Visual Studio, C#, PC, TCP/IP, CAN Bus, Serial      Bus, PIC on a PCBoard, Cabinet, and Power supply. BOM, Architecture      layout, software plan. Test plan.
• Developed      architecture (software and hardware) documents.
• Fabricated a      CAN selector test box using PCB and PIC.
• Developed      software code via a document plan.
• Tested the unit      per documented plan and stored results metrics in the Caliber repository.
• Retained all documentation      in the Caliber repository.
• Finishing      installation of solution in the manufacturing plant.

Results: The unit was tested and qualified on time and within budget per company standard: vibration, temperature, and functionality installed in the field.  The unit was able to be excepted and deployed in the field.

 Programming:  C#,C, C++, Java, Control Logic, VB, HTML, PHP, MySQL, Verilog, VHDL.

Embedded: PIC, security system using a WC16 micro-controller (Xilinx Spartan2(E)) FPGA; 6713 DSK board with DSP for DTMF; HC12 microprocessor to interface CAN to RS232; SB Computer for ID and tag reading, armature testing; PLC assembly line control.

Experience & Certification:  TFS, VxWorks 6.9 and Workbench 3.3, Visual Studio 2008/2010/2019,  UNIX, Linux, NetBeans IDE,  Pass 1000, CAN Analyzer, multi-meter, oscilloscope; Matlab, Statemate, Lotus Notes, Microsoft products, Adobe Acrobat Professional, AutoCAD, Allen Bradley PLC.

Hardware experience:  i7540D Ethernet to CAN converter, Adam 6060, Atmel AVR processor, Atom processor, CAN bus, 1553 bus, 485 utility bus, TCP/IP, RS232, SB CPU, RISC, and CISC architectures, EPLARS, SINCGARS, JAGUARS, GPS (Global Positioning System).

Administration: Talent Management System, Caliber RM, SAP, Test Procedures and Results, Travel Reports, Status Reports, Flow Diagrams, Trouble Reports, Requirements Design Document (RDD), Software Design Document (SDD), DOORS (Database Object-Oriented Requirements), PIFS (Prime Item Development Specification), Familiar with CMMI (Capability Maturity Model Integration); Interface control documents (ICDs).