Engineering software analysis into manuals software technical drawings and How to further understand formal writings engineered into these Manuals and so forth design test code or so to say trial and error phase for the separated model design code test for the integrated design model.I would like to touch base on some factual evidence of the engineering principals of the past.I have run into an old MIT school picture and work on some of the grade designs the mathematics in those days 1800s where as so simple X2+X1=Algebra seemed so simple.I do not think it is  some to be as scary are all in the kitchen mit after all and the top of the education portal.Some quotions programmed by people are necessary.Why buy a computer if you do not own software.Some software for Buildings schematics alone are in the billions.Because the person owning them has a course of learning.Yes even though the building could be studied.Some costing more than most buildings.What i would like to see some of the histories of old come into reality so people in a friendly way could engineer software.After all typically the computer knows what it needs.Acceptance inputs for software.Whether you feel as fiber optic wire or farmer model.Yes acceptance software an educational farm of software engineers test and case.As for the code involved it should lay in the offense.A superior notion giving as it where a sheep software or cow or horse or chicken always giving.not receiving information.Not receiving Then defense is receiving Psycholinguistics Linguistics Receiving non receiviBut first let us see how the programmer feels separate from the imperative.Quality substance implementation.Optimizing software into a next generation of thought while working in a network that intermin within itself as so coded software life cycle of instruments find errors in codes evolving software higher executing adaptation correction equal to the general rule great for implementing.