Change search
Refine search result
3456789 251 - 300 of 2740
CiteExportLink to result list
Permanent link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
Rows per page
  • 5
  • 10
  • 20
  • 50
  • 100
  • 250
Sort
  • Standard (Relevance)
  • Author A-Ö
  • Author Ö-A
  • Title A-Ö
  • Title Ö-A
  • Publication type A-Ö
  • Publication type Ö-A
  • Issued (Oldest first)
  • Issued (Newest first)
  • Created (Oldest first)
  • Created (Newest first)
  • Last updated (Oldest first)
  • Last updated (Newest first)
  • Standard (Relevance)
  • Author A-Ö
  • Author Ö-A
  • Title A-Ö
  • Title Ö-A
  • Publication type A-Ö
  • Publication type Ö-A
  • Issued (Oldest first)
  • Issued (Newest first)
  • Created (Oldest first)
  • Created (Newest first)
  • Last updated (Oldest first)
  • Last updated (Newest first)
Select
The maximal number of hits you can export is 250. When you want to export more records please use the 'Create feeds' function.
  • 251. Bengtsson, PerOlof
    Architecture-Level Modifiability Analysis2002Doctoral thesis, comprehensive summary (Other academic)
    Abstract [en]

    Cost, quality and lead-time are three main concerns in software engineering projects. The quality of developed software has traditionally been evaluated on completed systems. Evaluating the product quality at completion introduces a great risk of wasting effort on software products with inadequate system qualities. It is the objective of this thesis to define and study methods for assessment, evaluation and prediction of software systems’ modifiability characteristics based on their architecture designs. Since software architecture design is made early in the development, architecture evaluation helps detect inadequate designs and thus reduces the risk of implementing systems of insufficient quality. We present a method for architecture-level analysis of modifiability (ALMA) that analyses the modifiability potential of a software system based on its software architecture design. The method is scenario-based and either compares architecture candidates, assesses the risk associated with modifications of the architecture, or predicts the effort needed to implement anticipated modifications. The modification prediction results in three values; a prediction of the modification effort and the predicted best- and worst-case effort for the same system and change scenario profile. In this way the prediction method provides a frame-of-reference that supports the architect in the decision whether the modifiability is acceptable or not. The method is based on the experiences and results from one controlled experiment and seven case-studies, where five case studies are part of this thesis. The experiment investigates different ways to organize the scenario elicitation and finds that a group of individually prepared persons produce better profiles than individuals or unprepared groups.

  • 252. Bengtsson, PerOlof
    Design and Evaluation of Software Architecture1999Report (Other academic)
    Abstract [en]

    The challenge in software development is to develop software with the right quality levels. The main problem is not to know if a project is technically feasible concerning functionality, but if a solution exists that meet the software quality requirements. It is therefore desired to get an early indication of the qualities of the resulting software. Software architecture is concerned with what modules are used to compose a system and how these modules are related to each other, i.e. the structure of system. The software architecture of a system sets the boundaries for these qualities. Hence, to design the software architecture to meet the quality requirements is to reduce the risks of not achieving the required quality levels. In this thesis we present the experiences from a software architecture design project with two industry partners. Based on these we propose a method for reengineering architectures and exemplify by an applying the method on a real world example. The method is based on architecture transformations and software quality evaluation of the architecture. Further, we present a method for predicting software maintenance effort from the software architecture, for use in the design and reengineering method. The method uses change scenario profiles to describe future changes to the system and architecture impact analysis provide knowl-edge of the modification volume required for the realization of each sce-nario. The results from a quasi experiment supports that groups consisting of prepared members create better scenario profiles. Also, the results suggest that there is a large room for variation between scenario profiles created by individual persons.

  • 253. Bengtsson, PerOlof
    Design and Evaluation of Software Architecture1999Licentiate thesis, comprehensive summary (Other academic)
    Abstract [en]

    The challenge in software development is to develop software with the right quality levels. The main problem is not to know if a project is technically feasible concerning functionality, but if a solution exists that meet the software quality requirements. It is therefore desired to get an early indication of the qualities of the resulting software. Software architecture is concerned with what modules are used to compose a system and how these modules are related to each other, i.e. the structure of system. The software architecture of a system sets the boundaries for these qualities. Hence, to design the software architec-ture to meet the quality requirements is to reduce the risks of not achieving the required quality levels. In this thesis we present the experiences from a software architecture design project with two industry partners. Based on these we propose a method for reengineering architectures and exemplify by an applying the method on a real world example. The method is based on architec-ture transformations and software quality evaluation of the architecture. Further, we present a method for predicting software maintenance effort from the software architecture, for use in the design and reengineering method. The method uses change scenario profiles to describe future changes to the system and architecture impact analysis provide knowl-edge of the modification volume required for the realization of each sce-nario. The results from a quasi experiment supports that groups consisting of prepared members create better scenario profiles. Also, the results suggest that there is a large room for variation between scenario profiles created by individual persons.

  • 254. Bengtsson, PerOlof
    First Swedish Conference on Software Engineering Research and Practise2001Conference paper (Refereed)
    Abstract [en]

    Sweden is considered as a leading nation in modern IT business. The growth of software development business provides an opportunity to strengthen the software engineering research in Sweden even further. This conference is intended as a starting point for a national network on software engineering and provides opportunity to discuss the current situation in software engineering research. Besides that the conference present a forum for Ph. D. students to meet and exchange ideas.

  • 255. Bengtsson, PerOlof
    First Swedish Conference on Software Engineering Research and Practise: Proceedings2001Report (Other academic)
  • 256. Bengtsson, PerOlof
    SERP'012001Conference paper (Refereed)
    Abstract [en]

    These proceedings comprise of eight peer-reviewed articles ranging from software engineering fields such as process improvement to component based development and software architecture.

  • 257. Bengtsson, PerOlof
    et al.
    Bosch, Jan
    An Experiment on Creating Scenario Profiles for Software Change1999Report (Other academic)
    Abstract [en]

    Scenario profiles are used increasingly often for the assessment of quality attributes during the architectural design of software systems. However, the definition of scenario profiles is subjective and no data is available on the effects of individuals on scenario profiles. In this paper we present the design, analysis and results of a controlled experiment on the effect of individuals on scenario profiles, so that others can replicate the experiments on other projects and people. Both scenario profiles created by individuals and by groups are studied. The findings from the experiment showed that groups with prepared members proved to be the best method for creating scenario profiles. Unprepared groups did not perform better than individuals when creating scenario profiles.

  • 258.
    Bengtsson, PerOlof
    et al.
    Blekinge Institute of Technology, Department of Software Engineering and Computer Science.
    Bosch, Jan
    An experiment on creating scenario profiles for software change2000In: Annals of Software Engineering, ISSN 1022-7091, E-ISSN 1573-7489, Vol. 9, no 1-4, 59-78 p.Article in journal (Refereed)
    Abstract [en]

    Scenario profiles are used increasingly often for the assessment of quality attributes during the architectural design of software systems. However, the definition of scenario profiles is subjective and no data is available on the effects of individuals on scenario profiles. In this paper we present the design, analysis and results of a controlled experiment on the effect of individuals on scenario profiles, so that others can replicate the experiments on other projects and people. Both scenario profiles created by individuals and by groups are studied. The findings from the experiment showed that groups with prepared members proved to be the best method for creating scenario profiles. Unprepared groups did not perform better than individuals when creating scenario profiles.

  • 259. Bengtsson, PerOlof
    et al.
    Bosch, Jan
    Architecture level prediction of software maintenance1999Conference paper (Refereed)
    Abstract [en]

    A method for the prediction of software maintainability during software architecture design is presented. The method rakes (1) the requirement specification (2) the design of the architecture (3) expertise from software engineers and, possibly, (4) historical data as input and generates a prediction of the average effort for a maintenance task. Scenarios are used by the method to concretize the maintainability requirements and to analyze the architecture for the prediction of the maintainability. The method is formulated based on extensive experience in software architecture design and detailed design and exemplified using the design of software architecture for a haemo dialysis machine. Experiments for evaluation and validation of the method are ongoing and future work.

  • 260. Bengtsson, PerOlof
    et al.
    Bosch, Jan
    Scenario-based software architecture reengineering1998Conference paper (Refereed)
    Abstract [en]

    This paper presents a method for reengineering software architectures. The method explicitly addresses the quality attributes of the software architecture. Assessment of quality attributes is performed primarily using scenarios. Design transformations are done to improve quality attributes that do not satisfy the requirements. Assessment and design transformation can be performed for several iterations until all requirements are met. To illustrate the method we use the reengineering of a prototypical measurement system into a domain-specific software architecture as an example.

  • 261. Bengtsson, PerOlof
    et al.
    Lassing, Nico
    Bosch, Jan
    Vliet, Hans van
    Analyzing Software Architectures for Modifiability2000Report (Other academic)
    Abstract [en]

    The software architecture plays an important role in achieving a modifiable system, but few methods for modifiability analysis exist. In this paper, we propose an analysis method for software architecture modifiability that has successfully been applied in several cases. The method consists of five main steps, i.e. goal selection, software architecture description, scenario elicitation, scenario evaluation and interpretation.

  • 262.
    Beohar, Harsh
    et al.
    Halmstad University, School of Information Technology, Halmstad Embedded and Intelligent Systems Research (EIS), Centre for Research on Embedded Systems (CERES).
    Mousavi, Mohammad Reza
    Halmstad University, School of Information Technology, Halmstad Embedded and Intelligent Systems Research (EIS), Centre for Research on Embedded Systems (CERES).
    Input–output conformance testing for software product lines2016In: The Journal of logical and algebraic methods in programming, ISSN 2352-2216, E-ISSN 2352-2208, Vol. 85, no 6, 1131-1153 p.Article in journal (Refereed)
    Abstract [en]

    We extend the theory of input-output conformance (IOCO) testing to accommodate behavioral models of software product lines (SPLs). We present the notions of residual and spinal testing. These notions allow for structuring the test process for SPLs by taking variability into account and extracting separate test suites for common and specific features of an SPL. The introduced notions of residual and spinal test suites allow for focusing on the newly introduced behavior and avoiding unnecessary re-test of the old one. Residual test suites are very conservative in that they require retesting the old behavior that can reach to new behavior. However, spinal test suites more aggressively prune the old tests and only focus on those test sequences that are necessary in reaching the new behavior. We show that residual testing is complete but does not usually lead to much reduction in the test-suite. In contrast, spinal testing is not necessarily complete but does reduce the test-suite. We give sufficient conditions on the implementation to guarantee completeness of spinal testing. Finally, we specify and analyze an example regarding the Ceiling Speed Monitoring Function from the European Train Control System. (C) 2016 The Author(s). Published by Elsevier Inc.

  • 263. Berander, Patrik
    Evolving Prioritization for Software Product Management2007Doctoral thesis, comprehensive summary (Other academic)
    Abstract [en]

    The quality of a product is commonly defined by its ability to satisfy stakeholder needs and expectations. Therefore, it is important to find, select, and plan the content of a software product to maximize the value for internal and external stakeholders. This process is traditionally referred to as requirements engineering in the software industry, while it is often referred to as product management in industries with a larger market focus. As an increasing number of software products are delivered to a market instead of single customers, the need for product management in software companies is increasing. As a side effect, the need for mechanisms supporting decisions regarding the content of software products also increases. While decision-support within requirements engineering and product management is a broad area, requirements prioritization together with release planning and negotiation are considered as some of the most important decision activities. This is particularly true because these activities support decisions regarding the content of products, and are hence drivers for quality. At the same time, requirements prioritization is seen as an integral and important component in both requirements negotiation (with single customers) and release planning (with markets) in incremental software development. This makes requirements prioritization a key component in software engineering decision support, in particular as input to more sophisticated approaches for release planning and negotiation, where decisions about what and when to develop are made. This thesis primarily focuses on evolving the current body of knowledge in relation to release planning in general and requirements prioritization in particular. The research is carried out by performing qualitative and quantitative studies in industrial and academic environments with an empirical focus. Each of the presented studies has its own focus and scope while together contributing to the research area. Together they answer questions about why and how requirements prioritization should be conducted, as well as what aspects should be taken into account when making decisions about the content of products. The primary objective of the thesis is to give guidelines on how to evolve requirements prioritization to better facilitate decisions regarding the content of software products. This is accomplished by giving suggestions on how to perform research to evolve the area, by evaluating current approaches and suggest ways on how these can be improved, and by giving directions on how to align and focus future research to be more successful in development of decision-support approaches. This means that the thesis solves problems with requirements prioritization today, and gives directions and support on how to evolve the area in a successful way.

  • 264. Berander, Patrik
    Prioritization of Stakeholder Needs in Software Engineering: Understanding and Evaluation2004Licentiate thesis, comprehensive summary (Other academic)
    Abstract [en]

    In everyday life, humans confront situations where different decisions have to be made. Such decisions can be non-trivial even though they often are relatively simple, such as which bus to take or which flavor of a soft drink to buy. When facing decisions of more complex nature, and when more is at stake, they tend to get much harder. It is often possible to deal with such decisions by prioritizing different alternatives to find the most suitable one. In software engineering, decision-makers are often confronted with situations where complex decisions have to be made, and where the concept of prioritization can be utilized. Traditionally in software engineering, discussions about prioritization have focused on the software product. However, when defining or improving software processes, complex decisions also have to be made. In fact, software products and software processes have many characteristics in common which invite thoughts about using prioritization when developing and evolving software processes as well. The results presented in this thesis indicate that it is possible to share results and knowledge regarding prioritization between the two areas. In this thesis, the area of prioritization of software products is investigated in detail and a number of studies where prioritizations are performed in both process and product settings are presented. It is shown that it is possible to use prioritization techniques commonly used in product development also when prioritizing improvement issues in a software company. It is also shown that priorities between stakeholders of a software process sometimes differ, just as they do when developing software products. The thesis also presents an experiment where different prioritization techniques are evaluated with regard to ease of use, time consumption, and accuracy. Finally, an investigation of the suitability of students as subjects when evaluating prioritization techniques is presented.

  • 265.
    Berander, Patrik
    Blekinge Institute of Technology, Department of Software Engineering and Computer Science.
    Understanding and Evaluation of Software Process Deviations2002Independent thesis Advanced level (degree of Master (One Year))Student thesis
    Abstract [en]

    Software process improvement is often mentioned in today?s software marketplace. To be able to do process improvement, the organisation must have a process to improve from. These processes are commonly deviated from, and the PDU/PAY organisation at Ericsson AB has experienced that this happens too often within their organisation. The aim of this master thesis was to investigate why such deviations occur and how they could be prevented at PDU/PAY. A survey including a qualitative and a quantitative part was conducted at PDU/PAY to investigate this issue. The result was that processes were often deviated from due to lack of: management commitment, user involvement, synchronisation between processes, change management, anchoring of processes, and communication of processes. In addition to the conducted studies, an improvement proposal is given to the PDU/PAY organisation. This includes one organisational part and one part that is directly related to the actual work with processes. The proposal is intended to give PDU/PAY an essence of how to improve their work with their organisational processes.

  • 266. Berander, Patrik
    Using students as subjects in requirements prioritization2004Conference paper (Refereed)
  • 267. Berander, Patrik
    et al.
    Andrews, Anneliese Amschler
    Requirements Prioritization2005In: Engineering and Managing Software Requirements / [ed] Aurum, Aybüke; Wohlin, Claes, Berlin: Springer Verlag , 2005, 69-94 p.Chapter in book (Refereed)
    Abstract [en]

    This chapter provides an overview of techniques for prioritization of requirements for software products. Prioritization is a crucial step towards making good decisions regarding product planning for single and multiple releases. Various aspects of functionality are considered, such as importance, risk, cost, etc. Prioritization decisions are made by stakeholders, including users, managers, developers, or their representatives. Methods are given how to combine individual prioritizations based on overall objectives and constraints. A range of different techniques and aspects are applied to an example to illustrate their use. Finally, limitations and shortcomings of current methods are pointed out, and open research questions in the area of requirements prioritization are discussed.

  • 268. Berander, Patrik
    et al.
    Jönsson, Per
    A Goal Question Metric Based Approach for Efficient Measurement Framework Definition2006Conference paper (Refereed)
  • 269. Berander, Patrik
    et al.
    Jönsson, Per
    Hierarchical Cumulative Voting (HCV) Prioritization of Requirements in Hierarchies2006In: International Journal of Software Engineering & Knowledge Engineering, ISSN 0218-1940 , Vol. 16, no 6, 819-849 p.Article in journal (Refereed)
    Abstract [en]

    Decision support in requirements engineering is an activity that plays an important role in enabling the delivery of value to stakeholders. Requirements prioritization has been identified as an integral (and important) part of requirements negotiation and release planning in incremental software development, which makes prioritization a key issue in requirements engineering decision support. The Analytical Hierarchy Process (AHP) has for long been considered as the technique to use when prioritizing requirements on a ratio scale. Several studies have reported positively about AHP, but lately a number of studies have also reported about weaknesses, without identifying any better ratio-scale alternatives. In this paper, the strengths and weaknesses of AHP and another ratioscale prioritization technique, Cumulative Voting (CV), are compared. Based on this comparison, a new technique for prioritizing hierarchically structured requirements on a ratio scale is presented, called Hierarchical Cumulative Voting (HCV). HCV addresses the weaknesses of AHP while inheriting the strengths of CV. The suitability of HCV is discussed theoretically as well as in the light of empirical results from using HCV and CV in industrial settings. It is concluded that HCV seems very promising, but additional empirical studies are needed to address some of the open questions about the technique.

  • 270. Berander, Patrik
    et al.
    Khan, K.A.
    Lehtola, L.
    Towards a Research Framework on Requirements Prioritization2006Conference paper (Refereed)
  • 271. Berander, Patrik
    et al.
    Svahnberg, Mikael
    Evaluating two Ways of Calculating Priorities in Requirements Hierarchies: an Experiment on Hierarchical Cumulative Voting2009In: Journal of Systems and Software, ISSN 0164-1212 , Vol. 82, no 5, 836-850 p.Article in journal (Refereed)
    Abstract [en]

    When developing large-scale software systems, there is often a large amount of requirements present, and they often reside on several hierarchical levels. In most cases, not all stated requirements can be implemented into the product due to different constraints, and the requirements must hence be prioritized. As requirements on different abstraction levels shall not be compared, prioritization techniques that are able to handle multi-level prioritization are needed. Different such techniques exist, but they seem to result in unfair comparisons when a hierarchy is unbalanced. In this paper, an empirical experiment is presented where an approach that compensate for this challenge is evaluated. The results indicate that some form of compensation is preferred, and that the subjects’ preference is not influenced by the amount of information given.

  • 272. Berander, Patrik
    et al.
    Wohlin, Claes
    Differences in Views between Development Roles in Software Process Improvement: A Quantitative Comparison2004Conference paper (Refereed)
    Abstract [en]

    This paper presents a quantitative study that evaluates how different roles in a software development organization view different issues in software process improvement. The study is conducted in a large Swedish telecommunication organization with the traditional roles of software development. The respondents of the study got five different questions related to process improvement. The result was that the different roles disagreed in three of the questions while they agreed in two of the questions. The disagreement was related to issues about importance of improvement, urgency of problems, and threat against successful process management, while the questions where the roles agreed focused on communication of the processes (documentation and teaching). It is concluded that it is important to be aware and take into account the different needs of different roles and that looking into other areas (e.g. marketing) could be beneficial when conducting process improvements.

  • 273. Berander, Patrik
    et al.
    Wohlin, Claes
    Identification of Key Factors in Software Process Management: A Case Study2003Conference paper (Refereed)
    Abstract [en]

    When conducting process related work within an organization, it is important to be aware of which factors that are most important to consider. This paper presents an empirical study that was performed in order to find the key success factors in process management. One factor, namely synchronization of processes, was considered as much more important within the studied organization than within the studied literature. This shows that more research might be needed in this area. The study further shows that it is important to relate process improvement work to the properties of the affected organization and that the key factors identified are highly interrelated.

  • 274.
    Berg, Isabel
    Mid Sweden University, Faculty of Science, Technology and Media, Department of Information Systems and Technology.
    George JR, Home automation system interface2017Independent thesis Basic level (university diploma), 10 credits / 15 HE creditsStudent thesis
    Abstract [en]

    I have developed an interactive graphical user interface (GUI), which displays the current statuses of my personal home automation system based on relevance. Relevance is determined by event, such as motion detection, triggered by connected subsystems. The interface updates the order the

    subsystems are displayed to give the user faster access to relevant status overviews and controls. Event logs and controllers are accessible through HomeSeer via a JSON API.

    The application is built with HTML, CSS, JavaScript (jQuery) only. Its test program uses PHP features. All graphic elements are vectors for responsiveness.

    The application is launched on a local IIS server, achieved by converting the application to an ASP.NET website.

    I have carried out this project and written all code for it alone.

     

  • 275. Berglund, Anders
    et al.
    Börstler, Jürgen
    Umeå universitet, Institutionen för datavetenskap.
    Dagiéne, Valentina
    Forword to the Special Section on the ECOOP'06 Workshop on Pedagogies and Tools for the Teaching and Learning of Object-Oriented Concepts2007In: Informatics in Education, Vol. 6, no 1, 3-4 p.Article in journal (Other academic)
  • 276.
    Berglund, Aseel
    et al.
    Linköping University, Department of Computer and Information Science, Software and Systems. Linköping University, The Institute of Technology.
    Heintz, Fredrik
    Linköping University, Department of Computer and Information Science, Artificial Intelligence and Intergrated Computer systems. Linköping University, The Institute of Technology.
    Integrating Soft Skills into Engineering Education for Increased Student Throughput and more Professional Engineers2014In: Proceedings of LTHs 8:e Pedagogiska Inspirationskonferens (PIK), Lund, Sweden: Lunds university , 2014Conference paper (Other academic)
    Abstract [en]

    Soft skills are recognized as crucial for engineers as technical work is becoming more and more collaborative and interdisciplinary. Today many engineering educations fail to give appropriate training in soft skills. Linköping University has therefore developed a completely new course “Professionalism for Engineers” for two of its 5-year engineering programs in the area of computer science. The course stretches over the first 3 years with students from the three years taking it together. The purpose of the course is to give engineering students training in soft skills that are of importance during the engineering education as well as during their professional career. The examination is based on the Dialogue Seminar Method developed for learning from experience and through reflection. The organization of the course is innovative in many ways.

  • 277.
    Berglund, Johan
    Mid Sweden University, Faculty of Science, Technology and Media, Department of Information and Communication systems.
    Testautomatisering for Android: Integration av automatiserade tester i ett agilt arbetssätt2016Independent thesis Basic level (degree of Bachelor), 10 credits / 15 HE creditsStudent thesis
    Abstract [en]

    Mobile application development and testing involves even greater challenges than traditional software development, given that the large number of existing devices, each with unique hardware configuration and operating system needs to be considered. Software testing constitutes a big and important part of development, where the majority of the tests are performed manually. This is time consuming and expensive. The purpose of this thesis project is therefor to examine the current test process at the company Dewire, in an effort to find ways to improve it by introducing automated tests for the Android mobile platform. The automation frameworks Appium and Espresso will be evaluated and combined with existing systems like Jenkins that already applied in Dewires agile work procedure. A test environment been implemented during this thesis project as a proof of concept, where tests are run on a real device as the application is being built. Test cases from an ongoing development project has been implemented and the results evaluated. This thesis project has shown that the framework Espresso together with a Jenkins build-server has great potential to reduce manual testing and streamline the test process. It has also shown that test automation should be implemented from start of a project, where tests are continuously kept up to date during development to be profitable. At the same time results show that test automation involves a significant time investment before time and money can be saved.

  • 278.
    Bergman, Ken
    Mid Sweden University, Faculty of Science, Technology and Media, Department of Information Systems and Technology.
    Företagspresentation: Med WordPress och typografi2017Independent thesis Basic level (university diploma), 10 credits / 15 HE creditsStudent thesis
    Abstract [sv]

    Målet med detta projektet har varit att utveckla en webbplats åt ett företag med

    webbutveckling och användbarhet som kärnverksamhet. För att knyta designen

    och layouten till företagets verksamhet, så har projektet valt att titta på vad

    typografi för webb innebär, och hur det kan implementeras på webbplatsen.

    Resultatet ska ligga till grund för projektets webbplats samt framtida produkter

    och tjänster till företaget. Webbplatsen har utvecklats som ett tema för

    innehållshanteringssystem WordPress, tillsammans med ett eget

    insticksprogram för att utöka funktionaliteten till att innefatta en kontakt

    funktion. Det kompletta temat, typografi, layout och dess funktioner har

    utvecklats genom att använda HTML5, CSS samt PHP, tillsammans med en

    lokal webbserver och relationsdatabsen MySQL. Rapporten följer projekts

    utveckling av en webbplats som är både dynamisk och anpassar sin typografi

    och layout till storleken på användarens enhet, samt presenterar produkten av

    projektet.

  • 279.
    Bergqvist, Emil
    University of Skövde, School of Informatics.
    Auditory displays: A study in effectiveness between binaural and stereo audio to support interface navigation2014Independent thesis Advanced level (degree of Master (One Year)), 10 credits / 15 HE creditsStudent thesis
    Abstract [en]

    This thesis analyses if the change of auditory feedback can improve the effectiveness of performance in the interaction with a non-visual system, or with a system used by individuals with visual impairment. Two prototypes were developed, one with binaural audio and the other with stereo audio. The interaction was evaluated in an experiment where 22 participants, divided into two groups, performed a number of interaction tasks. A post-interview were conducted together with the experiment. The result of the experiment displayed that there were no great difference between binaural audio and stereo regarding the speed and accuracy of the interaction. The post-interviews displayed interesting differences in the way participants visualized the virtual environment that affected the interaction. This opened up interesting questions for future studies.

  • 280.
    Bergstrand, Fredrik
    et al.
    Blekinge Institute of Technology, School of Engineering, Department of Systems and Software Engineering.
    Bergstrand, Johan
    Blekinge Institute of Technology, School of Engineering, Department of Systems and Software Engineering.
    Gunnarsson, Håkan
    Blekinge Institute of Technology, School of Engineering, Department of Systems and Software Engineering.
    Localization of Spyware in Windows Environments2004Independent thesis Advanced level (degree of Master (One Year))Student thesis
    Abstract [en]

    This is a thesis about different methods that can be used to detect spyware. Methods included are Layered Service Provider, Internet Protocol Helper API, TDI filtering and API hooking. Some firewall testing applications, leak tests, that use methods that can be used by real spyware program to penetrate firewalls have also been examined. The goal was to develop a Windows 2000/XP program that is able to detect as many of our examined leak tests as possible. Our program uses the methods TDI filtering and API hooking for detection of spyware because our study showed that these methods were the best. To evaluate the program it was tested against our examined leak test programs. Our program managed to detect all leak tests except one.

  • 281.
    Bergström, Jonas
    et al.
    Blekinge Institute of Technology, School of Engineering, Department of Systems and Software Engineering.
    Dahlqvist, Andreas
    Blekinge Institute of Technology, School of Engineering, Department of Systems and Software Engineering.
    BESMART: a framework for shifting from BESpoke to MARkeT-driven requirements engineering2007Independent thesis Advanced level (degree of Master (One Year))Student thesis
    Abstract [en]

    Requirements Engineering has two main directions, Bespoke (product developed for one customer) and Market-Driven (several potential customers for the same product). These two are in some ways very much alike but in some aspects very different. Over the last couple of years the software development industry has tended to shift more and more to Market-Driven Requirements Engineering. This has brought attention to the challenges facing a Market-Driven development organization, without focusing on the actual shift from Bespoke development. Based on the differences and similarities between Bespoke and Market-Driven Requirements Engineering, this thesis presents a framework for shifting from the former to the latter. The framework (BESMART) involves three steps. Firstly, the organization assesses their potential to become more Market-Driven. Secondly they assess their current way of working to identify which areas that may need to be improved. Finally, BESMART provides multiple suggestions that address the identified improvement areas. The organization is then able to choose the one that best suits their needs. This also lets the organization choose a solution that they find feasible. The framework was used at a case organization during its development. This way it was ensured that the theoretical framework could actually be used in a real world setting. The practical use of BESMART resulted in some refinements aimed at making it more applicable in industry. Once the framework had been applied, it was evaluated by representatives from the case organization. The industry evaluation resulted in some improvement suggestions but showed that the framework was both useful and usable and provided an improvement plan that seemed promising enough to pilot in the organization.

  • 282.
    Bernau, Maja
    et al.
    Örebro University, School of Science and Technology.
    Olsson, Tobias
    Örebro University, School of Science and Technology.
    Kundtjänster för mobilapplikationer: Utveckling av rapportgenerator, symbolgenerator,RevitArchitecture–add-in och metadatahantering2014Independent thesis Basic level (degree of Bachelor), 10 credits / 15 HE creditsStudent thesis
    Abstract [en]

    The goal of this project was to streamline and automate a business system. This was achieved through the implementation of four subtasks. This report describes what parts of the system that needed to be updated and why. It also describes how the development was carried out and what results the project ultimately led to.

     

    The project's tasks were to: Create a report generator designed to generate Excel documents.

    Develop a symbol generator where a user, through a web-based interface, could generate

    symbols. The symbols could then be used in the company's mobile application. Create an

    interface for a web service, and to develop an add-in for the modeling software Revit

    Architecture 2014.

  • 283.
    Berndtsson, Wilhelm
    et al.
    Linköping University, Department of Computer and Information Science. Linköping University, The Institute of Technology.
    Claesson, Filip
    Linköping University, Department of Computer and Information Science.
    Daveby, Eric
    Linköping University, Department of Computer and Information Science.
    Gudjonsson, Adam
    Linköping University, Department of Computer and Information Science. Linköping University, The Institute of Technology.
    Lemos, Josefine
    Linköping University, Department of Computer and Information Science.
    Rosander, Sebastian
    Linköping University, Department of Computer and Information Science.
    Åquist, Alexander
    Linköping University, Department of Computer and Information Science.
    Webbutveckling och agila arbetsmetoder: erfarenheter från projekt inom programvaruutveckling2014Independent thesis Basic level (degree of Bachelor), 12 credits / 18 HE creditsStudent thesis
    Abstract [sv]

    Rapporten beskriver framtagandet av en webbshop för glasögonförsäljning. Läsaren får ta del av lärdomar om hur det fungerar att arbeta efter den agila projektmodellen Scrum i praktiken och förslag till hur metodiken kan anpassas för effektiv användning i ett utvecklingsteam. Vidare diskuteras även hur sammanslagning av flera projektmodeller kan ske för att skapa en mer produktiv projektmiljö. 

    Lösningar till tekniska problem som uppstått under projektets gång presenteras och diskuteras utifrån ett utvecklarprespektiv. Vidare presenteras en marknadsundersökning där kundsegmentet identifieras och analyseras för utformning av slutprodukten. Utmärkande för slutprodukten är en smidig och enkel köpprocess uppdelad i tre enkla steg. 

  • 284.
    Bernhem, Kristoffer
    et al.
    KTH, School of Engineering Sciences (SCI), Applied Physics.
    Brismar, Hjalmar
    KTH, School of Engineering Sciences (SCI), Applied Physics. KTH, Centres, Science for Life Laboratory, SciLifeLab. Karolinska Institutet, Sweden.
    SMLocalizer, a GPU accelerated ImageJ plugin for single molecule localization microscopy2017In: Bioinformatics, ISSN 1367-4803, E-ISSN 1367-4811Article in journal (Refereed)
    Abstract [en]

    Summary

    SMLocalizer combines the availability of ImageJ with the power of GPU processing for fast and accurate analysis of single molecule localization microscopy data. Analysis of 2D and 3D data in multiple channels is supported.

    Availability and implementation

    Plugin freely available for Fiji and ImageJ2.0 through https://sourceforge.net/projects/smlocalizer/. Plugin also available for continuous updates through ImageJ update system, add http://sites.imagej.net/Cellular-Biophysics-KTH/ as update site in ImageJ. Java and CUDA source code freely available on the web at https://github.com/KristofferBernhem/SMlocalizer.

    Contact

    brismar@kth.se

    Supplementary information

    Supplementary data are available at Bioinformatics online.

  • 285.
    Bernström, Kristian
    et al.
    Uppsala University, Disciplinary Domain of Science and Technology, Mathematics and Computer Science, Department of Information Technology, Division of Computing Science.
    Näsman, Anders
    Uppsala University, Disciplinary Domain of Science and Technology, Mathematics and Computer Science, Department of Information Technology, Division of Computing Science.
    Utredning och implementering av en prototyp för integration av Prevas FOCS och ABB 800xA2014Independent thesis Advanced level (professional degree), 20 credits / 30 HE creditsStudent thesis
    Abstract [en]

    ABB and Prevas have initiated a collaboration to sell a system to optimize steel industry furnaces, called FOCS. The purpose of this thesis is to investigate possibilities for integrating Prevas FOCS and ABB 800xA.

    The result of the investigation is used for an implementation of a prototype of the integrated system. The study shows a general method that can be used when implementing two software systems. The prototype of the integrated systems is made with usability principles in mind. This is a very important aspect in order to create a good working environment for the operators of a steel plant. It is also important to follow communication standards when integrating software systems. In an industrial network used in the steel industry OPC is a standard for communication. We recommend ABB and Prevas to follow this standard when possible to make the integration smoother. To keep the cost of the integration to a minimum it is also recommended to reuse existing resources. This can however have a negative effect on usability and it is therefore important to keep a balance between cost and usability.

    The prototype made in this thesis accomplishes the goal of transferring the functionalities used by operators of Prevas FOCS to 800xA so that operators can control the processes using only one integrated system.

  • 286. Berntsson Svensson, Richard
    et al.
    Aurum, Aybüke
    Paech, Barbara
    Gorschek, Tony
    Blekinge Institute of Technology, School of Computing.
    Sharma, Devesh
    Software architecture as a means of communication in a globally distributed software development context2012Conference paper (Refereed)
    Abstract [en]

    The management and coordination of globally distributed development poses many new challenges, including compensating for informal implicit communication, which is aggravated by heterogeneous social and engineering traditions between development sites. Although much research has gone into identifying challenges and working with practical solutions, such as tools for communication, little research has focused on comparing communication mechanisms in terms of their ability to provide large volumes of rich information in a timely manner. Data was collected through in-depth interviews with eleven practitioners and twenty-eight responses through a web-based questionnaire from three product lines at an international software development organization. This paper assesses the relative importance of ten commonly used communication mechanisms and practices across local and global development sites. The results clearly indicate that some communication mechanisms are more important than others in providing large volumes of rich information in a timely manner. The prevalence of architecture in providing rich information in large volumes for both local and global communication can be clearly observed.

  • 287.
    Berntsson Svensson, Richard
    et al.
    Blekinge Institute of Technology, Faculty of Computing, Department of Software Engineering.
    Regnell, Björn
    Is role playing in Requirements Engineering Education increasing learning outcome?2016In: Requirements Engineering, ISSN 0947-3602, E-ISSN 1432-010XArticle in journal (Refereed)
    Abstract [en]

    Requirements Engineering has attracted a great deal of attention from researchers and practitioners in recent years. This increasing interest requires academia to provide students with a solid foundation in the subject matter. In Requirements Engineering Education (REE), it is important to cover three fundamental topics: traditional analysis and modeling skills, interviewing skills for requirements elicitation, and writing skills for specifying requirements. REE papers report about using role playing as a pedagogical tool; however, there is a surprising lack of empirical evidence on its utility. In this paper we investigate whether a higher grade in a role playing project have an effect on students’ score in an individual written exam in a Requirements Engineering course. Data are collected from 412 students between the years of 2007 and 2014 at Lund University and Chalmers | University of Gothenburg. The results show that students who received a higher grade in the role playing project scored statistically significant higher in the written exam compared to the students with a lower role playing project grade. © 2016 Springer-Verlag London

  • 288.
    Berntsson Svensson, Richard
    et al.
    Blekinge Institute of Technology, Faculty of Computing, Department of Software Engineering.
    Taghavianfar, Maryam
    Selecting creativity techniques for creative requirements: An evaluation of four techniques using creativity workshops2015In: 2015 IEEE 23RD INTERNATIONAL REQUIREMENTS ENGINEERING CONFERENCE (RE), IEEE, 2015, 66-75 p.Conference paper (Refereed)
    Abstract [en]

    Requirements engineering is recognized as a creative process where stakeholders jointly discover new creative ideas for innovative and novel products that eventually are expressed as requirements. This paper evaluates four different creativity techniques, namely Hall of Fame, Constraint Removal, Brainstorming, and Idea Box, using creativity workshops with students and industry practitioners. In total, 34 creativity workshops were conducted with 90 students from two universities, and 86 industrial practitioners from six companies. The results from this study indicate that Brainstorming can generate by far the most ideas, while Hall of Fame generates most creative ideas. Idea Box generates the least number of ideas, and the least number of creative ideas. Finally, Hall of Fame was the technique that led to the most number of requirements that was included in future releases of the products.

  • 289. Berntsson-Svensson, R.
    et al.
    Aurum, Aybüke
    Wohlin, Claes
    Hu, Ganglan
    Successful Software Project and Products: An Empirical Investigation Comparing Australia and Sweden2006Conference paper (Refereed)
  • 290.
    Berntsson-Svensson, Richard
    Blekinge Institute of Technology, School of Engineering, Department of Systems and Software Engineering.
    Successful Software Projects and Products: A quantitative study2006Independent thesis Advanced level (degree of Master (One Year))Student thesis
    Abstract [en]

    Successful or failed software projects have been discussed in literature for many years. Successful software projects are often defined as meeting business objectives, deliver on time and within budget, and meeting requirements. Different factors that contribute to software project success have been identified in the literature. Some of the most common factors that lead to software project success are: user involvement, management support, realistic requirements, and having good estimations. However, there are different opinions about what a successful software project is. Linberg found in a study that managers had a different perception from software practitioners (developers, testers etc.) about what a successful software project is. Since there are different perceptions of what a successful project is among different roles in software development, there may be differences from other perspectives too. This observation relates to the overall research questions in the thesis: Could there be different perceptions about what success factors are for software projects among different countries and customer-supplier relationships? Do people from different countries have different perceptions about what success factors are for software products? This study investigated if there are any differences and similarities between Swedish and Australian companies. In addition, a comparison between bespoke and market driven and bespoke and in-house customer-supplier relationships was made. The result shows that there are differences of which factors that lead to software project success among the two countries as well as between different types of customer-supplier relationships.

  • 291.
    Berntzon, Fredrik
    et al.
    Linköping University, Department of Computer and Information Science.
    Dahlström, Didrik
    Linköping University, Department of Computer and Information Science.
    Fries, Niklas
    Linköping University, Department of Computer and Information Science.
    Håstad, Oskar
    Linköping University, Department of Computer and Information Science.
    Markgren, Hedvig
    Linköping University, Department of Computer and Information Science.
    Persson, Gustaf
    Linköping University, Department of Computer and Information Science.
    Strandberg, Axel
    Linköping University, Department of Computer and Information Science.
    Söderlind, Marcus
    Linköping University, Department of Computer and Information Science.
    Implementering av en användbar och förtroendeingivande C2C-plattform för matlådor: En fallstudie av webbapplikationen Delish2017Independent thesis Basic level (degree of Bachelor), 12 credits / 18 HE creditsStudent thesis
    Abstract [en]

    This report covers a case study performed at Linköping University. The project consists of the development of a web application of type e-commerce, named Delish, which is a service for trading lunch boxes among students. The report treats the compilation of a theoretical framework, the development and its results followed by a discussion. The web application serves as a foundation in order to examine how an application should be designed to ensure high navigability and simplicity while establishing user trust. Information is gathered in order to define a theoretical and methodical framework. The development is accompanied by an evaluation of the products fulfilment of earlier set goals, by conducting market surveys and usability testing. Navigability is achieved through the implementation of different navigational systems and the application is perceived as simple as a result of effective use of colours and typography. Through the implementation of a ranking system and communication of data integrity, the application is perceived as trustworthy.

  • 292.
    Bertilsson, Henrik
    et al.
    Blekinge Institute of Technology, Department of Software Engineering and Computer Science.
    Näsman, Gustav
    Blekinge Institute of Technology, Department of Software Engineering and Computer Science.
    Improving progress tracking using automated testing techniques2002Independent thesis Advanced level (degree of Master (One Year))Student thesis
    Abstract [en]

    One of the problems when developing software is the difficulty of knowing how much that is done in a project. This is a basic condition to be able to estimate the remaining efforts with increased accuracy over time. To get accurate progress information it is important that the progress tracking is done in an objective way and also in an as simple way as possible. Our focus in this work has been software projects in general but a case study has also been performed at Ericsson Software Technology AB in Ronneby. We have studied the organization and performed interviews with project managers to find out if this really is a problem and if the process can be improved in some way to ease the task of progress tracking. This case study together with our literature study has resulted in a proposition for a solution. Our approach has been to use automated testing as a way to make progress tracking more objective. The result presented in this thesis is a base for a system that could ease the tracking of progress. In short, the system extracts information from an automated testing process and compares it with estimated figures to be able to automatically generate progress information.

  • 293.
    Betz, Stefanie
    et al.
    Blekinge Institute of Technology, Faculty of Computing, Department of Software Engineering.
    Andreas, Oberweis
    Rolf, Stephan
    Knowledge transfer in offshore outsourcing software development projects: an analysis of the challenges and solutions from German clients2014In: Expert systems (Print), ISSN 0266-4720, E-ISSN 1468-0394, Vol. 31, no 3Article in journal (Refereed)
    Abstract [en]

    Knowledge transfer is a critical factor in ensuring the success of offshore outsourcing software development projects and is, in many cases, neglected. Compared to in-house or co-located projects, however, such globally distributed projects feature far greater complexity. In addition to language barriers, factors such as cultural differences, time zone variance, distinct methods and practices, as well as unique equipment and infrastructure can all lead to problems that negatively impact knowledge transfer, and as a result, a project's overall success. In order to help minimise such risks to knowledge transfer, we conducted a research study based on expert interviews in six projects. Our study used German clients and focused on offshore outsourcing software development projects. We first identified known problems in knowledge transfer that can occur with offshore outsourcing projects. Then we collected best-practice solutions proven to overcome the types of problems described. Afterward, we conducted a follow-up study to evaluate our findings. In this subsequent stage, we presented our findings to a different group of experts in five projects and asked them to evaluate these solutions and recommendations in terms of our original goal, namely to find ways to minimise knowledge-transfer problems in offshore outsourcing software development projects. Thus, the result of our study is a catalog of evaluated solutions and associated recommendations mapped to the identified problem areas.

  • 294.
    Betz, Stefanie
    et al.
    Blekinge Institute of Technology, School of Computing.
    Wohlin, Claes
    Blekinge Institute of Technology, School of Computing.
    Alignment of business, architecture, process, and organisation in a software development context2012Conference paper (Refereed)
    Abstract [en]

    In this paper we investigate the current state of work regarding alignment of Business, Architecture, Process, and Organisation (BAPO) perspectives in a software product development context. We planned to do that by conducting a systematic literature study to capture the state of the art in alignment of BAPO in software development. But, as it turned out we found that almost no substantial information is available about the alignment of BAPO in software development. Thus, based on the available literature and a small qualitative study, we defined a conceptual model of the alignment of BAPO including five levels of alignment that can be used as a basis for future empirical studies.

  • 295.
    Betz, Stefanie
    et al.
    Blekinge Institute of Technology, School of Computing.
    Šmite, Darja
    Blekinge Institute of Technology, School of Computing.
    Fricker, Samuel
    Blekinge Institute of Technology, School of Computing.
    Moss, Andrew
    Blekinge Institute of Technology, School of Computing.
    Afzal, Wasif
    Svahnberg, Mikael
    Blekinge Institute of Technology, School of Computing.
    Wohlin, Claes
    Blekinge Institute of Technology, School of Computing.
    Börstler, Jürgen
    Blekinge Institute of Technology, School of Computing.
    Gorschek, Tony
    Blekinge Institute of Technology, School of Computing.
    An Evolutionary Perspective on Socio-Technical Congruence:The Rubber Band Effect2013Conference paper (Refereed)
    Abstract [en]

    Conway’s law assumes a strong association between the system’s architecture and the organization’s communication structure that designs it. In the light of contemporary software development, when many companies rely on geographically distributed teams, which often turn out to be temporarily composed and thus having an often changing communication structure, the importance of Conway’s law and its inspired work grows. In this paper, we examine empirical research related to Conway’s law and its application for cross-site coordination. Based on the results obtained we conjecture that changes in the communication structure alone sooner or later trigger changes in the design structure of the software products to return the sociotechnical system into the state of congruence. This is further used to formulate a concept of a rubber band effect and propose a replication study that goes beyond the original idea of Conway’s law by investigating the evolution of socio-technical congruence over time.

  • 296.
    Bhalsingh, Ashwini
    KTH, School of Information and Communication Technology (ICT).
    Cloud Infrastructure for Smart Devices: SmartClouds2015Independent thesis Advanced level (degree of Master (Two Years)), 20 credits / 30 HE creditsStudent thesis
    Abstract [en]

    On-demand resource provisioning is an important feature of cloud, which offers several benefits such as scalability, enhanced performance, low maintenance cost, elasticity, adequate storage, ubiquitous accessibility, minimum infrastructure etc. At the same time, usage of mobile phones is becoming increasingly common throughout the world. Also, these phones are coming in the market with appealing features like fast processing unit, internal and external memory up to MBs and GBs respectively, web browsing, inbuilt sensors, powerful cameras etc. This master’s thesis project proposes a novel approach of utilizing all these features of semi-autonomous mobile devices (especially smart phones) and cloud infrastructure altogether.

    The specific aim of project is to design, implement and present a framework for multi-featured smart phone on top of cloud infrastructure. Proposed framework is implemented and tested for two different communication methods known as client poll and server push. In the second phase, performance analysis of implemented framework is carried out via simulation to compare two methods of interaction and to observe server’s load. As a result, first it is found that the server-initiated communication (i.e. server push) requires 40% to 50% less times as compared to the client-initiated communication (i.e. client poll). Second, it is observed that the application server load of framework is not affected too much regarding increasing number of client’s requests.

  • 297.
    Bhatti, Ansar Malook
    et al.
    Blekinge Institute of Technology, School of Engineering, Department of Systems and Software Engineering.
    Abdullah, Hafiz Muhammad
    Blekinge Institute of Technology, School of Engineering, Department of Systems and Software Engineering.
    Deciding on Optimum Set of Measures in Software Organizations2009Independent thesis Advanced level (degree of Master (Two Years))Student thesis
    Abstract [en]

    Software measurement process is a significant part of process improvement in software organizations. The organizations usually follow a measurement process that includes measures selection, data collection, and analysis to improve their processes. Most of the software organizations face difficulties in deciding the measures to collect since there is no universal set of measures for all types of organizations and projects. Experience shows that measurement can be more successful if the measures are collected based on the goals of the organization or the project which it will serve. A few methodologies exist to aid the software organizations. Goal Question Metric (GQM) is one of the most widely known and used one. However, one of the major constraints for the organizations is the associated cost when collecting the measures. Therefore, software organizations also require selecting the optimum set of measures which are good enough for the organization. This thesis study aims to provide solution for this problem. We propose a model, named ‗Optimum Measure Set Decision Model (OMSD)‘, which is an extension of GQM paradigm. The model is based on a heuristics approach, which aims to provide the optimum set of measures from a large number of possible measures. To develop the model, we identified the factors which are significant in selecting the optimum set of measures based on the literature survey results. Then, we evaluated those factors by conducting an empirical study. As the empirical research strategy, we used traditional fixed non-experimental design strategy. We performed a survey by distributing a structured questionnaire in order to evaluate the important factors we identified when selecting the optimum number of measures to be collected in an organization. We evaluated the heuristics rules by means of some sample cases we created. Moreover, we provided an idea for an alternative solution to optimize the number of measures to be collected for the future research.

  • 298. Bhatti, Ansar Malook
    et al.
    Abdullah, Hafiz Muhammad
    Gencel, Cigdem
    A Model for Selecting an Optimum Set of Measures in Software Organizations2009Conference paper (Refereed)
    Abstract [en]

    Most of the software organizations face difficulties in choosing the measures to collect since there is no universal set of measures for all types of organizations and projects. Experience shows that measurement can be more successful if the measures are collected based on the goals of the organization or the project which it will serve. However, one of the major constraints for the organizations is the associated cost for the resources needed when collecting the measures. Therefore, based on their goals, the software organizations require collecting not only as few measures from a large number of possible measures as possible but an optimum set of measures as well. In this paper, we propose a model, called ‘Optimum Measures Set Decision (OMSD) Model’, which is an extension of the well-known Goal Question Metric (GQM) paradigm using a heuristics approach. We performed a survey by distributing a structured questionnaire to a number of people from the industry in order evaluate and get feedback on these factors. We evaluated the rules of the model by means of some sample cases we created. In this paper, we discuss OMSD as well as the empirical studies we conducted in order to develop it.

  • 299.
    Bhatti, Khurram
    et al.
    Blekinge Institute of Technology, School of Computing.
    Ghazi, Ahmad Nauman
    Blekinge Institute of Technology, School of Computing.
    Effectiveness of Exploratory Testing, An empirical scrutiny of the challenges and factors affecting the defect detection efficiency2010Independent thesis Advanced level (degree of Master (Two Years))Student thesis
    Abstract [en]

    Context: Software testing is an integral part of software development life cycle. To improve the quality of software there are different testing approaches practiced over the years. Traditionally software testing is carried out by following approach focusing on prior test design. While exploratory testing is an approach to test software where the tester does not require to follow a specific test design. But rather, exploratory testing should facilitate the tester in testing the complete system comprehensively. Exploratory testing is seen by some, as a way to conduct simultaneous learning, test design and execution of tests simultaneously. While others point to exploratory testing enabling constant evolution of tests in an easy manner. Objectives: In this study we have investigated the field of exploratory testing in literature and industry to understand its perception and application. Further among the stated claims by practitioners, we selected defect detection efficiency and effectiveness claim for empirical validation through an experiment and survey. Methods: In this study, a systematic literature review, interview, experiment and survey are conducted. In the systematic review a number of article sources are used, including IEEE Xplore, ACM Digital Library, Engineering village, Springer Link, Google Scholar and Books database. The systematic review also includes the gray literature published by the practitioners. The selection of studies was done using two-phase and tollgate approach. A total of 47 references were selected as primary studies. Eight semi-structures interviews were conducted with industry practitioners. Experiment had total 4 iterations and 70 subjects. The subjects were selected from industry and academia. The experimental design used was one factor with two interventions and one response variable. Results: Based on our findings from literature review and interviews, the understanding of exploratory testing has improved over the period but still lacks empirical investigation. The results drawn from experimental and survey data shows that exploratory testing proved effective and efficient in finding more critical bugs in limited time. Conclusions: We conclude that exploratory testing has a lot of potential and much more to offer to testing industry. But more empirical investigation and true facts and figures are required to motivate the testing industry to adapt it. We have reported a number of advantages, disadvantages, challenges and factors in this study. We further investigated the claims stated by the ET practitioners through an experiment and survey. The statistical tests were conducted on the collected data to draw meaningful results. We found statistical significance difference in number of true defects found. Using exploratory testing approach testers found far more defects than test case based testing. Although, there was no statistical significance difference between the two approaches for false defects.

  • 300.
    Bhatti, ZafarAhmad
    Mälardalen University, School of Innovation, Design and Engineering.
    Incorporating Safety Requirements using Patterns in ArchWiz Tool: Safety requirements in Archwiz tool2011Independent thesis Advanced level (degree of Master (Two Years)), 20 credits / 30 HE creditsStudent thesis
    Abstract [en]

    Usability Supporting Architectural Patterns (USAP) has already introduced a concept in software architecture for coping usability issues in better style and revealing its obscured dimensions. A support is also needed to develop the safety systems in such a way that they employ the same rules and get a better understanding of safety, its requirements and the architecture. A way to determine safety requirements from the patterns and working with the responsibilities of patterns was the aim for this thesis report. On the other hand, a useful tool with the name “ArchWiz” was to be developed further from its prototypical form-an assisting tool for architects to look for requirements and evaluation of their architecture. The mature development of ArchWiz tool, and incorporating the safety perspective with respect to USAP vogue was also the goal of the thesis.

    In a development process, architecture designing is a crucial and vital part of software system. During architecture designing process very first decisions and information are gained to validate if the system has the potential to meet its requirements and intended behaviours. Along with other important quality attributes, safety architecture has played an important role in developing today’s critical software and automated systems. These safety issues especially in software architecture are to protect, recover, discover and mitigate the hazards, faults, failures and catastrophic perils. The deficiency and obscurity of these inherent dangers can be reduced by understanding the safety in general and analysing its requirements from unseen perspectives. Later, these requirements can be traced into the architecture of a similar system as a knowledge base or experience gained.

    Architectural patterns and their investigation in safety provide a broad horizon for requirement and solution in various aspects. They help to bring out the requirements in refined way and in general manners too. The report, therefore, presents the suggestion to formalize the suggestions in safety with respect to requirement engineering in architectural context as well as reusable solution for these issues; alike in USAP style.

3456789 251 - 300 of 2740
CiteExportLink to result list
Permanent link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf