Satisfactory communication between developers and stake holders during system development is important to ensure satisfactory outcomes for those investing in the system. Unfortunately, communication is hampered when the two parties do not speak in the same language. Here, we identify and advocate the use of self-definition to alleviate some of these problems in certain types of systems where a formal or semiformal language is provided by the system for the user. Selfdefinition will be defined as describing the user's system in the language intended for use by the user. This will require effort by the developer to use the user's language but we will hypothesise that the systems so specified have advantages of otherwise specified systems, for both the developer and the user. To support our hypotheses we will draw on well-known examples of what we call "self-definition" from mathematics, computer science and other areas.
Conference proceeding
Self-definition for software development
Proceedings of Software Engineering Workshop (SEW), 2012 35th Annual IEEE, pp.52-61
Proceedings of Software Engineering Workshop (SEW), 2012 35th Annual IEEE (Heraclion, Crete, Greece, 12-13 October)
2012
Metrics
24 Record Views
UN Sustainable Development Goals (SDGs)
This output has contributed to the advancement of the following goals:
Source: InCites
Abstract
Details
- Title
- Self-definition for software development
- Creators
- Barry Wilks - Southern Cross UniversityPaul Bailes - University of Queensland
- Publication Details
- Proceedings of Software Engineering Workshop (SEW), 2012 35th Annual IEEE, pp.52-61
- Conference
- Proceedings of Software Engineering Workshop (SEW), 2012 35th Annual IEEE (Heraclion, Crete, Greece, 12-13 October)
- Publisher
- IEEE Computer Society Conference Publishing Services; Los Alamitos, CA
- Number of pages
- 52-61
- Identifiers
- 1546; 991012822159702368
- Academic Unit
- School of Business and Tourism; Faculty of Business, Law and Arts
- Resource Type
- Conference proceeding