Desde a década de 90 o conceito de design for safety (DFS) vem sendo difundido como meio de reduzir os acidentes do trabalho com causas oriundas nas características do projeto do produto. A utilização do DFS na indústria da construção civil desperta o interesse de vários pesquisadores, mas ainda é pequena e conta com uma lacuna entre o conceito e a aplicação do mesmo. Assim, o objetivo deste trabalho consiste em propor um protocolo para integração de requisitos de segurança no trabalho ao processo de desenvolvimento do produto – PISP, com vistas a auxiliar engenheiros e arquitetos a desenvolver projetos seguros para os usuários temporários das edificações (trabalhadores de construção e manutenção). O método de pesquisa envolveu a realização de três estudos de caso: um empreendimento residencial, um industrial e um hospitalar, executados nas cidades da região central do estado RS, respectivamente, formaram o objeto de análise. A integração de requisitos de saúde e segurança do trabalho (SST) ao processo de desenvolvimento do produto (PDP), foi a unidade de análise deste trabalho. O protocolo inclui quatro etapas: identificação de perigos, avaliação de riscos, identificação de requisitos e avaliação e registro do aprendizado. Sua aplicação no desenvolvimento de projetos favorece o trabalho colaborativo entre os envolvidos no PDP, sendo recomendado sua incorporação ao processo de engenharia simultânea ou ao desenvolvimento integrado de produtos, no entanto, é adaptável a qualquer método de PDP adotado pela empresa construtora ou projetista. O estudo constatou que a integração de requisitos de SST desde as fases iniciais do PDP é viável e mais consistente do que quando realizada na fase de projeto ou reprojeto, como sugere o conceito tradicional de DFS. / Since 1990s, the concept design for safety (DFS) has been diffused as way of to reduce the accidents in construction site with causes derived of the characteristics of design. The utilization of DFS in the construction industry awakes the interest of several researches, but yet is low and has a gap between the concept and the application. So, the target this work is to propose a protocol for integration of health and safety work requirements at product development process (PISP), as way of to help engineers and architects to develop safe designs for temporary users of building (workers of construction and maintenance). The research method involved the realization of three cases: a residential undertaking, an industrial and a clinical, was the analysis object. The integration of health and safety work requirements at product development process was analysis unit this work. The protocol has four stages: identification of hazards, assessment of risks, identification of requirements and assessment and register of learning. The application in the development of designs allow the collaborative work between the participants of product development process (PDP), been recommended for incorporation at concurrent engineering process or at integrated development product, however, is adaptive at some method of development of product adopted by designer . The study verified that the integration of health and safety requirements since the early stages of PDP is viable and more solid that when made in design or redesign stages, as suggest the traditional concept of DFS.

Desde a década de 90 o conceito de design for safety (DFS) vem sendo difundido como meio de reduzir os acidentes do trabalho com causas oriundas nas características do projeto do produto. A utilização do DFS na indústria da construção civil desperta o interesse de vários pesquisadores, mas ainda é pequena e conta com uma lacuna entre o conceito e a aplicação do mesmo. Assim, o objetivo deste trabalho consiste em propor um protocolo para integração de requisitos de segurança no trabalho ao processo de desenvolvimento do produto – PISP, com vistas a auxiliar engenheiros e arquitetos a desenvolver projetos seguros para os usuários temporários das edificações (trabalhadores de construção e manutenção). O método de pesquisa envolveu a realização de três estudos de caso: um empreendimento residencial, um industrial e um hospitalar, executados nas cidades da região central do estado RS, respectivamente, formaram o objeto de análise. A integração de requisitos de saúde e segurança do trabalho (SST) ao processo de desenvolvimento do produto (PDP), foi a unidade de análise deste trabalho. O protocolo inclui quatro etapas: identificação de perigos, avaliação de riscos, identificação de requisitos e avaliação e registro do aprendizado. Sua aplicação no desenvolvimento de projetos favorece o trabalho colaborativo entre os envolvidos no PDP, sendo recomendado sua incorporação ao processo de engenharia simultânea ou ao desenvolvimento integrado de produtos, no entanto, é adaptável a qualquer método de PDP adotado pela empresa construtora ou projetista. O estudo constatou que a integração de requisitos de SST desde as fases iniciais do PDP é viável e mais consistente do que quando realizada na fase de projeto ou reprojeto, como sugere o conceito tradicional de DFS. / Since 1990s, the concept design for safety (DFS) has been diffused as way of to reduce the accidents in construction site with causes derived of the characteristics of design. The utilization of DFS in the construction industry awakes the interest of several researches, but yet is low and has a gap between the concept and the application. So, the target this work is to propose a protocol for integration of health and safety work requirements at product development process (PISP), as way of to help engineers and architects to develop safe designs for temporary users of building (workers of construction and maintenance). The research method involved the realization of three cases: a residential undertaking, an industrial and a clinical, was the analysis object. The integration of health and safety work requirements at product development process was analysis unit this work. The protocol has four stages: identification of hazards, assessment of risks, identification of requirements and assessment and register of learning. The application in the development of designs allow the collaborative work between the participants of product development process (PDP), been recommended for incorporation at concurrent engineering process or at integrated development product, however, is adaptive at some method of development of product adopted by designer . The study verified that the integration of health and safety requirements since the early stages of PDP is viable and more solid that when made in design or redesign stages, as suggest the traditional concept of DFS.

Recentemente, alguns empreendimentos habitacionais de interesse social (EHIS) no Brasil têm sido realizados através de programas integrados que envolvem o desenvolvimento conjunto de empreendimentos habitacionais, assistência social e obras de infra-estrutura sob uma delimitada área urbana a ser recuperada. Outra tendência importante desses programas é que resultam de um planejamento realizado em conjunto com a comunidade a ser beneficiada. O Programa Integrado Entrada da Cidade (PIEC), objeto de estudo desta tese, propõe a reestruturação urbana de uma importante área da cidade de Porto Alegre. Neste contexto, existe uma ampla gama de fatores que devem ser considerados na realização de empreendimentos, tais como a regularização fundiária, o reassentamento de população, o impacto ambiental, restrições orçamentárias, o atendimento de prazos, a participação comunitária e a inclusão social. Como resultado o processo de desenvolvimento de EHIS tende a ser bastante complexo, demandando um esforço específico de gerenciamento dos requisitos dos clientes ao longo da realização desses empreendimentos. Considerando os pesados recursos investidos nos programas integrados, destaca-se a importância da formação da satisfação e da geração de valor para a população atendida e reassentada a fim de que, a mesma seja efetivamente incorporada à cidade formal. O presente trabalho tem como objetivo geral de pesquisa identificar oportunidades de geração de valor no processo de desenvolvimento de EHIS de programas integrados através do gerenciamento dos requisitos dos principais clientes desses empreendimentos. Os desdobramentos desse objetivo envolveram a adaptação de conceitos e abordagens teóricas das áreas de marketing e de desenvolvimento do produto para o gerenciamento dos requisitos dos principais clientes de EHIS, bem como a proposta de contribuições conceituais e metodológicas para a análise da geração de valor em EHIS realizados através de programas integrados. O método da pesquisa foi constituído por um estudo de caso dividido em três etapas. A Etapa A teve um caráter exploratório-descritivo com o objetivo de entender o contexto de concepção do PIEC e o processo de desenvolvimento do mesmo. Na Etapa B o foco do estudo passou a ser a população atendida pelo programa, particularmente as 413 famílias reassentadas na primeira etapa da fase de intervenção, concluída em março de 2004. Esse ajuste se fez necessário para possibilitar uma investigação mais aprofundada sobre a percepção de valor dos clientes finais. A Etapa C foi desenvolvida para possibilitar a discussão e análise dos resultados obtidos nas etapas anteriores do estudo de caso e a devida confrontação desses resultados com a bibliografia. As principais conclusões estão relacionadas à identificação de oportunidades de geração de valor no processo de desenvolvimento de EHIS de programas integrados através do gerenciamento dos requisitos dos principais clientes desses empreendimentos. Além disso, o estudo também resultou em contribuições conceituais para a consolidação do conceito de geração de valor no processo de desenvolvimento desse tipo de EHIS. / Recently several social interest housing projects (SIHP) have been carried out in Brazil throughout integrated programs that involve the joint development of housing projects, social service and infrastructure for a specific urban area to be recovered. Another important tendency of these programs is that they result from a joint planning carried out with the community to be benefited. The City Entrance Integrated Program (CEIP), study object of this thesis, proposes the urban restructuring of an important area of Porto Alegre City. In this context, there is a wide range of factors that must be considered to build the housing projects, such as: urban land regularization, population resettlement, environmental impact, budgetary constraints, scheduled date fulfillment, community participation and social inclusion. As a result the development process of SIHP tends to be quite complex, demanding a specific effort of client requirements management throughout the building of these projects. Considering the heavy investments in integrated programs, the importance of satisfaction and value generation for the assisted and resettled population stands out so that it may be incorporated to the formal city. This research has as main objective to identify opportunities for value generation in the SIHP development process of the integrated programs through the main clients’ requirements management of these projects. These objective spin-offs involved the adaptation of concepts and theoreticians approaches of the marketing and product development process areas to SIHP main client requirements management, such as the proposal of conceptual and methodological contributions to value generation analysis in SIHP carried out through integrated programs. The research method was constituted by a case study divided in three phases. The Phase A had an exploratory-descriptive character aiming to understand the context of CEIP conception and its development process. In Phase B the study focused the population served by the program, particularly the 413 families resettled in the first stage that was concluded in March 2004. This adjustment was necessary to make possible a deeper investigation on final clients’ perceived value. The Phase C was developed to make possible the discussion and analysis of the results obtained in the case study previous phases as well as these results comparison with the bibliography. The main conclusions are related to the identification of opportunities for value generation in SIHP development process of integrated programs through main client requirements management of these projects. Besides, the study has also resulted in conceptual contributions for the consolidation of the value generation concept in the development process of this kind of SIHP.

Um dos caminhos mais seguros para que as empresas conquistem clientes é através do aperfeiçoamento constante em seus portfólios de produtos, direcionando-os ao atendimento de requisitos dos clientes. Devido à carência de métodos que incorporem os requisitos dos clientes nas especificações de projeto de máquinas agrícolas, o objetivo deste trabalho é propor atividades de gestão dos mesmos ao longo do PDP. As contribuições deste trabalho para o PDP de uma empresa do setor de máquinas agrícolas resume-se na formalização das atividades de gestão de requisitos, nas discussões das atividades que apresentam deficiências e também no levantamento de sugestões propostas para as deficiências encontradas no método atual. A partir desses objetivos, o trabalho mostra uma revisão teórica sobre o tema, a qual nos proporcionou um amplo conhecimento dos processos de requisitos dentro dos modelos de PDP propostos por autores. Em seguida, foi apresentada uma metodologia para a gestão de requisitos dentro do PDP de máquinas agrícolas levando em consideração as literaturas pesquisadas e as condições atuais de uma empresa, quanto a este assunto. A consolidação desta pesquisa deu-se através de uma aplicação visando a exequibilidade do método durante o desenvolvimento de um subsistema de uma colheitadeira. Os resultados indicaram que as atividades propostas foram adequadas no sentido de assegurar a rastreabilidade dos requisitos de tal forma que o produto desenvolvido, efetivamente, incorporasse as demandas iniciais dos clientes. / Organizations have invested in the continuous improvement of product portfolios viewing to incorporate customers' needs and requirements. Due to the lack of systematic methods to incorporate the requirements of customers in the design specifications of the agricultural equipments, this paper aim is to propose activities for managing requirements throughout the PDP (Product Development Process). The contributions of this paper for the PDP of an agricultural machine company are summarized in the formalization of the requirement management activities, in the discussions of the activities that present deficiencies and also the proposition of solutions for these deficiencies. This research includes a theoretical review on the subject that provided us a wide knowledge of the requirement processes in the PDP models proposed by the authors. Next it puts forward a methodology for requirement management within the PDP agricultural equipments taking into account the literature and the company current PDP conditions. The proposed activities consolidation was achieved throughout the development of a combine subsystem. The results indicated that the proposed activities were adequate to ensure the traceability of requirements, so that the product developed effectively incorporated the initial demands of customers.

Sammanfattning Kravhanteringsprocessen är en av de viktigaste faserna vid utvecklandet av ett IT-system. Kravhantering är alltså grundläggande för att utveckla ett stabilt system som uppfyller beställarens önskemål. Med en väl utförd kravhantering som grund får man ett system som är fritt från bristfälliga fel, utvecklandet av systemet går även till på ett effektivare sätt. Vid byggandet av ett system eftersträvar man alltid en framgångsrik mjukvara. Kravhantering ses som den viktigaste faktorn vid utvecklandet av ett IT-system. Föreliggande studie genomförs som en litteraturstudie där undersöks vilka brister som är vanligt förekommande under kravhanteringsprocessen. Syftet med föreliggande studie är att identifiera förekommande brister under kravhanteringsprocessen samt om det finns eventuella lösningar till dessa brister. För att kunna utreda detta så måste bristerna definieras och hur arbeta ska ske för att eliminera eller undvika dessa. Resultatet av föreliggande studie visar på att det finns en del brister som är vanligt förekommande och även föreslagna lösningar. Vidare tyder resultatet på att majoriteten av bristerna förekommer på grund av dålig kommunikation och missförstånd. / Abstract Requirements management process is one of the most important stages in the development of an IT system. Requirements management is therefore essential to develop a stable system that meets client needs. With a well-executed requirements management as the basis to get a system that is free from error, inadequate development of system allows to more effectively. In the construction of a system always seeks successful software. Requirements management is seen as the most important factor in the development of an IT system. The present study is conducted as a literature review which examines the shortcomings that are commonplace during the requirements management process. The aim of the present study is to identify deficiencies in the requirements management process, and if there are any solutions to these shortcomings. In order to investigate this, we must define the gaps and to work to eliminate or avoid them. The result of this study shows that there are some deficiencies are common and even proposed solutions. Furthermore, the results indicate that the majority of shortcomings due to poor communication and misunderstandings.

Context. Requirements changes are unavoidable in any software project. Requirements change over time as software projects progress, and involved stakeholders (mainly customers) and developers gain better understanding of the final product. Additionally, time and budget constraints prevent implementing all candidate requirements and force project management to select a subset of requirements that are prioritized more important than the others so as to be implemented. As a result, some requirements become cancelled and deleted during the elicitation and specification phase while other requirements are considered not important during the prioritization phase. A common scenario in this situation is to leave the excluded requirements for being considered in the next release. The constant leaving of the excluded requirements for the next release may simply render them obsolete.

This work is a study examining the causes of fire fighting in software projects. Fire fighting is the practice of reactive management, i.e. focus being put at solving the problem of the moment. The study in the thesis is performed in two parts, one part is a literature study examining what academia considers as the reasons of fire fighting and how to minimise the problem. The other part of the thesis is an interview series performed in the industry with the purpose of finding what they consider the causes of the fire fighting phenomena. What is indicated by the interview series, as being the main causes of the problems are problems that are related to requirements, and problems caused by persons with key knowledge leaving the project. / Detta arbete undersöker orsakerna bakom "fire fighting" i mjukvaru projekt. "Fire fighting", eller brandsläckning, är utövandet av reaktivt management, dvs. att gruppen lägger fokus på att lösa de problem som för tillfället finns i projektet. Arbete är uppbyggt i två delar, den ena delen är en literaturstudie och den andra en studie av vad industrin anser orsaka "fire fighting" beteendet.

Requirements engineering (RE) is the primary task (process) that is done when agreed upon to develop a software product. The success of the software product is gauged on its ability to meet the intended needs of the stakeholders. There is abundant literature emphasizing the significance of RE and its influence on the entire software project, apart from its importance as the first step for a successful development endeavor. There are several established methodologies that are acknowledged to support the RE process and assist in creating a reliable structure of creating software. Despite the availability of such techniques and solutions, it was observed that umpteen number of software product failures are attributed to unsatisfactory RE practices. In this thesis, we have conducted a study with six organizations to emphasize the gap between the state of the art and the state of the practice, and consequently identify the factors that hinder the industrial community to implement state of the art RE. As a result of this empirical research we have found that to a great extent, state of the art practices are unpopular, more specifically in small organizations. Interestingly the majority of the problems associated with RE are associated to non technical issues.

In many smaller companies, requirements management is a daunting challenge. Smaller groups mean fewer resources, and many organizations focus their efforts on design, development and testing not on managing requirements. Some small organizations may perceive requirements management as an activity only for large organizations that have complex products and large staffs to support the effort. Poor and uncontrolled requirement engineering processes yield low quality, highly expensive software products. Obviously, customers are highly dissatisfied with such systems. One of the most critical requirement engineering processes that grossly contribute to this misnomer is lack of “effective requirements management” Information Technology Associates (ITA) has had many challenges resulting from some poor and uncontrolled requirements engineering processes. Lack of effective requirements traceability has also had its share in plaguing ITA in software development activities. ITA started small and so it handled its requirements documentation manually as it only dealt with few customer requirements. Time has seen the company expand, and manual handling of customer requirement became difficult. This master thesis therefore aims to investigate: ♦ The state-of-practice, regarding requirements engineering and requirements management within a medium-sized software development company. ♦ How to successfully implement effective requirement management process within the ITA Company. ♦ How to successfully migrate ITA Company into this RE process while ensuring minimum hassles.

Requirements Engineering (RE) is nowadays considered to be an activity, that aims at supporting the whole lifecycle of an information system by: eliciting, documenting, validating, and managing the requirements of the system. This thesis aims at providing an overview of the area of Requirements Management (RM) and to identify important and interesting issues or areas where further research is needed. RM includes two major areas; organising requirements and requirements change management. Organising requirements is concerned with structuring the requirements and storing additional relevant information about them e.g. attributes and traceability information. Requirements change management is concerned with dealing with changing requirement in a systematic way i.e. making informed decisions whether to implement a certain change or not, and support the implementation of approved changes. In order to provided a broader view of RM, the literature study were complemented by an interview study of how RM is conducted in practice. This interview study shows that the effort resources spent on RM differs substantially between different organisations. Various reasons for these discrepancies are elaborated in the work, but one of the main reasons are the type of software development that is conducted in the organisation. There is a tendency that organisations that develop software products and continuously releases new versions of there products are more likely to spend resources on RM, compared with organisations that develop customers specific solutions in one shoot projects. The need to reuse requirements and knowledge, as well as the maturity of the RE/RM process, are other factors that affects the resources spent on RM. The RM activities performed in practice are concordant with the activities found in literature. A number of areas where further research is needed were identified: requirements change management, dependencies between requirements, RM tools, and information management