Component Object Model

SHURE, INC. August 2005 – December 2006: Consulting Programmer:

Technical Lead Windows Development: COM, COM, nothing but COM, Visual C++ 7.1 and 8.0, Niles, IL.

Simulation and test. Developed the messages for communication to the hardware. Wrapped an existing hardware communications simulator in an MFC GUI and added the capability to represent various devices and frequency configurations. Built a simulator client which duplicated the functionality of existing and new hardware. This software looks just like a device and behaves the same way. The simulator and its client are fully functional models at the external messaging level. This is to support testing the communication protocols prior to delivery of the hardware. The new components, from project #2, recognize the new device, but still retain much of the behavior of the original components. The simulator client can also talk to existing hardware and can be used for automated test of the hardware if required.

Enhancements. Wrote a requirements document and an interface control document [ICD]. I built twelve new COM modules, but this was not new code, I was simply cloning the existing modules and refitting them for the new hardware. I reverse engineered the COM modules to produce the ICD. Built a top level COM drawing containing the software connections for the new system. Wrote a project development plan for the GUI component of this project. Developed a Microsoft project schedule for the GUI software development. The new COM modules are running and the simulator below shows up in the application as a valid and communicating device. Picture of COM diagram and little simulator front end.

Maintenance. Performed Software cost estimates for all defects. I used an exponential grid philosophy to produce the estimates. Wrote a software documentation specification, that is, a document to describe what does and does not need to be documented in their software. Performed bug fixes and new development in C++ and performed install shield builds. After doing estimates for all of the defects and enhancements, I created a software development plan containing a schedule of development. We created a phased software release and have made all releases, so far, on schedule. I wrote most of the code for the first two milestones. Lately, I have been more involved in managing since we have more activities to coordinate and we are integrating a number of parts and pieces.

[ Home ] [ Up ]