How to select a suitable tool for a software development project: three case studies and the lessons learned
dc.contributor.author | Kibanov, Mark | |
dc.contributor.author | Erdmann, Dominik J. | |
dc.contributor.author | Atzmueller, Martin | |
dc.contributor.editor | Wagner, Stefan | |
dc.contributor.editor | Lichter, Horst | |
dc.date.accessioned | 2018-10-24T10:00:13Z | |
dc.date.available | 2018-10-24T10:00:13Z | |
dc.date.issued | 2013 | |
dc.description.abstract | This paper describes a framework for evaluating and selecting suitable software tools for a software project, which is easily extendable depending on needs of the project. For an evaluation, we applied the presented framework in three different projects. These projects use different software development methods (from classical models to Scrum) in different environments (industry and academia). We discuss our experiences and the lessons learned. | en |
dc.identifier.isbn | 978-3-88579-609-1 | |
dc.identifier.pissn | 1617-5468 | |
dc.identifier.uri | https://dl.gi.de/handle/20.500.12116/17392 | |
dc.language.iso | en | |
dc.publisher | Gesellschaft für Informatik e.V. | |
dc.relation.ispartof | Software Engineering 2013 - Workshopband | |
dc.relation.ispartofseries | Lecture Notes in Informatics (LNI) - Proceedings, Volume P-215 | |
dc.title | How to select a suitable tool for a software development project: three case studies and the lessons learned | en |
dc.type | Text/Conference Paper | |
gi.citation.endPage | 424 | |
gi.citation.publisherPlace | Bonn | |
gi.citation.startPage | 415 | |
gi.conference.date | 26. Februar-1. März 2013 | |
gi.conference.location | Aachen | |
gi.conference.sessiontitle | Regular Research Papers |
Dateien
Originalbündel
1 - 1 von 1