Example of your knowledge and experience with full life cycle 
software development

I am experienced in and comfortable with working on a product 
through its whole life cycle.

My role in the current project, benefits administration automation, 
includes inception, architecture and design. Another example of a 
project when I worked on new development (at SDRC): my involvement 
started with analyzing marketing materials. Later, I led a small 
team developing requirements for the prototype of a complex 
distributed instrument management system.

My qualifications and experience include working on software 
requirements, systems architecture, design, implementation and 
testing. I have also worked in quality assurance, developing test 
plans and using automated testing suites. Most of my career was 
devoted to design and implementation phases. On a few occasions, I 
was also involved in post-development stages (maintenance, and, 
occasionally, planned obsolescing).

For about a decade, I develop the systems strictly following 
object-oriented principles. During the last half of it, I am using 
UML as it evolved from the diagram notations introduced by OOD 
³amigos².

The first phase of analysis in my design work usually includes 
decomposition to create an adequate abstraction of the system 
(classes) and capture the major relations between the classes 
(represented in UML). The next iteration of design usually involves 
using a programming language. For about 10 years, it was mostly C++, 
and for the last 18 months ­ C#. Previously, and for most of 
embedded software development, it was C.

I am quite versed in usability and enjoy working on user interfaces. 
Lately, I developed an interface for a hand-held device controlling 
the teaching process for a robotics system (at FSI). It proved to 
significantly lower the operator error rate.

The most laborious part of the life cycle is the implementation 
(programming). Using the development suites (for a number of years, 
mostly, Microsoft Visual Studio; since early 2002 ­ Visual 
Studio.NET) and source control tools, programming became a highly 
collaborative activity. I am accustomed to frequent builds, and have 
experience in administering source control systems.