| dc.contributor.author | ALTETMEK, ALTUG | |
| dc.contributor.author | LEWENHAGEN, FILIP | |
| dc.date.accessioned | 2022-10-05T11:52:44Z | |
| dc.date.available | 2022-10-05T11:52:44Z | |
| dc.date.issued | 2022-10-05 | |
| dc.identifier.uri | https://hdl.handle.net/2077/73744 | |
| dc.description.abstract | Due 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_US |
| dc.language.iso | eng | en_US |
| dc.subject | DevOps | en_US |
| dc.subject | NFR | en_US |
| dc.subject | requirement | en_US |
| dc.subject | traceability | en_US |
| dc.title | A Closer Look Into Traceability Management of Non-Functional Requirements in a DevOps Environment | en_US |
| dc.title.alternative | An Exploratory Case Study | en_US |
| dc.type | text | |
| dc.setspec.uppsok | Technology | |
| dc.type.uppsok | M2 | |
| dc.contributor.department | Göteborgs universitet/Institutionen för data- och informationsteknik | swe |
| dc.contributor.department | University of Gothenburg/Department of Computer Science and Engineering | eng |
| dc.type.degree | Student essay | |
