Show simple item record

dc.contributor.advisorMichael, J. Bret
dc.contributor.authorRiehle, Richard D.
dc.dateSeptember 2008
dc.date.accessioned2012-08-22T15:32:07Z
dc.date.available2012-08-22T15:32:07Z
dc.date.issued2008-09
dc.identifier.urihttp://hdl.handle.net/10945/10379
dc.description.abstractNew engineering disciplines are emerging in the late Twentieth and early Twenty-first Century. One such emerging discipline is software engineering. The engineering community at large has long harbored a sense of skepticism about the validity of the term software engineering. During most of the fifty-plus years of software practice, that skepticism was probably justified. Professional education of software developers often fell short of the standard expected for conventional engineers; software practice seemed to be a "hit or miss" approach; and the available knowledge, tools, and language designs were not sufficiently mature to support an engineering model for software practice. Much progress has occurred in recent years, due to improved tools and languages along with a better ways of reasoning about and designing software products. This progress has contributed to the increase in success in the way software is developed and managed. However, even with a growing number of software successes, there are still enough horror-stories to reinforce the skepticism of the larger engineering community. Those skeptics continue to ask the reasonable question, "Where is the engineering in software engineering?" The primary contribution of this dissertation is to establish a foundation for answering the question at the end of the previous paragraph. Another contribution is a foundation for answering that same question for other emerging engineering disciplines. We call this foundation a context. The context is derived from: a study of conventional engineering, a review of contemporary software practices, recent advances in software engineering and computer science, and analysis of the relationships between those four concerns. This engineering context for software engineering includes two chapters on the topic of engineering. It opens the door to a dialogue about both the philosophical and practical concerns of emerging engineering disciplines. It also includes chapters mapping the engineering context to both current and expected trends in software engineering practices.en_US
dc.description.urihttp://archive.org/details/anengineeringcon1094510379
dc.format.extentxvi, 121 p. ; 28 cm.en_US
dc.publisherMonterey, California. Naval Postgraduate Schoolen_US
dc.rightsApproved for public release, distribution unlimiteden_US
dc.subject.lcshAgile software developmenten_US
dc.titleAn engineering context for software engineeringen_US
dc.contributor.departmentComputer Science
dc.subject.authorSoftware Engineeringen_US
dc.subject.authorProgrammingen_US
dc.subject.authorComputer Softwareen_US
dc.subject.authorEngineeringen_US
dc.subject.authorSoftware Processen_US
dc.subject.authorPre-Conditionsen_US
dc.subject.authorPost-Conditionsen_US
dc.subject.authorInvariantsen_US
dc.subject.authorAdaen_US
dc.subject.authorRisk Managementen_US
dc.subject.authorPredictable Outcomeen_US
dc.subject.authorLinguistic Continuityen_US
dc.subject.authorSoftware Physicsen_US
dc.subject.authorDesign Metricsen_US
dc.subject.authorDesign to Tolerancesen_US
etd.thesisdegree.namePh.D in Software Engineeringen_US
etd.thesisdegree.levelDoctoralen_US
etd.thesisdegree.disciplineSoftware Engineeringen_US
etd.thesisdegree.grantorNaval Postgraduate Schoolen_US


Files in this item

Thumbnail

This item appears in the following Collection(s)

Show simple item record