The Postclassic (pre-conquest) Nahua often performed displays of religious devotion. Usually involving stripping victims of their skin, flesh and internal organs, these public, state-sanctioned rites have been understood as astonishing, even exceptional, for their brutality. As a consequence, scholars have focused on human sacrifice at the steps of the Templo Mayor; ritual away from the imperial capital Tenochtitlan has remained very poorly understood. Where attempts have been made to understand regional practices, scholars have generally assumed binary distinctions between central versus periphery or state versus local. Existing studies fail to appreciate Nahua ritual as fluid and dynamic, instead casting ceremonial behaviour across space as unrelated and fundamentally oppositional. Integrating the ethnohistorical and archaeological records, this thesis takes understandings of Nahua ritual in new directions by examining the relationship between the public arena, the sacred landscape and domestic spheres. Crucially, this thesis argues that rituals were sensitive to circumstantial pressures and personal imperatives, across hierarchies,space and time. In so doing, this study suggests a more fluid model for understanding Nahua ritual than binary distinctions can allow. A lack of appreciation for variation or agency in ritual performance has perpetuated the understanding that the Nahua were trapped in a cycle of ferocious ritualism which left little room for critical thought. Using alphabetic, pictorial and archaeological evidence for a rounded perspective, this thesis examines the intersection between official structures and personal agency to question the notion that all Nahuas unthinkingly repeated human sacrifice and other ritual bloodshed. This study argues that the household was a crucial arena for the normalisation of the blood debt which permitted the acceptance of mass public human sacrifice. This thesis finds that, within the Nahua's symbiotic worldview, activities of the temple, mountain and household rituals were mutually supporting. Moreover, it is shown that the Nahuas chose to adapt their rituals throughout the years, to suit individual preferences and environmental circumstances. Taken as a whole, my findings suggest that the Nahuas sought to control their daily existence by adapting rituals to assuage violent and impulsive supernatural forces.

Changes to a software system are the result of changing requirements or defects during the development. Each change consumes resources for the analysis, decision making, implementation, and verification. Hence, having control over changes is crucial for software development projects to meet schedules, keep quality standards and budgets. Reuse of functionality helps to create new products based on already existing building blocks. Integrating mature components enables to create reliable systems. Software product lines provide means to develop several similar systems based on reuse. Often new products also need to be released frequently to fulfil the customer needs. Shortened lead time for the development then strengthens the importance of reuse. At the same time, limited budgets and competition on the market requires projects to utilize resources efficiently. Developing several releases in parallel enables an even distribution of tasks among different roles in a development organization. Both developing software based on a product line approach and parallel releases put requirements on how changes need to be controlled. In this thesis, software engineering literature is reviewed regarding the knowledge areas of software release management, software product lines and software configuration management. Beyond the most considerable research results also related case studies are presented to show how industry practices counter existing problems. The major part of the thesis is a case study conducted at Sony Ericsson Mobile Communications AB. The outcome of the thesis is an identification of challenges of controlling changes regarding parallel development and using software product lines based on available research results and industry case studies. It further provides a case of a software development organization which faces a high market-pace, uses a software product line approach, and develops several software releases in parallel on different sites around the world.

Made available in DSpace on 2016-06-21T13:45:01Z (GMT). No. of bitstreams: 2 14.pdf: 2172969 bytes, checksum: 5870afdec610eecdb4638ac12252003e (MD5) license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5) Previous issue date: 2014 / Made available in DSpace on 2016-07-05T22:38:03Z (GMT). No. of bitstreams: 3 14.pdf.txt: 158846 bytes, checksum: a09547088a1e8f43b3a1b15cdb523c55 (MD5) license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5) 14.pdf: 2172969 bytes, checksum: 5870afdec610eecdb4638ac12252003e (MD5) Previous issue date: 2014 / Fundação Oswaldo Cruz. Instituto de Tecnologia em Fármacos/Farmanguinhos. Rio de Janeiro, RJ, Brasil. / A indústria farmacêutica apresenta-se, no contexto do cenário globalizado atual, relevantemente dinâmica e inovadora. Tal dinâmica está estritamente relacionada às mudanças de tecnologias empregadas pelas empresas que vem sendo, ao longo das últimas décadas, flexíveis o suficiente para se adaptarem à nova realidade das práticas empresariais, refletidas em ganhos financeiros maiores, em menores intervalos de tempo. Perante este panorama recente e promissor, o componente qualidade encontra-se intrínseco em todas as etapas produtivas, desde a Pesquisa e Desenvolvimento (P&D) de novos fármacos até a obtenção e disponibilização do medicamento propriamente dito. Este processo de monitoramento da qualidade é regido, quer seja por organismos internacionais, como Food and Drug Administration (FDA), European Medicines Agency (EMA), entre outros, bem como por nacionais, como a Agência Nacional de Vigilância Sanitária (ANVISA), no caso do Brasil. As normas estabelecidas pela ANVISA para o mercado industrial farmacêutico nacional estão descritas, atualmente, através da Resolução da Diretoria Colegiada (RDC) n° 17 de Abril de 2010. Dentre outras diretrizes, a melhoria contínua é um dos principais pilares abordados por esta legislação, na qual atividades relacionadas ao armazenamento, produção, distribuição, entre outras, ligadas direta ou indiretamente ao fluxo de manufatura de medicamentos, passam por constantes alterações, à medida que novos conhecimentos científicos e atributos regulatórios são contemplados. Muitas vezes, a busca por ações de melhorias contínuas podem culminar em resultados inesperados, em razão da falta de planejamento e análise robusta das possíveis conseqüências e impactos destas aos processos. Em geral, mudanças estão sempre ocorrendo dentro das organizações, também em razão de falhas de processo e desvios de qualidade. Neste sentido, a RDC 17 ratifica o conceito de controle de mudanças, ferramenta de qualidade que possui a finalidade de assegurar que um determinado produto ou processo não sofrerá mudanças capazes de afetar sua segurança, qualidade e eficácia. O controle de mudanças é um elemento-chave das Boas Práticas de Fabricação, sendo considerado um dos mais críticos na indústria farmacêutica, por sua complexidade e decorrência, uma vez que procedimentos de controle de mudanças inadequados podem trazer diversos prejuízos e inconvenientes. A sistemática de gerenciamento destas mudanças possuem natureza preventiva e visam atuar diretamente na manutenção dos parâmetros de qualidade, custos e exposição regulatória, correlacionados às indústrias farmacêuticas. Assim, essa dissertação objetiva avaliar e mensurar a importância da relação entre Gerenciamento do Controle de Mudanças e riscos associados à qualidade, exposição regulatória e custos da qualidade na indústria farmacêutica, bem como apresentar os resultados provenientes do estudo de caso. / The pharmaceutical industry presents itself, in the context of the current global scenario, relevantly dynamic and innovative. Such dynamic is strictly related to changes of technologies applied by companies, that have been, over the last decades, flexible enough to adapt to the new reality of business practices. Towards this recent and promising panorama, component "quality" is inherent in all production stages, from Research and Development (R&D) of new drugs to acquisition and availability of the drug itself. This process of quality monitoring is governed either by international organizations, such as Food and Drug Administration (FDA), European Medicines Agency (EMA), among others, as well as the national entities, like Agência Nacional de Vigilância Sanitária (ANVISA), in the Brazil case. Standards established by ANVISA for the national pharmaceutical industrial market are described nowadays by the Resolução da Diretoria Colegiada (RDC) number 17 of 2010. Among other guidelines, continuous improvement is one of the main pillars covered by this legislation, in which activities related to storage, production, distribution, among other things, directly or indirectly linked to the flow of manufacturing drugs, undergo constant change as new scientific knowledge and regulatory attributes are contemplated. Often, the quest for continuous improvement actions may culminate in unexpected results, due to the lack of planning and robust analysis of the possible consequences and impacts of these processes. In a way, changes are always occurring within organizations, also because of process deviations and quality failures. In this sense, the RDC 17 ratifies the concept of change control, quality tool that has the purpose of ensuring that a particular product or process does not suffer changes that could affect, negatively, safety, quality and efficacy. Change control is a key element of the Good Manufacturing Practices and is considered one of the most critical in the pharmaceutical industry, and due to its complexity, since inadequate control procedures change can bring many losses and inconveniences. The systematic management of these changes have a preventive nature, and are intended to act directly on maintenance of quality parameters, costs and regulatory exposure, correlated to pharmaceutical industries.

A gerência de configuração vem sendo estudada desde os anos sessenta. Inicialmente, era aplicada da mesma forma para software e hardware, sendo que no final dos anos setenta já havia padrões de gerência de configuração específicos para software. Com a crescente demanda por qualidade de software, as práticas de gerência de configuração vem sendo cada vez mais utilizadas no desenvolvimento de software, uma vez que a gerência de configuração de software é um dos processos fundamentais para se ter qualidade no desenvolvimento e manutenção de software. Embora cada vez mais amplamente utilizado, não existe um consenso de práticas e nomenclaturas sobre as práticas de gerência de configuração. Dessa forma, o objetivo deste trabalho é elaborar um modelo de avaliação do processo de Gerência de Configuração, que permite avaliar as práticas e processos fundamentais para a implantação da gerência de configuração, levando em consideração as práticas e processos descritos nas principais normas internacionais de desenvolvimento de software. Esse modelo de avaliação também permite que as ferramentas disponíveis para gerência de configuração sejam avaliadas, identificando quais práticas e processos elas auxiliam na execução. / The Configuration Management has been studied since the 70’s. In the beginning it was applied in the same way for software and hardware, but in the late 70’s there were some specific configuration management patterns defined for software. The demand for software quality has increased recently, this way the configuration management practices have been more used in software development, because the software configuration management is one of the most important processes to assess quality during software development or maintenance. Although its use is increasing, there is no consensus about the configuration management practices and the names applied to them. The objective of this work is to elaborate an evaluation model for configuration management process, to evaluate the practices and the fundamental processes to perform configuration management, based on the most important software development standards. This evaluation model can also be used to evaluate configuration management tools, identifying what practices and process it help to execute.

A gerência de configuração vem sendo estudada desde os anos sessenta. Inicialmente, era aplicada da mesma forma para software e hardware, sendo que no final dos anos setenta já havia padrões de gerência de configuração específicos para software. Com a crescente demanda por qualidade de software, as práticas de gerência de configuração vem sendo cada vez mais utilizadas no desenvolvimento de software, uma vez que a gerência de configuração de software é um dos processos fundamentais para se ter qualidade no desenvolvimento e manutenção de software. Embora cada vez mais amplamente utilizado, não existe um consenso de práticas e nomenclaturas sobre as práticas de gerência de configuração. Dessa forma, o objetivo deste trabalho é elaborar um modelo de avaliação do processo de Gerência de Configuração, que permite avaliar as práticas e processos fundamentais para a implantação da gerência de configuração, levando em consideração as práticas e processos descritos nas principais normas internacionais de desenvolvimento de software. Esse modelo de avaliação também permite que as ferramentas disponíveis para gerência de configuração sejam avaliadas, identificando quais práticas e processos elas auxiliam na execução. / The Configuration Management has been studied since the 70’s. In the beginning it was applied in the same way for software and hardware, but in the late 70’s there were some specific configuration management patterns defined for software. The demand for software quality has increased recently, this way the configuration management practices have been more used in software development, because the software configuration management is one of the most important processes to assess quality during software development or maintenance. Although its use is increasing, there is no consensus about the configuration management practices and the names applied to them. The objective of this work is to elaborate an evaluation model for configuration management process, to evaluate the practices and the fundamental processes to perform configuration management, based on the most important software development standards. This evaluation model can also be used to evaluate configuration management tools, identifying what practices and process it help to execute.

The thesis will discuss the Systems Engineering phase of an original Conceptual Design Engineering Methodology for Aerospace Engineering-Vehicle Synthesis. This iterative phase is shown to benefit from digitization of Integrated Product&Process Design (IPPD) activities, through the application of Product Lifecycle Management (PLM) technologies. Requirements analysis through the use of Quality Function Deployment (QFD) and 7 MaP tools is explored as an illustration. A "Requirements Data Manager" (RDM) is used to show the ability to reduce the time and cost to design for both new and legacy/derivative designs. Here the COTS tool Teamcenter Systems Engineering (TCSE) is used as the RDM. The utility of the new methodology is explored through consideration of a legacy RFP based vehicle design proposal and associated aerospace engineering. The 2001 American Helicopter Society (AHS) 18th Student Design Competition RFP is considered as a starting point for the Systems Engineering phase. A Conceptual Design Engineering activity was conducted in 2000/2001 by Graduate students (including the author) in Rotorcraft Engineering at the Daniel Guggenheim School of Aerospace Engineering at the Georgia Institute of Technology, Atlanta GA. This resulted in the "Kingfisher" vehicle design, an advanced search and rescue rotorcraft capable of performing the "Perfect Storm" mission, from the movie of the same name. The associated requirements, architectures, and work breakdown structure data sets for the Kingfisher are used to relate the capabilities of the proposed Integrated Digital Environment (IDE). The IDE is discussed as a repository for legacy knowledge capture, management, and design template creation. A primary thesis theme is to promote the automation of the up-front conceptual definition of complex systems, specifically aerospace vehicles, while anticipating downstream preliminary and full spectrum lifecycle design activities. The thesis forms a basis for additional discussions of PLM tool integration across the engineering, manufacturing, MRO and EOL lifecycle phases to support business management processes.