Defining a Security-Oriented Evolution Scenario for the CoCoME Case Study
| dc.contributor.author | Pilipchuk, Roman | |
| dc.contributor.author | Seifermann, Stephan | |
| dc.contributor.author | Taspolatoglu, Emre | |
| dc.date.accessioned | 2017-09-26T20:08:19Z | |
| dc.date.available | 2017-09-26T20:08:19Z | |
| dc.date.issued | 2017 | |
| dc.description.abstract | Information systems are subject to continuous change. In order to conduct empirical research on methods for software evolution, CoCoME was developed as a community-driven case study system. It is, however, not suitable for the validation of security-related approaches, as neither security nor privacy have been addressed in any evolution scenario. We elicited 53 secu- rity requirements coming from law, security guidelines and known threats. In this paper, we present three out of twelve security requirement categories including one representative requirement and share our experience in building the foundation for a security-oriented evolution scenario. Researchers in the field of secure software evolution can validate their approaches using this future evolution scenario. | en |
| dc.identifier.pissn | 0720-8928 | |
| dc.identifier.uri | https://dl.gi.de/handle/20.500.12116/4699 | |
| dc.language.iso | en | |
| dc.publisher | Gesellschaft für Informatik e.V., Fachgruppe PARS | |
| dc.relation.ispartof | Softwaretechnik-Trends: Vol. 37, No. 2 | |
| dc.title | Defining a Security-Oriented Evolution Scenario for the CoCoME Case Study | en |
| gi.citation.endPage | 73 | |
| gi.citation.publisherPlace | Berlin | |
| gi.citation.startPage | 70 | |
| gi.conference.sessiontitle | 4th Collaborative Workshop on Evolution and Maintenance of Long-Living Software Systems (EMLS’17) |
Dateien
Originalbündel
1 - 1 von 1