This diploma thesis deals with a type of a project management of marketing activities in a company, where agile methods are used for development of its software product. The theoretical part describes specifications of traditional and agile methods, their comparison, a profound description of the Scrum method and the use of agile methods for marketing activities. In the following part, there is issued an analysis of the current situation in the company oriented to marketing department and possible solutions of discovered problems are suggested there.

This thesis is concerned about performance and stress testing of Xtend product developed by Xura, Inc. Software development knowledge, theoretical knowledge of testing and testing tools are described in opening chapters together with key features and services provided by Xtend. Emphasis was put on implementation of performance and stress testing tool, which focuses on short-term and long-term testing scenarios and output of this tool serves Xtend developers. Part of this thesis also focuses on results of stress and performance tests.

The goal of master thesis "Automation of Processes in Agile Development" is research of agile metodics with a focus on development practices in the Kentico company. This thesis describes different tools used as a support of agile software development including JIRA Software and Confluence, which are used in Kentico. Important part of this thesis is analysis of the current company processes and a plan of their optimization and automation. During the implementation part a web application which displays metrics arising from analysis and optimization proposal phase is realized. This thesis also contains discussion of it's realization and possible improvements.

Context: In the requirements engineering phase, requirements elicitation is considered as the most important task as it is the initial phase in which the requirements are gathered and prioritised. Changes in requirements may lead to project failure or delay in project deliveries. So, it is essential to elicit the requirements at the early stage to avoid changes in requirements in the later stage of development. Therefore, there is a need to study the impact of volatility in elicitation techniques to gather requirements appropriately in the early stages. Objectives: In the present thesis, we focused on the analysis of the requirements volatility in the requirement elicitation phase. The main objectives we have formulated to achieve our goal are Objective 1: To identify and determine the various causes of requirement volatility. Objective 2: To examine the impact of requirement volatility in the requirement elicitation process. Objective 3: To examine whether the procedure of elicitation techniques differ if volatility occurs while eliciting the requirements. Methods: In this thesis, we have implemented a Systematic Literature Review(SLR) and Survey research methods in order to attain our aim and objectives. SLR is performed for objective 1, to receive the data about the causes of volatility in various development life cycle phases. A survey is conducted to identify the causes of volatility in all phases of development, in the elicitation phase, and check whether the process of elicitation techniques differ if volatility occurs while eliciting the requirements. Results: From the SLR and survey, numerous factors of causes of volatility on the software development lifecycle were identified. Several new factors were identified from both the research methods. The factors have its own interpretation for the cause of volatility. Moreover, from the survey results, we can determine that the volatility occurs in the elicitation phase and has a huge impact while eliciting the requirements. Most of the practitioners working with the agile development process and waterfall model have stated that the impact of volatility results in prolonging the elicitation phase, slowing down the project, etc. Conclusions: For this research, our contribution is to provide insights on the impact of volatility in the elicitation process and check whether the elicitation techniques and its process change due to volatility. Based on the results of the respondents, we can conclude that the elicitation techniques procedure change is not intentional and not only because of the volatility but also due to some external factors while eliciting the requirements.

abstract: TolTEC is a three-color millimeter wavelength camera currently being developed for the Large Millimeter Telescope (LMT) in Mexico. Synthesizing data from previous astronomy cameras as well as knowledge of atmospheric physics, I have developed a simulation of the data collection of TolTEC on the LMT. The simulation was built off smaller sub-projects that informed the development with an understanding of the detector array, the time streams for astronomical mapping, and the science behind Lumped Element Kinetic Inductance Detectors (LEKIDs). Additionally, key aspects of software development processes were integrated into the scientific development process to streamline collaboration across multiple universities and plan for integration on the servers at LMT. The work I have done benefits the data reduction pipeline team by enabling them to efficiently develop their software and test it on simulated data. / Dissertation/Thesis / Masters Thesis Software Engineering 2019

Throughout numerous analyses and proposals of the capabilities of the Lyee methodology for software development there has been done a lot of work concerning how Lyee works, what its benefits are, and what its perspectives will be. Most of the time this has been done in relation to automated software generation. But concerning all the proposed benefits and the announced major breakthrough Lyee would be for software development, Lyee has also positioned itself in direct concurrence to traditional, already established software development models. The intention of this article is to put the Lyee technology into perspective to established software technologies, which is done at the example of a comparison of the Lyee and the Catalysis approach for software development.

Based on the static structure of Lyee programs, a configuration management concept for Lyee software projects is presented. After describing a modularization concept which is vital for configuration management, the configuration management concept itself is elaborated by showing the involved elements and procedures. Finally, the structure of the actual configuration management tool is presented and discussed.

Hohe Benutzertauglichkeit und Akzeptanz eines Webseitenservices sind nur dann gewährleistet, wenn diese auf die funktionalen Bedürfnisse, aber auch auf die strukturellen Vorstellungen ihrer Benutzer zugeschnitten sind. Im Kontext einer Webseite zur „Suche nach E-Learning-Produkten im Internet“ wurde untersucht, inwieweit die Kenntnis der Mentalen Modelle potenzieller Nutzer den Softwareentwicklungsprozess positiv beeinflussen kann. Dabei erlaubte die Erhebung Mentaler Modelle mit Hilfe der Struktur-Lege-Technik (SLT) als Evaluationsmethode einen Vergleich mit der tatsächlich entwickelten Webseite. Die Studie zeigte, dass trotz zuvor bereits durchgeführter, klassischer Evaluationen (Usability Tests, Anwendung von Heuristiken und Cognitive Walkthroughs) 40 Funktionsbereiche genannt wurden, die auf der tatsächlichen Webseite nicht vorgesehen oder umgesetzt sind. Daraus folgt, dass die Erhebung von Mentalen Modellen ebenfalls bereits vor dem Software-Entwicklungsprozess durchgeführt werden soll.

The number of vulnerable systems with exploitable security defects has increased. This led to an increase in the demand for secure software systems. Software developers lack security experiences to design and build secure software, some even believe security is not their responsibility. Despite the increased need for teaching security and secure programming, security is not well integrated into the undergraduate computing curriculum and is only offered as part of a program or as an elective course. The aim of this project is to outline the importance of incorporating security and secure programming concepts in programming courses starting from the introductory courses. By evaluating the students' security consideration and knowledge regarding software security. As a result, based on the knowledge students lack regarding software security, security and secure programming concepts are identified which need to be integrated into the programming courses.

This thesis examines and evaluates whether it is possible to measure the quality of a software project and introduces a metric that will evaluate if the quality of every test performed when developing software can be measured. This subject is examined because it can be hard to conclude how well a project and all its parts performed, both during implementation and after it is done. To facilitate this need, this thesis provides a possible solution.   To try and answer these questions and meet the needs of this tool a prototype has been developed. The prototype is automated and runs through all the software development tests selected for this project. It sums up the test results and later translates them with the help of a metric to tell its quality grade. The metric is calculated with the help of an arbitrary formula developed for this thesis. Once the metric is concluded the development team working with the project will have an overview of how well each test area is performing and how well the project's end result was. With the help of this metric it is also easier to see if the quality achieved meets the company’s standards and the customer’s wishes. The prototype aims to be sustainable because the solution should last for a long term and also because sustainability means a smoother and more efficient way for developers and other people involved to work with the prototype since not much extra work will be required when updates need to be implemented or other necessary implementations.   The prototype is applied on a second project, which is larger and more advanced than the project created for this thesis, to get a better and accurate understanding if the implementation is correct and if the metric can be used as a value to describe a project. The metric results are compared and evaluated. The results of this thesis conclude a proof-of-concept and can be seen as a first step in a longer evaluation and process in determining the quality of tests. The results conclusion is that more parameters and more weighing of each tests importance are needed in order to achieve a reliable metric result.   This tool is meant to ease and help developers to quickly come to a conclusion about how good the work is. It could also be beneficial for a company with focus on web development and IT-solutions though it will be easier to follow and set a standard for the services they provide.