Show simple item record

dc.contributor.authorALTETMEK, ALTUG
dc.contributor.authorLEWENHAGEN, FILIP
dc.date.accessioned2022-10-05T11:52:44Z
dc.date.available2022-10-05T11:52:44Z
dc.date.issued2022-10-05
dc.identifier.urihttps://hdl.handle.net/2077/73744
dc.description.abstractDue to DevOps being a fast emerging way of conducting a software development process, there are little to no research covering how the traceability of non-functional requirements is managed in these environments. We conducted an exploratory case study at an IT consultant company who had a team working with DevOps practices, interviewing the team and collecting observational data. The results showed that there were a lack of structure related to traceability and requirements. Every member of the team was open to changes that could be tailored to their current way of working, with an open mind to process changes and introduction to new tools to make their daily way of working easier and more structured.en
dc.language.isoengen
dc.subjectDevOpsen
dc.subjectNFRen
dc.subjectrequirementen
dc.subjecttraceabilityen
dc.titleA Closer Look Into Traceability Management of Non-Functional Requirements in a DevOps Environmenten
dc.title.alternativeAn Exploratory Case Studyen
dc.typetext
dc.setspec.uppsokTechnology
dc.type.uppsokM2
dc.contributor.departmentGöteborgs universitet/Institutionen för data- och informationsteknikswe
dc.contributor.departmentUniversity of Gothenburg/Department of Computer Science and Engineeringeng
dc.type.degreeStudent essay


Files in this item

Thumbnail

This item appears in the following Collection(s)

Show simple item record