Introducing Morphit, a new type of spreadsheet technology
@article{Hawkins2014IntroducingMA, title={Introducing Morphit, a new type of spreadsheet technology}, author={Ted Hawkins and Andrew Lemon and Alec Gibson}, journal={ArXiv}, year={2014}, volume={abs/1401.7799} }
This paper describes a new type of spreadsheet which mitigates the errors caused by incorrect range referencing in formulae. This spreadsheet is composed of structured worksheets called tables which contain a hierarchical organization of fields. Formulae are defined at the field-level removing the need for positional references. In addition, relationships can be defined between fields in tables, allowing data to be modeled rather than simply processed and providing a re-usable framework for…
2 Citations
The 'lish': a data model for grid free spreadsheets
- Computer Science
- 2019
A “lish calculus” is developed, an extension to vector arithmetic for hierarchical structures that provides a concise notation for calculations with lishes that simplifies the usual spreadsheet formula expressions, and enables the machine to interpret them consistently with the context in which they are located.
Wide, long, or nested data? Reconciling the machine and human viewpoints
- Computer Science
- 2018
A new data model is proposed, the “lish”, which supports a spreadsheet-like flexibility of layout, while capturing sufficient structure to facilitate processing, and demonstrates how it might help users resolve the tension between the two forms.
References
SHOWING 1-10 OF 24 REFERENCES
Detecting Errors in Spreadsheets
- EducationArXiv
- 2008
The paper presents two complementary strategies for identifying errors in spreadsheet programs, grounded on the assumption that spreadsheets are software, albeit of a different nature than conventional procedural software.
In Search of a Taxonomy for Classifying Qualitative Spreadsheet Errors
- BusinessArXiv
- 2011
A taxonomy for categorizing qualitative errors in spreadsheet models that offers a framework for evaluating the readiness of a spreadsheet model before it is released for use by others in the organization is proposed.
Revising the Panko-Halverson taxonomy of spreadsheet errors
- BusinessDecis. Support Syst.
- 2010
Spreadsheets - the Good, the Bad and the Downright Ugly
- EducationArXiv
- 2010
The author asserts that the use of automated spreadsheet development could markedly help in ensuring and demonstrating compliance with set of characteristics that a spreadsheet must possess and as "bad practice" another set that it must avoid.
Errors in Operational Spreadsheets
- EconomicsJ. Organ. End User Comput.
- 2009
This research addresses three questions about errors in operational spreadsheets: what is the aver age cell error rate, how does it differ among spreadsheets, and what types of errors are most prevalent.
Reducing Overconfidence in Spreadsheet Development
- EconomicsArXiv
- 2008
Two experiments in overconfidence in spreadsheet development are described, including a pilot study to determine the existence of overconfidence, and a manipulation to reduce overconfidence and errors.
Protecting Spreadsheets Against Fraud
- Computer ScienceArXiv
- 2008
This paper surveys the available means for fraud protection by contrasting approaches suitable for spreadsheets with those known from fraud protection for conventional software.
Managing Critical Spreadsheets in a Compliant Environment
- BusinessArXiv
- 2008
This paper summarises the key issues regarding the establishment and maintenance of control of Business Critical spreadsheets.
Training Gamble leads to Corporate Grumble?
- BusinessArXiv
- 2008
To date, only one technique, cell-by-cell code inspection, has been demonstrated to be effective, and further research is needed to determine the degree to which other techniques can reduce spreadsheet errors.
Documenting Problem-Solving Knowledge: Proposed Annotation Design Guidelines and their Application to Spreadsheet Tools
- Computer ScienceArXiv
- 2009
A 3-level model of annotation is presented and guidelines are proposed for the design of end-user programming environments supporting the explicit and literate annotation levels.