<p>Denna uppsats beskriver arbetet med att utveckla ett inkassohanteringsprogram. Arbetet är utfört åt inkassobyrån Exactor International Debt Collection från Mariestad. Bakgrunden till projektet är att Exactor behöver en programvara för att hålla ordning på de inkassoärenden som de har. En programvara som passar deras sätt att arbeta.</p><p>I programmet finns det möjlighet för användaren att registrera ärenden som var och en innehåller en klient, en eller flera betalningsskyldiga (gäldenärer) och en eller flera fakturor. Vidare finns det möjlighet att söka och redigera de olika delarna i ett ärende.</p><p>Uppsatsen beskriver hur programmet är konstruerat och hur det fungerar. Den beskriver också grundligt hur det kommer sig att ett ärende kommer till inkassoförfarandet. Detta för att lättare få förståelse kring resterande del av uppsatsen. Vidare beskrivs databasens design samt hur information lagras i den.</p> / <p>This paper describes the work of developing a debt collection management program. The work was carried out as an assignment from Exactor, an international debt collection company in Mariestad. The motivation was that Exactor needed a program to manage the debt collection errands they have. The program would have to fit their way of working.</p><p>In the program, it is possible for the user to register errands that each contains a client, one or more that is liable for payment (debtors), and one or more invoices. The program also implements a feature for searching and editing the different parts of an errand.</p><p>The paper describes how the program is designed and how it works. The paper also describes the basic process from the beginning of a debt to the debt collection procedures. This description is for understanding the rest of the paper. Furthermore, the database design and how information is stored in the database is described.</p>

Moderne Softwaresysteme sind komplexe Gebilde, welche häufig im Verbund mit anderen technischen und betriebswirtschaftlichen Systemen eingesetzt werden. Für die Hersteller solcher Systeme stellt es oft eine große Herausforderung dar, den oft weit reichenden Anforderungen bezüglich der Anpassbarkeit solcher Systeme gerecht zu werden. Zur Erfüllung dieser Anforderungen hat es sich vielfach bewährt, eine virtuelle Maschine in das betreffende System zu integrieren. <br><br> Die Dissertation richtet sich insbesondere an Personen, die vor der Aufgabe der Integration virtueller Maschinen in bestehende Systeme stehen und zielt darauf ab, solche für die Entscheidung über Integrationsfragen wichtigen Zusammenhänge klar darzustellen. <br><br> Typischerweise treten bei der Integration einer virtuellen Maschine in ein System eine Reihe unterschiedlicher Problemstellungen auf. Da diese Problemstellungen oft eng miteinander verzahnt sind, ist eine isolierte Betrachtung meist nicht sinnvoll. Daher werden die Problemstellungen anhand eines zentral gewählten, sehr umfangreichen Beispiels aus der industriellen Praxis eingeführt. Dieses Beispiel hat die Integration der "Java Virtual Machine" in den SAP R/3 Application Server zum Gegenstand. Im Anschluss an dieses Praxisbeispiel wird die Diskussion der Integrationsproblematik unter Bezug auf eine Auswahl weiterer, in der Literatur beschriebener Integrationsbeispiele vertieft. <br><br> Das Hauptproblem bei der Behandlung der Integrationsproblematik bestand darin, dass die vorgefundenen Beschreibungen, der als Beispiel herangezogenen Systeme, nur bedingt als Basis für die Auseinandersetzung mit der Integrationsproblematik geeignet waren. Zur Schaffung einer verwertbaren Diskussionsgrundlage war es daher erforderlich, eine homogene, durchgängige Modellierung dieser Systeme vorzunehmen. Die Modellierung der Systeme erfolgte dabei unter Verwendung der "Fundamental Modeling Concepts (FMC)". Die erstellten Modelle sowie die auf Basis dieser Modelle durchgeführte Gegenüberstellung der unterschiedlichen Ansätze zur LÖsung typischer Integrationsprobleme bilden den Hauptbeitrag der Dissertation. <br><br> Im Zusammenhang mit der Integration virtueller Maschinen in bestehende Systeme besteht häufig der Bedarf, zeitgleich mehrere "Programme" durch die integrierte virtuelle Maschine ausführen zu lassen. Angesichts der Konstruktionsmerkmale vieler heute verbreiteter virtueller Maschinen stellt die Realisierung eines "betriebsmittelschonenden Mehrprogrammbetriebs" eine große Herausforderung dar. Die Darstellung des Spektrums an Maßnahmen zur Realisierung eines "betriebsmittelschonenden Mehrprogrammbetriebs" bildet einen zweiten wesentlichen Beitrag der Dissertation. / Modern software systems are complex entities which are frequently linked to other technical and economic systems. For the manufacturers of such systems it often represents a big challenge to fulfill the demanding requirements concerning the adaptability of such systems. One possible way to meet the demands is to integrate a virtual machine into the system concerned. <br><br> This thesis is primarily intended to be used by persons who intend to integrate a virtual machine into an existing system. The primary goal is to pinpoint those dependencies which are important for decisions about integration questions. <br><br> The integration of a virtual machine into an existing system is typically accompanied by many different problems. Since these problems are often closely interconnected, it often makes no sense to treat them individually. Therefore, the problems are introduced along with an adequately chosen, complex real life example. This example deals with the integration of the "Java Virtual Machine" into the "SAP R/3" application server. Following this practical example, the discussion of integration problems is deepened by presenting an assortment of additional examples taken from the literature. <br><br> The main problem encountered during the treatment of the integration process was caused by inadequate and incomparable descriptions of the samples used. The existing descriptions were therefore unsuitable as a basis of discussion for the integration topic. For a useful discussion, it was necessary to prepare a uniform and sound modeling of these systems. This was done by adopting the "Fundamental Modeling Concepts (FMC)" technique. The created models as well as the comparison of the different approaches that can be used to solve typical integration problems form the main contribution of the thesis. <br><br> The integration of virtual machines into existing systems is frequently accompanied by the requirement to have the integrated virtual machine process several "programs" simultaneously. In view of the design features of many common virtual machines, the realization of a virtual machine integration that allows the integrated virtual machine to be operated in "multiprogram" mode is still challenging. The most challenging task in this context is the problem of keeping the resource usage of the system at a tolerable level. A comparison of measures that can be taken to reduce the resource usage of an integrated virtual machine that can be operated in "multiprogram" mode forms a second essential contribution of the thesis.

This paper presents a novel implementation of an embedded Java microarchitecture for secure, realtime, and multi-threaded applications. Together with the support of modern features of object-oriented languages, such as exception handling, automatic garbage collection and interface types, a general-purpose platform is established which also fits for the agent concept. Especially, considering real-time issues, new techniques have been implemented in our Java microarchitecture, such as an integrated stack and thread management for fast context switching, concurrent garbage collection for real-time threads and autonomous control flows through preemptive round-robin scheduling.

Denna rapport dokumenterar arbetet med att utreda hur C# och Pitch RTI fungerar tillsammans, och vilka prestandaeffekter som resulterar av denna koppling. Motiveringen kommer från att kunder till företaget Pitch har efterfrågat stöd för C# som programmeringsspråk när de använder Pitch RTI. Metoden gick ut på att successivt lära sig använda de tekniker som finns tillgängliga, för att sedan implementera lösningar på hur kopplingen ska ske. Resultaten visar hur övergången går till och prestandan som uppnåddes med hjälp av indexnotation. Tekniken IKVM hade högre prestandaindex och gick snabbare att komma igång med jämfört med tekniken C++/CLI. Men C++/CLI passar bättre ur ett distributionsperspektiv. Slutsatsen blev att Pitch som företag med hjälp av denna rapport är bättre förberett på framtida utredningar och implementationer som skulle använda de utvärderade teknikerna.

No description available.

Techn. University, Diss., 2005--Darmstadt.

Made available in DSpace on 2014-12-17T15:47:43Z (GMT). No. of bitstreams: 1 PlacidoASN.pdf: 652214 bytes, checksum: b7912104bf8e3ec91262c75b9ef5d36b (MD5) Previous issue date: 2007-09-06 / Coordena??o de Aperfei?oamento de Pessoal de N?vel Superior / Formal methods should be used to specify and verify on-card software in Java Card applications. Furthermore, Java Card programming style requires runtime verification of all input conditions for all on-card methods, where the main goal is to preserve the data in the card. Design by contract, and in particular, the JML language, are an option for this kind of development and verification, as runtime verification is part of the Design by contract method implemented by JML. However, JML and its currently available tools for runtime verification were not designed with Java Card limitations in mind and are not Java Card compliant. In this thesis, we analyze how much of this situation is really intrinsic of Java Card limitations and how much is just a matter of a complete re-design of JML and its tools. We propose the requirements for a new language which is Java Card compliant and indicate the lines on which a compiler for this language should be built. JCML strips from JML non-Java Card aspects such as concurrency and unsupported types. This would not be enough, however, without a great effort in optimization of the verification code generated by its compiler, as this verification code must run on the card. The JCML compiler, although being much more restricted than the one for JML, is able to generate Java Card compliant verification code for some lightweight specifications. As conclusion, we present a Java Card compliant variant of JML, JCML (Java Card Modeling Language), with a preliminary version of its compiler / M?todos formais poderiam ser usados para especificar e verificar software on-card em aplica??es Java Card. O estilo de programa??o para smart cards requer verifica??o em tempo de execu??o para condi??es de entrada em todos os m?todos Java Card, onde o objetivo principal ? preservar os dados do cart?o. Projeto por Contrato, em particular, a linguagem JML, ? uma op??o para este tipo de desenvolvimento e verifica??o, pelo fato da verifica??o em tempo de execu??o ser parte da implementa??o pela JML. Contudo, JML e suas respectivas ferramentas para verifica??o em tempo de execu??o n?o foram projetadas com o foco nas limita??es Java Card, sendo, dessa forma, n?o compat?veis com Java Card. Nesta disserta??o, analisamos o quanto esta situa??o ? realmente intr?nseca ?s limita??es Java Card e, se ? poss?vel re-definir a JML e suas ferramentas. Propomos requisitos para uma nova linguagem, a qual ? compat?vel com Java Card e apresentamos como o compilador desta linguagem pode ser constru?do. JCML retira da JML aspectos n?o definidos em Java Card, como por exemplo, concorr?ncia e tipos n?o suportados. Isto pode n?o ser o bastante, contudo, sem o esfor?o em otimiza??o de c?digo de verifica??o gerado pelo compilador, n?o ? poss?vel gerar c?digo de verifica??o para rodar no cart?o. O compilador JCML, apesar de ser bem mais restrito em rela??o ao compilador JML, est? habilitado a gerar c?digo de verifica??o compat?vel com Java Card, para algumas especifica??es lightweight. Como conclus?o, apresentamos uma variante da JML compat?vel com Java Card, JCML (Java Card Modeling Language), com uma vers?o de seu compilador

Made available in DSpace on 2014-12-17T15:47:44Z (GMT). No. of bitstreams: 1 BrunoEGG.pdf: 1320681 bytes, checksum: 897ca75ef7f0e564e8588d949fcc67d5 (MD5) Previous issue date: 2007-11-19 / Coordena??o de Aperfei?oamento de Pessoal de N?vel Superior / Java Card technology allows the development and execution of small applications embedded in smart cards. A Java Card application is composed of an external card client and of an application in the card that implements the services available to the client by means of an Application Programming Interface (API). Usually, these applications manipulate and store important information, such as cash and confidential data of their owners. Thus, it is necessary to adopt rigor on developing a smart card application to improve its quality and trustworthiness. The use of formal methods on the development of these applications is a way to reach these quality requirements. The B method is one of the many formal methods for system specification. The development in B starts with the functional specification of the system, continues with the application of some optional refinements to the specification and, from the last level of refinement, it is possible to generate code for some programming language. The B formalism has a good tool support and its application to Java Card is adequate since the specification and development of APIs is one of the major applications of B. The BSmart method proposed here aims to promote the rigorous development of Java Card applications up to the generation of its code, based on the refinement of its formal specification described in the B notation. This development is supported by the BSmart tool, that is composed of some programs that automate each stage of the method; and by a library of B modules and Java Card classes that model primitive types, essential Java Card API classes and reusable data structures / A tecnologia Java Card permite o desenvolvimento e execu??o de pequenas aplica??es embutidas em smart cards. Uma aplica??o Java Card ? composta por um cliente, externo ao cart?o, e por uma aplica??o contida no cart?o que implementa os servi?os dispon?veis ao cliente por meio de uma Application Programming Interface (API). Usualmente, essas aplica??es manipulam e armazenam informa??es importantes, tais como valores monet?rios ou dados confidenciais do seu portador. Sendo assim, faz-se necess?rio adotar um maior rigor no processo de desenvolvimento de uma aplica??o smart card, visando melhorar a sua qualidade e confiabilidade. O emprego de m?todos formais como parte desse processo ? um meio de se alcan?ar esses requisitos de qualidade. O m?todo formal B ?e um dentre os diversos m?todos formais para a especifica??o de sistemas. O desenvolvimento em B tem in?cio com a especifica??o funcional do sistema, continua com a aplica??o opcional de refinamentos ? especifica??o e, a partir do ?ltimo n?vel de refinamento, ? poss?vel a gera??o de c?digo para alguma linguagem de programa??o. O formalismo B conta com bom suporte de ferramentas e a sua aplica??o a Java Card mostra-se bastante adequada, uma vez que a especifica??o e desenvolvimento de APIs ?e o ponto forte de B. O m?todo BSmart aqui proposto visa promover o desenvolvimento rigoroso de aplica??es Java Card a partir da gera??o de c?digo da aplica??o com base em refinamentos da sua especifica??o formal descrita na nota??o B. O processo de desenvolvimento descrito no m?todo ? apoiado pela ferramenta BSmart, a qual constitui-se por alguns programas que automatizam cada etapa do m?todo; e por uma biblioteca de m?dulos B e classes Java Card que modelam tipos primitivos, classes essenciais da API Java Card e estruturas de dados reutiliz?veis

Made available in DSpace on 2014-12-17T15:48:00Z (GMT). No. of bitstreams: 1 SimoneOS_DISSERT_capa_ate_pag44.pdf: 4276014 bytes, checksum: c178262769ab9981c0bbfc10faf1c633 (MD5) Previous issue date: 2012-02-10 / Coordena??o de Aperfei?oamento de Pessoal de N?vel Superior / The development of smart card applications requires a high level of reliability. Formal methods provide means for this reliability to be achieved. The BSmart method and tool contribute to the development of smart card applications with the support of the B method, generating Java Card code from B specifications. For the development with BSmart to be effectively rigorous without overloading the user it is important to have a library of reusable components built in B. The goal of KitSmart is to provide this support. A first research about the composition of this library was a graduation work from Universidade Federal do Rio Grande do Norte, made by Thiago Dutra in 2006. This first version of the kit resulted in a specification of Java Card primitive types byte, short and boolean in B and the creation of reusable components for application development. This work provides an improvement of KitSmart with the addition of API Java Card specification made in B and a guide for the creation of new components. The API Java Card in B, besides being available to be used for development of applications, is also useful as a documentation of each API class. The reusable components correspond to modules to manipulate specific structures, such as date and time. These structures are not available for B or Java Card. These components for Java Card are generated from specifications formally verified in B. The guide contains quick reference on how to specify some structures and how some situations were adapted from object-orientation to the B Method. This work was evaluated through a case study made through the BSmart tool, that makes use of the KitSmart library. In this case study, it is possible to see the contribution of the components in a B specification. This kit should be useful for B method users and Java Card application developers / O desenvolvimento de aplica??es para smart cards requer um alto grau de confiabilidade. M?todos formais fornecem meios para que esta confiabilidade seja alcan?ada. O m?todo e a ferramenta BSmart fornecem uma contribui??o para que o desenvolvimento para smart cards seja feito com o aux?lio do m?todo formal B, gerando c?digo Java Card a partir de especifica??es B. Para que o desenvolvimento com o BSmart seja efetivamente rigoroso sem sobrecarregar o usu?rio do m?todo ? importante que haja uma biblioteca de componentes reutiliz?veis feitos em B. O KitSmart tem como objetivo prover esse aux?lio. Um primeiro estudo sobre a composi??o dessa biblioteca foi tema de uma monografia de gradua??o do curso de Bacharelado em Ci?ncia da Computa??o da Universidade Federal do Rio Grande do Norte, feita por Thiago Dutra em 2006. Esta primeira vers?o do kit resultou na especifica??o dos tipos primitivos permitidos em Java Card (byte, short e boolean) em B e a cria??o de componentes reutiliz?veis para o desenvolvimento de aplica??es. Esta disserta??o prov? o aperfei?oamento do KitSmart com o acr?scimo da especifica??o da API Java Card em B, e um guia para o desenvolvimento de novos componentes. A API Java Card especificada em B, al?m de estar dispon?vel para ser usada no desenvolvimento de projetos, serve como documenta??o ao especificar restri??es de uso para cada classe da API. Os componentes reutiliz?veis correspondem a m?dulos para manipula??o de estruturas espec?ficas, como data e hora, por exemplo. Estes tipos de estruturas n?o est?o dispon?veis em B ou Java Card. Os componentes reutiliz?veis para Java Card s?o gerados a partir das especifica??es verificadas formalmente em B. O guia cont?m informa??es de consulta r?pida para especifica??o de diversas estruturas e como algumas situa??es foram contornadas para adaptar a orienta??o a objetos ao M?todo B. Este trabalho foi avaliado atrav?s de um estudo de caso feito com a ferramenta BSmart que faz uso da biblioteca KitSmart. Neste estudo de caso, ? poss?vel ver a contribui??o dos componentes em uma especifica??o B. Este kit dever? ser ?til tanto para usu?rios do m?todo B como para desenvolvedores de aplica??es Java Card em geral

Made available in DSpace on 2014-12-17T14:52:34Z (GMT). No. of bitstreams: 1 IdelmarciaDO.pdf: 781272 bytes, checksum: fb2e5ba3247ab47eff60bb3c30b07e21 (MD5) Previous issue date: 2007-10-19 / The spread of the Web boosted the dissemination of Information Systems (IS) based on the Web. In order to support the implementation of these systems, several technologies came up or evolved with this purpose, namely the programming languages. The Technology Acceptance Model TAM (Davis, 1986) was conceived aiming to evaluate the acceptance/use of information technologies by their users. A lot of studies and many applications have used the TAM, however, in the literature it was not found a mention of the use of such model related to the use of programming languages. This study aims to investigate which factors influence the use of programming languages on the development of Web systems by their developers, applying an extension of the TAM, proposed in this work. To do so, a research was done with Web developers in two Yahoo groups: java-br and python-brasil, where 26 Java questionnaires and 39 Python questionnaires were fully answered. The questionnaire had general questions and questions which measured intrinsic and extrinsic factors of the programming languages, the perceived usefulness, the perceived ease of use, the attitude toward the using and the programming language use. Most of the respondents were men, graduate, between 20 and 30 years old, working in the southeast and south regions. The research was descriptive in the sense of its objectives. Statistical tools, descriptive statistics, main components and linear regression analysis were used for the data analysis. The foremost research results were: Java and Python have machine independence, extensibility, generality and reliability; Java and Python are more used by corporations and international organizations than supported by the government or educational institutions; there are more Java programmers than Python programmers; the perceived usefulness is influenced by the perceived ease of use; the generality and the extensibility are intrinsic factors of programming languages which influence the perceived ease of use; the perceived ease of use influences the attitude toward the using of the programming language / A difus?o da Web impulsionou a dissemina??o de Sistemas de Informa??o (SI) baseados na Web. Para apoiar a implementa??o desses sistemas, diversas tecnologias surgiram ou evolu?ram com este prop?sito, dentre elas as linguagens de programa??o. O Modelo de Aceita??o de Tecnologia - TAM (Davis, 1986) foi concebido com o intuito de avaliar a aceita??o/uso de tecnologias da informa??o por seus usu?rios. V?rios estudos e aplica??es diversas t?m utilizado o TAM, no entanto, n?o foi encontrada na literatura men??o a utiliza??o de tal modelo com rela??o ao uso de linguagens de programa??o. Este estudo objetiva investigar que fatores influenciam o uso de linguagens de programa??o utilizadas no desenvolvimento de sistemas Web por parte de seus desenvolvedores, utilizando uma extens?o do TAM, proposta neste estudo. Para tanto, foi realizada uma pesquisa com desenvolvedores Web pertencentes a dois grupos do Yahoo: java-br e python-brasil, no qual foram respondidos, na ?ntegra, 26 question?rios Java e 39 Python. O question?rio tinha quest?es de car?ter geral e quest?es que mediam os fatores intr?nsecos e extr?nsecos das linguagens de programa??o, a utilidade percebida, a facilidade de uso percebida, a atitude sobre o uso e o uso da linguagem de programa??o. A maioria dos respondentes eram homens, com n?vel superior, idade entre 20 e 30 anos, atuando nas regi?es sudeste e sul. Do ponto de vista de seus objetivos, a pesquisa foi descritiva. Em rela??o ? forma de abordagem, quantitativa. Para a an?lise de dados foram utilizadas ferramentas estat?sticas, estat?stica descritiva, componentes principais e an?lise de regress?o linear m?ltipla. Os principais resultados da pesquisa foram: Java e Python possuem independ?ncia de m?quina, extensibilidade, generalidade e confian?a; Java e Python s?o mais utilizadas por corpora??es e organiza??es internacionais do que apoiadas pelo governo ou institui??es de ensino; h? mais programadores Java do que Python; a utilidade percebida ? influenciada pela facilidade de uso percebida; a generalidade e a extensibilidade s?o fatores intr?nsecos as linguagens de programa??o que influenciam a facilidade de uso percebida; a facilidade de uso percebida influencia a atitude em rela??o ao uso da linguagem de programa??o