No description available.

Over the years, packed malware have started to appear at a more rapid pace.Hackers are modifying the source code of popular packers to create new typesof compressors which can fool the Anti Virus software. Due to the sheer vol-ume of packer variations, creating unpacking scripts based on the packer’ssignature has become a tedious task. In this paper we will analyse genericunpacking techniques and apply them on ten popular compression software.The techniques prove to be successful in nine out of ten cases, providing aneasy and accessible way to unpack the provided samples

This candidate report describes how a group of students can develop a smartphone applicationwithout any prior knowledge in the field. To make the project more realistic there is also a clientwho has requests and wishes regarding the finished product.The document describes the methods used to produce the application and also includesexperiences that the group gained. How the interaction with the client has been performed togain a good understanding of what they wished the product to become is also accounted for.The research questions focus on how the development has proceeded and how one can learnsomething new in a relatively short timespan as a group. / Denna kandidatrapport redogör för hur en grupp studenter kan utveckla ensmartphoneapplikationutan några tidigare kunskaper inom applikationsprogrammering. För attfå uppdraget mer verklighetsanknutet finns det även en kund som har önskemål kring denslutgiltiga produkten.I dokumentet beskrivs det vilka metoder som använts för att ta fram applikationen och vilkaerfarenheter som gruppen tagit del av. Det beskrivs även hur interaktion med kunden hargenomförts för att få en bra bild av vad denne önskade. Frågeställningarna fokuserar på hurutvecklingen gått tillväga och hur man som grupp kan lära sig något nytt under relativt kort tid.

Digimergo är en digitalisering av Emergo Train System, ett system där personal inom räddningstjänst kan öva på olika katastrofscenarion. För att göra Digimergo användbart behövdes ytterligare programvara: ett administrationsverktyg till övningar och en scenarioeditor. I det programvaruutvecklingsprojekt som denna rapport behandlar har ny programvara utvecklats och integrerats med det ursprungliga Digimergosystemet. I den här rapporten diskuteras vilka risker som existerar när ny funktionalitet skall läggas till ett gammalt projekt samt hur dessa risker kan minimeras. Rapporten undersöker också vilka utvecklingsmetoder som lämpar sig i projekt där ny funktionalitet ska läggas till befintliga system. Resultatet visar att den största risken med att utöka befintliga projekt är att underskatta tiden som krävs för att sätta sig in i projektet i fråga. Det mest effektiva sättet att minimera risken för detta är att mycket tidigt studera det tidigare arbetet och utbilda projektmedlemmarna i det gamla systemet. Ett annat angreppssätt är att välja en metod som är flexibel när det kommer till nya risker eller ändringar i projektets plan, förslagsvis iterativa metoder.

Abstract This thesis examines and evaluates the Object-Oriented Client/Server (OOCS) model, a process model that can be used when IT organizations develop object-oriented client/server applications. In particular, it defines the roles in the development team and combines them into the process model. Furthermore, the model focuses on the client/server architecture, considering it explicitly. The model has been under construction for several years and it has been tested in a number of industrial projects. Feedback from practice has thus been an important source when the model has been evolving into its current form. Another source for evolution has been other process models and technical progress in this field. This thesis reveals the theoretical and practical aspects that have influenced the model's characteristics and developmnt. The object-oriented paradigm has been the driving force when creating the OOCS model. The first object-oriented development models were, however, both inadequate and contradictory to each other. The OOCS model utilizes the best practices from these early models. The model also defines artifacts to be delivered in each phase. The artifacts are synchronized with the Unified Modeling Language (UML), a new standard modeling notation. From the very beginning the OOCS model has included a strong client/server viewpoint, which is not stated so clearly in other object-oriented models. A three-tier division of the application (presentation, business logic, data management) can be found in each phase. This division has become crucial in recent years, when applications have been built on distributed architecture. The team-based roles included in the model are based on the work of a few other researchers, although this topic has not gained the importance it should have had. Namely, it is people that develop the application and their involvement in the process should be stated explicitly. The roles of the developers are closely connected to the OOCS process model via the concept of activities included in the model. The roles concentrate mainly on project members, but company-level aspects have also been considered. This thesis summarizes the work carried out in the last five years. It shows how the model has evolved in practice and how other models have contributed to it. The team-based OOCS model is in use in some IT organizations. The cases presented in this thesis illustrate how to adapt the model into specific organizational needs.

No description available.

In this dissertation we identify two problems with current integrated development environments (IDEs) and present JQuery as a tool to address these issues. The first problem is that IDE views answer low level questions and do not provide a mechanism to combine results to answer complex higher level questions. Even relatively simple questions force the developers to mentally combine results from different views. The second problem is that IDEs do not provide an easy way to create perspectives on project specific concerns such as naming conventions or annotations. Most IDEs do offer support for creating custom perspectives but the effort required to create a perspective is considerably more than the benefit a custom perspective provides. JQuery is an Eclipse plugin which generates code views using an expressive query language. We have redesigned JQuery to support a number of new user interface (UI) features and add a more flexible architecture with better support for extending the UI. To address the first problem, we have added multiple views to JQuery where each view supports drag and drop of results, selection linking, and regular expression search. These features enable a user to combine results from different views to answer more complex higher level questions. To address the second problem, we can leverage the fact that JQuery is built on an expressive query language. Through this query language we are able to define project specific concerns such as naming conventions or annotations and then create views and perspectives for these concerns through the JQuery UI. / Science, Faculty of / Computer Science, Department of / Graduate

Model-Driven Engineering has been developing since the first release of the Unified Modeling Language, passing several milestones and advancing ever since. Model-Driven Engineering is being used in various fields like medical, cyber-physical systems, web applications, etc. It is an engineering paradigm that allows developers to model systems at the level of abstraction of their choice. There are many available tools in the market offering different modelling capabilities to their users. Making use of more than one tool would give the users a wider range of options and higher flexibility in modelling their applications. The current market of open-source modelling tools has two main actors, being JetBrains MPS, mostly focused on textual modelling languages, and Eclipse Modelling Framework, mostly focused on graphical modelling languages. The goal of this thesis is to design and implement a bridge between these two modelling environments. More specifically, we engineer the modelling language Ecore, at the heart of the Eclipse Modeling Framework, in JetBrains MPS in order to enable the exchange of metamodels based on Ecore from MPS to Eclipse Modeling Framework.

Background: Due to the complexity involved in robotic software development, the progress in the field has been slow. Component-based software engineering was observed to have a strong influence on the improvement of the robotic software development process and its adoption achieved good results. DevOps was seen to be compatible and produced efficient results in software engineering. Objectives: The aim of this thesis work is to present the potential usage of DevOps practices in robotic software development. 15 DevOps practices were selected from prior research from software engineering and mapped to the robotic software development process and checked for success in terms of applicability and effectiveness. Methods: By performing a research synthesis of the literature, the usage of DevOps practices in robotic software development is proposed and presented. Interview based survey was performed by approaching industry experts on robotic software development to get their response on the results of the research synthesis. Results: The applicability of the DevOps practices in robotic software development is presented and the implications of the potential usage of the practices in the proposed manner are discussed. The potential advantages and limitations of the proposed mapping are discussed and presented. Conclusions: DevOps, like other software development frameworks, has various observable advantages when applied in robotic software development. The interviews confirmed the need for DevOps to be adapted into robotic software development and the benefits it has.

The ABC Company has been developing human resource administration software for over 10 years. Although this software is not overly technical and ABC has sufficient resources and tools for software development, one significant problem continues to be encountered. The primary problem faced by ABC software is properly defining and fulfilling user expectations and requirements. This problem can be measured primarily through the growing number of change and maintenance requests from clients upon installation. Numerous hours are spent in these maintenance activities which result in budget overruns and lower profits (or losses). The purpose of this project was to develop recommendations for alleviating the problem as described above. A study of the problem and possible approaches resulted in the hypothesis that a re-engineering of ABC's software development process to more rigorously follow a systems engineering process, including concurrent engineering (CE) techniques, would help alleviate the problem. The project methodology was implemented on two software development efforts -- one using ABC's current development approach and the other utilizing a systems engineering approach with CE principles. A systems engineering evaluation tool, the objectives matrix, was used to measure each projects' performance in order to test the hypothesis. / Master of Science