The maintenance of large-scale software systems without trace information between development artifacts is a challenging task. This thesis focuses on the problem of supporting software maintenance through a mechanism for establishing traceability relations between the system requirements and its code elements. The core of the proposed solution is a set of design rules that regulates the positional (e.g., package), structural (e.g., class), and behavioral (e.g., method) aspects of the system elements, thus establishing traceability between requirements and code. We identify several types of requirements each of which can be supported by design rules. We introduce a rule-based approach to software construction and demonstrate that such a process can support maintainability through two mechanisms: (a) traceability and (b) reduction of defect rate. We distinguish our work from traditional traceability approaches in that we regard traceability as an intrinsic structural property of software systems. This view of traceability is in contrast to traditional traceability approaches where traceability is achieved extrinsically through creating maps such as the traceability matrices or allocation tables. The approach presented in this thesis has been evaluated through conducting several empirical studies as well as building a proof-of-concept system. The results we obtained demonstrate the effectiveness and usefulness of our approach.

The maintenance of large-scale software systems without trace information between development artifacts is a challenging task. This thesis focuses on the problem of supporting software maintenance through a mechanism for establishing traceability relations between the system requirements and its code elements. The core of the proposed solution is a set of design rules that regulates the positional (e.g., package), structural (e.g., class), and behavioral (e.g., method) aspects of the system elements, thus establishing traceability between requirements and code. We identify several types of requirements each of which can be supported by design rules. We introduce a rule-based approach to software construction and demonstrate that such a process can support maintainability through two mechanisms: (a) traceability and (b) reduction of defect rate. We distinguish our work from traditional traceability approaches in that we regard traceability as an intrinsic structural property of software systems. This view of traceability is in contrast to traditional traceability approaches where traceability is achieved extrinsically through creating maps such as the traceability matrices or allocation tables. The approach presented in this thesis has been evaluated through conducting several empirical studies as well as building a proof-of-concept system. The results we obtained demonstrate the effectiveness and usefulness of our approach.

Made available in DSpace on 2014-06-12T15:52:08Z (GMT). No. of bitstreams: 1 license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5) Previous issue date: 2008 / O projeto de software visa descrever os principais aspectos do sistema a ser construído através de mecanismos que ajudam a raciocinar sobre a complexidade. Dentre as ativi- dades do projeto de software, destaca-se a elaboração e documentação da arquitetura, um dos principais mecanismos para raciocinar e lidar com essa complexidade. Uma das principais metas do projeto da arquitetura é a modularizadão do sistema através do esta- belecimento de design rules que deverão ser obedecidas pelos desenvolvedores. Exemplos de design rules estabelecidas no projeto da arquitetura são os serviços disponibilizados pelos componentes e as regras de comunicação entre estes. A modularizacão dos sistemas de software também motivou o surgimento da Pro- gramação Orientada a Aspectos (POA). Entretanto estudos recentes mostraram que a utilização da POA apesar de ser um meio efetivo para modularizacão de interesses trans- versais, pode prejudicar a modularidade dos demais interesses se design rules não forem estabelecidas pelo projetista. Muitas das design rules necessárias para melhorar a modu- laridade de sistemas orientados a aspectos são definidas na fase de projeto da arquitetura do software. Para criação e documentação do projeto da arquitetura uma das principais abordagens é a utilização de Linguagens de Descrição de Arquitetura (LDA), que permitem descrever a arquitetura de forma clara e não ambígua, possibilitando a verificação de uma série de propriedades que antes são poderiam ser analisadas depois do implementação do software. O problema na utilização desta abordagem é que o modelo de arquitetura utilizado pela maioria das LDAs, formado por abstrações como componentes e conectores, é diferente do modelo baseado em objetos utilizado por muitas linguagens de programação, tornado difícil o mapeamento e a consistência entre essas fases do desenvolvimento. Entretanto, para garantir a modularidade do sistema e as propriedades arquiteturais obtidas através de uma LDA, é necessário apenas garantir que as design rules estabelecidas por esta são obedecidas pelo código desenvolvido. Neste trabalho propomos um mapeamento das design rules implicitamente definidas por uma linguagem de descrição arquitetural para uma linguagem de descrição de design rules, responsável por verificar se estas estão sendo obedecidas no código desenvolvido. A verificação das design rules permite garantir que a modularidade e as propriedades arqui- teturais obtidas através do projeto da arquitetura sejam válidas no código desenvolvido. A LDA escolhida foi a linguagem AspectualAcme, que utiliza os conceitos da orientação a aspectos, permitindo que as design rules geradas melhorem também a modularidade de sistemas orientados a aspectos. Para diminuir os custos com a tradução, também foi construída uma ferramenta capaz de gerar automaticamente, a partir de uma especificação válida em AspectualAcme, as regras na linguagem de descrição de design rules. Além da economia de tempo dos desenvolvedores, o suporte automático para tradução evita que erros sejam cometidos ou que design rules sejam esquecidas, garantindo dessa forma as propriedades verificadas no modelo arquitetura e a modularidade do sistema

This thesis is on the fatigue assessment of cast components with special attention to defects. The primary material in view is nodular cast iron, but also cast steel is considered. However, the fatigue behaviour is in principle valid for general use on other cast metals.The first two papers is about general cast material behaviour in fatigue loading. The materials considered are a high strength alloyed cast steel and a medium strength nodular cast iron. It is concluded that cast defects is the main fatigue initiation cause and it is only in exception that the fatigue life is not ruled by fracture mechanics. The third paper is a fracture mechanics evaluation of a nodular iron cast sleeve. The analysis of the component is based on crack initiation from cast defects and low-cycle fatigue. Fracture mechanics material parameters for Paris law, c and m, are extracted for the materials considered. In paper D design quality rules for nodular cast iron based on the Swedish standard SS 11 40 60 is presented. The quality rules regard cast defects in fatigue assessments and facilitate defect-based component design. In paper E, a finite element tool that is capable to predict and calculate 3D crack propagation for embedded cracks and defects is presented. The tool is an add-on for ANSYS finite element program. In paper F, closure equations for nodular cast iron are proposed in parallel to refined fracture mechanics material data. The paper includes crack propagation at different load ratios and in different microstructures.Summarized, the thesis composes a further development of the fatigue assessment of cast components. The central role of defects in fatigue is clarified and tools are provided for fracture mechanics evaluations of defects as well as for defect based design. The quality rules are also fit for application in manufacturing and for acceptance tests, hence covering the span from design to complete product. / QC 20100712 / Gjutdesign

Electronic Design Automation (EDA) tools are today very capable computer programs supporting electronic engineers with the design of printed circuit board (PCB). All tools have their strengths and weaknesses; when choosing the right tool many factors needs to be taken into consideration aside from the tools themselves. Companies need to focus on the product and revenues for a business to be viable. Depending on the knowledge and strengths of the company, the choice of tools varies. The decision should be based on the efficiency of the tools and the functions necessity for the company rather than the price tags. The quality and availability of support for the tools, training costs, how long will it take to put the tool in operation and present or future collaboration partners is equally important factors when deciding the right tool. The absence of experience and knowledge of the current tool within a company is a factor which could affect important operation; therefore it is important to provide training and education on how to use the tool to increase its efficiency. Providing training and education can be a large expense, but avoids changes within and makes the business competitive. The choice of EDA tool should be based on the employed engineer’s current knowledge and experience of the preferred tool. If the employed engineer’s knowledge and experience varies too much, it might be preferable to make a transition to one of the tool by training and education. Product lifecycle management (PLM) is a data management system and business activity management system which focuses on the lifecycle of a product. To manage the lifecycle of a product it is necessary to split the lifecycle into stages and phases for a more manageable and transparent workflow. By overseeing a product’s entire lifecycle there are benefits which affects many areas. PLM greatest benefits for EDA are collaboration across separate groups and companies by working together through a PLM platform, companies can forge strong design chains that combine their best capabilities to deliver the product to the customers. This report is a study on evaluating which EDA suits the company with consideration of the employed engineer’s demands, requests and competence. The interests in PLM made the company suggest a short theory study on PLM and EDA benefits.

La miniaturisation des circuits intégrés est largement tributaire de la lithographie optique qui va définir la taille minimale qu’il est possible d’obtenir sur un circuit. Actuellement, des moyens considérables sont mises en œuvre pour aller au-delà de la limite de résolution des systèmes optiques qui sont en production. Parmi les techniques qui sont envisagées, l'auto-assemblage des copolymères à bloc permet de diminuer la résolution des systèmes optiques utilisés et apparait donc comme une possible solution. Les copolymères à bloc sont des chaînes de polymères constituées de 2 polymères. Sous l’action de la chaleur, un mélange de copolymères à bloc va s’organiser de sorte que les polymères forment des domaines disjoints et réguliers. Ensuite, l’un des 2 domaines peut être gravé pour former les motifs désirés. En contraignant cet assemblage, il est possible de contrôler l’impression des motifs ainsi obtenus.Pour être utilisé en production, ce procédé doit être capable d’imprimer les motifs désirés avec une certaine précision afin d’assurer la fiabilité des niveaux ainsi obtenus. Tout l’enjeu de cette thèse est de mettre en place une analyse permettant de garantir cette impression avec une fiabilité suffisante. Nous nous sommes en particulier intéressés à un critère à un critère statistique portant sur le recouvrement de motifs entre 2 niveaux différents.Pour y parvenir, nous avons établis une plateforme pour établir des règles de dessin permettant d’assurer ce critère. Nous avons dans un premier temps simplifier le critère statistique en un critère plus simple à utiliser en étudiant finement les variabilités misent en jeux. Pour obtenir expérimentalement des valeurs de variabilités, nous nous sommes intéressés à l’étude des images SEM afin d’extraire de manière la plus automatisée possible ce type d’information. Finalement, nous avons établi pour le procédé DSA un ensemble de règles de dessin spécifique pour assurer notre critère. / The miniaturization of integrated circuits is largely dependent on optical lithography which is used to define the minimum size that can be obtained on a circuit. Currently, considerable resources are being deployed to go beyond the resolution limit of the optical systems that are in production. Among the techniques that are envisaged, block copolymer self-assembly makes it possible to reduce the resolution of the optical systems used and thus appears as a possible solution. Block copolymers are polymer chains consisting of two polymers. Under the action of heat, a mixture of block copolymers will be organized so that the polymers form disjoint and regular domains. Then one of the two domains can be etched to form the desired patterns. By constraining this assembly, it is possible to control the printing of the patterns thus obtained.To be used in production, this process must be able to print the desired patterns with a certain precision in order to ensure the reliability of the levels thus obtained. This thesis aims to set up an analysis to guarantee this impression with sufficient reliability. In particular, we look at a statistical criterion relating to the recovery of motifs between two different levels.To achieve this, we have established a platform to establish drawing rules to ensure this criterion. We first simplify the statistical criterion into a simpler criterion to use by studying finely the variabilities involved. To obtain variability values experimentally, we are interested in studying SEM images in order to extract this type of information in the most automated way possible. Finally, we have established for the DSA process a set of specific drawing rules to ensure our criterion.

Made available in DSpace on 2014-06-12T15:55:28Z (GMT). No. of bitstreams: 2 arquivo2238_1.pdf: 2132040 bytes, checksum: 7403ada2f7f20b6592ef20ce13dad893 (MD5) license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5) Previous issue date: 2011 / Conselho Nacional de Desenvolvimento Científico e Tecnológico / Programação Orientada a Aspectos (POA) é um mecanismo de programação proposto para modularizar os requisitos transversais, visando um aumento na modularidade de software. Entretanto, recentemente alguns autores tem alegado que o uso de POA quebra a modularidade das classes. Isso acontece pois, sem o uso de interfaces apropriadas entre classes e aspectos, diversas propriedades de um design modular, como compreensibilidade, manutenabilidade e desenvolvimento em paralelo, são comprometidas na presença de aspectos. Diversas interfaces especializadas (design rules) para desacoplar classes e aspectos foram propostas visando atenuar esse problema, como XPIs e LSD. Entretanto, tais interfaces são específicas para a linguagem AspectJ, que possui problemas de reúso e modularidade de aspectos. CaesarJ, por outro lado, é uma linguagem de programação orientada a aspectos com forte suporte para reúso e modularidade de aspectos. Essa linguagem combina as construções OA pointcut e advice com avan¸cados mecanismos de modularização OO. Nesse trabalho nós exploramos algumas construções de CaesarJ com o intuito de verificar se elas podem ser utilizadas para definir Design Rules que permitam um desenvolvimento modular de código OO e OA. Além disso, nós propomos CaesarJ+, uma extensão de CaesarJ que foca no aumento de modularidade. Essa extensão introduz construções que permitem impor restrições estruturais sobre os códigos OO e OA. Um compilador para CaesarJ+, que verifica se as restrições especificadas nas Design Rules estão sendo seguidas, e transforma o código CaesarJ+ em código CaesarJ também foi desenvolvido nesse trabalho. Para avaliar CaesarJ+, nós comparamos as implementações de três estudos de caso em CaesarJ+ e CaesarJ. Nossos resultados revelam que o uso de CaesarJ+ proporciona ganho de expressividade.

The anti-coagulant warfarin is consumed by around 200 000 people in Sweden every year. There are many dose affecting factors, and if the dose is wrong the consequences can be severe. Hence patients are required to regularly have their coagulation ability tested so that the dosage can be adjusted if needed. In this study the dosage regulation processes of warfarin in Swedish home care are examined through a case study, where-after an information infrastructure design is created that could support the identified needs. The proposed design is formed through combining three separate IT-capabilities: a general purpose health care platform, a warfarin specialist software and a medication reminder application. The design was guided by the application of the information infrastructure design rules with the aim of uncovering problems and possibilities associated with this design approach. By applying the information infrastructure design rules a technical architecture could successfully be created. Additionally, information exchange specifications and important decision making points could be identified or solved successfully. However the design rules were found to assume an unlikely level of openness and to lack a focus on organizational and legal factors which make them difficult to apply in practice.

This work deals with handicapped users' issues caused by limitations of their handicap and their ability of reading and text understanding. It reports on a summary of basic rules of accessible web pages' creation. It also introduces a solution with help of automatic transformation of inaccessible web pages to their accessible version.

No description available.