Show simple item record

dc.contributor.advisorPerry, Dewayne E.en
dc.contributor.committeeMemberBias, Randolphen
dc.contributor.committeeMemberJulien, Christineen
dc.contributor.committeeMemberKim, Miryungen
dc.contributor.committeeMemberKhurshid, Sarfrazen
dc.creatorWright, Hyrum Kurten
dc.date.accessioned2012-07-12T14:40:29Zen
dc.date.accessioned2017-05-11T22:25:48Z
dc.date.available2012-07-12T14:40:29Zen
dc.date.available2017-05-11T22:25:48Z
dc.date.issued2012-05en
dc.date.submittedMay 2012en
dc.identifier.urihttp://hdl.handle.net/2152/ETD-UT-2012-05-5465en
dc.descriptiontexten
dc.description.abstractRelease processes form an important, if overlooked, part of the complete software development life cycle. Many organizations implement the roles of release engineering and release management in different ways, with a wide amount of variance within the software industry. Ill-designed processes can lead to a higher number of software faults and costly delays. Failures in release engineering can have negative implications, yet the causes of release process failures are not well understood within in the software engineering research community. This dissertation addresses the questions of what the common release process structure is, what the common failure modes are, and how organizations recover from and prevent these failures. We address these questions through a series of case studies with practicing release engineers at commercial software companies. The live interviews with these individual companies provide insight into the state of the practice in release engineering today across a broad spectrum of organization and software domains. The results of these studies indicate four areas of theory in release engineering which future researchers can probe in more depth. These areas center around process organization, social causes of release process failure, the relationship between software architecture and the release process, and how organizations attempt to improve release processes. For practicing release engineers, these results show that most organizations would benefit from three primary improvements: increased process automation, more modular software design, and improved organizational communication and support of release engineering groups. By implementing these improvements, software development companies and the release engineering processes they support will avoid the most common process failures in this critical phase of the software life cycle.en
dc.format.mimetypeapplication/pdfen
dc.language.isoengen
dc.subjectRelease engineeringen
dc.subjectSoftware release managementen
dc.titleRelease engineering processes, their faults and failuresen
dc.description.departmentElectrical and Computer Engineeringen
dc.type.genrethesisen
dc.date.updated2012-07-12T14:40:34Zen
dc.identifier.slug2152/ETD-UT-2012-05-5465en


Files in this item

FilesSizeFormatView

There are no files associated with this item.

This item appears in the following Collection(s)

Show simple item record