Co-designing DSL Quality Assurance Measures for and with Non-programming Experts
Domain-specific languages seek to provide domain guarantees that eliminate many errors allowed by general-purpose languages.
Still, a domain-specific language requires additional quality assurance measures to ensure that specifications behave as intended by the users.
However, some domains may have specific quality assurance measures (e.g., proofs, experiments, or case studies) with little tradition of using quality assurance measures customary to software engineering.
We investigate the possibility of accommodating such domains by conducting a workshop with 11 prospective users of a domain-specific language named MAL for the pension industry.
The workshop emphasised the need for supporting actuaries with new analytical tools for quality assurance and resulted in three designs: quantity monitors let users identify outlier behaviour, fragment debugging lets users debug with limited evaluative power, and debugging spreadsheets let users visualise, analyse, and remodel concrete calculations with an established domain tool.
Based on our experiences, we hypothesise that co-design workshops are a viable approach for DSLs in a similar situation.
Mon 18 OctDisplayed time zone: Central Time (US & Canada) change
10:50 - 12:10
|Co-designing DSL Quality Assurance Measures for and with Non-programming Experts|
Holger Borum IT University of Copenhagen, Christoph Seidl IT University of Copenhagen, Peter Sestoft IT University of CopenhagenDOI
|Integration of Modeling and Verification for System Model Based on KARMA Language|
Jie Ding Beijing Institute of Technology, Michel Reniers Eindhoven University of Technology, Jinzhi Lu EPFL, Guoxin Wang Beijing Institute of Technology, Lei Feng KTH, Dimitris Kiritsis EPFLDOI
|Differential-FORMULA: Towards a Semantic Backplane for Incremental Modeling|
Qishen Zhang Vanderbilt University, Daniel Balasubramanian Vanderbilt University, Tamas Kecskes Vanderbilt University, Janos Sztipanovits Vanderbilt UniversityDOI
|Discussion and summary|