Modus Operandi (United States)

Conhecer a prevalência de ortorexia e vigorexia em estudantes de Medicina. Foram aplicados os questionários Ortho-15 e de Adônis para os estudantes de Medicina, do 1º ao 12º semestre da Universidade do Extremo Sul Catarinense. Dos 265 estudantes questionados, 232 apresentaram ortorexia e 255 apresentaram sintomas leves a moderados de vigorexia. Há uma alta prevalência de ortorexia e vigorexia nos estudantes entrevistados. Em relação à ortorexia, houve prevalência maior em mulheres, na faixa etária menor de 20 anos e em fases mais avançadas do curso. E na vigorexia, a maioria apresentara sintomas leves a moderados. A prevalência foi maior em mulheres cis, pessoas com idade média de 21 anos e o caso mais preocupante está presente no internato. Há um número considerável de estudantes com ortorexia e vigorexia. Torna-se necessária a realização de estudos em âmbito nacional para conhecer, traçar perfil e informar profissionais da saúde sobre essas afecções.

Apresenta-se um desdobramento da pesquisa em desenvolvimento no Programa de Pós-Graduação em Arquitetura e Urbanismo da Universidade Federal de Viçosa intitulada "SOLUÇÕES LUMINOTÉCNICAS PARA O ESPAÇO CÊNICO: SOFTWARES COMO FERRAMENTA DE CRIAÇÃO E OPERACIONALIZAÇÃO DA LUZ". A partir do levantamento para a realização do referido estudo, encontramos uma relação de softwares, programas e aplicativos voltados à Iluminação, os quais apresentamos neste artigo com o objetivo de expor a gama de ferramentas disponíveis no Brasil, no intuito de discutir suas funcionalidades e potencialidades no desenvolvimento de projetos de Iluminação Cênica, considerando as diversas configurações espaciais com objetivo cênico: edifícios dos teatros, casas de shows, eventos, galerias, ambientes cenográficos, fachadas e suas aplicações artísticas. O levantamento tem um perfil descritivo e exploratório buscando catalogar, apresentar e analisar as funcionalidades e potencialidades das ferramentas digitais elencadas, bem como sua viabilidade de acesso e navegabilidade. Tendo como parâmetro a linguagem da Iluminação, nos propomos a discutir seu protagonismo na construção do pensamento que envolve o desenho da luz no espaço, com o auxílio de ferramentas de criação, operacionalização, registro e soluções luminotécnicas.

Cet article décrit une double démarche : d’une part, celle de conduire une recherche sans dominer en produisant collectivement du savoir avec des personnes qui cherchent un refuge ; et, d’autre part celle de créer les conditions de leur prise de parole émancipée des processus de subalternisation. Les violences structurelles dans lesquelles sont prises les personnes qui cherchent refuge produisent notamment des injustices d’ordre épistémique. En effet, la procédure d’asile tout autant que les discours sur les requérant·es contraignent leur parole et ne permettent pas qu’iels soient vu·es comme des sujets politiques. Comment permettre alors la prise de parole ? Comment ne pas reproduire la violence épistémique en tant que chercheur·e ? Interrogeant notre position dominante tant comme chercheures que comme bénévoles aidantes, nous nous appuyons sur le cadre conceptuel des subaltern studies et de la pensée décoloniale pour analyser la position assignée aux personnes en recherche de protection, et les relations qu’elles entretiennent avec les personnes « établies » à partir d’une multitude de continuités coloniales. Sur la base de ces constats, nous avons créé un atelier radio qui fonctionne comme une succession d’espaces pour transformer ces relations et créer les conditions d’une parole libérée des contraintes analysées en amont. L’atelier s’organise ainsi sous la forme d’un continuum de trois espaces : du plus protégé où la parole peut surgir, à des espaces qui s’ouvrent vers l’extérieur – avec des invité·es – jusqu’aux rencontres publiques où les productions radiophoniques de l’atelier sont présentées et débattues. Ce faisant, l’atelier est questionné sur les modalités d’une recherche transformatrice des rapports sociaux à l’œuvre : la production collective du savoir peut-elle être une praxis de l’égalité permettant d’apercevoir ces personnes comme sujets pensants et agissants ?

Software is one of the most important products in human history and is widely used by all industries and all countries. It is also one of the most expensive and labor-intensive products in human history. Software also has very poor quality that has caused many major disasters and wasted many millions of dollars. Software is also the target of frequent and increasingly serious cyber-attacks. Among the reasons for these software problems is a chronic lack of reliable quantified data. This reference provides quantified data from many countries and many industries based on about 26,000 projects developed using a variety of methodologies and team experience levels. The data has been gathered between 1970 and 2017, so interesting historical trends are available. Since current average software productivity and quality results are suboptimal, this book focuses on "best in class" results and shows not only quantified quality and productivity data from best-in-class organizations, but also the technology stacks used to achieve best-in-class results. The overall goal of this book is to encourage the adoption of best-in-class software metrics and best-in-class technology stacks. It does so by providing current data on average software schedules, effort, costs, and quality for several industries and countries. Because productivity and quality vary by technology and size, the book presents quantitative results for applications between 100 function points and 100,000 function points. It shows quality results using defect potential and DRE metrics because the number one cost driver for software is finding and fixing bugs. The book presents data on cost of quality for software projects and discusses technical debt, but that metric is not standardized. Finally, the book includes some data on three years of software maintenance and enhancements as well as some data on total cost of ownership.

This comprehensive reference uses a formal and standard evaluation technique to show the strengths and weakness of more than 60 software development methodologies such as agile, DevOps, RUP, Waterfall, TSP, XP and many more. Each methodology is applied to an application of 1000 function points using the Java language. Each methodology produces a characteristic set of results for development schedules, productivity, costs, and quality. The intent of the book is to show readers the optimum kinds of methodologies for the projects they are concerned with and to warn them about counter indications and possible harm from unsuitable methodologies.

Abstract Learning and applying lessons is one requirement for continuing to improve business processes. Too often, companies neither collect lessons nor apply them well, or else they collect lessons well but have difficulty incorporating the lessons into future work. This paper describes the phases of learning lessons, necessary cultural factors and infrastructures, and how lessons‐learned programs evolve over time. The phases of a process for learning lessons are identification and collection, analysis and description, and communication and implementation. Additionally, this paper shows many dimensions of lessons‐learned efforts, provides pointers to many examples available online, and helps the reader establish a strategy for improving the ability of the organization to learn lessons.

Abstract Process improvement requires two major steps. First, new processes must be defined (or existing processes modified). Second, the organization must begin to use those new or changed process descriptions. The literature has provided good guidance on writing new process descriptions, but very little has stated clearly what actions must be taken to implement and then institutionalize the use of the processes. This paper provides a list of implementation and institutionalization actions that organizations should consider to ensure that the new processes are used. These actions fall into the categories of training, ensuring management support, obtaining a measurement baseline, auditing the use of the processes, collecting and maintaining a library of process assets, tailoring the processes, improving the processes, and appraising the organization.

This tutorial provides a one-day overview of Practical Software Measurement (PSM). The measurement approach focuses on satisfying the information needs of project managers. Innovative elements of PSM include the measurement process model and the measurement information model. Rather than discussing specific numerical techniques in detail, this course emphasizes basic concepts.

This paper describes two common approaches to measuring and modeling software quality across the project life cycle so that it can be made visible to management. It discusses examples of their application in real industry settings. Both of the examples presented come from CMM Level 4 organizations.

Abstract A process for application of systems engineering in the middle of a program has been described (Bahill and Briggs) that is based on analysis of the work breakdown structure to determine the scope of the program. The process provides general guidance and recommends specific reduced activities. This paper proposes a different start in the process to more thoroughly review the situation and determine where key information is missing. It also provides specifics and examples from several such applications of systems engineering and instances where it would have been beneficial.