The security of software applications is a major concern, especially for information owners, software developers and users. Increasingly, these stakeholders need to be confident that the software applications being developed are secure and can be trusted when used in the intended environment. However, a problem exists in terms of how to confidently address the security of software applications in order to protect the information to be stored, processed and transmitted by them, thereby increasing their associated levels of trust. The purpose of this paper is therefore to address some key aspects relating to the security and trustworthiness of a software application functioning within the intended environment. These key aspects include those relating to the security controls implemented and installed by the software developers and those involving the actual usage of the security controls implemented.
Small software companies make for the majority of software companies around the world, but their software development processes are often not as clearly defined and structured as in their larger counterparts. Especially the test process is often the most neglected part of the software process. This contribution analyses the software testing process in a small South African IT company, here called X, to determine the problems that currently cause it to deliver software fraught with too many defects. The dings of a survey conducted with all software developers in company X are discussed, and several typical problems are identified. Solutions to those (or similar) problems often already exist, but a major part of the problem addressed in this contribution is the unawareness, or unfamiliarity, of many small-industrial software developers and IT managers as far as the scientific literature on software science and engineering, and especially in our case: software testing, is concerned. We also discuss two prevalent test process improvement models that can be used to reason about the possibilities of process improvement. This contribution is an extended and revised summary of a longer project report  which can be obtained from the corresponding author of this article upon request.
In this paper, we discuss the advantages of using formal medical ontologies to enhance health information systems. In particular, we consider the suitability of the medical ontology Snomed CT for enhancing a health information system developed in the OpenMRS framework. We propose ways in which Snomed CT can be linked to an OpenMRS application, based on our experience of extracting a module of Snomed CT for tuberculosis.
Donor funds are available for treatment of many diseases such as HIV. However, privacy constraints make it hard for donor organisations to verify that they have not sponsored the same patient twice - or sponsored a patient whose treatment was also sponsored by another donor.
This paper presents a protocol based on digital cash that enables donor organisations to obtain a proof (in the form of an e-coin) from healthcare providers for patients such a provider claims to have treated. These coins are distributed to patients at the beginning of a funding cycle.
The major challenge is to issue a unique coin to a patient - even if the coin is reissued. This is achieved without giving anyone access to a national database of identities; all databases contain effectively concealed information. Reissued coins will be identical to previous coins with a probability that can be decided beforehand.