@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}
}
@book{BeckmannHildebrandJascheketal.2019,
  author    = {Beckmann, Tom and Hildebrand, Justus and Jaschek, Corinna and Krebs, Eva and L{\"o}ser, Alexander and Taeumel, Marcel and Pape, Tobias and Fister, Lasse and Hirschfeld, Robert},
  title     = {The font engineering platform},
  number    = {128},
  publisher = {Universit{\"a}tsverlag Potsdam},
  address   = {Potsdam},
  isbn      = {978-3-86956-464-7},
  issn      = {1613-5652},
  doi       = {10.25932/publishup-42748},
  url       = {http://nbn-resolving.de/urn:nbn:de:kobv:517-opus4-427487},
  publisher      = {Universit{\"a}t Potsdam},
  pages     = {viii, 115},
  year      = {2019},
  abstract  = {Creating fonts is a complex task that requires expert knowledge in a variety of domains. Often, this knowledge is not held by a single person, but spread across a number of domain experts. A central concept needed for designing fonts is the glyph, an elemental symbol representing a readable character. Required domains include designing glyph shapes, engineering rules to combine glyphs for complex scripts and checking legibility. This process is most often iterative and requires communication in all directions. This report outlines a platform that aims to enhance the means of communication, describes our prototyping process, discusses complex font rendering and editing in a live environment and an approach to generate code based on a user's live-edits.},
  language  = {en}
}
@article{FreudenbergIngallsFelgentreffetal.2015,
  author    = {Freudenberg, Bert and Ingalls, Dan and Felgentreff, Tim and Pape, Tobias and Hirschfeld, Robert},
  title     = {SqueakJS A Modern and Practical Smalltalk that Runs in Any Browser},
  series = {ACM SIGPLAN notices},
  volume    = {50},
  journal   = {ACM SIGPLAN notices},
  number    = {2},
  publisher = {Association for Computing Machinery},
  address   = {New York},
  issn      = {0362-1340},
  doi       = {10.1145/10.1145/2661088.2661100},
  pages     = {57 -- 66},
  year      = {2015},
  abstract  = {We report our experience in implementing SqueakJS, a bitcompatible implementation of Squeak/Smalltalk written in pure JavaScript. SqueakJS runs entirely in theWeb browser with a virtual file system that can be directed to a server or client-side storage. Our implementation is notable for simplicity and performance gained through adaptation to the host object memory and deployment leverage gained through the Lively Web development environment. We present several novel techniques as well as performance measurements for the resulting virtual machine. Much of this experience is potentially relevant to preserving other dynamic language systems and making them available in a browser-based environment.},
  language  = {en}
}