Senior staff software engineer

COVER NOTE

I wish to have contract or direct position within 3 hours of Fort Wayne as a software engineer.

I have extensive experience in embedded software and have authored many documents. I seriously enjoy the work. I am a quick study. I have a love of the problem environment.

Thank you and regards,

Aaron Quandt

RESUME

Aaron E. Quandt Senior Staff Software/Systems Engineer

7924 Buttermore Run Purdue University

Fort Wayne, In. 46804

E-mail: ************@*****.***

Home: 260-***-****

Cell: 260-***-****

Summary of Experience:

Real-time Embedded Software/ Systems Engineer

Over twenty years of real-time software engineering. Specific experience with jet engines, tanks, command control, electric motors, communication, navigation, flight management, electronic warfare software development. Includes five years of C, eight years of C++, one year and nine months SCADE, six years of assembly, and seven years of Ada. Various commercial-off-the-shelf real-time executives (RTEs). Software architect and technical lead on several projects.

Versed on various software development standards and methodologies. Authored or contributed to requirements specifications, design specifications, test plans, software development plans, and other DOD, MIL-STD, NASA, NSA, and DO-178B documents. Also developed software related parts of several systems documents. A few projects were CMM level 5 and CMMI level 3. Also worked on several commercial applications.

Methodologies followed included waterfall, spiral, and Agile.

Languages & Tools Operating Systems/Environments

Ada 7 years VxWorks 5.5 and 6.3, and

C 5 years other operating sys.

C++ 8 years TCP/IP, Ethernet, and

Rational Rose UML 1 1/2 years Mil. Std. 1553

Assembly language 6 years

SCADE 1 year and 9 mos.

DOORS requirements recording

Clearcase and SVN (Subversion)

I Logix Statemate

Documentation/ Design

DOD Std. 498, NSA, and DO-178B specifically:

System/ Subsystem Specifications (SSS)

System/ Subsystem Design Documents (SSDD)

Software Architecture Design Documents (SADD)

Software Requirements Specifications (SRS) and Design Documents (SDD)

Software Test Plans and Procedures (STP)

Software Development Plans, (SDP)

2014 to present Early retirement. Wrote several programs for myself but wish to go back to employment since I miss the environment and the challenges of a project.

2011 to 2013 Aero Engine Controls (AEC) part of Rolls Royce, Indianapolis, Indiana. – (Contract) Responsible for writing software for jet engine controls and testing. Worked there for 1 yr. and 9 mos. Used SCADE software. More of a data flow software program than object oriented software so that it could be more easily be tested (follow the data). Also wrote a little C code. The engine controls had two processors per engine, one active and one mirroring, and the pair talked to the other engine’s pair to compare controls. DO-178B level A.

2010 Sikorsky Aircraft, Stratford, Ct. – (Contract) Responsible for interface control document (ICD) specifying interfacing navigation database (airports, heliports, waypoints) with helicopter flight management software. Developing screen software for nearest airports, heliports, navigation aids, and waypoints using the navigation database. Using Rational Rose UML and Ada 95.

2007 to 2009 General Dynamics Land Systems, Sterling Heights, Mi. – (Contract) Continued as software architect for the Mounted Combat Systems Mission Equipment (MCSME) vehicle of the Future Combat Systems (FCS) Project (please see 8/2000 to 10/2005 below). Developing in C++ / Ada software for this variant specific Manned Ground Vehicle (MGV) of the Future Combat Systems Project (FCS). Architecture was 8 executables on 2 to 3 processors communicating over UDP/IP with each other and controlling the tank’s azimuth/elevation, its ammunition loading/unloading, its aiming, firing, fault management, and user interfacing. Coordinated with system’s engineering on requirements, hardware, and architecture, and wrote some basic component parts. Controlled some hardware at 1000 Hz and other threads were at human cadence (event driven). Future Combat Systems project was cancelled by DOD.

2005 to 2007 Fort Wayne In. - (Contract) Worked at ITT Space Systems Division for approx. 8 mos. Embedded satellite instrument software including design of earth command reception, validation, and instrument routing. Completed Software Requirements Specification and beginning preliminary design using Rose. Software in C++. Redirected serial channel devices onto UDP/IP under VxWorks 6.3.

2000 to 2005 General Dynamics Land Systems, Sterling Heights, Mi. – (Contract) Technical Software Lead for the Mounted Combat Systems (MCSME) vehicle of the Future Combat Systems (FCS) Project. Developing in C++ / Ada software for this variant specific Manned Ground Vehicle (MGV). It is a multi-year project and we were in the prototype stage. Using a component based architecture, our team demonstrated much of the vehicle’s anticipated functionality. With extensive use of Unified Modeling Language (UML) and programming patterns, the team had a versatile architecture with which to move forward. For visualization, we used Open Scene Graph and Open GL. Also responsible for scheduling and work task creation and completion. CMM level 5 organization.

3/2000 to 8/2000 EEIT, Inc. Sterling Heights, Mi. Started company of four engineers writing Statemate models through I-Logix, Inc., the authors of Statemate, for Daimler/ Chrysler. The models were state machines demonstrating the proposed operation of power windows, door locks, mirrors, seats, lights, and accessories on Chrysler vehicles. Completed as a known short-term venture (5 to 6 months), it was well received and successful.

1999 to 2000 General Dynamics Land Systems, Sterling Heights, Mi. (Contract) Software lead for enhancements to fire control software for Abrams M1A2 tank. Most of the work was done in Ada using Rational Apex. Responsible for design, code, and test of various changes to the fire control electronics unit (FCEU) of the tank. The FCEU is a two-processor unit communicating with the other units of the tank. The FCEU causes the turret and gun to move and fires the main gun. Also developed waypoint navigation editing software for tank’s display terminals. Software used client/ server model with event manager. All line-replaceable-units (LRUs) were Mil-Std 1553 remote terminals.

1998 to 1999 Rockwell International, Cedar Rapids, Ia. (Contract) Designed and coded flight management software. Wrote bridge protocol software between ground based data communications equipment (DCE) and communications satellite. Most of the work was done in Ada using Rational Apex with some C. Designed and wrote a throughput analysis tool showing CPU time on a per task basis.

1997 Command Systems, Fort Wayne, In. Designed C++ communications protocols for radios and interface drivers for Rockwell PLGR96+ GPS receiver. Wrote much of the Software Design Document for contract with Canadian Military. Platform was Windows 95. Used Watcom C++ compiler. Very object oriented design. Extensive use of inheritance. Technical liaison with Canadian customer.

1994 to 1997 Eaton Milwaukee, Wi. (Contract) Software project lead for control and display panel for distribution of electricity for Centurion fast attack submarine. Analyzed various LANS (including FDDI) for communicating commands and status messages between panel and up to 38 power transformer nodes. Used Motorola MC6360 communications processor HDLC (SDLC) communications over an optic LAN. System in the panel used multiple processors over VME bus and was also interfaced to laptop computer for diagnostic purposes. Used object oriented techniques closely following Schlear-Mellor and Rebecca Wirfs-Brock methods. Code written in C++ using both Borland and Microtek compilers. Used Visio drawing tool for class interface diagrams and object communication models and other software design drawings.

References Upon Request

Contact this candidate