Conceptual Frameworks for SIA Revisited: a cumulative effects study on lead contamination and economic change

This article trials three conceptual frameworks on an Australian case study of a small remote city suffering lead contamination, with cumulative effects from concurrent economic change due to downsizing in the mining industry. It interprets the usefulness of these frameworks, and explores two questions: can they apply to circumstances other than project assessment, and what are their relative merits as guides to SIA? All the frameworks reviewed can be used in non-project and cumulative SIA, although, if they had been used to predict the impacts in our case study, we may easily have been misled as to the resilience of the community. Choosing among these frameworks becomes a matter personal preference: each has different merits.

An approach to specifying software frameworks

A framework is a reusable design that requires software components to function. To instantiate a framework, a software engineer must provide the software components required by the framework. To do this effectively, the framework-component interfaces must be specified so the software engineer knows what assumptions the framework makes about the components, and so the components can be verified against these assumptions. This paper presents an approach to specifying software frameworks. The approach involves the specification of the framework’s syntax, semantics, and the interfaces between the framework and its components. The approach is demonstrated with a simple case study.

Impact of specialised first-episode psychosis treatment on suicide following initial presentation to mental health services: Retrospective cohort study

Background: Suicide risk in psychosis peaks early in the course, however little is known about the effect on rates of suicide of specialised first-episode psychosis (FEP) programs.