Michael J. McCann309 Roscoman WayAvondale PA 19311

Michael.J.McCann@Boeing.com

Objective: To be a project or lead engineer for integrating a system into an aircraft and to be a critical part of an engineering design team providing technical innovation and leadership skills.

EDUCATION

University of Delaware, Newark, DEBachelor's Degree: Electrical Engineering Minor: Mathematics Graduation: May 1998

Cornell University, Ithaca, NYMaster's Degree: Systems Engineering Expected Graduation: May 2017

EXPERIENCE

Software Requirements Engineer – Boeing, Philadelphia, PA Jun 1998 – presentWorked as the Technical Lead Engineer on the Boeing V-22 Osprey Avionics Operational Software Requirements Integrated Product Team overseeing a team of 15 engineers. Responsible for managing task assignments and ensuring technical accuracy of each team member’s work. Acted as Subject Matter Expert for V-22 Osprey Avionics Software which consists of Controls and Displays, Fault Processing, Sensors, Electronic Warfare, Flight Director and Guidance, Mission Management and Navigation functionality. Acted as point of contact with other V-22 teams including Marine, Air Force and foreign military customers, equipment, suppliers and other Boeing teams for Avionics Software issues and questions.

Developed detailed software requirements documents for avionics software and interface with remote terminals. Wrote integration, regression and formal qualification test procedures to ensure that the software was adhering to documented requirements. Performed lab testing to assist in problem investigation and analysis including analyzing MIL-STD-1553 and Ethernet bus data traffic. Performed flight test anomaly investigation to determine root cause of issues and to verify that the software was meeting specified requirements. Initiated numerous engineering software process improvements to reduce inefficiencies and improve software quality.

Worked as Subsystem Technical Lead Engineer on the Japan V-22, the initial V-22 foreign military sale, responsible for aircraft integration of the new intercom system, exportable UHF/VHF radios, and avionics and display software changes. Responsible for overseeing software sanitization to ensure all non-exportable software content is removed. Oversaw 20 teams with regards to technical, schedule and budget concerns for these subsystems. Lead daily standup meetings to discuss status and technical concerns.

Led agile software development team of 8 engineers for initial Japan V-22 avionics software release. Acted as agile scrum master by overseeing team's software development effort. Assisted in developing road map and processes for V-22 avionics software development for all future V-22 foreign military contracts.

Directed daily software issue meetings to determine criticality of reported defects. Facilitated staff and status meetings with engineering personnel including the Avionics Software team of 50 engineers.

Mentored less experienced engineers on the avionics team. Led team of engineers in root cause analysis of avionics software defects. Made recommendations and process changes to prevent future defects and ensure software quality.

Created and presented Software Differences Briefs to Marine and Air Force flight test and fleet pilots and maintainer community at bases in California, Florida, Maryland, New Mexico and North Carolina. Assisted in developing future software updates and content by meeting with Marine and Air Force customers and user communities.

Developed software requirements estimates for Marine, Air Force and foreign military customers. Oversaw avionics team task estimating for proposal preparation. Assisted in creating software development schedules. Performed earned value management tasks by monitoring and tracking schedule and cost performance for software teams.

Participated as Avionics software subject matter expert in Non-Advocate Review for Dutch CH-47 Chinook software processes. Made recommendations for improvements and presented findings to CH-47 leadership team.

Developed Crew Systems requirements which deal with pilot interface to the aircraft. Participated in pilot working groups to determine aircraft software functional design. Created detailed Crew Systems requirements to describe software behavior and pilot interface.

Flight Controls Engineer – Boeing, Philadelphia, PA Jun 1997 – Aug 1997, Jan 1998 –

Feb 1998Worked as a flight controls engineer intern on the Bell-Boeing 609 program. Created database using Microsoft Access to finalize and document the flight controls system electrical interfaces. Updated electrical schematic diagrams and flight controls interface control documents.

CAD Operator – Pennoni Associates, Inc., Philadelphia, PA Dec 1996 – Feb 1997Worked as a CAD operator in the electrical department. Prepared and updated schematic drawings for various clients, including Trump Taj Mahal, Educational Testing Services, and Lower Merion Township, Pennsylvania.

Research Assistant – University of Delaware, Newark, DE Jun 1996 – Aug 1996Worked with Dr. Gonzalo Arce of the electrical engineering department in developing a better algorithm for printing images on laser and ink jet printers. Developed research skills in an educational environment.

educational environment. aoisj;lkdjasd;fkjational environment.