Tactics for Transformational Programming

This paper discusses the relationship between transformational programming and theorem proving. It illustrates the use of the theorem proving environment as a basis for a program construction tool DEBATE 1 (Deduction Based Transformational Environment) which is under construction in University College Dublin. Using a theorem proving framework directly would require the user to be familiar with theorem proving details. The tool user should only be concerned with transformational programming steps and not with theorem proving activities. Therefore a layer of transformational tactics are discussed and presented. These tactics consist of the application of theoremproving tactics. However, they ensure that the user’s only interaction with DEBATE are design decisions required within the transformational programming paradigm. The N Queens problem is used throughout the paper to demonstrate how the Isabelle theorem prover is adapted by a transformation tactic layer so that it may be used as a program construction tool

Building an IDE for the Calculational Derivation of Imperative Programs

In this paper, we describe an IDE called CAPS (Calculational Assistant for Programming from Specifications) for the interactive, calculational derivation of imperative programs. In building CAPS, our aim has been to make the IDE accessible to non-experts while retaining the overall flavor of the pen-and-paper calculational style. We discuss the overall architecture of the CAPS system, the main features of the IDE, the GUI design, and the trade-offs involved.Comment: In Proceedings F-IDE 2015, arXiv:1508.0338

Proving theorems by program transformation

In this paper we present an overview of the unfold/fold proof method, a method for proving theorems about programs, based on program transformation. As a metalanguage for specifying programs and program properties we adopt constraint logic programming (CLP), and we present a set of transformation rules (including the familiar unfolding and folding rules) which preserve the semantics of CLP programs. Then, we show how program transformation strategies can be used, similarly to theorem proving tactics, for guiding the application of the transformation rules and inferring the properties to be proved. We work out three examples: (i) the proof of predicate equivalences, applied to the verification of equality between CCS processes, (ii) the proof of first order formulas via an extension of the quantifier elimination method, and (iii) the proof of temporal properties of infinite state concurrent systems, by using a transformation strategy that performs program specialization

Cultural Awareness and Change Management: Embracing the Benefits of Merging a Community College with a University in Atlantic Canada

The organizational merger of two post-secondary organizations is fraught with synergies and complications that lend themselves to positive and negative outcomes of the joining. The need for a consolidated credential pathway model that defined the academic and administrative authorities of the merged organization was required. The organizational improvement plan (OIP) reviews the historical context of Ocean Institute of Eastern University (OIEU) to uncover the cultural underpinnings of resistance that exhibited themselves. While blind resistance exists within almost every organization, including true ideological resistance, within the context of OIEU, most of the resistance is rooted in political resistance, where some feel they will lose their power base, status, and role within the organization. Leading an organization through change involving many systems, structures, and functions requires a humanistic leadership approach combining transformational and distributed leadership principles. Ownership of the change is realized through appreciative inquiry and Plan-Do-Study-Act cycles to encourage stakeholders the ability to own and effect change in the organization. As per Edgar Schein’s change model, leading through change will require the organization to unfreeze, learn new things, and re-freeze. This change process is fundamental to all organizational change models. It is specifically well-considered for OIEU, frozen in a three-decade position of two academic authorities. The OIP will propose a solution to address the dichotomy in credential pathways, thus enabling OIEU to realize its full potential within the post-secondary landscape

USTOPIA REQUIREMENTS THOUGHTS ON A USER-FRIENDLY SYSTEM FOR TRANSFORMATION OF PROGRAMS IN ABSTRACTO

Transformational programming is a program development method which is usually applied using 'pen and paper'. Since this requires a lot of clerical work (copying expressions, con- sistent substitution) which is tiresome and prone to error, some form of machine support is desirable. In this paper a number of systems are described that have already been built to this aim. Some of their shortcomings and limitations are identified. Based on experience with program transformation and transformation systems, a long list of features is given that would be useful in an 'utopian' transformation system. This list is presented using an orthogonal division of the problem area. A number of problems with the realisation of some aspects of our 'utopian' system are identified, and some areas for further research are indicated

Transformational maintenance by reuse of design histories

This thesis provides theory and procedures for modifying software artifacts implemented by a formal transformation process. Installing modifications requires knowing not only what transformations were applied (a derivation history) to construct the artifact, but also why the application sequence ensures that the artifact meets its specification. The derivation history and the justification are collectively called a design history. A Design Maintenance System (DMS), when provided with a formal change called a maintenance delta, revises a design history to guide construction of a new artifact. A DMS can be used to integrate a stream of deltas into a history, providing implementations as a side effect, leading to an incremental-evolution model for software construction.We provide a broadly applicable formal model of transformation systems in which specifications are performance predicates, subsuming the functional specifications which are traditional for transformation systems. Such performance predicates provide vocabulary used in the design history to describe the effect of applying sets of transformations.A nonprocedural, performance-goal-oriented Transformation Control Language (TCL) is defined to control navigation of the design space for a transformation system. Recording the execution of a TCL metaprogram directly provides a design history.A complete classification of, and representation for, the set of possible maintenance deltas is given in terms of the inputs defined by the transformation system model. Such deltas include not only specification changes, but also changes to implementation support technologies. Delta integration procedures for revising derivation histories given functional or support technology deltas are provided, based on rearranging the order of transformations in the design space. Building on these operations, integration procedures that revise the design history for each type of delta are described. An agenda-oriented TCL execution process dovetails smoothly with the integration procedures.Our DMS is compared to a number of other maintenance systems. By using an explicit delta and verified commutativity, our DMS often reuses transformations correctly when others fail

Just below the surface: developing knowledge management systems using the paradigm of the noetic prism

In this paper we examine how the principles embodied in the paradigm of the noetic prism can illuminate the construction of knowledge management systems. We draw on the formalism of the prism to examine three successful tools: frames, spreadsheets and databases, and show how their power and also their shortcomings arise from their domain representation, and how any organisational system based on integration of these tools and conversion between them is inevitably lossy. We suggest how a late-binding, hybrid knowledge based management system (KBMS) could be designed that draws on the lessons learnt from these tools, by maintaining noetica at an atomic level and storing the combinatory processes necessary to create higher level structure as the need arises. We outline the “just-below-the-surface” systems design, and describe its implementation in an enterprise-wide knowledge-based system that has all of the conventional office automation features

Military-connected students in higher education: A Canadian approach

Canadian military-connected students are adult learners who maintain a significant tie to the Canadian Armed Forces (CAF) and who enter higher education without the benefit of purposefully crafted academic and social supports. When CAF service members move from the collective nature of the military to individual pursuits in civilian society, transition difficulties occur. While there is a dearth of Canadian-specific research on military-connected students, the US context can help contextualize this higher education issue for a greater understanding of inclusion difficulties. Based on a transformative research paradigm, this organizational improvement plan (OIP) looks to provide a voice to this underrepresented group of leaners in order to lead to an organization-wide recognition of the heterogeneity of military-connected students. Enabled by a transformational leadership approach at the macro-level of University X and an adaptive approach at the meso- and micro-levels, the OIP presents an interconnected implementation plan. The problem of practice (PoP) that drives the investigation is aimed at recognizing the diverse needs of military-connected students and cultivating a sustainable positive learning environment. The OIP will employ successive quality improvement cycles of a plan-do-study-act strategy to address the PoP. The desired outcome of the OIP is to link military-connected students to a supporting learning environment, peer support, and the local community through a harmonized institutional approach across all levels of University X

Extensional and Intensional Strategies

This paper is a contribution to the theoretical foundations of strategies. We first present a general definition of abstract strategies which is extensional in the sense that a strategy is defined explicitly as a set of derivations of an abstract reduction system. We then move to a more intensional definition supporting the abstract view but more operational in the sense that it describes a means for determining such a set. We characterize the class of extensional strategies that can be defined intensionally. We also give some hints towards a logical characterization of intensional strategies and propose a few challenging perspectives