The application of metrics to industrial prototyping processes: An empirical study

A key problem in the development of information systems is understanding features of the development process. To this end, in recent years, considerable interest has been focused on modelling processes. In this paper, the results of an empirical investigation into the use of prototyping in information systems development is described. Nine prototyping processes across eight different sites of varying size were analysed and data relating to each process collected. The notation of Role Activity Diagrams (RADs) was used to capture each of the nine processes. Analysis of the interactions in each process revealed that the project manager interacted with the prototyper far more often in large developments than in small or medium-sized developments. However, significantly more interactions between the project manager and end-user were found in small-sized developments than for any other sized site. The study demonstrates how measures of business models can aid analysis of the process rather than the product and highlights the need for more empirical investigation into this and other facets of the development process. A number of lessons have been learnt from our analysis; these we also explain

Using Counts as Heuristics for the Analysis of Static Models

The upstream activities of software development are often viewed as both the most important, in terms of cost, and the yet the least understood, and most problematic, particularly in terms of satisfying customer requirements. Business process modelling is one solution that is being increasingly used in conjunction with traditional software development, often feeding in to requirements and analysis activities. In addition, research in Systems Engineering for Business Process Change, highlights the importance of modelling business processes in evolving and maintaining the legacy systems that support those processes. However, the major use of business process modelling, is to attempt to restructure the business process, in order to improve some given aspect, e.g., cost or time. This restructuring may be seen either as separate activity or as a pre-cursor to the development of systems to support the new or improved process. Hence, the analysis of these business models is vital to the improvement of the process, and as a consequence to the development of supporting software systems. Supporting this analysis is the focus of this paper. Business processes are typically described with static (diagrammatic) models. This paper proposes the use of measures (counts) to aid analysis and comparison of these static process descriptions. The proposition is illustrated by showing how measures can be applied to a commonly used process-modelling notation, Role Activity Diagrams (RADs). Heuristics for RADs are described and measures suggested which support those heuristics. An example process is used to show how a coupling measure can be used to highlight features in RADs useful to the process modeller. To fully illustrate the proposition the paper describes and applies a framework for the theoretical validation of the coupling measure. An empirical evaluation follows. This is illustrated by two case studies; the first based on the bidding process of a large telecommunications systems supplier, and the second a study of ten prototyping processes across a number of organisations. These studies found that roles of the same type exhibited similar levels of coupling across processes. Where roles did not adhere to tentative threshold values, further investigation revealed unusual circumstances or hidden behaviour. Notably, study of the prototyping roles, which exhibited the greatest variation in coupling, found that coupling was highly correlated with the size of the development team. This suggests that prototyping in large projects had a different process to that for small projects, using more mechanisms for communication. Hence, the empirical studies support the view that counts (measures) may be useful in the analysis of static process models

A framework for the simulation of structural software evolution

This is the author's accepted manuscript. The final published article is available from the link below. Copyright @ 2008 ACM.As functionality is added to an aging piece of software, its original design and structure will tend to erode. This can lead to high coupling, low cohesion and other undesirable effects associated with spaghetti architectures. The underlying forces that cause such degradation have been the subject of much research. However, progress in this field is slow, as its complexity makes it difficult to isolate the causal flows leading to these effects. This is further complicated by the difficulty of generating enough empirical data, in sufficient quantity, and attributing such data to specific points in the causal chain. This article describes a framework for simulating the structural evolution of software. A complete simulation model is built by incrementally adding modules to the framework, each of which contributes an individual evolutionary effect. These effects are then combined to form a multifaceted simulation that evolves a fictitious code base in a manner approximating real-world behavior. We describe the underlying principles and structures of our framework from a theoretical and user perspective; a validation of a simple set of evolutionary parameters is then provided and three empirical software studies generated from open-source software (OSS) are used to support claims and generated results. The research illustrates how simulation can be used to investigate a complex and under-researched area of the development cycle. It also shows the value of incorporating certain human traits into a simulation—factors that, in real-world system development, can significantly influence evolutionary structures

Impact of general practice endorsement on the social gradient in uptake in bowel cancer screening

This is a summary of independent research funded by the National Institute for Health. Research (NIHR)’s Programme Grants for Applied Research Programme (RP-PG-0609–10106

The third international stroke trial (IST-3) of thrombolysis for acute ischaemic stroke

<p>Abstract</p> <p>Background</p> <p>Intravenous recombinant tissue plasminogen activator (rt-PA) is approved for use in selected patients with ischaemic stroke within 3 hours of symptom onset. IST-3 seeks to determine whether a wider range of patients may benefit.</p> <p>Design</p> <p>International, multi-centre, prospective, randomized, open, blinded endpoint (PROBE) trial of intravenous rt-PA in acute ischaemic stroke. Suitable patients must be assessed and able to start treatment within 6 hours of developing symptoms, and brain imaging must have excluded intracerebral haemorrhage. With 1000 patients, the trial can detect a 7% absolute difference in the primary outcome. With3500 patients, it can detect a 4.0% absolute benefit & with 6000, (mostly treated between 3 & 6 hours), it can detect a 3% benefit.</p> <p>Trial procedures</p> <p>Patients are entered into the trial by telephoning a fast, secure computerised central randomisation system or via a secure web interface. Repeat brain imaging must be performed at 24–48 hours. The scans are reviewed 'blind' by expert readers. The primary measure of outcome is the proportion of patients alive and independent (Modified Rankin 0–2) at six months (assessed via a postal questionnaire mailed directly to the patient). Secondary outcomes include: events within 7 days (death, recurrent stroke, symptomatic intracranial haemorrhage), outcome at six months (death, functional status, EuroQol).</p> <p>Trial registration</p> <p>ISRCTN25765518</p

Effects of antiplatelet therapy after stroke due to intracerebral haemorrhage (RESTART): a randomised, open-label trial

BACKGROUND: Antiplatelet therapy reduces the risk of major vascular events for people with occlusive vascular disease, although it might increase the risk of intracranial haemorrhage. Patients surviving the commonest subtype of intracranial haemorrhage, intracerebral haemorrhage, are at risk of both haemorrhagic and occlusive vascular events, but whether antiplatelet therapy can be used safely is unclear. We aimed to estimate the relative and absolute effects of antiplatelet therapy on recurrent intracerebral haemorrhage and whether this risk might exceed any reduction of occlusive vascular events. METHODS: The REstart or STop Antithrombotics Randomised Trial (RESTART) was a prospective, randomised, open-label, blinded endpoint, parallel-group trial at 122 hospitals in the UK. We recruited adults (≥18 years) who were taking antithrombotic (antiplatelet or anticoagulant) therapy for the prevention of occlusive vascular disease when they developed intracerebral haemorrhage, discontinued antithrombotic therapy, and survived for 24 h. Computerised randomisation incorporating minimisation allocated participants (1:1) to start or avoid antiplatelet therapy. We followed participants for the primary outcome (recurrent symptomatic intracerebral haemorrhage) for up to 5 years. We analysed data from all randomised participants using Cox proportional hazards regression, adjusted for minimisation covariates. This trial is registered with ISRCTN (number ISRCTN71907627). FINDINGS: Between May 22, 2013, and May 31, 2018, 537 participants were recruited a median of 76 days (IQR 29-146) after intracerebral haemorrhage onset: 268 were assigned to start and 269 (one withdrew) to avoid antiplatelet therapy. Participants were followed for a median of 2·0 years (IQR [1·0- 3·0]; completeness 99·3%). 12 (4%) of 268 participants allocated to antiplatelet therapy had recurrence of intracerebral haemorrhage compared with 23 (9%) of 268 participants allocated to avoid antiplatelet therapy (adjusted hazard ratio 0·51 [95% CI 0·25-1·03]; p=0·060). 18 (7%) participants allocated to antiplatelet therapy experienced major haemorrhagic events compared with 25 (9%) participants allocated to avoid antiplatelet therapy (0·71 [0·39-1·30]; p=0·27), and 39 [15%] participants allocated to antiplatelet therapy had major occlusive vascular events compared with 38 [14%] allocated to avoid antiplatelet therapy (1·02 [0·65-1·60]; p=0·92). INTERPRETATION: These results exclude all but a very modest increase in the risk of recurrent intracerebral haemorrhage with antiplatelet therapy for patients on antithrombotic therapy for the prevention of occlusive vascular disease when they developed intracerebral haemorrhage. The risk of recurrent intracerebral haemorrhage is probably too small to exceed the established benefits of antiplatelet therapy for secondary prevention. FUNDING: British Heart Foundation

User acceptance determinants of information technology innovation in organizations

Several models have been developed for understanding and predicting user acceptance of IT. Research examining the factors influencing IT user acceptance has produced contradictory outcomes. The study presents a meta-analysis of past findings for five determinants of user acceptance of IT. We analysed the relative strength and impact of the relationship between perceived usefulness, perceived ease of use, subjective norms, facilitating conditions and computer self-efficacy for user acceptance of IT in organizations. Results of the meta-analysis confirmed the significance of all five factors on user acceptance behaviour and found that perceived usefulness and perceived ease of use were the strongest predictors of IT user acceptance

Establishing relationships between innovation characteristics and it innovation adoption in orgnisations: A meta-analysis approache

This article presents the findings of a meta-analysis of innovation characteristics that influence the adoption of Information Technology (IT) in organizations. Past studies that examine the determinants of IT innovation adoption have produced inconsistent and contradictory results and deducing a definitive set of attributes for innovation adoption has become impractical. The study aggregated findings of past research on IT adoption using meta-analysis to identify key factors in terms of innovation or technology that influences adoption of IT in organization. Six innovation characteristics most commonly examined by researchers were analysed. The results of our meta-analysis confirmed that relative advantage, compatibility, cost, observability and trialability were strong determinants of IT innovation adoption. However, the study found no association between complexity and IT innovation adoption. The effect of stage of innovation, type of innovation, type of organization and size of organization as four moderating conditions was also examined