Letting software engineers do software engineering or freeing software engineers from the shackles of documentation
Benson H. Scheff, Tom Georgon · 1988
9 This is a paper about -Achieving higher software l Productivity l Quality -Minimizing software risk Underlying thesis l $3OB worth of DoD software needs for the early 1990's l Not enough software engineers to fill these needs l Software engineers must be more efficient l Software engineering documentation is a good candidate for study -High cost -Pervasive activity -Strong repetitive elements Engineering documentation is an integral part of the DOD software process l Shows technical progress .Deiscrik software product l Facilitates subsequent product maintenance l Serves as the primary mechanism for technical communication l Often transitions from internal documentation to customer deliverables