Made available in DSpace on 2014-06-12T15:49:28Z (GMT). No. of bitstreams: 1 license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5) Previous issue date: 2009 / Coordenação de Aperfeiçoamento de Pessoal de Nível Superior / Um grande desafio da Engenharia de Software Baseada em Componentes (ESBC) é a qualidade dos componentes utilizados em um sistema. A confiabilidade de um sistema baseado em componentes depende da confiabilidade dos componentes dos quais ele é composto. Na ESBC, a busca, seleção e avaliação de componentes de software é considerado um ponto chave para o efetivo desenvolvimento de sistemas baseado em componentes. Até agora a indústria de software tem se concentrado nos aspectos funcionais dos componentes de software, deixando de lado uma das tarefas mais árduas, que é a avaliação de sua qualidade. Se a garantia de qualidade de componentes desenvolvidos in-house é uma tarefa custosa, a garantia da qualidade utilizando componentes desenvolvidos externamente os quais frequentemente não se tem acesso ao código fonte e documentação detalhada se torna um desafio ainda maior. Assim, esta Tese introduz um Framework de Qualidade de Componentes de Software, baseado em módulos bem definidos que se complementam a fim de garantir a qualidade dos componentes de software. Por fim, um estudo experimental foi desenvolvido e executado de modo que se possa analisar a viabilidade do framework proposto

Made available in DSpace on 2014-06-12T16:01:14Z (GMT). No. of bitstreams: 2 arquivo7273_1.pdf: 859722 bytes, checksum: 0a10aaaffe0f345515ef1d4559599ff4 (MD5) license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5) Previous issue date: 2005 / Coordenação de Aperfeiçoamento de Pessoal de Nível Superior / Desenvolvimento de Software Baseado em Componentes tem sido amplamente adotado na academia e na prática, representando assim um mercado promissor para a indústria de software. A perspectiva de redução do custo e do ciclo de desenvolvimento do software tem sido a principal motivação para esta expansão. Entretanto, inúmeros problemas técnicos ainda permanecem sem solução antes mesmo que a indústria de componentes de software alcance a maturidade de outras indústrias de software. Problemas como a seleção de componentes, a carência de catálogos de componentes formalizados e a falta de informações sobre a qualidade dos componentes desenvolvidos trazem novos desafios para a comunidade de engenharia de software. Por outro lado, a área de certificação de componentes de software é relativamente imatura e necessita de consideráveis pesquisas para o estabelecimento de um padrão para certificação de componentes de software. Assim, esta dissertação apresenta um modelo de qualidade de componentes, baseada em características consistentes e bem definida, atributos de qualidade e métricas relacionadas para avaliação dos componentes. Um estudo experimental foi desenvolvimento visando analisar a viabilidade de utilização do modelo. Os resultados obtidos mostrar-se-iam que o modelo é um interessante candidato para avaliação da qualidade em componentes de software, e trabalhos futuros estão sendo planejamentos para que a evolução do modelo alcance o nível de maturação necessário e torne-o diretamente aplicável à indústria de software

Previous research suggests that people employ priority-related task attributes (e.g., task importance, task length, and task deadline) in prioritization. The process of prioritization employs heuristics to determine task order (Zhang & Feyen, 2007a). These models only address the prioritization process at a task level and do not address the cognitive mechanisms underlying prioritization. Building on previous findings, a process model of prioritization is proposed to explain prioritization during multitasking. Two experiments examined three cognitive processes of prioritization and the influence of time pressure. Three processes were investigated: 1) a process makes magnitude comparisons on priority-related information, 2) a process integrates multiple pieces of information and checks for potential conflicts among information, and 3) a process solves conflicts among priority-related information during prioritization. Under the influence of time pressure, it is hypothesized that people will adopt strategies that require fewer cognitive resources compared to situations where no time pressure exists. A series of task conditions with various configurations of priority-related task attributes was used to illuminate these processes and hypothesis. Hierarchical regression analyses provided evidence for the three cognitive components and suggested that these cognitive components played different roles under time pressure compared to performance under no time pressure. Three fundamental cognitive processes were identified in prioritization and provide implications for personnel selection and training for jobs demanding prioritization and multitasking in the real world.

The entity component system architecture (ECSA) is a data-oriented composition pattern and a data-driven design pattern. Data-oriented software takes into consideration generalized knowledge of hardware. Data-driven design is a methodology used to replace inflexible code with reusable components that can be added, deleted, or modified in interactive systems and games. This thesis explores the ECSA and its alternatives and their strengths and weaknesses. The paper details the creation of an ECSA and benchmarks its performance against object-oriented architectures. The hypothesis of this thesis is that the ECSA has CPU cache performance advantages over object-oriented architectures as tested by multiple benchmarks. The results suggest that the ECSA provides superior CPU performance. These results could be valuable for interactive game developers to get higher frame rates out of their games, MMORPG server developers to process millions of entities per second, and mobile developers to create battery-efficient apps.

The intent of this thesis was to develop a component system derived from a desired form. Through analysis of the initial form, I gained an understanding of the underlying parameters, principles, and topologies the form exhibited that could then be interpreted into the development of a component system. Through the process of design, utilizing iterative attempts of creating a component system directly mimicking the original form, I began to realize the need to better understand the underlying principles and topologies of the original form. This understanding became the basis in my attempts to assemble components toward a direct copy of the original form. This experimentation led to the realization that direct copy was not achievable. However, the deeper understanding of the principles exhibited within the initial form provided the framework to develop a component system that would exhibit similar results while simultaneously allowing for greater control in the development of a member with a particular desired outcome. The conversation between Form and Method was a continuous dialogue throughout the project: from the form of the initial model and the method of developing a component system based on the principles it exhibited, to the formal expression of the component itself, and eventually to a final iteration that combines the principles of the original construct through the method of assembly based on the form of the component. / Master of Architecture

No description available.

One of the difficulties of Component Based Software Engineering (CBSE) [1] in reusing pre-existing components is the need to adapt these components to work within the desired target systems [2, 3, 4, 5, 6]. Third-party or in-house Commercial Off-the-shelf (COTS) components may not always have the required exact functionality demanded by the builders of the target system, so these systems have to be either modified [2, 3, 4, 5, 6] or adapted to provide this required functionality. Modifying these components may not be always practically possible. In this thesis, we propose an infrastructure that supports the active interface adaptation technique [3, 8, 9, 10]. This infrastructure directly addresses the problem of effectively packaging components for third-party use, adaptation, and deployment. Doing so we support both component designers and third party application builders. Further we evaluate our approach using several adaptations over the case studies.

Due to the fact that the environment which business confront is very dynamic, so the business require the software to reduce the response time, provide the high quality, and supply the flexible modeling process and high maintainability. In order to meet the requirement, a new software solution is emerged. Component-based software engineering is a method to integrate existed component to produce faster speed, lower cost and higher quality software. And it is concerned with the rapid assembly of systems from components where components and frameworks have certified properties; and these certified properties provide the basis for predicting the properties of systems built from components. Therefore, component based software engineering replace the position belong to traditional software engineering progressively, it become the next generation software engineering paradigm. Because businesses want to transform their requirement to be final components, so the component-based software engineering must have component modeling methodology in the system analysis stage. For this reason, the advantage and disadvantage of the component modeling methodology makes a very deep influence on component-based software engineering. And after the survey we made, we discover the greater parts of the existed component modeling methodology have a lot of defects, for example: the modeling method stay at abstract level, lack of clear and definite modeling rules, short of consistence of process document and can¡¦t meet the good component modeling characteristics. Fortunately, in our surveyed methodology, we discover the ¡§UML Component¡¨ is a component modeling methodology which can meet the good component modeling characteristics and have the develop potential. But the ¡§UML Component¡¨ methodology still has some problem, for example: lack of explicit component identify rules, complete tools support and simply modeling process. Due to these reasons, our study provides three solutions to refine and extend the ¡§UML Components¡¨ methodology. First of all, we utilize the use case identify method by [§d¤¯©M2002]¡Bthe concept of ¡§Fan-in and Fan-out¡¨ by [Marquis2002] and the use case association transform method to refine the problem of component modeling rules. Secondly, we employ data glossary, data relation matrix and operation reference matrix to improve the problem of component modeling tools. Finally, we redesign the process model which includes four stages as follows, requirement acquisition, component identification, component interaction and component specification to resolve the irrational parts of original modeling process. With this refined methodology, the system analysts can follow the stand modeling rules and process. In the other hand, the system developer also can develop the system which meet the business requirement exactly, ensure the component quality and speed up the software develop rate.

The objectives of the present study were: 1) to determine if there is a sex-based difference in lifting technique across increasing load conditions; and, 2) to examine the use of body size-adjusted tasks and back strength-adjusted loads in the analysis of lifting technique. Eleven male and 14 female participants (n=25) with no previous history of low back pain participated in the study. Participants completed freestyle, symmetric lifts of a box with handles from the floor to table height for five trials under three load conditions (10%, 20%, and 30% of their individual maximum isometric back strength). Joint kinematic data for the ankle, knee, hip, and lumbar and thoracic spine were collected using a two-camera Optotrak 3020 system (NDI, Waterloo, ON). Joint angles were calculated using a three-dimensional Euler rotation sequence and PCA was applied to assess differences in lifting technique across the entire waveform. A repeated measures ANOVA with a mixed design revealed no significant effect of sex for any of the PCs. This was contrary to previous research that used discrete points on the lifting curve to analyze sex-based differences but agreed with more recent research using more complex analysis techniques. There was a significant effect of load on lifting technique for six PCs of the lower limb (p<0.005). However, there was no significant difference in lifting technique for the thoracic and lumbar spine. It was concluded that, when load is standardized to individual back strength characteristics, males and females adopted a similar lifting technique. In addition, as load increases participants used more of a semi-squat or squat lifting technique. / Thesis (Master, Kinesiology & Health Studies) -- Queen's University, 2012-10-03 21:10:11.889

Thesis (M.App.Sc.) - Carleton University, 2005. / Includes bibliographical references (p. 162-166). Also available in electronic format on the Internet.