Coexisting graphical and structured textual representations of requirements
dc.contributor.author | Beckmann, Martin | |
dc.contributor.author | Reuter, Christian | |
dc.contributor.author | Vogelsang, Andreas | |
dc.date.accessioned | 2018-03-10T16:04:59Z | |
dc.date.available | 2018-03-10T16:04:59Z | |
dc.date.issued | 2018 | |
dc.description.abstract | [Context & motivation] Many requirements documents contain graphical and textual representations of requirements side-byside. These representations may be complementary but oftentimes they are strongly related or even express the same content. [Question/problem] Since both representation may be used on their own, we want to nd out why and how a combination of them is used in practice. In consequence, we want to know what advantages such an approach provides and whether challenges arise from the coexistence. [Principal ideas/results] To get more insights into how graphical and textual representations are used in requirements documents, we conducted eight interviews with stakeholders at Daimler. These stakeholders work on a system that is speci ed by tabular textual descriptions and UML activity diagrams. The results indicate that the di erent representations are associated with di erent activities. [Contribution] Our study provides insights into a possible implementation of a speci cation approach using mixed representations of requirements. We use these insights to make suggestions on how to apply the approach in a way that pro ts from its advantages and mitigates potential weaknesses. While we draw our conclusions from a single use case, some aspects might be applicable in general. | en |
dc.identifier.isbn | 978-3-319-77242-4 | |
dc.identifier.isbn | 978-3-319-77243-1 | |
dc.identifier.uri | https://depositonce.tu-berlin.de/handle/11303/7501 | |
dc.identifier.uri | http://dx.doi.org/10.14279/depositonce-6721 | |
dc.language.iso | en | en |
dc.relation.ispartof | 10.14279/depositonce-7546 | |
dc.rights.uri | http://rightsstatements.org/vocab/InC/1.0/ | en |
dc.subject.ddc | 004 Datenverarbeitung; Informatik | en |
dc.subject.ddc | 620 Ingenieurwissenschaften und zugeordnete Tätigkeiten | en |
dc.subject.other | model-driven software specification | en |
dc.subject.other | graphical models | en |
dc.subject.other | requirements documents | en |
dc.subject.other | UML activity diagram | en |
dc.title | Coexisting graphical and structured textual representations of requirements | en |
dc.title.subtitle | insights and suggestions | en |
dc.type | Conference Object | en |
dc.type.version | acceptedVersion | en |
dcterms.bibliographicCitation.doi | 10.1007/978-3-319-77243-1_16 | en |
dcterms.bibliographicCitation.originalpublishername | Springer | en |
dcterms.bibliographicCitation.originalpublisherplace | Berlin, Heidelberg | en |
dcterms.bibliographicCitation.pageend | 280 | en |
dcterms.bibliographicCitation.pagestart | 265 | en |
dcterms.bibliographicCitation.proceedingstitle | Requirements Engineering: Foundation for Software Quality | en |
dcterms.bibliographicCitation.volume | 2018 | en |
tub.accessrights.dnb | domain | en |
tub.affiliation | Fak. 4 Elektrotechnik und Informatik::Inst. Telekommunikationssysteme::FG IT-basierte Fahrzeuginnovationen | de |
tub.affiliation.faculty | Fak. 4 Elektrotechnik und Informatik | de |
tub.affiliation.group | FG IT-basierte Fahrzeuginnovationen | de |
tub.affiliation.institute | Inst. Telekommunikationssysteme | de |
tub.publisher.universityorinstitution | Technische Universität Berlin | en |
tub.series.issuenumber | 10753 | en |
tub.series.name | Lecture Notes in Computer Science | en |