244 research outputs found

    THE INTRA SYSTEM SHIFT AND LEVEL SHIFT IN ENGLISH-INDONESIAN SUBTITLE OF HARRY POTTER AND SORCERER’S STONE FILM by CHRIS COLUMBUS

    Get PDF
    The translation shift is divided into two types, namely level shift and category shift which are to achieve a good level of equivalence for the quality of the resulting translation. The category shift is further divided into four sub sections, namely structure shift, class shift, unit shift and intra system shift. The objective of this research is to describe what do the intra system shift and level shift in subtitle of Harry Potter and Sorcerer’s Stone Film by Chris Columbus, the causal of intra system shift and level shift in subtitle of Harry Potter and Sorcerer’s Stone Film by Chris Columbus, the more dominant between intra and level shift in subtitle of Harry Potter and Sorcerer’s Stone Film by Chris Columbus. Object in this research is Harry Potter and Sorcerer’s Stone Film by Chris Columbus. This research employs qualitative research with descriptive method. The object of this research was Harry Potter and Sorcerer’s Stone Film by Chris Columbus. The data used subtitle in Harry Potter and Sorcerer’s Stone who containing intra system and level shift. The data classified in J.C. Catford theory about translation shift, they are containing of intra system shift, level shift, and the causal of intra system shift and level shift. The findings of research show that from intra system shift, the researcher founds all sentence that contained intra system shift, level shift, and causal of intra system shift and level shift that used by characters in Harry Potter and Sorcerer’s Stone, the intra system was found in subtitle are 12 data, level shift was found in subtitle are 10 data, and the causal of intra system shift and level shift was found in subtitle are 7 data. In conclusion, intra system shift was mostly dominant used in sentence by characters in Harry Potter and Sorcerer’s Stone Film

    Central bank Financial Independence

    Get PDF
    Central bank independence is a multifaceted institutional design. The financial component has been seldom analysed. This paper intends to set a comprehensive conceptual background for central bank financial independence. Quite often central banks are modelled as robot like maximizers of some goal. This perspective neglects the fact that central bank functions are inevitably deployed on its balance sheet and have effects on its income statement. A financially independent central bank exhibits the adequate balance sheet structure and earnings generation capacity to efficiently perform its functions. From a long term perspective, as far as the demand for banknotes is maintained seignorage waters down any central bank financial independence concern. However, from a short term perspective central bank financial vulnerability may condition its effective independence. Vulnerability may be real or accounting based. However, no matter its origin, institutional solutions are needed to minimize their impact. Adequate capitalization turns out to be a key issue. Alternatively, contingent capital in the form of institutional arrangements to bear central bank losses may be a (second- best) solution. The paper analyses in the context of simple VAR model the interplay between capitalization, accounting rules and dividend distribution. This analysis is preceded by a thorough discussion of the risk return profile of central banks net return on assets. Three main conclusions shape the input to the capitalization model. Central banks return on assets can be very volatile from a short term perspective. From a medium term perspective, natural earnings generation cycles dampen down volatility. On average, central banks net return on assets typically exhibits a discount over government debt financing cost. These observations shape the central bank financing planning problem as follows. Namely, the size of the discount relative to the social costs that would arise in case of a lack of central bank independence, along with central bank exposure to risks and the volatility thereof, determine the incentives of the government to maintain an excess of financial assets in the form of central bank capital. Actually, the working of smoothing mechanisms operating across time on central banks earnings leads to a distinction between short term and medium term capital, i.e. the optimum capital solution is a band. In the same vein, the need to maintain optimal consistence between central bank financial strength and dividends distribution policy leads also to smoothing proposals for pay out policy.Central Banking Capital, Independence, Accounting, Profits

    Central bank financial independence

    Get PDF
    Central bank independence is a multifaceted institutional design. The financial component has been seldom analysed. This paper intends to set a comprehensive conceptual background for central bank financial independence. Quite often central banks are modelled as robot-like maximizers of some goal. This perspective neglects the fact that central bank functions are inevitably deployed on its balance sheet and have effects on its income statement. A financially independent central bank exhibits the adequate balance sheet structure and earnings generation capacity to efficiently perform its functions. From a long-term perspective, as far as the demand for banknotes is maintained seignorage waters down any central bank financial independence concern. However, from a short-term perspective central bank financial vulnerability may condition its effective independence. Vulnerability may be real or accounting based. However, no matter its origin, institutional solutions are needed to minimize their impact. Adequate capitalization turns out to be a key issue. Alternatively, contingent capital in the form of institutional arrangements to bear central bank losses may be a (second-best) solution. The paper analyses in the context of simple VAR model the interplay between capitalization, accounting rules and dividend distribution. This analysis is preceded by a thorough discussion of the risk-return profile of central banks net return on assets. Three main conclusions shape the input to the capitalization model. Central banks return on assets can be very volatile from a short term perspective. From a medium term perspective, natural earnings generation cycles dampen down volatility. On average, central banks net return on assets typically exhibits a discount over government debt financing cost. These observations shape the central bank financing planning problem as follows. Namely, the size of the discount relative to the social costs that would arise in case of a lack of central bank independence, along with central bank exposure to risks and the volatility thereof, determine the incentives of the government to maintain an excess of financial assets in the form of central bank capital. Actually, the working of smoothing mechanisms operating across time on central banks earnings leads to a distinction between short-term and medium term capital, i.e. the optimum capital solution is a band. In the same vein, the need to maintain optimal consistence between central bank financial strength and dividends distribution policy leads also to smoothing proporsals for pay-policy

    Impacts and Detection of Design Smells

    Full text link
    Les changements sont faits de façon continue dans le code source des logiciels pour prendre en compte les besoins des clients et corriger les fautes. Les changements continus peuvent conduire aux dĂ©fauts de code et de conception. Les dĂ©fauts de conception sont des mauvaises solutions Ă  des problĂšmes rĂ©currents de conception ou d’implĂ©mentation, gĂ©nĂ©ralement dans le dĂ©veloppement orientĂ© objet. Au cours des activitĂ©s de comprĂ©hension et de changement et en raison du temps d’accĂšs au marchĂ©, du manque de comprĂ©hension, et de leur expĂ©rience, les dĂ©veloppeurs ne peuvent pas toujours suivre les normes de conception et les techniques de codage comme les patrons de conception. Par consĂ©quent, ils introduisent des dĂ©fauts de conception dans leurs systĂšmes. Dans la littĂ©rature, plusieurs auteurs ont fait valoir que les dĂ©fauts de conception rendent les systĂšmes orientĂ©s objet plus difficile Ă  comprendre, plus sujets aux fautes, et plus difficiles Ă  changer que les systĂšmes sans les dĂ©fauts de conception. Pourtant, seulement quelques-uns de ces auteurs ont fait une Ă©tude empirique sur l’impact des dĂ©fauts de conception sur la comprĂ©hension et aucun d’entre eux n’a Ă©tudiĂ© l’impact des dĂ©fauts de conception sur l’effort des dĂ©veloppeurs pour corriger les fautes. Dans cette thĂšse, nous proposons trois principales contributions. La premiĂšre contribution est une Ă©tude empirique pour apporter des preuves de l’impact des dĂ©fauts de conception sur la comprĂ©hension et le changement. Nous concevons et effectuons deux expĂ©riences avec 59 sujets, afin d’évaluer l’impact de la composition de deux occurrences de Blob ou deux occurrences de spaghetti code sur la performance des dĂ©veloppeurs effectuant des tĂąches de comprĂ©hension et de changement. Nous mesurons la performance des dĂ©veloppeurs en utilisant: (1) l’indice de charge de travail de la NASA pour leurs efforts, (2) le temps qu’ils ont passĂ© dans l’accomplissement de leurs tĂąches, et (3) les pourcentages de bonnes rĂ©ponses. Les rĂ©sultats des deux expĂ©riences ont montrĂ© que deux occurrences de Blob ou de spaghetti code sont un obstacle significatif pour la performance des dĂ©veloppeurs lors de tĂąches de comprĂ©hension et de changement. Les rĂ©sultats obtenus justifient les recherches antĂ©rieures sur la spĂ©cification et la dĂ©tection des dĂ©fauts de conception. Les Ă©quipes de dĂ©veloppement de logiciels doivent mettre en garde les dĂ©veloppeurs contre le nombre Ă©levĂ© d’occurrences de dĂ©fauts de conception et recommander des refactorisations Ă  chaque Ă©tape du processus de dĂ©veloppement pour supprimer ces dĂ©fauts de conception quand c’est possible. Dans la deuxiĂšme contribution, nous Ă©tudions la relation entre les dĂ©fauts de conception et les fautes. Nous Ă©tudions l’impact de la prĂ©sence des dĂ©fauts de conception sur l’effort nĂ©cessaire pour corriger les fautes. Nous mesurons l’effort pour corriger les fautes Ă  l’aide de trois indicateurs: (1) la durĂ©e de la pĂ©riode de correction, (2) le nombre de champs et mĂ©thodes touchĂ©s par la correction des fautes et (3) l’entropie des corrections de fautes dans le code-source. Nous menons une Ă©tude empirique avec 12 dĂ©fauts de conception dĂ©tectĂ©s dans 54 versions de quatre systĂšmes: ArgoUML, Eclipse, Mylyn, et Rhino. Nos rĂ©sultats ont montrĂ© que la durĂ©e de la pĂ©riode de correction est plus longue pour les fautes impliquant des classes avec des dĂ©fauts de conception. En outre, la correction des fautes dans les classes avec des dĂ©fauts de conception fait changer plus de fichiers, plus les champs et des mĂ©thodes. Nous avons Ă©galement observĂ© que, aprĂšs la correction d’une faute, le nombre d’occurrences de dĂ©fauts de conception dans les classes impliquĂ©es dans la correction de la faute diminue. Comprendre l’impact des dĂ©fauts de conception sur l’effort des dĂ©veloppeurs pour corriger les fautes est important afin d’aider les Ă©quipes de dĂ©veloppement pour mieux Ă©valuer et prĂ©voir l’impact de leurs dĂ©cisions de conception et donc canaliser leurs efforts pour amĂ©liorer la qualitĂ© de leurs systĂšmes. Les Ă©quipes de dĂ©veloppement doivent contrĂŽler et supprimer les dĂ©fauts de conception de leurs systĂšmes car ils sont susceptibles d’augmenter les efforts de changement. La troisiĂšme contribution concerne la dĂ©tection des dĂ©fauts de conception. Pendant les activitĂ©s de maintenance, il est important de disposer d’un outil capable de dĂ©tecter les dĂ©fauts de conception de façon incrĂ©mentale et itĂ©rative. Ce processus de dĂ©tection incrĂ©mentale et itĂ©rative pourrait rĂ©duire les coĂ»ts, les efforts et les ressources en permettant aux praticiens d’identifier et de prendre en compte les occurrences de dĂ©fauts de conception comme ils les trouvent lors de la comprĂ©hension et des changements. Les chercheurs ont proposĂ© des approches pour dĂ©tecter les occurrences de dĂ©fauts de conception, mais ces approches ont actuellement quatre limites: (1) elles nĂ©cessitent une connaissance approfondie des dĂ©fauts de conception, (2) elles ont une prĂ©cision et un rappel limitĂ©s, (3) elles ne sont pas itĂ©ratives et incrĂ©mentales et (4) elles ne peuvent pas ĂȘtre appliquĂ©es sur des sous-ensembles de systĂšmes. Pour surmonter ces limitations, nous introduisons SMURF, une nouvelle approche pour dĂ©tecter les dĂ©fauts de conception, basĂ© sur une technique d’apprentissage automatique — machines Ă  vecteur de support — et prenant en compte les retours des praticiens. GrĂące Ă  une Ă©tude empirique portant sur trois systĂšmes et quatre dĂ©fauts de conception, nous avons montrĂ© que la prĂ©cision et le rappel de SMURF sont supĂ©rieurs Ă  ceux de DETEX et BDTEX lors de la dĂ©tection des occurrences de dĂ©fauts de conception. Nous avons Ă©galement montrĂ© que SMURF peut ĂȘtre appliquĂ© Ă  la fois dans les configurations intra-systĂšme et inter-systĂšme. Enfin, nous avons montrĂ© que la prĂ©cision et le rappel de SMURF sont amĂ©liorĂ©s quand on prend en compte les retours des praticiens.Changes are continuously made in the source code to take into account the needs of the customers and fix the faults. Continuous change can lead to antipatterns and code smells, collectively called “design smells” to occur in the source code. Design smells are poor solutions to recurring design or implementation problems, typically in object-oriented development. During comprehension and changes activities and due to the time-to-market, lack of understanding, and the developers’ experience, developers cannot always follow standard designing and coding techniques, i.e., design patterns. Consequently, they introduce design smells in their systems. In the literature, several authors claimed that design smells make object-oriented software systems more difficult to understand, more fault-prone, and harder to change than systems without such design smells. Yet, few of these authors empirically investigate the impact of design smells on software understandability and none of them authors studied the impact of design smells on developers’ effort. In this thesis, we propose three principal contributions. The first contribution is an empirical study to bring evidence of the impact of design smells on comprehension and change. We design and conduct two experiments with 59 subjects, to assess the impact of the composition of two Blob or two Spaghetti Code on the performance of developers performing comprehension and change tasks. We measure developers’ performance using: (1) the NASA task load index for their effort; (2) the time that they spent performing their tasks; and, (3) their percentages of correct answers. The results of the two experiments showed that two occurrences of Blob or Spaghetti Code design smells impedes significantly developers performance during comprehension and change tasks. The obtained results justify a posteriori previous researches on the specification and detection of design smells. Software development teams should warn developers against high number of occurrences of design smells and recommend refactorings at each step of the development to remove them when possible. In the second contribution, we investigate the relation between design smells and faults in classes from the point of view of developers who must fix faults. We study the impact of the presence of design smells on the effort required to fix faults, which we measure using three metrics: (1) the duration of the fixing period; (2) the number of fields and methods impacted by fault-fixes; and, (3) the entropy of the fault-fixes in the source code. We conduct an empirical study with 12 design smells detected in 54 releases of four systems: ArgoUML, Eclipse, Mylyn, and Rhino. Our results showed that the duration of the fixing period is longer for faults involving classes with design smells. Also, fixing faults in classes with design smells impacts more files, more fields, and more methods. We also observed that after a fault is fixed, the number of occurrences of design smells in the classes involved in the fault decreases. Understanding the impact of design smells on development effort is important to help development teams better assess and forecast the impact of their design decisions and therefore lead their effort to improve the quality of their software systems. Development teams should monitor and remove design smells from their software systems because they are likely to increase the change efforts. The third contribution concerns design smells detection. During maintenance and evolution tasks, it is important to have a tool able to detect design smells incrementally and iteratively. This incremental and iterative detection process could reduce costs, effort, and resources by allowing practitioners to identify and take into account occurrences of design smells as they find them during comprehension and change. Researchers have proposed approaches to detect occurrences of design smells but these approaches have currently four limitations: (1) they require extensive knowledge of design smells; (2) they have limited precision and recall; (3) they are not incremental; and (4) they cannot be applied on subsets of systems. To overcome these limitations, we introduce SMURF, a novel approach to detect design smells, based on a machine learning technique—support vector machines—and taking into account practitioners’ feedback. Through an empirical study involving three systems and four design smells, we showed that the accuracy of SMURF is greater than that of DETEX and BDTEX when detecting design smells occurrences. We also showed that SMURF can be applied in both intra-system and inter-system configurations. Finally, we reported that SMURF accuracy improves when using practitioners’ feedback

    Systems of State-Owned Enterprises: from Public Entrepreneurship to State Shareholding

    Get PDF
    This thesis outlines a new analytical perspective on state ownership through the original concept of systems of state-owned enterprises (SOSOEs). It is argued that the SOSOEs concept adequately captures the evolution of state-owned enterprises (SOEs) in modern capitalist economies, challenging and enriching existing economic theories as well as contributing to reinstate the policy instrumentality of state ownership. The concept is defined from a comparative case study analysis of two distinct SOSOEs, operating within the same national context in different time periods. The first case concerns the Istituto per la Ricostruzione Industriale (IRI), Italy’s former and most relevant state holding company, that played a central role in the Country’s post-WWII economic development. This thesis advances an interpretation of IRI’s economic function based on an original empirical investigation of its archival and documentary sources, focusing on its main public policy missions and on its display of industrial entrepreneurship features. The second case examines the current Italian system of SOEs, assessing the still relevant presence of SOEs in the Italian national context and evaluating the overall governance of the system through a set of interviews with leading executives. Despite the similarity in size and sectoral diversification, the two SOSOEs differ significantly in terms of their operating configurations. In fact, they could be assimilated to two dichotomous ideal types: the IRI SOSOEs represents a template for the policy-oriented and dynamic ‘public entrepreneurship’ model, while the current Italian SOSOEs resembles the policy-neutral and passive ‘state shareholding’ variant. Implicit in these results is the opportunity for current SOSOEs to embrace a public entrepreneurship configuration, in order to exploit the full policy potential of state ownership in driving economic change. The thesis concludes with a proposal for reforming Italy’s current SOSOEs via the creation of a state holding company

    State-Mandated Site-Based Management: Exploring the Level of Implementation in Texas High Schools.

    Get PDF
    The purpose of this study was to explore how Texas high schools responded to a state law which: (a) established that schools must implement site based management (SBM), and (b) outlined specific parameters under which the SBM program was to be constructed. This study was conducted using a four phase methodology that included both quantitative and qualitative techniques with a sample of 19 rural, suburban, and urban high schools. Phase One involved examining district level support and individualization of the SBM program. Phase Two explored school level SBM program structure to determine the consistency between mandated SBM elements and the school level program. Phase Three examined teachers\u27 perceptions of school and personal responsibility for decision making and teachers\u27 perceptions regarding the implementation of mandatory SBM elements. Phase Four utilized teacher interviews, school observations, and data collected during the previous phases of the study, to construct narrative case studies profiling two schools from each community. Principals in rural schools reported little alignment with required SBM structure, preferring more informal methods; however, teachers in rural schools reported high levels of school and personal decision making responsibility. Although lacking compliance with mandated program structure, rural schools appeared to be compliant with the intent of the law. Urban schools had strong alignment with required SBM program structure, but urban teachers reported the lowest levels of school and personal decision making responsibility. Thus, while compliant with mandated program structure, they were not compliant with the desired outcomes of the law. Suburban schools had both the required SBM program structure and high teacher perceptions of decision making responsibility. The findings of this study indicate that community type appears to wield the strongest influence on SBM program structure and teacher perceptions regarding personal and school decision making responsibility. There did not appear to be a direct relationship between a high degree of alignment with mandated elements of SBM program structure with high teacher perceptions of decision making involvement. In addition, many schools engaged in creative non-compliance with the law by utilizing alternative decision making vehicles for which teachers were not elected and there was no community or parent representation
    • 

    corecore