Thesis (M.S.)--Mississippi State University. Department of Computer Science. / Title from title screen. Includes bibliographical references.

In an orthogonally persistent programming system, data is treated in a manner independent of its persistence. This gives simpler semantics, allows the programmer to ignore details of long-term data storage and enables type checking protection mechanisms to operate over the entire lifetime of the data. The ultimate goal of persistent programming language research is to reduce the costs of producing software. The work presented in this thesis seeks to improve programmer productivity in the following ways: • by reducing the amount of code that has to be written to construct an application; • by increasing the reliability of the code written; and • by improving the programmer’s understanding of the persistent environment in which applications are constructed. Two programming techniques that may be used to pursue these goals in a persistent environment are type-safe linguistic reflection and hyper-programming. The first provides a mechanism by which the programmer can write generators that, when executed, produce new program representations. This allows the specification of programs that are highly generic yet depend in non-trivial ways on the types of the data on which they operate. Genericity promotes software reuse which in turn reduces the amount of new code that has to be written. Hyper-programming allows a source program to contain links to data items in the persistent store. This improves program reliability by allowing certain program checking to be performed earlier than is otherwise possible. It also reduces the amount of code written by permitting direct links to data in the place of textual descriptions. Both techniques contribute to the understanding of the persistent environment through supporting the implementation of store browsing tools and allowing source representations to be associated with all executable programs in the persistent store. This thesis describes in detail the structure of type-safe linguistic reflection and hyper-programming, their benefits in the persistent context, and a suite of programming tools that support reflective programming and hyper-programming. These tools may be used in conjunction to allow reflection over hyper-program representations. The implementation of the tools is described.

Knowing ‘what’ to build is an integral part of an Information System Development, and it is generally understood that this, which is known as Requirements, is achievable through a process of understanding, communication and management. It is currently maintained by the Requirements theorists that successful system design clarifies the interrelations between information and its representations. However, this belief can be shown to be based on flawed assumptions, as there are persistent reports of failures, indicating that there is a gap between the theory and the practice, and that this gap needs to be bridged. A year long in-depth case study of a project group, starting with their strategy announcement and ending with the commissioning system hand-over meeting, followed the group in their ‘doing’ of the Requirements. These mundane meetings were recorded and transcribed, forming a detailed data set of ‘what-is-done’ and ‘how-it-is-done’. The developed research approach adhesively maintained the practical situation, aiming to investigate and make sense of the here-and-now actions of the scoping and defining processes that were at work. The results of the investigation led the researcher to question previous beliefs and assumptions in Requirements, because of ambiguities that were uncovered, also because there was no sufficiently distinct process found that could assuredly be labelled as Requirements. This phenomenon evoked further questioning of “how strange?”, which triggered the testing of the validity of the Requirements theory. The second stage adapted an analysis framework on decision-making in order to reveal a causal connection between the actions found in the ‘doing’ and in the stocks of knowledge that form the Requirements theory. This phase analysed the operationalization of the theory to examine its commensurate, incommensurate and defective activities. The analysis revealed the existence of other dominant processes that affect the Requirements theory, leaving it underdetermined, with no true causal connections that can be established. This led to the inevitable conclusion that the current Information Systems thinking on Requirements is on the horns of a dilemma without any prospective resolution, because of the elliptical misalignment between the theoretical and the empirical worlds.