The next generation of tactical equipment will include embedded trainers. The concept of embedded training is for a part of the tactical hardware, whether aircraft avionics, shipboard electronics, or ground-based electronics, to be used to provide training to an operator. The operator will be trained in a variety of tasks to enhance his proficiency in target recognition, equipment procedures, kill tactics and others. The requirements for the embedded trainer are specified in a contract systems specification. Embedding a trainer within tactical hardware poses new considerations in developing the tactical hardware. The embedded trainer requirements may dictate an interactive photo-based imagery to the digital map generator vendor and impose unique weight considerations for the mechanical design teams just to allow proper procedural or operations training. Since the embedded trainer is provided on tactical hardware, the tactical hardware vendors receive the requirements. Who should develop the embedded trainer, the tactical hardware developer or a training simulator manufacturer? If the tactical hardware developer builds the embedded trainer, he must understand the training requirements provided by the government training organization. If the simulator manufacturer develops the embedded trainer, he is faced with new concerns of limited memory and processor speed, tactical equipment weight restrictions, and ruggidized requirements. This paper will offer candidate criteria (Strap on vs. Embedded, host hardware to Mission Planning hardware commonality) to determine proper embedded training requirements, will address how technology advances like the Ada programming language will enhance the embedded training development and will present, from a lessons-learned viewpoint, the interfacing requirements between the tactical hardware and software and the embedded trainer software.