• Refine Query
  • Source
  • Publication year
  • to
  • Language
  • 36
  • 28
  • 5
  • 4
  • 3
  • 2
  • 2
  • 2
  • 1
  • 1
  • 1
  • Tagged with
  • 91
  • 91
  • 34
  • 33
  • 27
  • 18
  • 18
  • 15
  • 15
  • 15
  • 14
  • 12
  • 12
  • 11
  • 11
  • About
  • The Global ETD Search service is a free service for researchers to find electronic theses and dissertations. This service is provided by the Networked Digital Library of Theses and Dissertations.
    Our metadata is collected from universities around the world. If you manage a university/consortium/country archive and want to be added, details can be found on the NDLTD website.
31

A SOFTWARE DEVELOPMENT DOCUMENTATION INTERNSHIP WITH BLUESPRING SOFTWARE, INC

Waleszonia, Nicholas W. 21 April 2011 (has links)
No description available.
32

Merging Functional Requirements with Test Cases

Kolla, Madhuri, Banka, Mounika January 2015 (has links)
A lot of research is done in requirements engineering and testing but often the extensive literature is missing on defining good methods for linking functional requirements with test cases. Most of the delays occurring in the software development projects are because of incomplete or inaccurate functional requirements. The two main goals of our project are to achieve a successful software project by First, to design a template, which will merge functional requirements with test cases and second is to find the benefits of the aligning requirements to test cases. Changing, updating and tracing the requirements during the development of the project is not an easy task. The main reason for project failure is due to possibility of not fulfilling specified project requirements, so one way to solve this problem is to merge functional requirements with test cases. Thus removes the need of creating a separate requirements document, which will improve the traceability process between requirements and testing, thus leads to high quality and efficient development. The template helps us to drive a successful project by identifying the issues at an earlier stage of the development cycle.
33

How a remote software organization builds a shared understanding of NFRs

Okpara, Laura Onyinyechi 22 September 2022 (has links)
Building a shared understanding of non-functional requirements (NFRs) is a known but understudied challenge in requirements engineering, primarily in organizations that adopt continuous software engineering (CSE) practices. During the peak of the COVID-19 pandemic, many CSE organizations complied with working remotely due to the imposed health restrictions; some continued with remote work while implementing business processes to facilitate team communication and productivity. In remote CSE organizations, managing NFRs becomes more challenging due to the limitations to team communication coupled with the incentive to deliver products quickly. While previous research has identified the factors that lead to a lack of shared understanding of NFRs in CSE, we still have a significant gap in understanding how CSE organizations, particularly in remote work, build a shared understanding of NFRs in their software development. This thesis presents a study that explores how a remote CSE organization builds a shared understanding of NFRs. We conducted a six-month case study of a remote CSE organization using ethnography-informed methods and methods from grounded theory. Through thematic analysis of our qualitative data from interviews and observations, we identify some practices in building a shared understanding of NFRs, such as validating NFRs through feedback. In addition, we identified some of the impediments to building a shared understanding of NFRs in the organization, such as gaps in communication and the limited understanding of customer context. Furthermore, we conducted member-checking interviews to validate our findings for relevance and to gain additional insights on the shared understanding of NFRs within the organization. The collaborative workspace the organization uses for remote interaction is Gather, which simulates physical workspaces, and which our findings suggest allows for informal communications instrumental for building shared understanding. As actionable insights, we discuss our findings in light of proactive practices that represent opportunities for software organizations to invest in building a shared understanding of NFRs in their development. / Graduate
34

Functional Modelling of Systems with Multiple Operation Modes: Case Study on an Active Spoiler System

Yildirim, Unal, Campean, Felician 12 December 2021 (has links)
Yes / This article presents the application of the Enhanced Sequence Diagram (ESD) for the analysis of the functionality of a system with shape-changing aspects in the context of its multiple operational modes, considering an active rear spoiler as a case study. The article provides new insights on the ESD support for model-based capture and articulation of functional requirements across multiple operation modes of the same system, with appropriate detail on attributes and metrics, and the alignment of these attributes and metrics in line with the concept of time through scope lines. The article also provides a comprehensive argument and discussion, exemplified based on the case study, for the support that the ESD provides for early systems functional and architecture analysis, within the context of a broader model-based Failure Mode Analysis methodology.
35

Resource Description and Access (RDA): continuity in an ever-fluxing information age with reference to tertiary institutions in the Western Cape

van Rensburg, Rachel Janse January 2018 (has links)
Magister Library and Information Studies - MLIS / Although Resource Description and Access (RDA) has been discussed extensively amongst the ranks of cataloguers internationally, no research on the perceptions of South African cataloguers was available at the time of this research. The aim of this study was to determine how well RDA was faring during the study's timeframe, to give a detailed description regarding cataloguer perceptions within a higher education setting in South Africa. Furthermore, to determine whether the implementation of RDA has overcome most of the limitations that AACR2 had within a digital environment, to identify advantages and/or perceived limitations of RDA as well as to assist cataloguers to adopt and implement the new standard effectively. The study employed a qualitative research design assisted by a phenomenological philosophy to gain insight into how cataloguers experienced the implementation and adoption of RDA by means of two concurrent web-based questionnaires. The study concluded that higher education cataloguing professionals residing in the Western Cape were decidedly positive towards the new cataloguing standard. Although there were some initial reservations, they were overcome to such an extent that ultimately no real limitations were identified, and that RDA has indeed overcome most of the limitations displayed by AACR2. Many advantages of RDA were identified, and participants expressed excitement about the future capabilities of RDA as it continues toward a link-data milieu, making library metadata more easily available.
36

Resource Description and Access (RDA): continuity in an ever-fluxing information age with reference to tertiary institutions in the Western Cape.

Janse van Rensburg, Rachel January 2018 (has links)
Magister Library and Information Studies - MLIS / Although Resource Description and Access (RDA) has been discussed extensively amongst the ranks of cataloguers internationally, no research on the perceptions of South African cataloguers was available at the time of this research. The aim of this study was to determine how well RDA was faring during the study's timeframe, to give a detailed description regarding cataloguer perceptions within a higher education setting in South Africa. Furthermore, to determine whether the implementation of RDA has overcome most of the limitations that AACR2 had within a digital environment, to identify advantages and/or perceived limitations of RDA as well as to assist cataloguers to adopt and implement the new standard effectively. The study employed a qualitative research design assisted by a phenomenological philosophy to gain insight into how cataloguers experienced the implementation and adoption of RDA by means of two concurrent web-based questionnaires. The study concluded that higher education cataloguing professionals residing in the Western Cape were decidedly positive towards the new cataloguing standard. Although there were some initial reservations, they were overcome to such an extent that ultimately no real limitations were identified, and that RDA has indeed overcome most of the limitations displayed by AACR2. Many advantages of RDA were identified, and participants expressed excitement about the future capabilities of RDA as it continues toward a link-data milieu, making library metadata more easily available. As this research has revealed a distinctly positive attitude from cataloguers' two main matters for future research remains, being: ? Why South African participants in this study voiced almost no perceived limitations to RDA as a cataloguing standard. Future research might be able to relay information regarding this trend, especially in the light that it was not a global phenomenon. ? A deeper look might have to be taken at how participants' experienced RDA training as this phenomenon might be closely linked to the reasons why the participants did not mention more limitations.
37

Riktlinjer för begränsad gränssnittsdesign – Att designa gränssnitt med begränsningar i designarbetet / Guidelines for limited graphical user interface design – Designing user-interface with design work limitations

Karlsson, Mathias, Löverdal, Gea January 2016 (has links)
Gränssnittsdesign är en av de viktigaste aktiviteterna vid systemutveckling, eftersom gränssnittet utgör den beståndsdel för vilket slutanvändare kommer göra sin primära helhetsbedömning av systemet utefter. Det innebär att gränssnittsdesignarbetet har en avgörande roll för hur systemet kommer att mottas och bedömas vid leverans och upphandlingar av system. Att designa tillfredställande gränssnitt handlar om att ta hänsyn till en rad olika human computer interaction (HCI)-aspekter. Dessa är användbarhet, användarupplevelse samt estetik, det vill säga hur visuellt tilltalande gränssnittet är. Följande tre aspekter kommer på olika sätt påverka hur en användare upplever ett system, vilket i sin tur kommer påverka huruvida en beställare är beredd att investera i ett system. Att utveckla gränssnitt för system innebär ofta att designers och utvecklare måste göra avvägningar kring i vilken mån en designer skall få realisera gränssnittsdesign. Detta eftersom en samansättning av för många visuella gränssnittselement kan få inverkan på systemets prestanda. Stundtals hamnar de två elementen, visuella designattribut och systemkrav, i konflikt med varandra och i de fall där de senare föregår designattribut ställs gränssnittsdesigners inför en utmaning eftersom att de bli begränsade i sitt arbete. Trots detta ställs dock samma krav på att designers skall uppnå tilltalande gränssnitt som väcker känslor av professionalism, samtidigt som systemet skall bibehålla optimal systemprestanda och funktionalitet.Syftet med denna studie var att undersöka hur ett tillfredställande gränssnitt i aspekter av estetik, användbarhet och användarupplevelse kan designas i ett standardsystem när designarbete begränsas till att enbart kunna justera placering och färg av gränssnittselement. Detta har inneburit en designforskningsansats bestående av en iterativ utvecklingsprocess där ett gränssnitt designat och realiserat baserat på av teorin förslagna riktlinjer för gränssnittsdesign som fortfarande har varit möjliga att tillämpa trots designarbetets begränsningar. Gränssnittet har därefter utvärderats genom experiment i form av användbarhetstester och expertutvärdering. Empirisk data från utvärderingarna har därefter analyserats och införlivats i gränssnittet och slutligen har en slutsats genererats och presenterats.Studiens resultat visar att genom en kombination av befintliga teoribaserade riktlinjer kommer designers en god bit på väg för att lyckas design tillfredställande gränssnitt i aspekter av estetik, användbarhet och användarupplevelse. I slutet av studien presenteras detta i form av sju nya riktlinjer. Variabeln användarupplevelse visade sig dock vara svårare att designa för i studiens begränsade kontext. Detta beror på att användarupplevelse är en svår variabel att utvärdera på grund av dess subtila natur. Slutligen presenteras förslag för framtida forskning och på vilket sätt studiens resultat vidare bör beprövas. / User-Interface design is one of the most important aspects of development of a system, as the user-interface is one of the elements that the user primarily will take in consideration when assessing a system. This means that user-interface design plays an important role in how the system will be received and assessed at procurement. A designer has to consider a couple of human computer interaction (HCI)-aspects such as usability, user experience, and aesthetics, in order to design a satisfactory user-interface. These three aspects of human computer interaction affect user experience of a system, which will influence a client’s decision on investment in the system. Designing a user-interface of a system often means that designers and developers have to consider the extent to which a designer can implement their version of the interface. A composition of many visual interface elements can have an impact on the systems performance. Sometimes the visual design attributes can conflict with the system requirements. If designers are challenged system requirements are prioritised because they will be limited in their work. Despite those limitations, the designers are still needed to design an appealing user-interface that can invoke feelings of professionalism, parallel to the system requirement of optimal performance and functionality.The purpose of this study was to explore how an appealing user-interface with regards to aesthetics, usability and user experience can be designed when the design work is limited to only be able to adjust placement and visual appearance in terms of names and colour of UI elements. This has been explored by doing an iterative development process in which an interface has been designed and developed based on guidelines from theory on user-interface design which the authors has been able to implement based on the limitations on the design work. The interface has subsequently been evaluated by experiments in terms of usability tests and an expert evaluation in the form of a heuristic evaluation. The evaluations resulted in empirical data which has been analysed and set against existing theory upon which a conclusion has been generated and presented.The result of the study show that designers are well on the way to successfully design an appealing user-interface in relation to aesthetic, usability and user experience, which the authors presents in the form of seven new guidelines. The variable user experience turned out to be more difficult to design in the study’s limited context. The authors believe that one of the reasons for this is that user experience is difficult to evaluate because of its subtle nature. Lastly we present suggestions for future research and how the results of the study should be further proved.
38

Evolução de software baseada em avaliação de arquiteturas. / Software evolution based on architecture evaluation.

Pontes, Danielle Pompeu Noronha 16 March 2012 (has links)
Este trabalho discorre sobre o estudo da utilização do método de avaliação ATAM como referência para um roteiro para evolução arquitetural. O estudo apresentado está dividido em duas partes: a elaboração de um roteiro para evolução de software e a aplicação do roteiro em um ambiente real de um sistema para automação de linhas aéreas. O objetivo é avaliar o uso do método de avaliação de arquitetura para direcionar a evolução do software. As diretrizes geradas neste trabalho orientam as ações a serem tomadas com base em evidências obtidas pela avaliação, possibilitando ao software que exiba os atributos de qualidade desejados. / This paper discusses the study of the use of ATAM evaluation method as a reference to a roadmap for architectural evolution. The present study is divided into two parts: the preparation of a roadmap for software development and implementation of the roadmap in a real environment of a system for automation of airlines. The goal is to evaluate the use of architecture evaluation method to direct the evolution of software. The guidelines generated in this work have guided the actions to be taken based on evidence obtained by the evaluation, enabling the software that displays the desired quality attributes.
39

Evolução de software baseada em avaliação de arquiteturas. / Software evolution based on architecture evaluation.

Danielle Pompeu Noronha Pontes 16 March 2012 (has links)
Este trabalho discorre sobre o estudo da utilização do método de avaliação ATAM como referência para um roteiro para evolução arquitetural. O estudo apresentado está dividido em duas partes: a elaboração de um roteiro para evolução de software e a aplicação do roteiro em um ambiente real de um sistema para automação de linhas aéreas. O objetivo é avaliar o uso do método de avaliação de arquitetura para direcionar a evolução do software. As diretrizes geradas neste trabalho orientam as ações a serem tomadas com base em evidências obtidas pela avaliação, possibilitando ao software que exiba os atributos de qualidade desejados. / This paper discusses the study of the use of ATAM evaluation method as a reference to a roadmap for architectural evolution. The present study is divided into two parts: the preparation of a roadmap for software development and implementation of the roadmap in a real environment of a system for automation of airlines. The goal is to evaluate the use of architecture evaluation method to direct the evolution of software. The guidelines generated in this work have guided the actions to be taken based on evidence obtained by the evaluation, enabling the software that displays the desired quality attributes.
40

Framework para estimar requisitos não funcionais em aplicações móveis / A framework for non-functional requirements estimation in mobile applications

Fernandes, Thiago Soares January 2015 (has links)
O desenvolvimento de aplicações móveis é guiado por uma especial atenção aos requisitos não funcionais (do inglês, NFR - Non Functional Requirements), sendo o principal objetivo proporcionar uma boa experiência ao usuário final. Entretanto, a avaliação de NFRs é ainda uma tarefa manual, não estruturada e que consome muito tempo. Esta dissertação apresenta um estudo de várias abordagens relacionadas à avaliação de desempenho (por exemplo, o uso de aplicações de benchmark) e de NFRs no âmbito de sistemas móveis. No entanto, os benchmarks atuais são genéricos, geralmente, voltados para a plataforma de execução e nem sempre instituem um consenso na classificação de dispositivos. Visando uma melhor avaliação de NFRs e uma classificação de dispositivos com base nas necessidades de aplicações reais, este trabalho propõe um framework para gerar benchmarks orientados às necessidades de cada aplicação e, assim, fornecer uma forma eficiente e eficaz para estimar requisitos não funcionais em sistemas móveis. Essa ferramenta é composta por uma biblioteca de testes parametrizáveis, métricas e uma estrutura para geração rápida de benchmarks orientados à aplicação. O framework foi construído utilizando o paradigma de programação orientada a aspectos para coleta das métricas por fornecer uma maior modularidade e separação de interesses, de modo que a sua evolução, através da adição de outras métricas ou testes, seja facilitada. Para validação da proposta, foram realizados experimentos com cinco aplicações Android reais disponíveis na Play Store, sendo que para cada aplicação foi gerado um benchmark específico cujos resultados foram comparados com os obtidos para as aplicações móveis reais. Os resultados são promissores, mostrando que é possível criar aplicações de teste com comportamento semelhante ao de aplicações reais e, assim, classificar dispositivos com base nas necessidades das aplicações, através da análise das métricas presentes no framework. Essas métricas podem, ainda, orientar o desenvolvedor na otimização de suas aplicações ou ainda na escolha de dispositivos com melhor custo benefício para executar seus aplicativos. / The mobile application development is guided by a special attention to non-functional requirements (NFRs), where a good experience for the end user is the primary goal. However, NFRs evaluation is still a manual, unstructured and time-consuming task. This thesis presents a study of several approaches related to performance and NFR evaluation within mobile systems. Among these approaches is the use of benchmark applications. Currently available benchmarks are generic, usually focused on the execution platform and do not always establish a consensus on the classification of devices. For a better NFRs assessment and classification of devices based on real application needs, this work proposes a framework for generating application-oriented benchmarks for the early estimation of non-functional requirements in mobile systems. This framework is composed of a configurable test library, a set of metrics and an engine the assembling of the test program. The framework uses aspect-oriented programming to collect the metrics of interest. This approach provides increased modularity and separation of concerns, thus facilitating the improvement of the framework itself, by adding other metrics or testing operations. In order to validate the proposed framework we used five application from the Android Play store. For each application, a specific benchmark is generated and executed in different devices. The results are compared to those of the execution of the actual applications in the same devices. Experimental results are promising, showing that it is possible to create test applications with similar behavior to that of real applications and thus classify devices based on the actual application needs, by analyzing the metrics present in the framework. These metrics can also guide the developer in optimizing her applications or in choosing devices with the best trade-off between cost and performance to run a given application.

Page generated in 0.5049 seconds