How do software architects consider non-functional requirements: an exploratory study

© 2012 IEEE. Personal use of this material is permitted. Permission from IEEE must be obtained for all other uses, in any current or future media, including reprinting/republishing this material for advertising or promotional purposes,creating new collective works, for resale or redistribution to servers or lists, or reuse of any copyrighted component of this work in other works.Dealing with non-functional requirements (NFRs) has posed a challenge onto software engineers for many years. Over the years, many methods and techniques have been proposed to improve their elicitation, documentation, and validation. Knowing more about the state of the practice on these topics may benefit both practitioners' and researchers' daily work. A few empirical studies have been conducted in the past, but none under the perspective of software architects, in spite of the great influence that NFRs have on daily architects' practices. This paper presents some of the findings of an empirical study based on 13 interviews with software architects. It addresses questions such as: who decides the NFRs, what types of NFRs matter to architects, how are NFRs documented, and how are NFRs validated. The results are contextualized with existing previous work.Peer ReviewedPostprint (author’s final draft

Occupational injuries among construction workers at the Chep Lap Kok Airport construction site, Hong Kong : analysis of accident rates, and the association between injuries, error types and their contributing factors : a thesis presented in partial fulfilment of the requirements for the degree of Master of Aviation at Massey University, Palmerston North, New Zealand

Accidents on construction sites are a major cause of morbidity and mortality in Hong Kong. This study investigated the likely causes of occupational injuries that were present among the construction workers during the construction of the new Chep Lap Kok (CLK) Airport in Hong Kong. In order to accumulate the requisite information, 1648 accident investigation reports in a four-year period (1993-1996) were reviewed. The first part of the study described the pattern and magnitude of occupational injuries among the CLK construction workers and compared the accident rates of the CLK workers with those of the construction industry as a whole in Hong Kong. The study examined the effects of the workplace infrastructure at CLK in order to explain why this site presented fewer work place injuries and accidents than other workplaces. The second part of the research used these injury and accident occurrences as the basis to construct the causes of accidents and injuries within an error causation classification system. The results showed that at CLK, the commonest workplace injury was contusion & crushing which appeared to be due to mistakes made through lapses in memory often caused by pressure of work being imposed on the employee. This section also indicated what types of errors were most closely associated with what kinds of injuries and what conditions were most likely to trigger these types of events. Among the major associations were links between contusion and crushing and violation error, perceptual error; between memory lapse and work pressure, equipment deficiencies, poor working environment, fatigue, and between violation error and work pressure. The research suggested that work pressure was an important contributing factor to construction injury and it increased the prevalence of a human error type namely, memory lapse many fold. The outcomes from this study provide important new information on the causes and types of errors which have led to occupational injuries among construction workers in Hong Kong. A better understanding of the human factors-based causes of accidents and injuries in the construction industry and an inculcation of a safety culture on construction sites are critically important in the reduction of the rate of construction accidents and improvement of workers' human performance. The results should assist the construction industry in the designing accident prevention training and education strategies, estimating human error probabilities, and the monitoring organizational safety performance

Relevance, benefits, and problems of software modelling and model driven techniques—A survey in the Italian industry

Context Claimed benefits of software modelling and model driven techniques are improvements in productivity, portability, maintainability and interoperability. However, little effort has been devoted at collecting evidence to evaluate their actual relevance, benefits and usage complications. Goal The main goals of this paper are: (1) assess the diffusion and relevance of software modelling and MD techniques in the Italian industry, (2) understand the expected and achieved benefits, and (3) identify which problems limit/prevent their diffusion. Method We conducted an exploratory personal opinion survey with a sample of 155 Italian software professionals by means of a Web-based questionnaire on-line from February to April 2011. Results Software modelling and MD techniques are very relevant in the Italian industry. The adoption of simple modelling brings common benefits (better design support, documentation improvement, better maintenance, and higher software quality), while MD techniques make it easier to achieve: improved standardization, higher productivity, and platform independence. We identified problems, some hindering adoption (too much effort required and limited usefulness) others preventing it (lack of competencies and supporting tools). Conclusions The relevance represents an important objective motivation for researchers in this area. The relationship between techniques and attainable benefits represents an instrument for practitioners planning the adoption of such techniques. In addition the findings may provide hints for companies and universitie

Australia cultural built heritage:Stakeholders' perceived conservation barriers and motivations

Stakeholders are recognised as drivers of effective conservation of cultural built heritage. Yet, as stakeholders have eclectic views in terms of their interest in, knowledge of and perceptions about the management of historic fabric, their practices are often diverse. The objective of this paper is to gain an understanding of the stakeholders' views drawn from relevant professional field on the issues that act as barriers to conservation and identify the factors that motivate built heritage management in Australia. Using a qualitative research design, two focus groups were conducted in Queensland and New South Wales with purposely selected key informants (N=14) working in the Australian heritage sector. The study presents stakeholders' interest in managing built heritage and the perceptions concerning the application of conservation policy and practices in the Australian built heritage sector, as influenced by the interdisciplinary backgrounds of participants. The paper contributes to an in-depth understanding of the conservation barriers and motivators and their implications for policy and practices in the management of Australian built heritage. The study is based on the perceptions of key informants with diverse interests and knowledge about the conservation of cultural built heritage; this makes the research analysis and implications inclusive and influential from both theoretical and practical points of view.</p

Why Modern Open Source Projects Fail

Open source is experiencing a renaissance period, due to the appearance of modern platforms and workflows for developing and maintaining public code. As a result, developers are creating open source software at speeds never seen before. Consequently, these projects are also facing unprecedented mortality rates. To better understand the reasons for the failure of modern open source projects, this paper describes the results of a survey with the maintainers of 104 popular GitHub systems that have been deprecated. We provide a set of nine reasons for the failure of these open source projects. We also show that some maintenance practices -- specifically the adoption of contributing guidelines and continuous integration -- have an important association with a project failure or success. Finally, we discuss and reveal the principal strategies developers have tried to overcome the failure of the studied projects.Comment: Paper accepted at 25th International Symposium on the Foundations of Software Engineering (FSE), pages 1-11, 201

The safety case and the lessons learned for the reliability and maintainability case

This paper examine the safety case and the lessons learned for the reliability and maintainability case

Developing a model to predict aircraft maintenance performance

[Abstract]: A three-pronged approach was adopted to the investigation of causes of maintenance errors in army aviation. In the first phase of the research, analysis of maintenance incident reports suggested that individuals were mostly at fault, making errors because they failed to follow procedures and were inadequately supervised. Interviews with maintenance technicians, on the other hand, put the spotlight on organisational variables, such as pressures created by poor planning. In the third phase, a survey instrument administered to 448 maintenance workers was used to develop a structural model that predicted 34% of the variance in psychological health, 16% of the variance in turnover intentions, and 16% of the variance in self-reported maintenance errors. Implications of these findings are discussed