@article{ReinTaeumelHirschfeld2017,
  author    = {Rein, Patrick and Taeumel, Marcel and Hirschfeld, Robert},
  title     = {Making the domain tangible},
  series = {Design Thinking Research},
  journal   = {Design Thinking Research},
  publisher = {Springer},
  address   = {New York},
  isbn      = {978-3-319-60967-6},
  doi       = {10.1007/978-3-319-60967-6_9},
  pages     = {171 -- 194},
  year      = {2017},
  abstract  = {Programmers collaborate continuously with domain experts to explore the problem space and to shape a solution that fits the users' needs. In doing so, all parties develop a shared vocabulary, which is above all a list of named concepts and their relationships to each other. Nowadays, many programmers favor object-oriented programming because it allows them to directly represent real-world concepts and interactions from the vocabulary as code. However, when existing domain data is not yet represented as objects, it becomes a challenge to initially bring existing domain data into object-oriented systems and to keep the source code readable. While source code might be comprehensible to programmers, domain experts can struggle, given their non-programming background. We present a new approach to provide a mapping of existing data sources into the object-oriented programming environment. We support keeping the code of the domain model compact and readable while adding implicit means to access external information as internal domain objects. This should encourage programmers to explore different ways to build the software system quickly. Eventually, our approach fosters communication with the domain experts, especially at the beginning of a project. When the details in the problem space are not yet clear, the source code provides a valuable, tangible communication artifact.},
  language  = {en}
}