Desenvolvimento, testes e qualidade de software

RESUMO: Hoje em dia o software tornou-se num elemento útil na vida das pessoas e das empresas. Existe cada vez mais a necessidade de utilização de aplicações de qualidade, com o objectivo das empresas se diferenciarem no mercado. As empresas produtoras de software procuram aumentar a qualidade nos seus processos de desenvolvimento, com o objectivo de garantir a qualidade do produto final. A dimensão e complexidade do software aumentam a probabilidade do aparecimento de não-conformidades nestes produtos, resultando daí o interesse pela actividade de testes de software ao longo de todo o seu processo de concepção, desenvolvimento e manutenção. Muitos projectos de desenvolvimento de software são entregues com atraso por se verificar que na data prevista para a sua conclusão não têm um desempenho satisfatório ou por não serem confiáveis, ou ainda por serem difíceis de manter. Um bom planeamento das actividades de produção de software significa usualmente um aumento da eficiência de todo o processo produtivo, pois poderá diminuir a quantidade de defeitos e os custos que decorrem da sua correcção, aumentando a confiança na utilização do software e a facilidade da sua operação e manutenção. Assim se reconhece a importância da adopção de boas práticas no desenvolvimento do software. Para isso deve-se utilizar uma abordagem sistemática e organizada com o intuito de produzir software de qualidade. Esta tese descreve os principais modelos de desenvolvimento de software, a importância da engenharia dos requisitos, os processos de testes e principais validações da qualidade de software e como algumas empresas utilizam estes princípios no seu dia-a-dia, com o intuito de produzir um produto final mais fiável. Descreve ainda alguns exemplos como complemento ao contexto da tese. ABSTRACT: Nowadays the software has become a useful element in people's lives and it is increasingly a need for the use of quality applications from companies in order to differentiate in the market. The producers of software increase quality in their development processes, in order to ensuring final product quality. The complexity and size of software, increases the probability of the emergence of non-conformities in these products, this reason increases of interest in the business of testing software throughout the process design, development and maintenance. Many software development projects are postpone because in the date for delivered it’s has not performed satisfactorily, not to be trusted, or because it’s harder to maintain. A good planning of software production activities, usually means an increase in the efficiency of all production process, because it can decrease the number of defects and the costs of it’s correction, increasing the reliability of software in use, and make it easy to operate and maintenance. In this manner, it’s recognized the importance of adopting best practices in software development. To produce quality software, a systematic and organized approach must be used. This thesis describes the main models of software development, the importance of requirements engineering, testing processes and key validation of software quality and how some companies use these principles daily, in order to produce a final product more reliable. It also describes some examples in addition to the context of this thesis.

Identification of resilience factors in rail engineering work

This paper discusses an ongoing project that aims at improving the potential for resilience of a system responsible for the planning of rail engineering work delivery. It focuses on the use of a human factors based approach as a way to achieve this end. In particular, the paper discusses the initial data collected by means of interviews and how this process gave way to a two fold goal: Understanding how the planning process works in reality and identifying any critical aspects of the system from a Resilience Engineering perspective. Given the nature of the process under study, information flows and communication issues have been given particular attention throughout the data collection and analysis stages. Initial data confirms that the planning process is greatly reliant on the capability of people using their knowledge and skills to communicate in a dynamic informational environment. Finally, the added value of the interviews is discussed from a human factors perspective and as a mean towards the aim of better understanding resilience in rail engineering planning.

Resilience in rail engineering work

This paper discusses an ongoing project that aims at improving the potential for resilience of a system responsible for the planning of rail engineering work delivery. This is being addressed by means of a methodology based on the observation and analysis of “real” planning activities, using resilience engineering concepts as a background. Interviews with planners have been carried out to provide an overview of the planning process and steer more in-depth investigation. Analysis of historic information and observation of planners’ main activities is underway. Given the nature of the process under study, information flows and communication issues have been given particular attention throughout the data collection and analysis stages. Initial data confirms that the planning process is greatly reliant on the capability of people using their knowledge and skills to communicate in a dynamic informational environment. Evidence was found of communication breakdowns at the boundaries of different planning levels and teams. The fact that the process is divided amongst several different areas of the organisation, often with different goals and needs, creates potential sources of conflict and tension.

Understanding safety and production risks in rail engineering planning and protection

Much of the published human factors work on risk is to do with safety and within this is concerned with prediction and analysis of human error and with human reliability assessment. Less has been published on human factors contributions to understanding and managing project, business, engineering and other forms of risk and still less jointly assessing risk to do with broad issues of ‘safety’ and broad issues of ‘production’ or ‘performance’. This paper contains a general commentary on human factors and assessment of risk of various kinds, in the context of the aims of ergonomics and concerns about being too risk averse. The paper then describes a specific project, in rail engineering, where the notion of a human factors case has been employed to analyse engineering functions and related human factors issues. A human factors issues register for potential system disturbances has been developed, prior to a human factors risk assessment, which jointly covers safety and production (engineering delivery) concerns. The paper concludes with a commentary on the potential relevance of a resilience engineering perspective to understanding rail engineering systems risk. Design, planning and management of complex systems will increasingly have to address the issue of making trade-offs between safety and production, and ergonomics should be central to this. The paper addresses the relevant issues and does so in an under-published domain – rail systems engineering work.