Engembangan Database Evaluasi Diri Jurusan Pendidikan Teknik Boga dan Busana Ft Uny

This research aims at develping database of self evaluation among the students and lecturers of Food and Clothing Department with empirical testing. This database was implemented to five study programs, i.e. Food Engineering Education (S1), Clothing Engineering Education (S1), Food Engineering (DIII), Clothing Engineering (DIII) and Make Up & Beauty (DIII). This research was using Reseach and Development Approach. The development of database was conducted through need analysis, planning, making program prototype, testing and evaluation. The software program to make database was using Microsoft Access 2007. The source of data was from the lecturers and the students. The data collection method was using need analysis data, documentation for planning, and datbase prototype creation, observation for program testing. Data analysis was conducted through qualitative descriptive analysis according to the research stages. The finding was in the form of database of self-evaluation consisted of students and lecturers data from Food and Clothing Department, which had been tested emphirically. The development stage had completed until the making of prototype of electronic database. The development procces had conducted throgh some stages, i.e. analysis, designing, implementation and evaluation

Re-engineering a database driven software tool: Rebuilding, automating processes and data migration

This thesis aims to re-engineer a database driven software tool that is used to insert engine related data and generate an EIAPP Technical File that is needed for certification of marine engines to show that they comply with IMO’s emission regulations specified in MARPOL Annex VI and NTC 2008. The need for an updated tool has emerged as the way of working is to be changed, from document management to content management. The current tool is also divided into two different tools, one for engines built in Italy and one for engines built in Finland, which leads to another objective that is to merge these tools into one. The tools are built-in Microsoft Access which does no longer suit the needs. Therefore, the last purpose of the research is to conduct a data migration from Microsoft Access to SQL Server. The research was divided into theoretical and empirical research. The theoretical part first presented the theory behind software engineering and software re-engineering. Then the theory behind databases and data migration was explored to at last go through the emission regulation and certification for marine diesel engines to better understand why the tool is needed. In the empirical part, first, the existing tool and the certification process were inspected. Furthermore, the research method, the constructive research approach was discussed, that focuses on producing a construction (solution) to a real-world problem in practice. At last, a more in-depth analysis of the tool was made to propose a plan on how to re-engineer the tool, which included an implementation process plan. The main result of this research is a re-engineered EIAPP tool that has the front-end in Microsoft Access and back-end in SQL Server. The tables have been restructured to comply with the change to only use one document number for the whole Technical File. The forms have been redesigned and processes have been automated to make the tool more reliable and efficient. The new re-engineered tool has more than 50 % fewer objects and fewer lines of code compared to the two existing tools. In addition, the research provides suggestions on how to further develop the certification process and the toolDenna avhandlings syfte är att återutveckla ett databasdrivet mjukvaruverktyg som används för att sätta in motor relaterad data och generera en EIAPP Teknisk Fil som krävs för certifiering av motorer för att visa att de uppfyller och följer IMO:s utsläppsbestämmelser som anges i MARPOL:s bilaga VI och NTC 2008. Behovet av ett uppdaterat verktyg har uppkommit eftersom strukturen och arbetsättet skall ändras, från dokumenthantering till innehållshantering. Det nuvarande verktyget är också indelat i två olika verktyg, ett för motorer byggda i Italien och ett för motorer byggda i Finland, vilket leder till ett annat syfte som är att slå samman dessa verktyg till ett. Verktygen är byggda i Microsoft Access som inte längre passar behoven. Därför är det sista syftet med forskningen att utföra en datamigrering från Microsoft Access till SQL Server. Forskningen delades in i teoretisk och empirisk forskning. Den teoretiska delen presenterade först teorin bakom mjukvaruteknik och omstrukturering (re-engineering) av mjukvara. Sedan undersöktes teorin bakom databaser och datamigrering för att till slut genomgå utsläppsreglering och certifiering av marina diesel motorer. I den empiriska delen inspekterades först det befintliga verktyget och certifieringsprocessen. Vidare diskuterades konstruktiva forsknings strategin, som fokuserar på att producera en konstruktion (lösning) till ett verkligt problem i praktiken. Till sista gjordes en mera djupgående analys av verktyget för att föreslå en plan för hur man skall omstrukturera (re-engineer) verktyget, som inkluderade en implementeringssprocessplan. Huvudresultatet av denna forskning är ett omstrukturerat EIAPP verktyg som har frontend i Microsft Access och backend i SQL Server. Tabellerna har omstrukturerats för att uppfylla ändringen i att bara använda ett dokumentnummer för hela tekniska filen. Formerna har omarbetats och processer har automatiserats för att göra verktyget mera tillförlitligt och effektivt. Det nya omstrukturerade verktyget har mer än 50 % färre object och färre kodrader jämfört med de två befintliga verktygen. Dessutom ger forskningen förslag på hur man kan vidareutveckla certifieringsprocessen och verktyget

Continuous Defect Prediction: The Idea and a Related Dataset

We would like to present the idea of our Continuous Defect Prediction (CDP) research and a related dataset that we created and share. Our dataset is currently a set of more than 11 million data rows, representing files involved in Continuous Integration (CI) builds, that synthesize the results of CI builds with data we mine from software repositories. Our dataset embraces 1265 software projects, 30,022 distinct commit authors and several software process metrics that in earlier research appeared to be useful in software defect prediction. In this particular dataset we use TravisTorrent as the source of CI data. TravisTorrent synthesizes commit level information from the Travis CI server and GitHub open-source projects repositories. We extend this data to a file change level and calculate the software process metrics that may be used, for example, as features to predict risky software changes that could break the build if committed to a repository with CI enabled.Comment: Lech Madeyski and Marcin Kawalerowicz. "Continuous Defect Prediction: The Idea and a Related Dataset" In: 14th International Conference on Mining Software Repositories (MSR'17). Buenos Aires. 2017, pp. 515-518. doi: 10.1109/MSR.2017.46. URL: http://madeyski.e-informatyka.pl/download/MadeyskiKawalerowiczMSR17.pd

A Study of the Relationship Between Antivirus Regressions and Label Changes

AntiVirus (AV) products use multiple components to detect malware. A component which is found in virtually all AVs is the signature-based detection engine: this component assigns a particular signature label to a malware that the AV detects. In previous analysis [1-3], we observed cases of regressions in several different AVs: i.e. cases where on a particular date a given AV detects a given malware but on a later date the same AV fails to detect the same malware. We studied this aspect further by analyzing the only externally observable behaviors from these AVs, namely whether AV engines detect a malware and what labels they assign to the detected malware. In this paper we present the results of the analysis about the relationship between the changing of the labels with which AV vendors recognize malware and the AV regressions

SmartUnit: Empirical Evaluations for Automated Unit Testing of Embedded Software in Industry

In this paper, we aim at the automated unit coverage-based testing for embedded software. To achieve the goal, by analyzing the industrial requirements and our previous work on automated unit testing tool CAUT, we rebuild a new tool, SmartUnit, to solve the engineering requirements that take place in our partner companies. SmartUnit is a dynamic symbolic execution implementation, which supports statement, branch, boundary value and MC/DC coverage. SmartUnit has been used to test more than one million lines of code in real projects. For confidentiality motives, we select three in-house real projects for the empirical evaluations. We also carry out our evaluations on two open source database projects, SQLite and PostgreSQL, to test the scalability of our tool since the scale of the embedded software project is mostly not large, 5K-50K lines of code on average. From our experimental results, in general, more than 90% of functions in commercial embedded software achieve 100% statement, branch, MC/DC coverage, more than 80% of functions in SQLite achieve 100% MC/DC coverage, and more than 60% of functions in PostgreSQL achieve 100% MC/DC coverage. Moreover, SmartUnit is able to find the runtime exceptions at the unit testing level. We also have reported exceptions like array index out of bounds and divided-by-zero in SQLite. Furthermore, we analyze the reasons of low coverage in automated unit testing in our setting and give a survey on the situation of manual unit testing with respect to automated unit testing in industry.Comment: In Proceedings of 40th International Conference on Software Engineering: Software Engineering in Practice Track, Gothenburg, Sweden, May 27-June 3, 2018 (ICSE-SEIP '18), 10 page

End-user assertions in forms/3 : an empirical study

Spreadsheets are arguably the most widely used programming language in use today, yet spreadsheets commonly contain errors. Research shows that regardless of the experience of the end user, an alarming number of spreadsheets contain errors (91% in recent field audits). Most spreadsheets are created by end users with little or no programming experience. Unfortunately, software engineering research has largely ignored these users. In an attempt to reduce this high error rate, our research is aimed at bringing the benefits of software engineering to end users without requiring that they first learn software engineering principles. One mechanism for creating error-free programs is assertions. An assertion is a program property that always holds. It provides a way to attach more of the specification to the program. We have developed an assertion tool for spreadsheet languages that extends Microsoft Excel's validation scheme and includes capabilities such as assertion propagation. This work describes an empirical study done to assess how well end users understand and use the information provided by the assertion tool as they perform maintenance tasks. The study also provides information about end users' testing behavior