Det denna rapport kommer att avhandla är ett projekt genomfört hos Roxtec AB, syftet har i detta projekt varit att underlätta hanteringen av så kallade utm-adresser. Vi kommer att gå igenom problemställning, hur vi väljer att lösa samma problem. Senare kommer vi att behandla hur vi löste de här problemen, huvudsyftet har varit att skapa ett enkelt verktyg för att generera nyss nämnda adresser. Lite extrafunktioner runt de här funktionerna kommer att avhandlas såsom sparning av historik, inlogg och så vidare. Projektet kom att innehålla många rader kod, de här kommer inte rapporten att avhandla i detalj, förutom vissa mer betydelsefulla delar av projektet. I de mer betydelsefulla avsnittet går vi igenom dess funktion samt med illustrationer försöker vi förklara dess syfte på ett enkelt sätt. Hur väl vi lyckats att lösa de uppställda problemen vi ställs inför går vi igenom och diskuterar även de här till sist. Projektet kommer att skapas i .NET och i lämplig programvara för att utföra och lösa senare uppställd problematik.

No description available.

I dagens webb används ofta många olika innehållshanteringssystem för att göra det enkelt för användare att hantera deras egna hemsidor. I utvecklingsarbetet hos webbyråer bedrivs även någon typ av projektledning. Syftet med denna undersökning är att utvärdera och analysera ett företags befintliga CMS och deras arbetsprocess. Denna utvärderingen kommer göras utifrån ett visst antal kriterier som är kännetecken för olika projektledningsmetoder samt en separat utvärdering för ett passande CMS utifrån specifikationer och intervjuer. Här kommer faktorer som licens, funktionalitet, plattformsstöd, vidareutveckling, popularitet samt exempelvis programmeringsspråk. Denna undersökning visade på att företaget arbetar med ett agilt arbetssätt, samt att deras befintliga CMsystem är det optimala för deras verksamhet för att de ska upprätthålla sina möjligheter att helt skräddarsy lösningar och ha full kontroll på produkten.

Projektet avser att implementera spelifieringselement på den ideella bloggen 400contacts, en blogg som coachar och tipsar om jobbsökning i Sverige för nyanlända. Detta ska uppnås genom att använda sig av modeller av Yu-kai Chou, en framstående person inom området om spelifiering. Målet var till en början att öka antalet återkommande besökare till 50% av alla besökare men ändrades senare i projektet till att konvertera besökare till att ansluta sig till företagets facebookgrupp. För att lyckas uppnå detta har en ny design till bloggen tagits fram och under arbetets gång har ett poängsystem tagits fram som styr belöningar i form av märken på användarnas profiler. Dessa poäng ställer även användarna i en topplista. Poäng och märken förtjänas genom att vara delaktig på sidan, exempelvis genom att logga in eller att läsa ett nytt blogginlägg. Webbplatsen är byggd i WordPress och förlitar sig kraftigt på de tillgängliga tillägg som plattformen erbjuder. Arbetet har inte stött på större problem och har lyckats uppnå båda mål i sitt slutresultat.

AbstractMachine learning is a subfield within artificial intelligence that revolves around constructingalgorithms that can learn from, and make predictions on data. Instead of following strict andstatic instruction, the system operates by adapting and learning from input data in order tomake predictions and decisions. This work will focus on a subcategory of machine learningcalled “MultilabelClassification”, which is the concept of where items introduced to thesystem is categorized by an analytical model, learned through supervised learning, whereeach instance of the dataset can belong to multiple labels, or classes.This paper presents the task of implementing a multilabelclassifier based on the ID3algorithm, which we call MLID (MultilabelIterative Dichotomiser). The solution is presentedboth in a sequentially executed version as well as an parallelized one.We also presents acomparison based on accuracy and execution time, that is performed against algorithms of asimilar nature in order to evaluate the viability of using ID3 as a base to further expand andbuild upon in regards of multi label classification.In order to evaluate the performance of the MLID algorithm, we have measured theexecution time, accuracy, and made a summarization of precision and recall into what iscalled Fmeasure,which is the harmonic mean of both precision and sensitivity of thealgorithm. These results are then compared to already defined and established algorithms,on a range of datasets of varying sizes, in order to assess the viability of the MLID algorithm.The results produced when comparing MLID against other multilabelalgorithms such asBinary relevance, Classifier Chains and Random Trees shows that MLID can compete withother classifiers in term of accuracy and Fmeasure,but in terms of training the algorithm,the time required is proven inferior. Through these results, we can conclude that MLID is aviable option to use as a multilabelclassifier. Although, some constraints inherited from theoriginal ID3 algorithm does impede the full utility of the algorithm, we are certain thatfollowing the same path of development and improvement as ID3 experienced would allowMLID to develop towards a suitable choice of algorithm for a diverse range of multilabelclassification problems.

Context: The need for empirical investigations in software engineering domain is growing immensely. Many researchers nowadays, conduct and validate their study using empirical evidences. Survey is one such empirical investigation method which enables researchers to collect data from the large population. Main aim of the survey is to generalize the findings. Many problems are faced by the researchers in the survey process. Survey outcomes also depend upon variables like sample size, response rate and analysis techniques. Hence there is need for the literature addressing all the possible problems faced and also the impact of survey variables on outcomes. Objectives: Firstly, to identify the common problems faced by the researchers from the existing literature and also analyze the impact of the survey variables. Secondly to collect the experiences of software engineering researchers regarding the problems faced and the survey variables. Finally come up with a checklist of all the problems and mitigation strategies along with the information about the impact of survey variables. Methods: Initially a systematic literature review was conducted, to identify the existing problems in the literature and to know the effect of response rate, sample size, analysis techniques on survey outcomes. Then systematic literature review results were validated by conducting semi-structured, faceto-face interviews with software engineering researchers. Results: We were successful in providing a checklist of problems along with their mitigation strategies. The survey variables dependency on type of research, researcher’s choices limited us from further analyzing their impact on survey outcomes. The face-to-face interviews with software engineering researchers provided validations to our research results. Conclusions: This research gave us deeper insights into the survey methodology. It helped us to explore the differences that exists between the state of art and state of practice towards problem mitigation in survey process.

With the recent growth of the mobile market, companies want to target mobile devices while at the same time keeping product development costs low. One way to do this is to develop web applications, which are accessed from a mobile de- vice’s web browser, instead of native applications. The same web application can then be used on different platforms such as Android and iOS. However, devices such as smart phones and tablets often include cameras and sensors that a web ap- plication may want to access, but which are only accessible from native applica- tions. A framework was developed that enables web applications to communicate with native Android applications. Native applications are launched by clicking a link in the browser, and the result produced is made available to the web applica- tion through a HTTP POST request or a local web server running on the device. Key characteristics of the framework include ease of extension and the ability to enable secure (SSL) communication if desired. The ZXing Barcode Scanner ap- plication was integrated with the framework so that a scanned barcode can be dis- played in the browser. Performance measurements were conducted measuring the time taken from clicking a link to start a test application to the result being avail- able in the browser. The mean times measured were between 323 and 394 mil- liseconds. This indicates that the method used is sufficiently fast to not detract from the user experience. Future work could expand on the measurements or per- form a feature and performance comparison with PhoneGap.

“When in Rome do as the Romans do” – this hundreds years old proverb is still very actual today. Even more, nowadays you don’t even have to go to Rome to feel cultural differences. The communication technology have changed the world economy, thousands of people work now for multinational companies, interacting daily not just with a culture, but possibly with as much as 5 or 6 different ones. Some teams even work in different geographical locations communicating exclusively by electronic means. Today’s managers just have to deal with culture whether they like it or not, but the whole employee-manager relationship may be turned upside down on another side of the globe. So what should we do and what do we do about it? Ho do we manage effectively? These are the questions that this study aims to answer at. The main research objects of this study are rather small software engineering teams and companies that are working in cross-cultural environment, but do have little or no special company policies and other formal ways to manage cultural differences. Yet we found out that managers develop there own understanding of cultural issues and are practicing different methods to deal with them. / mkitsul@yahoo.com; seza@km.ru

Abstract The purpose of writing this thesis was to improve methods during requirements engineering phase. Usercentred system engineering has some problem areas, which are examined and verified to create a new guideline for developers. This guideline tends to make requirements engineering more effective and help developers create more concrete requirements. It is not uncommon that system development projects ends up with unsatisfied users or delay in deliveries. The reasons are different kinds of communication problems between users and developers during verification of requirements. There is a therapy model, called solution-focused therapy, used in family and individual therapy. The model focuses on solutions for the future instead of problems in the past. This method has never been used in system developing until today. Based on literature studies and scenarios we have shown that it is possible to transfer this pedagogy into the system developing branch especially in requirements engineering. During our investigation we have shown that the pedagogy refute the difficulties within usercentred design. The pedagogy model can be used in four kinds of methods for capturing requirements; questionnaires, interviews, workshops and observations. The model activates and makes the user more implicated. To show this, we have applied the pedagogy model on scenarios taken from earlier experiences of requirements engineering. The outcome of this investigation is that developers can create a more pleasant communication atmosphere with this pedagogy. A result of this is that users becomes more willing and helpful to create a new system and therefore makes it easier for developers and users to cooperate. You can avoid many communication problems if you know how to go around them.

Object-Oriented frameworks, OO frameworks, have been discussed over a long period of time, that when introducing Object-Oriented frameworks, the defect-density will decrease and the quality of software will increase. Capgemini had developed a framework that had been in the organization for nine years. Since then, the framework has been reengineered several times to meet the continuously changing requirements of the software systems the framework supports. My work was to develop a new framework to make the maintainability and evolution of the framework easier while not compromising the quality of the framework or the applications built on it. The new framework that I developed was called the Capgemini Development Framework, CDF. Results from the case study, conducted to test the differences between these two frameworks, showed that the CDF framework preserved the maintainability of the applications built on the framework. The architecture of the CDF framework made it also easier to handle any future updates to the core functionality of the framework.