Stuttgart, Univ., Fakultät Informatik, Studienarb., 1997.

Stuttgart, Univ., Fakultät Informatik, Studienarb., 1997.

Konstanz, FH, Diplomarb., 2002.

Bergkvist insjön AB is a sawmill yard which is capable of producing 350,000 cubic meter of timber every year this requires lot of internal resources. Sawmill operations can be classified as unloading, sorting, storage and production of timber. In the company we have trucks arriving at random they have to be unloaded and sent back at the earliest to avoid queuing up of trucks creating a problem for truck owners. The sawmill yard has to operate with two log stackers that does several tasks including transporting the logs from trucks to measurement station where the logs will be sorted into classes and dropped into pockets from pockets to the sorted timber yard where they are stored and finally from there to sawmill for final processing. The main issue that needs to be answered here is the lining up trucks that are waiting to be unload, creating a problem for both sawmill as well as the truck owners and given huge production volume, it is certain that handling of resources is top priority. A key challenge in handling of resources would be unloading of trucks and finding a way to optimize internal resources.To address this problem i have experimented on different ways of using internal resources, i have designed different cases, in case 1 we have both the log stackers working on sawmill and measurement station. The main objective of having this case is to make sawmill and measurement station to work all the time. Then in case 2, i have divided the work between both the log stackers, one log stacker will be working on sawmill and pocket_control and second log stacker will be working on measurement station and truck. Then in case 3 we have only one log stacker working on all the agents, this case was designed to reduce cost of production, as the experiment cannot be done in real-time due to operational cost, for this purpose simulation is used, preliminary investigation into simulation results suggested that case 2 is the best option has it reduced waiting time of trucks considerably when compared with other cases and it showed 50% increase in optimizing internal resources.

對於不同團隊協同開發大型的應用程式，常會面臨應用程式自行處理例外事件而未正確回報用戶之執行結果與無法得知封閉式類別庫內部詳細呼叫流程，導致偵錯不易的困擾。有鑒於此，本研究將實作一個工具，利用Aspect-Oriented Programming(AOP)特性，將AspectJ織入JDBC驅動程式並賦予存取紀錄儲存之功能，既可免除應用程式本身未針對資料庫儲存存取紀錄的問題，直接儲存所有存取紀錄，亦不影響資料庫操作，更可以分辦造成錯誤發生的程式以釐清問題，有效幫助偵錯。此工具適用於任何使用JDBC介面去存取資料庫管理系統（DBMS）之JAVA應用程式，它能在不影響應用程式的情況下客製化儲存應用程式透過JDBC驅動程式連結資料庫管理系統（DBMS）的存取紀錄，並利用存取紀錄進行分析並複製存取行為，以提供更豐富的資訊進一步協助偵錯。 / When using a large database application which is jointly designed by different teams, the administrators are often confronted with a problem that the application handles the exception spontaneously and often fails to report back the result of user’s execution. Therefore, the administrator can’t be informed of the details of the calling flow in case of exceptions. This will make it not only difficult to find which part of the application goes wrong, but also hard to fix. To resolve this problem, this thesis designs and implements an aspect-based debugging tool for such database applications. The key idea behind the tool is that, instead of adapting the large application for logging database access activities, we target at the JDBC driver and make JDBC driver capable of saving access log. This tool works for any JAVA applications that use JDBC interface to access database. Without any modification to the user-level application, this tool can save the access log obtained by application which use JDBC driver to connect the database, and the administrator can customize the access log. By analyzing the access records and duplicating the access behavior, this tool provides more information to further assist in application debugging.

<p>Denna rapport beskriver utvecklingsprocessen av ett bokningssystem till en frisersalong. Bokningssystemet ska användasför att boka tider för kunder och också underlätta administrationen för de anställda. I rapporten beskrivs arbetsprocessen steg för steg med kravspecifikation, designspecifikation, gränssnitt och till sist resultat. </p><p>Bokningssystemet täckte alla grundläggande krav som kunden hade. En förbättring vore att i utvecklingen av gränssnittet mer noggrant analysera användarens krav ur ett användbarhetsperspektiv. På så sätt skulle en del problem i användbarheten av systemet identifieras tidigare. </p><p>Examensarbetet ledde fram till ett bokningssystem till en frisersalong som används dagligen för att sköta arbetet med bokningar av kunder. Systemet utvecklades i Java och använder databashanteraren MySQL.</p>

Diplomová práce se zaměřuje na propojení databáze Oracle s vývojovými platformami Java, .Net a Lotus Notes/Domino. Po vysvětlení základních principů a technik práce s databází následuje část, která si klade za cíl jednotlivé možnosti propojení porovnat a otestovat. Na všech 3 platformách existují vyspělé propojovací technologie pro práci s databází, mezi nejznámější patří ODBC, JDBC, ADO.NET a LC (Lotus Connectors). Jednotlivé možnosti propojení se na všech třech vývojových platformách značně liší. Společná zůstává jen základní funkcionalita pro práci s databází (sestavení připojení, řízení transakcí, volání SQL příkazů, přenášení základních datových typů a volání uložených procedur). Pro praktické ověření jednotlivých propojovacích produktů byla vyvinuta testovací/benchmark aplikace, která byla z jazyka Java naimplementována i do prostředí .NET (C#) a Lotus Notes/Domino (Lotus Script). Bylo naimplementováno a spuštěno 253 testů na 12 produktech od 8 výrobců. Podkladem pro zpracování diplomové práce a realizaci testů byla dokumentace k těmto systémům a další odborná literatura. Díky těmto testům bylo možné, v rámci možností, porovnání jednotlivých produktů i platforem. Systematické testování a práce s těmito produkty ukázaly, že jednotlivé produkty jsou velmi rozdílné v ceně, kvalitě, výkonu, ale i ve svých specifických funkcích.

The aim of this work is to create an application for interconnect diferrences among temporal databases. The main idea of this project is allow user work with languages TSQL2 and ATSQL without user intervention into relation database system. This work also contain implementation of interface JDBC and demonstration application for testing temporal queries.

No description available.

<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>