This thesis investigates how different Linux-distributions installation interface relate to the ISO 9241 standard, parts 12 and 13, and how they relate to the installation interface of Windows XP, with the hypothesis: "There is a Linux-distribution whose installation interface according to applicable HCIrecommendations is equivalent to that of Windows XP." With the checklists provided by ISO 9241 an empirical study has been made, and so comparable measurements of how well the Linux-distributions and Windows XP follows the recommendations of the standard was obtained. By comparing the results from the tests similarities and differences between the installation interfaces can be deducted. As the result and the conclusion shows there are Linux-distributions whose installation interface, according to the applicable HCI-recommendations, are equivalent to that of Windows XP.

In the software industry a number of different software processes has been used throughout the years to address known problems with software development, despite their intention complains has been raised that some of these are too bureaucratic. The Agile Alliance was formed in 2001 and aimed to solve this problem, they developed a manifesto and twelve principles which are supported by all Agile software processes. The purpose with the manifesto and its principles is to uncover better ways of developing software and these are by many intercessors of Agile seen as common sense and not completely new ideas. The aim with this master thesis is to answer the question if companies that explicitly claim that they do not use any Agile software process are already applying some of these ideas since they are thought of as obvious and common sense. The comparison in this thesis is performed between the project lifecycles used in specific projects by five non-Agile software companies and four identified lifecycle characteristics and two more general characteristics of the Agile software processes Extreme Programming (XP) and Dynamic Systems Development Method (DSDM). The result from the analysis of these interviews has shown that it is very difficult to decide if a software company really is working as described by XP or DSDM, this is due to that many different factors affect the final outcome. For example type of project and is the software company using different software processes for different kinds of projects. Since we just covered specific projects we were only able to conclude with absolute certainty actions that really were performed in just these projects. The project lifecycles of these software companies had some similarities with the above mentioned Agile software processes, but as a whole the analysis showed that they are quite different due to that two very important characteristics according to us, namely iterative development and frequent releases, were not applied by any of the software companies and that their project phases differed tremendously compared to XP and DSDM. Our common sense hypothesis for Agile software development was shown in this investigation to be incorrect since important activities were not performed by any of the software companies. Instead of using an iterative approach with frequent releases they all followed sequential waterfall like software processes.

Rapporten har som mål att skapa en fördjupad förståelse kring utvecklingsmetoder, tester och automatisering inom programvaruutveckling. Innehållet i rapporten berättar vad som påverkar valet av dessa samt går igenom de teoretiska grunderna i en omfattande teoridel. Rapporten tar också upp hur valet av utvecklingsmetod påverkar möjligheten till att testa och automatisera ett projekt. Förutom den grundliga teoretiska delen finns det intervjuer med personer och företag som är insatta inom ämnet. Huvudfrågan har varit hur deras organisation anpassar utvecklingsmetoderna, testerna och automatiseringen till de olika projekt de jobbar med. För de tre första intervjuerna finns det en mer ingående analys av arbetssätt samt förslag till förbättringar. I slutsatserna har skribenterna gjort en bedömning huruvida dessa olika faktorer påverkar varandra och vad som bör tänkas på vid val av utvecklingsmetod, tester och automatisering.

Workshop Mensch-Computer-Vernetzung Der Vortrag befasst sich mit der Umstellung der Betriebssystemplattform WindowsNT auf WindowsXP im Rechenzentrum der Technischen Universität Chemnitz. Der vorrangige Einsatz von WindowsXP erfolgt in PC-Pools. Es werden die angestrebten Basistechnologien vorgestellt: Authentifizierung Fileserving Systeminstallation Systemaktualisierung

Artikel zur bevorstehenden Einführung von Windows XP in das Dienstespektrum des URZ. Konkret werden ausgewählte PC-Pools genannt sowie technologische Ziele mit Auswirkungen auf den Nutzer. Weiterhin werden Aspekte zum angekündigten Admindienst Windows XP und die Einstellung des Admindienstes Windows NT diskutiert.

Es wird die unter XP verfügbare Anwendungssoftware genannt, Änderungen in der Technologie der Softwarebereitstellung, sowie organisatorische Informationen.

Folien eines Vortrages im Rahmen des Seminars "Administration heterogener verteilter Rechnersysteme". Es wird der "Administrationsdienst Windows XP" der TU Chemnitz vorgestellt. Im Rahmen dieses Dienstes wird eine größere Zahl von Arbeitsplatz-PCs zentral installiert und administriert. Fokus dieses Vortrags sind die Prinzipien sowie die verwendeten Basistechnologien.

Workshop "Netz- und Service-Infrastrukturen" Werkzeuge zur Konfiguration und Systemwartung von PCs im Administrationsdienst Windows.

Workshop "Netz- und Service-Infrastrukturen" Beschreibung und Bewertung systemeigener Verfahren zur automatisierten Installation von Druckern und Scannern unter Windows XP, daraus Ableitung und Beschreibung der im XP-Administrationsdienst praktizierten Verfahren.

Aims Preservation of peri-cervical dentin during the preparation of endodontic access is important to prevent fractures and improve the long-term prognosis. The purpose of this study was to evaluate the impact of rotary file instrumentation (TruNatomy and XP-Endo Shaper) on peri-cervical dentin removal, depending on access size. Materials and Methods Forty 3D printed mandibular first molars, with either a small or large access design, were instrumented using TruNatomy or XP-endo Shaper file systems. Canal volumes were calculated based on micro-computed tomography data obtained pre- and post-operatively. Digital sectioning of each reconstructed volume was performed 90-degrees to the long axis at the floor of the pulp chamber at 5 levels, at the pulp chamber floor (Level 0) as well as 1 and 2mm coronally and apically of Level 0. Linear measurements were taken from the inner wall of the access cavity or canal to the outer surface of the tooth for both instrumentation techniques and compared to the unprepared control dataset. These measurements served as an approximation of remaining peri-cervical dentin after root canal instrumentation. Results Some of the coronal measurements were not reportable for the control group due to incomplete capture of the crown during the microCT scan. The remaining peri-cervical dentin thickness at the level of the pulpal floor and coronally were significantly (p<0.01) affected by the access cavity size, with the smaller access preserving more dentin in all samples. Apical to the pulpal floor, there was no significant difference between instrumentation groups at the data points evaluated. Remaining dentin thickness was largest at coronal section 1 and smallest at apical section 6 with 3.81mm (p = 0.05) and 1.84mm (p = 0.06), respectively. Conclusion Access cavity size had a significant impact on remaining dentin thickness at the level of the pulpal floor and coronally, with more remaining dentin in the conservative access group, irrespective of instrumentation technique. Future studies will evaluate dentin thickness in the furcation and mid root level, as well as apical canal transportation, and procedural errors.