2. The integration architecture of claim 1 , wherein said firmware component further comprises: a plurality of connector components configured to connect said firmware component to an external requirements system database, an external repository database and the revision control repository database; a design artifacts component that manages files, properties, analyses, design and test data for a project design; a model component that manages an architecture framework and software based models; a code component that manages a collection of files to convert software files from a human readable form to a computer executable form; a working files component that manages properties and files including configuration files, libraries, settings and files needed to generate executable files; and a burn component for managing properties and files for executable files used to embed firmware code onto a programmable device.
2. The integration architecture of claim 1 , wherein said firmware component further comprises: a plurality of connector components configured to connect said firmware component to an external requirements system database, an external repository database and the revision control repository database; a design artifacts component that manages files, properties, analyses, design and test data for a project design; a model component that manages an architecture framework and software based models; a code component that manages a collection of files to convert software files from a human readable form to a computer executable form; a working files component that manages properties and files including configuration files, libraries, settings and files needed to generate executable files; and a burn component for managing properties and files for executable files used to embed firmware code onto a programmable device. 3. The integration architecture of claim 2 , wherein said model component is configured to manage SysML or UML models.