To see the other types of publications on this topic, follow the link: Research Software Engineering.
Dissertations / Theses on the topic 'Research Software Engineering'
Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles
Consult the top 50 dissertations / theses for your research on the topic 'Research Software Engineering.'
Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.
You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.
Browse dissertations / theses on a wide variety of disciplines and organise your bibliography correctly.
1
Moritz, Evan Alexander. "Tracelab: Reproducing Empirical Software Engineering Research." W&M ScholarWorks, 2013. https://scholarworks.wm.edu/etd/1539626949.
Full text
2
Fan, Yao-Long. "Re-engineering the solicitation management system." CSUSB ScholarWorks, 2006. https://scholarworks.lib.csusb.edu/etd-project/3179.
Full textAbstract:
The scope of this project includes a re-engineering of the internal architecture of the Solicitation Management System (SMS), a web-based application that facilitates the running of grant proposal solicitations for the Office of Technology Transfer and Commercialization at California State University San Bernardino (CSUSB). A goal of the project is to increase consistency and efficiency of the code base of the system, making it easier to understand, maintain, and extend. The previous version of SMS was written to rely on the Spring and Hibernate frameworks. The project includes a restructuring of the system to remove reliance on the Spring framework, but maintain reliance on Hibernate. The result is an updated version of the SMS. The system was written using current technologies such as Java, JSP, and CSS.
3
Pek, Ekaterina [Verfasser]. "Corpus-based empirical research in software engineering / Ekaterina Pek." Koblenz : Universitätsbibliothek Koblenz, 2014. http://d-nb.info/1063286468/34.
Full text
4
Krein, Jonathan L. "Replication and Knowledge Production in Empirical Software Engineering Research." BYU ScholarsArchive, 2014. https://scholarsarchive.byu.edu/etd/4296.
Full textAbstract:
Although replication is considered an indispensable part of the scientific method in software engineering, few replication studies are published each year. The rate of replication, however, is not surprising given that replication theory in software engineering is immature. Not only are replication taxonomies varied and difficult to reconcile, but opinions on the role of replication contradict. In general, we have no clear sense of how to build knowledge via replication, particularly given the practical realities of our research field. Consequently, most replications in software engineering yield little useful information. In particular, the vast majority of external replications (i.e., replications performed by researchers unaffiliated with the original study) not only fail to reproduce the original results, but defy explanation. The net effect is that, as a research field, we consistently fail to produce usable (i.e., transferable) knowledge, and thus, our research results have little if any impact on industry. In this dissertation, we dissect the problem of replication into four primary concerns: 1) rate and explicitness of replication; 2) theoretical foundations of replication; 3) tractability of methods for context analysis; and 4) effectiveness of inter-study communication. We address each of the four concerns via a two-part research strategy involving both a theoretical and a practical component. The theoretical component consists of a grounded theory study in which we integrate and then apply external replication theory to problems of replication in empirical software engineering. The theoretical component makes three key contributions to the literature: first, it clarifies the role of replication with respect to the overall process of science; second, it presents a flexible framework for reconciling disparate replication terminology; and third, it informs a broad range of practical replication concerns. The practical component involves a series of replication studies, through which we explore a variety of replication concepts and empirical methods, ultimately culminating in the development of a tractable method for context analysis (TCA). TCA enables the quantitative evaluation of context variables in greater detail, with greater statistical power, and via considerably smaller datasets than previously possible. As we show (via a complex, real-world example), the method ultimately enables the empirically and statistically-grounded reconciliation and generalization of otherwise contradictory results across dissimilar replications—which problem has previously remained unsolved in software engineering.
5
Ahmad, M. O. (Muhammad Ovais). "Exploring Kanban in software engineering." Doctoral thesis, Oulun yliopisto, 2016. http://urn.fi/urn:isbn:9789526214085.
Full textAbstract:
Abstract To gain competitive advantage and thrive in the market, companies have introduced Kanban in software development. Kanban has been used in the manufacturing industry for over six decades. In the software engineering domain, Kanban was introduced in 2004 to increase flexibility in coping with dynamic requirements, bring visibility to workflow and related tasks, improve communication, and promote the pull system. However, the existing scientific literature lacks empirical evidence of the use of Kanban in software companies. This doctoral thesis aims to improve the understanding of the use of Kanban in software engineering. The research was performed in two phases: 1) analysis of scientific literature on Kanban in software engineering and industrial engineering and 2) investigation of Kanban implementation trends in software companies. The data was collected through systematic literature reviews, survey and semi-structured interviews. The results were synthesized to draw conclusions and outline implications for research and practice. The results indicate growing interest in the use of Kanban in software companies. The findings suggest that Kanban is applicable to software development, software maintenance, and portfolio management in software companies. Kanban brings visibility to task and offering status, limits work in progress at any given time gives people greater control over their work and limit task switching. Although Kanban offers several benefits, as reported in this dissertation, the findings show that software companies find it challenging to implement Kanban incrementally<br>Tiivistelmä Ohjelmistoteollisuudessa Kanbanin käyttö on yleistynyt vuodesta 2004 alkaen. Sillä pyritään tuomaan joustavuutta muuttuvien vaatimusten hallintaan, tuomaan näkyvyyttä työnkulkuun ja toisiinsa liittyviin tehtäviin, parantamaan kommunikaatiota sekä edistämään imuohjauksen hyödyntämistä. Kanbania on käytetty valmistavassa teollisuudessa jo yli kuuden vuosikymmenen ajan. Olemassa olevassa tieteellisessä kirjallisuudessa on kuitenkin esitetty hyvin vähän empiirisiä tutkimustuloksia Kanbanin käytöstä ohjelmistoyrityksissä. Väitöskirjan tavoitteena on parantaa ymmärrystä Kanbanin käytöstä ohjelmistotuotannossa. Tutkimus toteutettiin kahdessa vaiheessa: 1) Kirjallisuusanalyysi Kanbanin käytöstä ohjelmistotuotannossa ja tuotantotekniikassa ja 2) Empiirinen tutkimus Kanbanin käyttöönoton trendeistä ohjelmistoyrityksissä. Tutkimusaineisto kerättiin systemaattisten kirjallisuuskatsausten, kyselytutkimuksen ja puolistrukturoitujen teemahaastattelujen kautta. Tutkimustulosten synteesin pohjalta tehtiin johtopäätöksiä Kanbanin käytöstä ohjelmistotuotannossa sekä niiden merkityksestä alan tutkimukselle ja Kanbanin käytölle yrityksissä. Tutkimuksen tulokset osoittavat kasvavaa kiinnostusta Kanbanin käyttöä kohtaan ohjelmistoyrityksissä. Tulosten perusteella Kanban soveltuu käytettäväksi ohjelmistokehityksessä, ohjelmistojen ylläpidossa sekä tuoteportfolion hallinnassa. Kanban tuo näkyvyyttä ohjelmistokehitykseen, niin meneillään olevien tehtävien kuin portfoliotarjoaman osalta. Se myös auttaa rajoittamaan työtehtävien ruuhkautumista ja antaa kehittäjille paremman tavan hallita työtään rajoittamalla työtehtävien vaihtoa. Vaikka Kanbanin käytöllä on mahdollista saavuttaa väitöskirjatutkimuksessa esitettyjä hyötyjä, tulokset osoittavat, että ohjelmistoyrityksillä on haasteita Kanbanin inkrementaalisessa käyttöönotossa
6
Bradley, Roxanne. "Software design : communication between human factors engineers and software developers /." Thesis, This resource online, 1991. http://scholar.lib.vt.edu/theses/available/etd-08222009-040239/.
Full text
7
Junered, Marcus. "Enabling hardware technology for GNSS software radio research." Licentiate thesis, Luleå : Luleå University of Technology, 2007. http://epubl.ltu.se/1402-1757/2007/32/.
Full text
8
Koch, Stefan, and Georg Schneider. "Results from software engineering research into open source development projects using public data." Institut für Informationsverarbeitung und Informationswirtschaft, WU Vienna University of Economics and Business, 2000. http://epub.wu.ac.at/494/1/document.pdf.
Full textAbstract:
This paper presents first results from research into open source projects from a software engineering perspective. The research methodology employed relies on public data retrieved from the CVS-repository of the GNOME project and relevant discussion groups. This methodology is described in detail and some of the results concerning the special characteristics of open source software development are given. (author's abstract)<br>Series: Diskussionspapiere zum Tätigkeitsfeld Informationsverarbeitung und Informationswirtschaft
9
Daly, John William. "Replication and a multi-method approach to empirical software engineering research." Thesis, University of Strathclyde, 1996. http://oleg.lib.strath.ac.uk:80/R/?func=dbin-jump-full&object_id=9350.
Full text
10
Smith, Terry L. "Recent Trends in Software Engineering Research As Seen Through Its Publications." UNF Digital Commons, 2004. http://digitalcommons.unf.edu/etd/205.
Full textAbstract:
This study provides some insight into the field of software engineering through analysis of its recent research publications. Data for this study are taken from the ACM's Guide to Computing Literature (GUIDE) They include both the professionally assigned Computing Classification System (CCS) descriptors and the title text of each software engineering publication reviewed by the GUIDE from 1998 through 2001.
The first part of this study provides a snapshot of software engineering by applying co-word analysis techniques to the data. This snapshot indicates recent themes or areas of interest, which, when compared with the results from earlier studies, reveal current trends in software engineering.
Software engineering continues to have no central focus. Concepts like software development, process improvement, applications, parallelism, and user interfaces are persistent and, thus, help define the field, but they provide little guidance for researchers or developers of academic curricula.
Of more interest and use are the specific themes illuminated by this study, which provide a clearer indication of the current interests of the field. Two prominent themes are the related issues of programming-in-the-large and best practices.
Programming-in-the-large is the term often applied to large-scale and long-term software development, where project and people management, code reusability, performance measures, documentation, and software maintenance issues take on special importance. These issues began emerging in earlier periods, but seem to have risen to prominence during the current period.
Another important discovery is the trend in software development toward using networking and the Internet. Many network- and Internet-related descriptors were added to the CCS in 1998. The prominent appearance and immediate use of these descriptors during this period indicate that this is a real trend and not just an aberration caused by their recent addition.
The titles of the period reflect the prominent themes and trends. In addition to corroborating the keyword analysis, the title text confirms the relevance of the CCS and its most recent revision.
By revealing current themes and trends in software engineering, this study provides some guidance to the developers of academic curricula and indicates directions for further research and study.
11
Anderson, Patrick William 1976. "A modular framework for reusable research software." Thesis, Massachusetts Institute of Technology, 2000. http://hdl.handle.net/1721.1/81539.
Full textAbstract:
Thesis (M.Eng.)--Massachusetts Institute of Technology, Dept. of Electrical Engineering and Computer Science, 2000.<br>Includes bibliographical references (leaves 63-64).<br>by Patrick William Anderson.<br>M.Eng.
12
Saboe, Michael S. "A software technology transition entropy based engineering model." Monterey, Calif. : Naval Postgraduate School, 2002. http://edocs.nps.edu/npspubs/scholarly/dissert/2002/Mar/02Mar%5FSaboe%5FPhD.pdf.
Full textAbstract:
Dissertation (Ph.D. in Software Engineering)--Naval Postgraduate School, March 2002.<br>Dissertation supervisor: Luqi. "March 2002." Description based on title screen as viewed on July 15, 2010. Author(s) subject terms: Software Engineering, Technology Transfer, Information Theory, Communication Theory, Statistical Mechanics, Dynamical Systems, Control Theory, Learning Curves, Entropy, Information Temperature, Temperature of Software (o Saboe), Technology Transfer Dynamics, Research Management, Diffusion of Innovation, Project Management, Physics of Software Includes bibliographical references (p. 457-489). Also available in print.
13
El, Shobaki Mohammed. "On-chip monitoring for non-intrusive hardware/software observability." Licentiate thesis, Uppsala : Dept. of Information Technology, Univ, 2004. http://www.it.uu.se/research/reports/lic/2004-004/.
Full text
14
Vakkalanka, Sairam, and SR Phanindra Kumar Narayanasetty. "Investigating Research on Teaching Modeling in Software Engineering -A Systematic Mapping Study." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-2468.
Full textAbstract:
Context: Modeling is an important activity, which is used, in different phases of software engineering. Without models and modeling, it is nearly impossible to design and develop software systems, which demands the need for modeling to be taught in software engineering. There exist a number of reported models, methods, tools and languages to teach modeling in software engineering, which suggests the need for a classification and an overview of the area. This research investigates the state of published research on teaching modeling in software engineering in order to provide a systematic overview and classification of these different ways of teaching modeling with an insight on their importance and relevance to this research area. Objectives: The overall goal of the research was achieved with fulfilling the following objectives: understanding how systematic mapping is conducted, developing a systematic mapping process that will properly provide data for investigating the published research, applying the process, and finally reflecting on the results of the mappings, analyzing the importance and evaluating relevance of the published research. Methods: Systematic literature review was used as a tool to understand and inspect how systematic mapping was carried out in the area of software engineering. Based on the results of systematic literature review, new guidelines were formulated to conduct systematic mapping. These guidelines were used to investigate the published research on teaching modeling in software engineering. The results obtained through the systematic mapping were evaluated based on Industrial relevance, Rigor and citation count to examine their importance and identify research gaps. Results: 131 articles were classified into five classes such as Languages, Course Design, Curriculum design, Diagrams, others using semi-manual classification scheme and classification facets such as the type of audience, type of contribution, type of research, type of publication, type of publication year, type of research method and type of study setting. After the evaluation of Industrial relevance, rigor & citation ranking on the obtained results of the classification, 8 processes, 4 tools, 3 methods, 2 measurement-metrics and 1 model were extracted to teach modeling in software engineering. Also, this classification when compared with an existing classification, which is based on interviews and discussions, showed that our classification provides a wider overview with a deeper insight of the different ways to teach modeling in software engineering. Conclusions: Results of this systematic mapping study indicate that there is an increase in the research activity on teaching modeling in software engineering, with Unified Modeling Language (UML) being the widely research area. Much research is emphasized on teaching modeling to students from academia which indicates a research gap in developing methods, models, tools and processes to teach modeling to students/practitioners from the industry. Also, considering the citation ranking, industrial relevance and rigor of the articles, areas such as course design and curriculum development are highly neglected, suggesting the need for more research focus.<br>Sammanhang : Modellering är en viktig verksamhet , som används i olika faser av programvaruteknik . Utan modeller och modellering , är det nästan omöjligt att utforma och utveckla mjukvarusystem , vilket kräver behovet av modellering för att undervisas i programvaruteknik . Det finns ett antal rapporterade modeller, metoder , verktyg och språk för att undervisa modellering i programvaruteknik , vilket tyder på att det behövs en klassificering och en överblick över området . Denna forskning undersöker tillståndet av publicerad forskning om undervisning modellering i programvaruteknik för att ge en systematisk överblick och klassificering av dessa olika sätt att undervisa modellering med en insikt om deras betydelse och relevans för detta forskningsområde . Mål : Det övergripande målet med forskningen uppnåddes med att uppfylla följande mål : att förstå hur systematisk kartläggning genomförs , att utveckla en systematisk kartläggning process som riktigt kommer att ge data för att undersöka publicerad forskning , tillämpning av processen , och slutligen reflektera över resultaten av de avbildningar, som analyserar betydelsen och utvärdera relevansen av den publicerade forskningen . Metoder : En systematisk litteraturstudie användes som ett verktyg för att förstå och kontrollera hur systematisk kartläggning genomfördes inom området programvaruteknik . Baserat på resultaten av en systematisk litteraturgenomgång har nya riktlinjer som formulerats för att bedriva systematisk kartläggning . Riktlinjerna användes för att undersöka den publicerade forskning om undervisning modellering i programvaruteknik . De resultat som erhållits genom systematisk kartläggning utvärderades baserat på industriell relevans , Rigor och stämningen räkning för att undersöka deras betydelse och identifiera kunskapsluckor . Resultat: 131 artiklar klassificerades i fem klasser , t.ex. språk , kurs Design , Curriculum design, diagram , andra med hjälp av semi - manuell klassificeringssystem och klassificerings fasetter såsom typ av publiken , typ av bidrag , typ av forskning , typ av publikation , typ av årtal , typ av forskningsmetod och typ av studieinställning. Efter utvärderingen av industriell relevans , noggrannhet och stämningen ranking på de erhållna resultaten av klassificeringen , 8 processer , 4 verktyg , 3 metoder , 2 mät - mått och 1 modell extraherades att lära modellering i programvaruteknik . Även denna klassificering i jämförelse med en befintlig klassificering , som bygger på intervjuer och diskussioner , visade att vår klassificering ger en bredare överblick med en djupare insikt om de olika sätten att lära modellering i programvaruteknik . Slutsatser : Resultaten av denna systematiska kartläggning visar att det finns en ökning av forskningsverksamheten på undervisning modellering i programvaruteknik , med Unified Modeling Language ( UML ) är den brett forskningsområde. Mycket forskning framhävs att lära modellering för studenter från den akademiska världen , som indikerar en lucka forskning för att utveckla metoder, modeller , verktyg och processer för att lära modellering för studenter / utövare från branschen . Dessutom , med tanke på stämningen ranking , industriell relevans och noggrannhet av artiklarna , områden som kursdesign och utveckling av läroplaner är mycket eftersatt , vilket tyder på att det behövs mer forskning fokus.<br>Flat # 503,Sri Krishna Residency, Mangapuram Colony,Vizag, Andhra Pradesh, India- 530017. +9989733724
15
Rönkkö, Kari. "Making Methods Work in Software Engineering : Method Deployment - as a Social Achievement." Doctoral thesis, Ronneby : Blekinge Institute of Technology, 2005. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-00264.
Full textAbstract:
The software engineering community is concerned with improvements in existing methods and development of new and better methods. The research approaches applied to take on this challenge have hitherto focused heavily on the formal and specifying aspect of the method. This has been done for good reasons, because formalizations are the means in software projects to predict, plan, and regulate the development efforts. As formalizations have been successfully developed new challenges have been recognized. The human and social role in software development has been identified as the next area that needs to be addressed. Organizational problems need to be solved if continued progress is to be made in the field. The social element is today a little explored area in software engineering. Following with the increased interest in the social element it has been identified a need of new research approaches suitable for the study of human behaviour. The one sided focus on formalizations has had the consequence that concepts and explanation models available in the community are one sided related in method discourses. Definition of method is little explored in the software engineering community. In relation to identified definitions of method the social appears to blurring. Today the software engineering community lacks powerful concepts and explanation models explaining the social element. This thesis approaches the understanding of the social element in software engineering by applying ethnomethodologically informed ethnography and ethnography. It is demonstrated how the ethnographic inquiry contributes to software engineering. Ethnography is also combined with an industrial cooperative method development approach. The results presented demonstrate how industrial external and internal socio political contingencies both hindered a method implementation, as well as solved what the method was targeted to do. It is also presented how project members’ method deployment - as a social achievement is played out in practice. In relation to this latter contribution it is provided a conceptual apparatus and explanation model borrowed from social science, The Documentary method of interpretation. This model addresses core features in the social element from a natural language point of view that is of importance in method engineering. This model provides a coherent complement to an existing method definition emphasizing formalizations. This explanation model has also constituted the underpinning in research methodology that made possible the concrete study results.
16
Thomas, Mathew. "Semi-Automated Dental Cast Analysis Software." Wright State University / OhioLINK, 2011. http://rave.ohiolink.edu/etdc/view?acc_num=wright1310404863.
Full text
17
Vajrapu, Rakesh Guptha, and Sravika Kothwar. "Software Requirements Prioritization Practices in Software Start-ups : A Qualitative research based on Start-ups in India." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-15967.
Full textAbstract:
Context: Requirements prioritization is used in software product management and is concerned with identifying the most valuable requirements from a given set. This is necessary to satisfy the needs of customers, to provide support for stakeholders and more importantly for release planning. Irrespective of the size of the organization (small, medium and large), requirements prioritization is important to minimize the risk during development. However, few studies explore how requirements prioritization is practiced in start-ups. Software start-ups are becoming important suppliers of innovative and software-intensive products.Earlier studies suggest that requirements discovery and validation is the core activity in start-ups. However, due to limited resources, start-ups need to prioritize on what requirements to focus. If they do it wrong it leads to wasted resources.While larger organizations may afford such waste, start-ups cannot.Moreover, researchers have identified that start-ups are not small versions of large companies and the existing software development practices cannot be transferred directly due to low rigor in current studies.Thus, we planned to conduct an exploratory study on requirements prioritization practices in the context of software start-ups. Objectives: The main aim of our study is to explore the state-of-art of requirements prioritization practices used in start-ups.We also identify the challenges associated with the corresponding practices and few possible solutions. Methods: In this qualitative research, we conduct a literature review by referring to many article sources like IEEE Xplore, Scopus, and Google Scholar to identify the prioritization practices and challenges in general. An interview study is conducted by using semi-structured interviews to collect data from practitioners.Thematic analysis was used to analyze the interview data. Results: We have identified 15 practices from 8 different start-ups companies with corresponding challenges and possible solutions. Our results show mixed reviews in terms of the prioritization practices at start-ups. From the total of 8 companies about 6 companies followed formal methods while in the remaining 2 companies, prioritization was informal and not clear. The results show that value-based method is the dominant prioritization technique in start-ups. The results also show that customer input and return on investment aspects of prioritization play a key role when compared to other aspects. Conclusions: The results of this study provide an understanding of the various requirements prioritization practices in start-ups and challenges faced in implementing them.These results are validated from the answers found in the literature. The solutions identified for the corresponding challenges allow the practitioners to approach them in a better way. As this study focused only on Indian software start-up companies, it is recommended to extend to Swedish software start-up companies as well to get a broader perspective. Scaling of sample size is also recommended. This study may help future research on requirements engineering in start-ups. It may also help practitioners who have an intention to begin a software start-up company to get an idea of what challenges they may face while prioritizing requirements and can use these solutions to mitigate them.
18
Pennington, Sandra Lynn. "A software engineering approach to the integration of CAD/CAM systems." Diss., This resource online, 1991. http://scholar.lib.vt.edu/theses/available/etd-07102007-142514/.
Full text
19
Vamsi, Appana Vamsi. "Evaluating Industrial Relevance in Search Based Software Engineering Research : A Systematic Mapping Study and Survey." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-14000.
Full textAbstract:
Search Based Software Engineering is one of the important field of software engineering. Over the past few years even though there is a lot of study performed on SBSE and its search techniques in software development areas, it appears SBSE is not very industry relevant at the moment because most of the academic work was limited towards the application of search techniques. Hence, author proposes a study to know the trend of SBSE literature over the past few years and also analyze to what degree current SBSE research is industry relevant
20
Ramstedt, Clayton D. "Modular 3D Printer System Software For Research Environments." BYU ScholarsArchive, 2020. https://scholarsarchive.byu.edu/etd/8688.
Full textAbstract:
The Nordin group at Brigham Young University has been focused on developing 3D printing technology for fabrication of lab-on-a-chip (microfluidic) devices since 2013. As we showed in 2015, commercial 3D printers and resins have not been developed to meet the highly specialized needs of microfluidic device fabrication. We have therefore created custom 3D printers and resins specifically designed to meet these needs. As part of this development process, ad hoc 3D printer control software has been developed. However, the software is difficult to modify and maintain to support the numerous experimental iterations of hardware used in our custom 3D printers. This highlights the need for modular yet reliable system software that is easy to use, learn, and work with to adapt to the unique challenges of a student workforce. This thesis details the design and implementation of new 3D printer system software that meets these needs. In particular, a software engineering principle-based design approach is taken that lends itself to several specific development patterns that permit easy incorporation of new hardware into a 3D printer to enable rapid evaluation of and development with such new hardware.
21
Wiklund, Kristian. "Impediments for Automated Software Test Execution." Doctoral thesis, Mälardalens högskola, Inbyggda system, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-27830.
Full textAbstract:
Automated software test execution is a critical part of the modern software development process, where rapid feedback on the product quality is expected. It is of high importance that impediments related to test execution automation are prevented and removed as quickly as possible. An enabling factor for all types of improvement is to understand the nature of what is to be improved. The goal with this thesis is to further the knowledge about common problems encountered by software developers using test execution automation, in order to enable improvement of test execution automation in industrial software development. The research has been performed through industrial case studies and literature reviews. The analysis of the data have primarily been performed using qualitative methods, searching for patterns, themes, and concepts in the data. Our main findings include: (a) a comprehensive list of potential impediments reported in the published body of knowledge on test execution automation, (b) an in-depth analysis of how such impediments may affect the performance of a development team, and (c) a proposal for a qualitative model of interactions between the main groups of phenomena that contribute to the formation of impediments in a test execution automation project. In addition to this, we contribute qualitative and quantitative empirical data from our industrial case studies. Through our results, we find that test execution automation is a commonly under-estimated activity, not only in terms of resources but also in terms of the complexity of the work. There is a clear tendency to perform the work ad hoc, down-prioritize the automation in favor of other activities, and ignore the long-term effects in favor of short-term gains. This is both a technical and a cultural problem that need to be managed by awareness of the problems that may arise, and also have to be solved in the long term through education and information. We conclude by proposing a theoretical model of the socio-technical system that needs to be managed to be successful with test execution automation.<br>Syftet med denna avhandling är att utöka den vetenskapliga kunskapen om problem som kan uppstå under användning av automatiserad testning i industriell programvaruutveckling. Utveckling av programvara består principiellt av ett antal processteg: kravbehandling, detaljerad systemkonstruktion, implementation i form av programmering, och slutligen testning som säkerställer att kvaliteten på programvaran är tillräcklig för dess tilltänkta användare. Testning representerar en stor del av tiden och kostnaden för utveckling av programvaran, och detta gör att det är attraktivt att automatisera testningen. Automatiserade tester kan bidra med många positiva effekter. Testning som utförs om och om igen, för att säkerställa att gammal funktionalitet inte slutar att fungera när ändringar görs i programvaran, kan med fördel göras automatiserat. Detta frigör kvalificerad personal till kvalificerat arbete. Automatisering kan även minska ledtiden för testningen och därmed möjliggöra snabbare leveranser till kund. Ett annat mål med testautomatisering är att vara säker på att samma tester utförs på ett likartat sätt varje gång produkten testas, så att den håller en jämn och stabil kvalitetsnivå. Automatiserad testning är dock en mer komplex och kostsam verksamhet än vad man kan tro, och problem som uppstår under dess användning kan ha stora konsekvenser. Detta gäller i ännu större utsträckning i organisationer som använder moderna utvecklingsmetoder där automatisering är grundstenen för en effektiv kvalitetskontroll. För att kunna undvika så många problem som möjligt, är det därför mycket viktigt att förstå vad som händer när man använder testautomatisering i stor skala. Denna avhandling presenterar resultat från fallstudier i svensk industri, som, kombinerat med en systematisk genomgång av befintlig forskning inom området, har utförts för att söka djupare kunskap och möjligheter till generalisering. Arbetet har varit beskrivande, och förklarande, och bygger på empirisk forskningsmetodik. I avhandlingen bidrar vi med (a) information om de problem relaterade till automatiserad testning som vi har identifierat i de empiriska fallstudierna, (b) en diskussion av dessa problem i relation till andra studier i området, (c) en systematisk litteraturstudie som ger en översikt över relevanta publikationer i området, (d) en analys av bevisen som insamlats genom litteraturstudien, samt (e) en modell av det organisatoriska och tekniska system som måste hanteras för att man skall nå framgång med ett testautomatiseringsprojekt. Resultaten tyder på att rent tekniska problem inte utgör huvuddelen av de problem som upplevs med testautomatisering. Istället handlar det till stora delar om organisationell dynamik: hantering av förändringen det innebär att införa automatisering, planering av automatisering och dess användning, samt vilka finansiella förväntningar man har på automatiseringen.<br>ITS-EASY Post Graduate School for Embedded Software and Systems
22
Johansson, Henrik. "Performance characterization and evaluation of parallel PDE solvers." Licentiate thesis, Uppsala : Department of Information Technology, Uppsala University, 2006. http://www.it.uu.se/research/publications/lic/2006-010/2006-010.pdf.
Full text
23
Varanovich, Andrei [Verfasser], Ralf [Akademischer Betreuer] Lämmel, Colin [Gutachter] Atkinson, and Alfonso [Gutachter] Pierantonio. "Software chrestomathy as a knowledge-driven research infrastructure for software engineering / Andrei Varanovich ; Gutachter: Colin Atkinson, Alfonso Pierantonio ; Betreuer: Ralf Lämmel." Koblenz, 2018. http://d-nb.info/115070473X/34.
Full text
24
Turer, Oncel Umut. "A Web-based Database For Experimental Structural Engineering Research." Master's thesis, METU, 2010. http://etd.lib.metu.edu.tr/upload/12611811/index.pdf.
Full textAbstract:
This study presents a web-based database application for storing experimental data and related documents at a single location and sharing them among researchers and engineers from all over the world. The database application, accessible from a website was developed for experimental structural engineering researches, and initially tested at Structural and Earthquake Engineering Laboratory of Civil Engineering Department, METU. The application is composed of two parts. The first part is the database that stores information about projects, specimens, experiments, experimental data, documentation, site members, and member groups at the server side. The second part is the website that provides a functional user interface for easy use of application and providing accessibility from everywhere via internet. After the development of the database and the website, these two parts were attached to each other and application functionalities that enabled users to create, modify, search, and delete projects, specimens and experiments<br>allowed users to upload/download documentation and experimental data<br>provided abilities to users to plot test data and share their opinions were ensured. ASP.NET framework and C# programming language was utilized for the web application development. Functionality and usability of the database application was then tested by uploading and sharing various experimental results.
25
Choi, Jongsup 1956. "A software laboratory and comparative study of computational methods for Markov decision processes." Diss., The University of Arizona, 1996. http://hdl.handle.net/10150/290578.
Full textAbstract:
Dynamic programming (DP) is one of the most important mathematical programming methods. However, a major limitation in the practical application of DP methods to stochastic decision and control problems has been the explosive computational burden. Significant amounts of research have been focused on improving the speed of convergence and allowing for larger state and action spaces. The principal methods and algorithms of DP are surveyed in this dissertation. The rank-one correction method for value iteration (ROC) recently proposed by Bertsekas was designed to increase the speed of convergence. In this dissertation we have extended the ROC method proposed by Bertsekas to problems with multiple policies. This method is particularly well-suited to systems with substochastic matrices, e.g., those arising in shortest path problems. In order to test, verify, and compare different computational methods we developed a FORTRAN software laboratory for Stochastic s (YS)tems (CO)ntrol and (DE)cision algorithms for discrete time, finite Markov decision processes (SYSCODE). This is a user-friendly, interactive software laboratory. SYSCODE provides the user with a choice of 39 combinations of DP algorithms for testing and 1 comparison. SYSCODE has also been endowed with sophisticated capabilities for random problem data generation. We present a comprehensive computational comparison of many of the algorithms provided by SYSCODE using well-known test problems as well as randomly generated problem data.
26
Penmetsa, Sneha, and Navya Lingampalli. "An Empirical Analysis of the Usageand Impact of RequirementsAttributes on RequirementsEngineering Research and Practice : A mixed method approach." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-13352.
Full textAbstract:
Context: Requirement Engineering (RE) is one of the important phases inthe development of any software. Hence, there is a need to take much careon the elicitation and management of these requirements. Attributes playan important role in order to store and manage the important informationabout the requirements. There has been a lot of research performed inthe literature regarding the attributes of requirements engineering, but stillthere is a gap in the research that is concerned to requirement attributesin particular. Hence we focused more on identification and management ofthese requirement attributes. Objectives: In the current thesis, we focused mainly on the requirementattributes used in the companies and how they are managed. The majorobjectives we have framed in order to achieve our aim are: 1. To identify the publication trends in the literature of requirementsengineering that mainly focus on requirement attributes. 2. To identify the requirement attributes that are used by the softwarecompanies which includes both global attributes and project specificattributes. 3. To investigate how the requirement engineering models impact theselection of requirement attributes in companies. 4. To identify the phase and sequence of the requirement attributesbased on the four phases (elicitation, analysis, documentation and validation)of requirements engineering. 5. To investigate how the requirement attributes help in documentingand managing the continuous changes to requirements. Methods: In this thesis, we have performed Systematic Mapping Study(SMS),Systematic Literature Review (SLR) and Survey methods in order to achieveour aim and objectives. SLR is performed through the snowballing procedurebased on the guidelines of Wohlin[1].SMS is performed based on theguidelines of petersen et al.[2]. The main aim of the SMS is to identifythe publication trends in the literature on requirements engineering. Themain aim of SLR is to extract important information about the RE modelsand changes in requirements engineering. The main aim of the Survey is tovalidate the information retrieved from the SLR. Results: 83 requirement attributes were identified through the SLR outof which 15 attributes are in common. These 15 attributes are includedin the survey questionnaire. From these attributes, ID and description areidentified as most commonly used attributes from the survey. Publication trends related to requirement attributes are observed from the past 25 yearsrequirement attributes. From the survey, it is observed that there is a highimpact of RE models on requirement attributes. It is also observed thatmaximum number of attributes is stored in the form of documents and indatabases by the companies and the attributes are generally documented inanalysis phase and in specification phase. Results from the survey indicatedthat there is no particular sequence to document the attributes and theyare identified and documented based on the needs. Conclusions: This thesis lists different attributes that are used by thecompanies and also gives important information about the requirement attributesin detail that is close to the practical scenarios. It also gives scopefor further researches related to requirement attributes. This thesis helpthe practitioners to know the importance of consideration of requirementattributes in developing a project and its advantages. This work can beextended further by considering large number of attributes and retrievingresponses and opinions by large population.
27
Gopagoni, Naveen Kumar, and Sri Ranganath Reddy Sabbella. "Misalignment of Stakeholder Objectives In Software start-ups : A Qualitative research based on Software start-ups in India." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-20154.
Full textAbstract:
Context: Misalignment of stakeholder objectives generally takes place in any of the software company irrespective of the small, middle, large scale companies if the misalignment takes place then the goal the project doesn't reach and the objective changes. These misalignment's lead to project failure. Failures of the project in start-ups company some times lead to the shutdown of a company permanently. Minimizing the misalignment in a company means to avoid the risk. Mostly it is more critical for the software start-ups. Objectives: The main aim of our research is to know the factors responsible for the misalignment of the stakeholder objectives in software start-ups along with the significant challenges and possible solutions. Methods: In this qualitative research, we conducted the semi-structured interviews from the twelve start-up companies and collected the data for the research questions. The collected information is then thematically analyzed. We referred to many articles from the google scholar to find the significant challenges responsible for the misalignment of the stakeholder objectives. Results: The main findings in our research are as follows RQ1 external sponsor with his focus on return on investment discussed by the ten out of twelve software start-ups. In the twelve companies, ten companies are dependent on the external sponsor. Human factor and the requirements prioritization are the factors discussed by the six and five interviewees of the start-up companies. The remote working, last-minute change of requirements, deadlines are discussed by two interviewees. The one interviewee discusses the technology factor. In the findings from RQ2, we observed that the challenges related to the humans, return on investment, the external sponsor is more dominant compared to others factors like technology factor, deadlines, remote working, a last-minute change of requirements. In the findings of RQ3, about the possible solutions for the challenges with the misalignment of stakeholder objectives. Conclusions: The results of this study may help the furthers researchers who can research on the misalignment of the stakeholder objectives in software start-ups. These solutions may help the software industry people to minimise the general challenges in future in a better way. This results also may use for the people who want to start a software start-up so that they can know the factors, challenges, solutions of the misalignment of the stakeholder objectives in software start-ups.
28
White, Maurice Walter. "Verification and evaluation of structural analysis and design software." Thesis, Virginia Tech, 1991. http://hdl.handle.net/10919/41489.
Full text
29
Eden, Grace. "The contextual evaluation framework : a prototype evaluation technique for e-Research." Thesis, University of Oxford, 2011. http://ora.ox.ac.uk/objects/uuid:e816cf1a-3514-400c-9f2f-e022b56710d9.
Full textAbstract:
The contextual evaluation framework (CEF) is a requirements engineering technique that incorporates a particular sociological orientation, Ethnomethodology, in the development of a rigorous and systematic approach for requirements elicitation. This qualitative approach examines how well a system may be aligned with the endogenous organisation of work within a community of practice. Assessing how well a system supports the knowledge, skills and practices that already exist within a community is equally as important as developing solutions that will eventually reconfigure those practices, create new ones and extend modes of collaboration. The aim of this thesis is to address the absence of a systematic approach to quasi-naturalistic prototype evaluation which may be useful to a broader community such as requirements engineers, computer scientists and others not familiar with the details of sociological approaches. Such an aim is in line with the ways in which prototype evaluation approaches, particularly in HCI, have successfully been disseminated throughout the computer science research community - with the provision of guidelines. Likewise, the CEF is conceived of to be implemented in a similar manner. Its focus is on the analysis of a prototype’s relevance as a tool that is in some manner familiar to those who might use it. Specifically, professionals within a discipline share complex skills and knowledge where they learn to use similar tools, instruments and processes necessary for their work. Implicit in these social practices, practitioners gradually acquire the knowledge and skills necessary to become full members of a community of practice. In this way, the processes, objects and artefacts of practice come to possess specific meaning and significance. The CEF examines how this complex architecture of meaning is supported, constrained or transformed when using a prototype and makes possible an assessment of the ways in which participants interpret its usefulness and usability.
30
Thalanki, Pavan Kumar, and Vinay Kiran Maddukuri. "Classifying Research on UML model Inconsistencies with Systematic Mapping." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-2628.
Full textAbstract:
Context: Unified Modeling Language (UML) is a universal and standard modeling language that has been extensively used in software development process. Due to overlap and synchronous nature among different modeling artefacts in UML, several consistency issues have been identified in many software development projects that may lead to project failure. To reduce the level of such threat, over the past decade, a substantial research addressing those problems has been done both in academic and industry. This study is intended to investigate the reported research and to provide a systematic picture on different researched aspects of UML model inconsistencies, using the systematic mapping method. Objectives: The overall goal was to be achieved by fulfilling the following two main objectives: elaborating a proper and justified tool for performing the mapping and later used the tool in order to obtain a systematic and multidimensional picture of the approaches and the performed research in the area relating to different issues considering inconsistencies when using UML in software development. Research Methods: In order to ensure quality of the final foreseen systematic picture of the conducted research, a considerable effort was put first on a preparation of the tool that was used to obtain the mapping. The tool was a rigorous process based on classification methods and mapping guidelines obtained from a systematic literature review on the systematic mapping in software engineering. Then the tool was applied in a systematic way to obtain a number of mappings, followed by the analysis of the obtained results. Results: The systematic literature review resulted in identifying 5 mapping guidelines, 21 classifications, and 2 categorization methods. After analysis of them, a justified mapping process was developed by selecting standard guidelines, appropriate classifications and categorization methods. The mapping process applied for the period of 1999-2012 revealed 198 relevant studies developed by 321 researchers. On the basis this evidences, a number of mappings illustrating the conducted research on UML model inconsistencies ware obtained. The mapping reviled that the published research is mostly focused on rather formal issues such as semantic, syntactic, intramodel, inter-model and evolution problems, while a less attention is placed on more practical on time, and security problems. When the quality of research is concerned, 38% of papers proposed solutions as well as validated them through academic, industry or both, 35% of papers proposed only solutions. When the usage of empirical methods is considered, case studies are most frequently used (in almost half of the relevant papers) and followed by experiments (reported in 15% of papers), while 25% carried works do on report a systematic method used. Conclusions: The findings of systematic mapping study revealed that there are some aspect related to consistency such as time and security that are not given big attention. Identification and in-depth studying of inconsistencies in UML designs along with their dependencies are also missing. Most of the investigations are also academic with no evidence whether these reports produce interest for industry or not. State-of-the-art followed by state-of-the-practice studies related to consistency checking techniques and validating them in real industrial setting could be recommended.<br>Context: Unified Modeling Language (UML) is a universal and standard modeling language that has been extensively used in software development process. Due to overlap and synchronous nature among different modeling artefacts in UML, several consistency issues have been identified in many software development projects that may lead to project failure. To reduce the level of such threat, over the past decade, a substantial research addressing those problems has been done both in academic and industry. This study is intended to investigate the reported research and to provide a systematic picture on different researched aspects of UML model inconsistencies, using the systematic mapping method. Objectives: The overall goal was to be achieved by fulfilling the following two main objectives: elaborating a proper and justified tool for performing the mapping and later used the tool in order to obtain a systematic and multidimensional picture of the approaches and the performed research in the area relating to different issues considering inconsistencies when using UML in software development. Research Methods: In order to ensure quality of the final foreseen systematic picture of the conducted research, a considerable effort was put first on a preparation of the tool that was used to obtain the mapping. The tool was a rigorous process based on classification methods and mapping guidelines obtained from a systematic literature review on the systematic mapping in software engineering. Then the tool was applied in a systematic way to obtain a number of mappings, followed by the analysis of the obtained results. Results: The systematic literature review resulted in identifying 5 mapping guidelines, 21 classifications, and 2 categorization methods. After analysis of them, a justified mapping process was developed by selecting standard guidelines, appropriate classifications and categorization methods. The mapping process applied for the period of 1999-2012 revealed 198 relevant studies developed by 321 researchers. On the basis this evidences, a number of mappings illustrating the conducted research on UML model inconsistencies ware obtained. The mapping reviled that the published research is mostly focused on rather formal issues such as semantic, syntactic, intramodel, inter-model and evolution problems, while a less attention is placed on more practical on time, and security problems. When the quality of research is concerned, 38% of papers proposed solutions as well as validated them through academic, industry or both, 35% of papers proposed only solutions. When the usage of empirical methods is considered, case studies are most frequently used (in almost half of the relevant papers) and followed by experiments (reported in 15% of papers), while 25% carried works do on report a systematic method used. Conclusions: The findings of systematic mapping study revealed that there are some aspect related to consistency such as time and security that are not given big attention. Identification and in-depth studying of inconsistencies in UML designs along with their dependencies are also missing. Most of the investigations are also academic with no evidence whether these reports produce interest for industry or not. State-of-the-art followed by state-of-the-practice studies related to consistency checking techniques and validating them in real industrial setting could be recommended.
31
Nasir, Nayla. "Acceptance Testing in Agile Software Development - Perspectives from Research and Practice." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-21141.
Full textAbstract:
Context: Acceptance testing is an important activity that verifies the conformance of a system to its acceptance criteria. It aims to provide a detailed communication of domain knowledge and is used to evaluate whether the customer requirements are met. Existing literature lacks empirical evidence for acceptance testing. Especially in the context of industry practice, it is not in the authors' consideration, except for a few studies, where the authors have investigated the state of practice in a specific domain. Objective: This study aims to recognize the state of research and practice of acceptance testing in Agile Software Development and investigate the similarities and differences in both perspectives. The study contributes to identify the industry-academia gap in the context of acceptance testing. Research Method: To identify the acceptance testing practices and challenges from research, I have conducted a literature review. For the industry perspective on acceptance testing practices and challenges, I have conducted an interview-based survey of the practitioners working in the Agile Software Development environment. I followed the snowball search strategy to search the primary studies, whereas to select the respondents, I used the convenience and snowball sampling method. For data analysis, I followed the approach of thematic synthesis. Results: The results of this thesis are the outcome of a literature review of 20 selected studies and an interview-based survey with 12 practitioners representing10 companies. I identified acceptance testing practices and challenges from research and industry. In the research, the most recommended form of acceptance testing is acceptance test-driven development (ATDD), and the majority of the studies are referring to the use of FIT for acceptance testing. Customer involvement in different phases of acceptance testing is recommended in research. From the interviews, I come across that acceptance testing is manual at large in the industry, and the most challenging aspect is the customer’s involvement. Conclusions: From the findings of this thesis, it is concluded that there is a gap between the research and industry perspective of acceptance testing practices. Currently, acceptance testing in the industry is mostly manual, the research is not focusing on this aspect of acceptance testing. Despite the differences, there are some commonalities as well. Especially, most challenges of acceptance testing are similar in both perspectives. Researchers have to consider the commonalities, and they have to look at how they can minimize the acceptance testing challenges from the perspective of the industry.
32
Khan, Kashif. "A Systematic Review of Software Requirements Prioritization." Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2006. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-4779.
Full textAbstract:
Software engineering research has been, and still is criticised as being immature and unscientific due to lack of evaluation. However, software engineering community is now focusing more on empirical research and there is a movement to adopt approaches from other mature fields like medical science and one such approach is Systematic Reviews. One of the major activities within the requirements engineering process is to use requirements prioritization that helps to focus on the most important requirements. There are many prioritization techniques available to prioritize software requirements; still there is lack of evidence of which technique to prefer. The reasons could be the differences in contexts, measurement of variables and usage of data sets. In this thesis, the area of requirements prioritization has been systematically reviewed in order to assess what evidence regarding different prioritisation techniques exist. The results from different studies are contradictory in nature due to variations in study designs, research methodologies and choice of different dependent and context variables. Based on the results of the systematic review, a research framework has been proposed to provide the researchers with a common background for further research with in requirements prioritization area. The goal of the framework is to develop reliable knowledge base as well as help researchers conduct and report prioritization studies.
33
Mefford, Greg. "Side Channel Analysis Research Framework (SCARF)." University of Cincinnati / OhioLINK, 2012. http://rave.ohiolink.edu/etdc/view?acc_num=ucin1342463791.
Full text
34
Vũ, John Huân. "Software Internationalization: A Framework Validated Against Industry Requirements for Computer Science and Software Engineering Programs." DigitalCommons@CalPoly, 2010. https://digitalcommons.calpoly.edu/theses/248.
Full textAbstract:
View John Huân Vũ's thesis presentation at http://youtu.be/y3bzNmkTr-c.
In 2001, the ACM and IEEE Computing Curriculum stated that it was necessary to address "the need to develop implementation models that are international in scope and could be practiced in universities around the world." With increasing connectivity through the internet, the move towards a global economy and growing use of technology places software internationalization as a more important concern for developers. However, there has been a "clear shortage in terms of numbers of trained persons applying for entry-level positions" in this area. Eric Brechner, Director of Microsoft Development Training, suggested five new courses to add to the computer science curriculum due to the growing "gap between what college graduates in any field are taught and what they need to know to work in industry." He concludes that "globalization and accessibility should be part of any course of introductory programming," stating:
A course on globalization and accessibility is long overdue on college campuses. It is embarrassing to take graduates from a college with a diverse student population and have to teach them how to write software for a diverse set of customers. This should be part of introductory software development. Anything less is insulting to students, their family, and the peoples of the world.
There is very little research into how the subject of software internationalization should be taught to meet the major requirements of the industry. The research question of the thesis is thus, "Is there a framework for software internationalization that has been validated against industry requirements?" The answer is no. The framework "would promote communication between academia and industry ... that could serve as a common reference point in discussions." Since no such framework for software internationalization currently exists, one will be developed here. The contribution of this thesis includes a provisional framework to prepare graduates to internationalize software and a validation of the framework against industry requirements. The requirement of this framework is to provide a portable and standardized set of requirements for computer science and software engineering programs to teach future graduates.
35
Kahlström, Joakim, and Johan Hedlin. "Automating software installation for cyber security research and testing public exploits in CRATE." Thesis, Linköpings universitet, Databas och informationsteknik, 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-177401.
Full textAbstract:
As cyber attacks are an ever-increasing threat to many organizations, the need for controlled environments where cyber security defenses can be tested against real-world attacks is increasing. These environments, called cyber ranges, exist across the world for both military and academic purposes of various scales. As the function of a cyber range involves having a set of computers, virtual or physical, that can be configured to replicate a corporate network or an industrial control system, having an automated method of configuring these can streamline the process of performing different exercises. This thesis aims to provide a proof of concept of how the installation of software with known vulnerabilities can be performed and examines if the software is vulnerable directly after installation. The Cyber Range And Training Environment (CRATE) developed by the Swedish Defence Research Agency (FOI) is used as a testbed for the installations and FOI-provided tools are used for launching automated attacks against the installed software. The results show that installations can be performed without Internet access and with minimal network traffic being generated and that our solution can rewrite existing software packages from the package manager Chocolatey to work with an on-premises repository with an 85% success rate. It is also shown that very few publicly available exploits succeed without any manual configuration of either the exploit or the targeted software. Our work contributes to making it easier to set up environments where cyber security research and training can be conducted by simplifying the process of installing vulnerable applications.
36
Seifvand, Atiyeh. "Between Innovation and Governance : The Case of Research-based Software Development in a Large Petroleum Company." Thesis, Norges teknisk-naturvitenskapelige universitet, Institutt for datateknikk og informasjonsvitenskap, 2012. http://urn.kb.se/resolve?urn=urn:nbn:no:ntnu:diva-19425.
Full textAbstract:
Software innovations can offer organizations with competitive advantages. Research and development entities within the petroleum industry therefore seek to utilize IT capabilities to produce innovative software. Many factors may influence the success or failure of developing and implementing research-based software innovations in organizations. Of these issues the relation between software innovation and IT governance remains largely unexplored in the research literature.This study explores the effects IT governance has on the success or failure of research-based software development projects in an international petroleum company through an interpretive case study. The results of the study are twofold: 1) practical and 2) theoretical.The practical results show that the investigated petroleum company's emphasis on formalization has unfortunate side-effects on successful development and implementation of research-based software in the organization. IT governance, focused on stability of operations, is not well aligned with the corporate strategy of increased innovation. Moreover, the central IT department uses governance structures to guard the boundaries around the department.The theoretical results from the study presented that the impact of IS innovation or digital technology innovation on the research projects and how they can help the researchers to realize their ideas, remain unnoticed in the literature. Furthermore, In IS innovation literature, the organizations’ IS unit is the main responsible for IS innovation and it starts the innovation. However in the presented study R&D department had the main responsibility in innovation and it initiates innovation.
37
Rahim, Humaira. "Athena: An online proposal development system." CSUSB ScholarWorks, 2005. https://scholarworks.lib.csusb.edu/etd-project/2856.
Full textAbstract:
Athena - Online Proposal Development System was the first version of a vision of Dr. Richard Botting, Professor, Department of Computer Science at California State University, San Bernardino. The program, a JSP based system incorporating a MySql database, moves the writing, review, and annotation of project proposals into the digital environment. It allows Computer Science Master's students to provide their project proposals online for review and annotation by the committee members.
38
Andersson, Oskar. "Simulations in 3D research : Can Unity3D be used to simulate a 3D display system?" Thesis, Mittuniversitetet, Avdelningen för informations- och kommunikationssystem, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:miun:diva-28044.
Full textAbstract:
Mid Sweden University is currently researching how to capture more of a scene with a camera and how to create 3D images that does not require extra equipment for the viewer. In the process of this research they have started looking into simulating some of the tests that they wish to conduct. The goal of this project is to research whether the 3D graphics engine Unity3D could be used to simulate these tests, and to what degree. To test this a simulation was designed and implemented. The simulation used a split display system where each camera is directly connected to a part of the screen and using the position of the viewer the correct part of the camera feed is shown. Some literary studies were also done into how current 3D technology works. The simulation was successfully implemented and shows that simple simulation can be done in Unity3D, however, some problems were encountered in the process. The conclusion of the project show that there is much work left before simulation is viable but that there is potential in the technology and that the research team should continue to investigate it.
39
Smaill, Christopher Raymond. "Online Assessment System with Integrated Study (OASIS) to enhance the learning of Electrical Engineering students: an action research study." Thesis, Curtin University, 2006. http://hdl.handle.net/20.500.11937/751.
Full textAbstract:
World-wide, there has been a large increase in tertiary student numbers, not entirely matched by funding increases. Consequently, instructors are faced with large, diverse classes, and find themselves struggling to provide adequate assessment and prompt feedback, two quantities critical in an effective learning environment. Personal computers and the Internet can help solve this problem. The aim of this study was to develop, implement and validate a Web-based software package that, through providing practice and assessment opportunities, improved student learning and reduced marking and related mundane aspects of instructor workload. At the start of the study, such a package already existed in prototype form: OASIS (Online Assessment System with Integrated Study). As the study progressed, this software package was first fully rewritten and then repeatedly modified. OASIS delivers individualised tasks, marks student responses, supplies prompt feedback, and logs student activity. Staff can deliver sets of practice questions and assessments to students: assessments may involve different questions for different students, not just numerically different versions of the same questions. Given my role as teacher, the traditional research ideal of observing without affecting the research environment was both impossible and unconscionable. In particular, since preliminary evidence suggested that OASIS did enhance student learning, I could not adopt a ‘two groups’ approach to the research, with one group using OASIS while the other did not. Instead, an action research methodology was seen as most appropriate for my double role of teacher and researcher.This methodology enabled me, in the light of my findings, to continuously modify the learning environment and enhance student learning. The action research proceeded through a spiral of one-semester cycles of planning, acting, observing and reflecting. To maximize rigour, the research ran through eight cycles over four years and involved considerable triangulation. OASIS itself collected much quantitative data. Further data were collected via interview, survey, email and informal discussion from three groups: current students, postgraduates and academics. My colleagues provided alternative perceptions and interpretations, as did Physics Department academics who were using OASIS, and an external academic who interviewed academics and investigated the implementation of OASIS. Perhaps surprisingly, academics had generally adopted OASIS to promote student learning rather than to decrease their own workloads. In some cases workloads were reduced; however, where OASIS assessments augmented rather than replaced existing traditional assessments, workloads actually went up slightly. All instructors who used OASIS reported enhanced student learning and wished to continue using it. Student surveys, interviews, focus-group discussions and informal feedback showed that students found the software easy to use and considered that it helped them improve their skills and understanding. OASIS questions were preferred over textbook questions. Students commonly requested OASIS to be available in more of their areas of study. In general students wanted hints or model answers though some argued against their provision.The majority of students were enthusiastic about the use of OASIS for practice, and activity logs revealed that they did use OASIS extensively. These logs also revealed the motivating power of assessments: typically half the online practice activity took place in the last 36 hours prior to assessments. Interviews provided further interesting insights into the ways different students approached their studies and assessments. However, students did voice concerns about the validity of OASIS assignments, noting their peers could rely on the efforts of others to score highly in these. A number of steps were carried out in an attempt to defuse these concerns, including: disabling OASIS practice during assignments, basing assignments on previously unseen questions, and providing different assignment questions to different students. While this study has achieved the goal of developing, implementing and validating OASIS, many future opportunities exist. OASIS may be used in schools as well as universities. Non-numerical questions, where answers may be somewhere between right and wrong, are possible. OASIS can also be used to deliver concept inventories to students to support research into concept acquisition and retention.
40
Ghazi, Ahmad Nauman. "Structuring Exploratory Testing through Test Charter Design and Decision Support." Doctoral thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-14121.
Full textAbstract:
Context: Exploratory testing (ET) is an approach to test software with a strong focus on personal skills and freedom of the tester. ET emphasises the simultaneous design and execution of tests with minimal test documentation. Test practitioners often claim that their choice to use ET as an important alternative to scripted testing is based on several benefits ET exhibits over the scripted testing. However, these claims lack empirical evidence as there is little research done in this area. Moreover, ET is usually considered an ad-hoc way of doing testing as everyone does it differently. There have been some attempts in past to provide structure to ET. Session based test management (SBTM) is an approach that attempts to provide some structure to ET and gives some basic guidelines to structuring the test sessions. However, these guidelines are still very abstract and are very open to individuals' interpretation. Objective: The main objective of this doctoral thesis is to support practitioners in their decisions about choosing exploratory versus scripted testing. Furthermore, it is also aimed to investigate the empirical evidence in support of ET and find ways to structure ET and classify different levels of exploration that drive the choices made by exploratory testers. Another objective of this thesis is to provide a decision support system to select levels of exploration in overall test process. Method: The findings presented in this thesis are obtained through a controlled experiment with participants from industry and academia, exploratory surveys, interviews and focus groups conducted at different companies including Ericsson AB, Sony Mobile Communications, Axis Communications AB and Softhouse Consulting Baltic AB. Results: Using the exploratory survey, we found three test techniques to be most relevant in context of testing software systems and in particular heterogeneous systems. The most frequently used technique mentioned by the practitioners is ET which is not a much researched topic. We also found many interesting claims about ET in grey literature produced by practitioners in the form of informal presentations and blogs but these claims lacked any empirical evidence. Therefore, a controlled experiment was conducted with students and industry practitioners to compare ET with scripted testing. The experiment results show that ET detects significantly more critical defects compared to scripted testing and is more time efficient. However, ET has its own limitations and there is not a single way to use it for testing. In order to provide structure to ET, we conducted a study where we propose checklists to support test charter design in ET. Furthermore, two more industrial focus group studies at four companies were conducted that resulted in a taxonomy of exploration levels in ET and a decision support method for selecting exploration levels in ET. Lastly, we investigated different problems that researchers face when conducting surveys in software engineering and have presented mitigation strategies for these problems. Conclusion: The taxonomy for levels of exploration in ET, proposed in this thesis, provided test practitioners at the companies a better understanding of the underlying concepts of ET and a way to structure their test charters. A number of influence factors elicited as part of this thesis also help them prioritise which level of exploration suits more to their testing in the context of their products. Furthermore, the decision support method provided the practitioners to reconsider their current test focus to test their products in a more effective way.
41
Senjaya, Rudy. "Web-based library for student projects/theses and faculty research papers." CSUSB ScholarWorks, 2007. https://scholarworks.lib.csusb.edu/etd-project/47.
Full textAbstract:
The purpose of this project is to make available a Web-based Library, a web application developed for the Department of Computer Science at CSUSB to manage student projects/theses and faculty papers. The project is designed in accordance with Model-View-Controller (MVC) design pattern using the Jakarta Struts framework and iBATIS Data Mapper framework from Apache Software Foundation, JavaServer Pages (JSP), and MySQL database.
42
Napier, Nannette. "Improving Practices in a Small Software Firm: An Ambidextrous Perspective." Digital Archive @ GSU, 2007. http://digitalarchive.gsu.edu/cis_diss/18.
Full textAbstract:
Despite documented best practices and specialized tools, software organizations struggle to deliver quality software that is on time, within budget, and meets customer requirements. Managers seeking improved software project outcomes face two dominant software paradigms which differ in their emphasis on upfront planning, customer collaboration, and product documentation: plan-driven and agile. Rather than promoting one approach over the other, this research advocates improving software management practices by developing the organization’s ambidextrous capability. Ambidextrous organizations have the ability to simultaneously succeed at two seemingly contradictory capabilities (e.g. discipline and agility) which leads to enhanced organizational performance. Overall, this study asks the question: How can an ambidextrous perspective facilitate improvement in software practices? Driven by this question, and based on a two year action research study at a small software firm, TelSoft, the objectives of this research are to: 1. Identify dualities involved in improving software practices 2. Design interventions based on these dualities to improve software practices 3. Explore the process of becoming an ambidextrous software organization The resulting dissertation consists of a summary and four papers that each identify and address particular dualities encountered during software process improvement. The first paper asserts that both process-driven and perception-driven inquiry should be used during assessment of software practices, presents a model that shows how this combination can occur, and demonstrates the use of this model at TelSoft. The second paper explicates two theories for understanding and resolving issues in requirements engineering practice – repeat-ability and response-ability – and argues for the need to negotiate between the two. The third paper identifies a tension between managing legacy and current processes and proposes a model for software process reengineering, a systematic process for leveraging legacy processes created during prior SPI efforts. Finally, the fourth paper applies the theoretical lens of ambidexterity to understand the overall change initiative in terms of the tension between alignment and adaptability. The study used a variety of data sources to diagnose software practices, including semi-structured interviews, software process documents, meeting interactions, and workshop discussions. Subsequently, we established, facilitated, and tracked focused improvement teams in the areas of customer relations, requirements management, quality assurance, project portfolio management, and process management. Furthermore, we created and trained two management teams with responsibility for ongoing management of SPI and project portfolio management respectively. We argue that these activities improved software practices at TelSoft and provided a stronger foundation for continuous improvement. Keywords: Ambidexterity, software process improvement (SPI), action research, requirements engineering assessment, action planning, software process reengineering, software management.
43
Oskarsson, Andreas. "Efficient transformation from general flow into a specific test case in an automated testing environment." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik och datavetenskap, 2003. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-3718.
Full textAbstract:
SIMON is an automated testing application developed by WM-Data Consulting in Växjö, Sweden. Previously the test cases, called BIFs, run by SIMON to test the applications under test has been written manually in a very time consuming manner offering no protection against errors in the structure or misspellings. This thesis investigates a replacement to the manual method when creating the BIFs; my own developed application called the BIF-Editor. The usage of the BIF-Editor guaranteed correct syntax and structure and made the creation of the BIFs faster, but did it increase the quality of the BIFs? So to evaluate the BIF-Editor, the quality regarding path coverage of BIFs manually created was compared with BIFs created during the same elapsed time using the BIF-Editor. This evaluation showed that the usage of the BIF-Editor increased the quality of the BIFs by making the creation safer, but primarily faster which enabled the user to produce more BIFs than previously possible resulting in a raised path cover.
44
Smaill, Christopher Raymond. "Online Assessment System with Integrated Study (OASIS) to enhance the learning of Electrical Engineering students: an action research study." Curtin University of Technology, Science and Mathematics Education Centre, 2006. http://espace.library.curtin.edu.au:80/R/?func=dbin-jump-full&object_id=16885.
Full textAbstract:
World-wide, there has been a large increase in tertiary student numbers, not entirely matched by funding increases. Consequently, instructors are faced with large, diverse classes, and find themselves struggling to provide adequate assessment and prompt feedback, two quantities critical in an effective learning environment. Personal computers and the Internet can help solve this problem. The aim of this study was to develop, implement and validate a Web-based software package that, through providing practice and assessment opportunities, improved student learning and reduced marking and related mundane aspects of instructor workload. At the start of the study, such a package already existed in prototype form: OASIS (Online Assessment System with Integrated Study). As the study progressed, this software package was first fully rewritten and then repeatedly modified. OASIS delivers individualised tasks, marks student responses, supplies prompt feedback, and logs student activity. Staff can deliver sets of practice questions and assessments to students: assessments may involve different questions for different students, not just numerically different versions of the same questions. Given my role as teacher, the traditional research ideal of observing without affecting the research environment was both impossible and unconscionable. In particular, since preliminary evidence suggested that OASIS did enhance student learning, I could not adopt a ‘two groups’ approach to the research, with one group using OASIS while the other did not. Instead, an action research methodology was seen as most appropriate for my double role of teacher and researcher.<br>This methodology enabled me, in the light of my findings, to continuously modify the learning environment and enhance student learning. The action research proceeded through a spiral of one-semester cycles of planning, acting, observing and reflecting. To maximize rigour, the research ran through eight cycles over four years and involved considerable triangulation. OASIS itself collected much quantitative data. Further data were collected via interview, survey, email and informal discussion from three groups: current students, postgraduates and academics. My colleagues provided alternative perceptions and interpretations, as did Physics Department academics who were using OASIS, and an external academic who interviewed academics and investigated the implementation of OASIS. Perhaps surprisingly, academics had generally adopted OASIS to promote student learning rather than to decrease their own workloads. In some cases workloads were reduced; however, where OASIS assessments augmented rather than replaced existing traditional assessments, workloads actually went up slightly. All instructors who used OASIS reported enhanced student learning and wished to continue using it. Student surveys, interviews, focus-group discussions and informal feedback showed that students found the software easy to use and considered that it helped them improve their skills and understanding. OASIS questions were preferred over textbook questions. Students commonly requested OASIS to be available in more of their areas of study. In general students wanted hints or model answers though some argued against their provision.<br>The majority of students were enthusiastic about the use of OASIS for practice, and activity logs revealed that they did use OASIS extensively. These logs also revealed the motivating power of assessments: typically half the online practice activity took place in the last 36 hours prior to assessments. Interviews provided further interesting insights into the ways different students approached their studies and assessments. However, students did voice concerns about the validity of OASIS assignments, noting their peers could rely on the efforts of others to score highly in these. A number of steps were carried out in an attempt to defuse these concerns, including: disabling OASIS practice during assignments, basing assignments on previously unseen questions, and providing different assignment questions to different students. While this study has achieved the goal of developing, implementing and validating OASIS, many future opportunities exist. OASIS may be used in schools as well as universities. Non-numerical questions, where answers may be somewhere between right and wrong, are possible. OASIS can also be used to deliver concept inventories to students to support research into concept acquisition and retention.
45
Mogili, Anusha, and Manoj Kumar Pallapu. "Evaluating the Effectiveness and Efficiency of Real Time Data Visualization : An Action Research Study." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-20638.
Full textAbstract:
Background. In today’s competitive world, dealing with real-time streaming data is a difficult task to be achieved by many organizations. The importance of real time streaming data is rapidly increasing in all software industries by passing time. For quick growth of the companies, the data should be analysed immediately as data will be changing in fraction of second. The huge data will be generated every day and it will lead to problems such as overload of resources, Performance delays etc.., Which in turn will impact behaviour of the system. Finding the problem area in real time is difficult task to achieve as the data changes every second. Dealing with detection of bottlenecks and making decisions to handle the problem area, based on the real time data has been slow over the past years. It is also complicated due to time and effort required for storing and analysing. Organizations are not intended to wait for decision making information up to weeks or months. Organizations need to make an timely-accurate decisions by detecting problem area, in real time to improve their business support systems behaviour and performance. One of the better solutions is through data visualization as an approach. The visualizations are developed and evaluated by using task based approach. The data is collected using interviews and paper survey, to obtain the effective and efficient visualization in detecting bottlenecks. Objectives. The main objective is to find the most effective and efficient data visualization technique for real time streaming data to detect potential bottlenecks. Methods. In this research study, an action research is opted to answer the objectives. We have used interviews and paper survey to collect data in the terms of performance time, accuracy rate and user preference. Data analysis is performed using the Statistical tests and Narrative analysis method. Results. The final results obtained are the effective and efficient visualization techniques based on less performance time, higher accuracy rate and better user preference. Conclusions. An effective and efficient visualization technique for detection of bottlenecks is obtained for real time streaming data. Different categories of tasks has been used to obtain accurate results.
46
Cooper, David. "Empirical investigations supporting an extensible, theoretical approach to understanding software inspections." Thesis, Curtin University, 2010. http://hdl.handle.net/20.500.11937/42.
Full textAbstract:
Empirical software engineering research has directed substantial effort towards understanding and improving software inspection, a defect detection method much less costly than testing. However, software inspection suffers from a lack of theory governing the process and its outcomes, leading to apparently contradictory experimental outcomes that cannot easily be reconciled. This theoretical uncertainty hinders efforts to effectively address delocalisation - the occurrence of related information in different artefacts, or parts of a software system. Delocalisation is a hurdle to software comprehension, an activity fundamental to inspection.A gap currently exists between the development of inspection strategies and theories of software comprehension, manifested in two ways. First, although some strategies seek to enhance an inspector's understanding of key parts of the software, they generally ignore variability between inspectors. A particular form of guidance or cognitive support given to one inspector may have a different effect when given to another. Second, while models of inspection cost effectiveness exist, they are not expressed in terms of factors that might be manipulated to improve inspection performance. It is not clear how far an inspector should go to address one particular concern in the software, before the benefits of doing so are outweighed by the risk of ignoring other concerns.This thesis first reports on an industry survey examining the current state of practice with respect to peer reviews. Two more qualitative studies were conducted to explore approaches inspectors might take to the comprehension of artefact interrelationships and the challenges posed by delocalisation. A controlled experiment is then presented to show how active guidance and inspector expertise affect the detection of individual defects.Using the results of these studies, a theoretical framework and model of inspection cost effectiveness are proposed in which the effects of experience, cognitive support and the reading technique can be used to predict the consequences of a given inspection strategy. A simulation of the model was conducted to compare several new and existing inspection strategies. Thus, the framework and model provide a basis upon which an appropriate inspection strategy can be developed, selected or refined for a given software project.The results of these investigations suggest several ways in which inspection practices might be improved, including through the additional use of tool support and selective use of active guidance under specific conditions. By instantiating and using the proposed inspection model, software development organisations can engineer optimally cost effective inspection strategies.
47
Tingström, Conrad, and Omar Zidan. "Do academia and industry agree? : A study on how cross-platform research aligns with the concerns of developers." Thesis, Jönköping University, JTH, Avdelningen för datateknik och informatik, 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:hj:diva-53944.
Full textAbstract:
The number of available mobile applications (or apps) as well as the usage of these are rapidly increasing. With this increase there naturally also follows an increased competitiveness in the app market, with developers needing to produce apps of high perceived quality in order to get return users and also needing to make their apps available to multiple different platforms and devices. With substantial platform and device fragmentation, this is often a difficult and costly task. While traditionally an app basically had to be build from scratch for each platform it needed to support, in later years alternative development techniques for what is called cross-platform development have emerged and seen a rapid increase in usage. Contrary to native development, cross-platform development aims to enable development of a single codebase that can then run on all platforms. The idea is that this would save development time and thereby cost. Academic literature was found to often evaluate and compare performance differences between apps developed with cross-platform frameworks and their natively developed counterparts. Typically, these studies reported several reoccurring drawbacks with cross-platform development, compared to native development. However, research within the field was found to be lacking in regard to developers’ experience in general, and specifically whether this focus on comparing performance and listing pros and cons was representative of the concerns of industry developers. This study aimed to begin filling this gap, byinvestigating the extent to which these developers were relating any drawbacks to cross-platform development as well as which these were. Also, the study sought to answer how big a part this awareness of drawbacks played in the decision when developers chose to develop natively instead of cross-platform. With this, the goal of the study was ultimately to discussthe state of cross-platform research and whether it focused on aspects that were relevant to the industry. Data in this study was gathered in two ways: (1) a literature study, aiming to get an image of the current state of cross-platform research and (2) a web survey, in which app developers were invited through various groups in Facebook and Reddit. Ultimately, the results indicated that industry developers were to a large extent relating the same drawbacks to cross-platform development as were found to be frequently reported by academia. Further, all of the survey participants that related drawbacks to cross-platform development and ever chose to develop natively instead of cross-platform, did so to a very large degree because of those drawbacks. There were limitations to both the planning and the execution of the methods that were used, primarily in the gathering of data but also the analysis of this. However, it was still deemed possible to conclude that the results of the study indicated that research regarding cross-platform development could reasonably keep its current focus moving forward, as this appeared to be of high relevance to the industry.
48
Eliote, Yvssa Carneiro Desmots. "Implanta??o e an?lise do framework scrum no desenvolvimento da plataforma aberta Nosso Exerc?cio." UFVJM, 2018. http://acervo.ufvjm.edu.br/jspui/handle/1/1817.
Full textAbstract:
Submitted by Raniere Barreto (raniere.barros@ufvjm.edu.br) on 2018-10-26T19:47:13Z
No. of bitstreams: 2
license_rdf: 0 bytes, checksum: d41d8cd98f00b204e9800998ecf8427e (MD5)
yvssa_carneiro_desmots_eliote.pdf: 2710883 bytes, checksum: d37c2db27a339449a69986281db2966a (MD5)<br>Approved for entry into archive by Rodrigo Martins Cruz (rodrigo.cruz@ufvjm.edu.br) on 2018-11-10T11:13:46Z (GMT) No. of bitstreams: 2
license_rdf: 0 bytes, checksum: d41d8cd98f00b204e9800998ecf8427e (MD5)
yvssa_carneiro_desmots_eliote.pdf: 2710883 bytes, checksum: d37c2db27a339449a69986281db2966a (MD5)<br>Made available in DSpace on 2018-11-10T11:13:47Z (GMT). No. of bitstreams: 2
license_rdf: 0 bytes, checksum: d41d8cd98f00b204e9800998ecf8427e (MD5)
yvssa_carneiro_desmots_eliote.pdf: 2710883 bytes, checksum: d37c2db27a339449a69986281db2966a (MD5)
Previous issue date: 2018<br>Este estudo prop?e a implementa??o e an?lise do Framework Scrum no desenvolvimento de novas funcionalidade para o website Nosso Exerc?cio. Esta aplica??o web consiste em um dos projetos do Programa de Educa??o Tutorial, PET-UFVJM/Campus do Mucuri situada na cidade de Te?filo Otoni-MG e tem como finalidade o compartilhamento aberto de exerc?cios did?ticos de diversas ?reas do conhecimento. Por solicita??o de seus idealizadores, novas funcionalidades foram demandadas para o Nosso Exerc?cio, por?m, n?o existiam para este projeto metas claras nem um plano de trabalho a ser seguido, os requisitos n?o estavam formalizados e a equipe dispon?vel n?o estava madura nas tecnologias utilizadas. Levando-se
em considera??o o desafio enfrentado na gera??o de software de qualidade e o limite de tempo dispon?vel para a realiza??o desta pesquisa, foi proposto o uso de um processo da Engenharia de Software com intuito de se obter maior controle e qualidade do produto final a ser desenvolvido. O m?todo ?gil Scrum foi o escolhido para gerenciar as atividades de desenvolvimento para este software. Assim, o objetivo geral desta pesquisa consistiu em buscar uma resposta para a seguinte pergunta-problema: Quais benef?cios e/ou dificuldades podem ser obtidas atrav?s da aplica??o do Framework Scrum na evolu??o do desenvolvimento da plataforma aberta Nosso Exerc?cio? Seguindo o modelo sugerido por Coughlan e Coghlan (2002), o m?todo de pesquisa-a??o foi utilizado para descrever a din?mica conduzida durante este trabalho. A implanta??o do Scrum no Nosso Exerc?cio ocorreu em duas etapas, a primeira, visou realizar uma capacita??o sobre o Scrum e as ferramentas tecnol?gicas utilizadas no desenvolvimento do Nosso Exerc?cio. J? a segunda, tratou do desenvolvimento das funcionalidades para este website. A an?lise dos resultados mostrou v?rios benef?cios obtidos com a implanta??o do Scrum neste projeto, como: o foco e compromisso do Time durante o seu trabalho, o atendimento ?s reais necessidades do cliente (Product Owner), a flexibilidade
do framework em se ajustar ?s condi??es de ambiente e trabalho de cada Time criado; o aprendizado cont?nuo do software e do processo resultante das discuss?es feitas nas Reuni?es de Planejamento, Revis?o e Retrospectiva. O ponto cr?tico do trabalho deu-se sobre a imaturidade com as tecnologias utilizadas para o desenvolvimento do website. As li??es aprendidas com esta pesquisa indicam que ? poss?vel obter benef?cios com a implanta??o do framework Scrum que superem as suas dificuldades, desde que sejam feitas as devidas an?lises do ambiente em que o mesmo for adotado.<br>Disserta??o (Mestrado Profissional) ? Programa de P?s-Gradua??o em Tecnologia, Sa?de e Sociedade, Universidade Federal dos Vales do Jequitinhonha e Mucuri, 2018.<br>This study proposes na implementation and analysis of Scrum Framework in the development of new functionalities to ?Nosso Exerc?cio? (Our Exercise) website. This web application consists in one of the Tutorial Education Program Projects, PET-UFVJM/Mucuri Campus, located in Te?filo Otoni city, Minas Gerais state and it has as its objective the open share of teaching exercises of several knowledge areas. At the request of its creators, new functionalities were demanded to ?Nosso Exerc?cio? (Our Exercise), however, there were not clear goals for this project nor a work plan to be followed, the requirements were not formalised and the available team was not mature enough on the tecnologies applied. Considering the challenge faced on the generation of a good quality software and the time limit available for taking this research, the use of a software engineering was proposed aiming to get bigger quality control of the final Product to be developed. The agile method Scrum was the one chosen to manage the developing activities to this software. So, the general goal of this research consisted in searching for an answer to the following question-problem: Which benefits and/or difficulties can be obtained through the apllication of Scrum Framework on the evolution of the development of ?Nosso Exerc?cio? open plataforma? According to the model suggested by Coughlan and Coghlan (2002), the research-action method was used to describe a dinamic conducted during this work. The Scrum implantation on ?Nosso Exerc?cio? occurred in two stages, the first one, aimed to do a training about Scrum and the technological tools used in the development of ?Nosso Exerc?cio?. The second one, dealt with the development of functionalities to this website. The analyses of the results showed many benefits gotten with the implatation of Scrum in this project, like focus and commitment of ?Time? during its work, the attendance to the costumer?s real needs (Product Owner), the framework flexibility in adjusting to environment and work conditions of each ?Time? created, the continuous learning of the software and of the process resulting of the discussions taken on planning, reviewing and retrospecto meetings. The critical work point was about the immaturity with the technologies used for the website development. The learned lessons with this research indicate that it?s
possible to get benefits with the implantation of Scrum Framework which overcome the difficulties, as long as the needed analysis of the enviroment where it was adopted be done.
49
Svanberg, Daniel, and Fredrik Winkvist. "Usability concerns in GIS development for a wider user-base : A qualitative usability research in Swedish municipal infrastructure." Thesis, Blekinge Tekniska Högskola, Avdelningen för för interaktion och systemdesign, 2008. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-2269.
Full textAbstract:
We now live in a society where communicating is done mostly through computer-technology based mediums. In Swedish municipal infrastructure a lot of the communication-data consists of geospatial data-collections. This data is generated with Geographical Information Systems (GIS) which usage in Sweden has increased rapidly. This has lead to a competition between developers in designing their systems for a wider user-base. A transition between designs that has its focus on a small target group and designs intended for a wide range of different users puts the developers in a challenge where usability is one of the big concerns. In this thesis we, have adopted a qualitative research approach with contextual observations and usability testing, in order to identify the crucial usability concerns when designing GIS for a wider user-base. Results show that the most crucial usability concerns are related to system feedback and the GIS not being compatible with other GIS data formats. The research has been concentrated within municipalities in Sweden and results presented in this thesis are rough, but true indications. More research is needed to get detailed accuracy of the usability concerns. We hope that this thesis will aid developers of GIS in their design-phase and to be part of a foundation to future GIS-standards.
50
Faria, Daniel C. "VERIFICATION AND VALIDATION OF A SAFETY SYSTEM FOR A FUEL-CELL RESEARCH FACILITY: A CASE STUDY." Ohio : Ohio University, 2007. http://www.ohiolink.edu/etd/view.cgi?ohiou1180552564.
Full text