This study aims to explore the decision-making criteria for requirements selection in market-driven software development projects in China. Requirements selection decisions are made by reconciling the conflicting stakeholders??? value propositions into a mutually-agreed set through the negotiation and communication process between stakeholders. Firstly, this study identified decision-making criteria according to different stakeholders??? value propositions, and then evaluated the importance of the criteria when making the decisions of requirements selection. Moreover, the study determined the degree to which the stakeholders from business, product, and project perspectives influence the decision-making process. Furthermore, the study explored the communication between major stakeholders in requirements selection process, as a foundation to support and guide the process. A Delphi survey was applied in this study. Opinions from experienced industrial experts were obtained to achieve reliable consensus among them on the criteria and relative importance of the criteria in requirements selection process. The Delphi survey in this study included four phases of data collection by a series of intensive questionnaires interspersed with controlled opinion feedback and follow-up interviews. 132 Experts from 11 companies were recruited by following the rigid procedure to ensure the validity and reliability of the research. The study indicated that criteria from the business perspective had a major influence on decision-making of requirements selection, while project- and product-perspective criteria were relatively lower in priority. However, there were some inconsistencies among the opinions of the recruited experts regarding the importance of the criteria. The inconsistencies may result from a number of different factors, for example; different software development projects; different size, culture, organizational structure or maturity level of the companies; or different working positions of the experts surveyed. In addition, the study found three different types of communication in requirements selection in the companies surveyed. Further, Chinese culture was believed to have effects on the communication process between stakeholders. While informal communication was highlighted in Chinese context, the Chinese culture of strictly hierarchical communication could lead to problems in the communication process. Further research is recommended to gain deeper insight into these issues.

Dissertation (Ph.D. in Software Engineering)--Naval Postgraduate School, March 2007.D / Dissertation supervisor: Berzins, Valdis. "March 2007." Description based on title screen as viewed on April 14, 2010. DTIC Descriptors: Software Engineering, Cognition, Learning Machines, Artificial Intelligence, Computer Programming, Simulation, Military Training, Vision, User Needs, Patterns, Employment, Command And Control Systems, Humans. DTIC Identifier(s): Software Engineering, Cognitive Systems, Machine Learning, Simulation, System Deployment, Artificial Intelligence, System Evaluation, Software Evaluation. Author(s) subject terms: Software Engineering, Cognitive Systems, Machine Learning, Simulation, System Deployment, Artificial Intelligence, System Evaluation, Software Evaluation. Includes bibliographical references (p. 395-399). Also available in print.

Submitted by Fernando Souza (fernandoafsou@gmail.com) on 2017-08-17T16:24:57Z No. of bitstreams: 1 arquivototal.pdf: 2693687 bytes, checksum: b83d46aca568cc0cd41d71706209817d (MD5) / Made available in DSpace on 2017-08-17T16:24:57Z (GMT). No. of bitstreams: 1 arquivototal.pdf: 2693687 bytes, checksum: b83d46aca568cc0cd41d71706209817d (MD5) Previous issue date: 2016-08-26 / Conselho Nacional de Pesquisa e Desenvolvimento Científico e Tecnológico - CNPq / Evaluation of Educational Software (ES) is important to identify the correct use of this tool as a facilitator of the teaching-learning process and also allows you to check the adequacy of the ES in accordance with the educational goals set by teachers; IF the correct operation according to the Software Engineering; the direction to the characteristics, needs and skills of its members, according to Engineering Usability. Therefore, the aim of this study was the analysis of 14 ES approaches to assessment in order to identify the coherence and comprehensiveness in relation to established models of classical literature for Software Quality (ISO 9126-1 and SWEBOK guide), Quality of Service (ISO 9241-1 and Heuristics Usability) and the. Precepts of Education. The process of knowledge appropriation of the approaches, was marked in the study of characterization of the same, from which it was possible to identify great heterogeneity of the adopted criteria, measurement instruments and diagnoses obtained. Thus, there was a comparison between the quality model in order to identify the intersection criteria for different models. As a result of the characterization of the 14 analyzed approaches and the intersection of the Software Quality Models, Use and Teaching, elaborated a dictionary of terms to map the criteria of each quality model, with those present in the ES assessment approaches considered in this study. It is expected that this tool will be useful to assist the actors involved in the ES evaluation process as it uses information taken and understood as a reference standard in the literature. / A avaliação de Softwares Educativos (SE) é importante para identificar a utilização correta desta ferramenta como facilitadora do processo de ensino-aprendizagem e, além disso, permite verificar a adequação do SE de acordo com os objetivos pedagógicos estabelecidos pelos professores; o correto funcionamento do SE de acordo com a Engenharia de Software e; o direcionamento para as características, necessidades e habilidades de seus usuários, segundo a Engenharia da Usabilidade. Portanto, o objetivo deste estudo foi realizar a análise de 14 abordagens para avaliação de SE, com o intuito de identificar a respectiva coerência e abrangência, em relação aos modelos consagrados da literatura clássica para a Qualidade de Software (Norma ISO 9126-1 e Swebok Guide), Qualidade de Uso (Norma ISO 9241-1 e Heurísticas de Usabilidade) e os Preceitos da Pedagogia. O processo de apropriação do conhecimento sobre as abordagens, pautou-se no estudo de caracterização das mesmas, a partir do qual foi possível identificar grande heterogeneidade dos critérios adotados, instrumentos de mensuração e diagnósticos obtidos. Dessa maneira, realizou-se uma comparação entre os modelos de qualidade, buscando identificar a intersecção entre critérios de modelos distintos. Como resultado da caracterização das 14 abordagens analisadas e da intersecção entre os modelos de Qualidade de Software, de Uso e Pedagógica, elaborou-se um dicionário de termos para mapear os critérios de cada modelo de qualidade, com aqueles presentes nas abordagens de avaliação de SE consideradas neste estudo. Espera-se que este instrumento seja útil para auxiliar os atores envolvidos no processo de avaliação de SE uma vez que se utiliza de informações adotadas e entendidas como padrão de referência na literatura.

Orientador: Ana Cervigni Guerra, Rogerio Drummond / Dissertação (mestrado profissional) - Universidade Estadual de Campinas, Instituto de Computação / Made available in DSpace on 2018-08-07T22:07:00Z (GMT). No. of bitstreams: 1 Silva_EduardodeVasconcelos_M.pdf: 694246 bytes, checksum: 7be11f3a0bafc2a11d2340ac3bdcdc26 (MD5) Previous issue date: 2006 / Resumo: A atividade da escrita de casos de testes para software é em sua essência não determinística e por conseguinte envolve riscos. Por outro lado, o grau de densidade de testes dos requisitos do sistema sofre influência da forma que esses requisitos são interpretados. Uma proposta para sistematizar o processo de criação de casos de teste encontra-se no uso de uma rede Bayesiana que modela a arquitetura de testes a ser implementada, aliada a uma ponderação estatística de riscos a cenários. A rede é muito adequada a problemas não determinísticos e que envolvam riscos. Aliada ao uso da rede Bayesiana, essa sistematização engloba o critério de adequação, cujo objetivo é minimizar o impacto da cobertura de requisitos. Cada requisito do sistema é interpretado segundo critérios pré definidos. Como produto final desta proposta sistêmica, além do ferramental gráfico que possibilita a descrição dos casos de testes segundo uma seqüência lógica e simulação de cenários, têm-se uma matriz que reúne todos os casos de testes obtidos da rede e demais oriundos da análise dos requisitos, segundo o enfoque do critério de adequação. O estudo experimental sinaliza um incremento de quatro vezes e meio na densidade de testes de requisitos comparativamente a técnica tradicional. Na fase de análise há uma tendência de redução de esforço em torno de um quarto. Um interessante resultado dessa técnica sistematizada, está na identificação de cenários não previstos pelos requisitos o que vem agregar na atualização da documentação de design / Abstract: The task of writing software use cases is in essence non deterministic and therefore involves risks. On the other hand, the coverage level of requirements depends the way of document requirements are interpreted.In order to bring a systematic approach in developing software use cases, the Bayesian network technique helps supporting with this problem. The current software test architecture is modeled in a graphical way, adding scenario simulation and risk statistic. The network addresses very well risks and non deterministic scenarios.Along with the Bayesian Network , the proposed systematic approach encompasses the adequacy criteria which main goal is to improve requirements coverage. Each system requirement is interpreted according to well defined criteria. A matrix will be the final product, as a result from the current systematic approach. All use cases obtained from the network and those discovered thanks of adequacy criteria can be seen together. In addition this, the technique allows scenarios simulation. The experimental results show an increase of four times and half in requirements coverage, as compared against the traditional technique. In the analysis phase , there is a trend of reducing the effort by a factor of 4.One interesting result using this technique is the amount of new scenarios identified. Most of them are not properly described in the requirement document. This brings a powerful tool to add value in updating the design document / Mestrado / Engenharia de Software / Mestre em Ciência da Computação

In der vorliegenden Arbeit wird die Evaluation einer neuen, softwarebasierten Volumetrie auf Basis von CT Datensätzen vorgestellt. Die experimentelle Studie findet vor dem Hintergrund der Kopf-Hals-Onkologie statt und basiert auf der zunehmend in den Vordergrund tretenden Evidenz des Tumorvolumens als prognostischer Marker für Patienten mit Kopf-, Halsmalignomen. Als eine der Methoden zur Volumetrie pathologischer Strukturen gilt die diameterbasierte Schätzung. Dem gegenüber steht die perimeterbasierte bzw. softwarebasierte Volumetrie. Diese ist zwar aufwändiger, hat jedoch den Vorteil bei irregulär begrenzten Strukturen wie beispielsweise Tumoren genauere Ergebnisse zu liefern. Ziel der Studie war es, die Genauigkeit und Grenzen der Volumetrie mittels dieser Methode zu bestimmen. Hierzu wurden Patienten, die für eine chirurgische Resektion und Neck Dissection im Rahmen ihres Kopf-Hals- Karzinoms vorgesehen waren, rekrutiert. Mehrere Lymphknoten wurden selektiert und mittels Software volumetriert. Im Anschluss an die Resektion wurden diese Lymphknoten nach dem archimedischen Prinzips vermessen. Die so gewonnenen realen Volumina wurden der perimeterbasierten und softwarebasierten Volumetrie gegenüber gestellt. Hierbei zeigte sich eine sehr gute Übereinstimmung der softwarebasierten mit den realen Volumina, wie der Pearson Korrelationskoeffizient (r=0.96) sowie die Bland-Altman Analyse zeigten. Weiterhin konnte ein minimaler Diameter von 0.95cm definiert werden, bis zu dem die softwarebasierte Volumetrie mit der momentan verfügbaren CT Bildgebung als verlässlich gelten kann.:BIBLIOGRAPHISCHE BESCHREIBUNG .....................................................3 I. EINLEITUNG.....................................................................................4 1.1 EPIDEMIOLOGIE UND ÄTIOLOGIE .................................................. 5 1.2 DIAGNOSTIK UND STAGING .......................................................... 7 1.3 THERAPIESTRATEGIEN ..................................................................9 1.4 PANENDOSKOPIE UND DOKUMENTATION ...................................... 11 1.5 ERSTELLUNG DER 3D KOPF-, HALSDATENSÄTZE MITTELS SEGMENTIERSOFTWARE .................................................................... 12 II. PUBLIKATION .............................................................................. 14 2.1 ABSTRACT ................................................................................ 16 2.2 INTRODUCTION ......................................................................... 17 2.3 METHODS.................................................................................. 18 2.4 RESULTS................................................................................... 21 2.5 DISCUSSION ............................................................................. 23 III. NICHT VERÖFFENTLICHTE DATEN ................................................. 25 3.1 EINLEITUNG .............................................................................. 26 3.2 METHODEN ............................................................................... 26 3.3 RESULTATE ............................................................................... 27 3.4 DISKUSSION .............................................................................. 31 IV. ZUSAMMENFASSUNG.....................................................................34 V. ANLAGEN .................................................................................... 35 5.1 BIBLIOGRAPHIE......................................................................... 38 5.2 ERKLÄRUNG ÜBER DIE EIGENSTÄNDIGE ABFASSUNG DER ARBEIT ... 46 5.3LEBENSLAUF............................................................................... 47 5.4 DANKSAGUNG ............................................................................ 55

Thesis (M. Tech. (Information Technology)) -- Central University of technology, Free State, 2013 / This study compared the usability of three Information and Communication Technology (ICT) network programs in a learning environment. The researcher wanted to establish which program was most adequate from a usability perspective among second-year Information Technology (IT) students at the Central University of Technology (CUT), Free State. The Software Usability Measurement Inventory (SUMI) testing technique can measure software quality from a user perspective. The technique is supported by an extensive reference database to measure a software product’s quality in use and is embedded in an effective analysis and reporting tool called SUMI scorer (SUMISCO). SUMI was applied in a controlled laboratory environment where second-year IT students of the CUT, utilized SUMI as part of their networking subject, System Software 1 (SPG1), to evaluate each of the three ICT network programs. The results, strengths and weaknesses, as well as usability improvements, as identified by SUMISCO, are discussed to determine the best ICT network program from a usability perspective according to SPG1 students.

Orientador: Jose Antonio Siqueira Dias / Dissertação (mestrado) - Universidade Estadual de Campinas, Faculdade de Engenharia Elétrica e de Computação / Made available in DSpace on 2018-08-12T16:52:31Z (GMT). No. of bitstreams: 1 Soares_PaulodaSilva_M.pdf: 2232600 bytes, checksum: 4a7346f73eea516fc1252d7abb6076a2 (MD5) Previous issue date: 2008 / Resumo: Este trabalho tem como objetivo desenvolver um sistema de baixo custo para monitoração de veículos automotivos em frotas de transporte. É apresentado o projeto e a implementação de um computador de bordo com módulo de memória externo e portátil, junto com um software de avaliação dos dados gravados na memória. O sistema permite uma avaliação da forma como o veículo está sendo dirigido, indicando não apenas os desvios de rota, tempo de parada excessivo (que já eram possíveis de serem obtidos com os sistemas convencionais de monitoração via GPS), mas também outras informações de muita valia para o gerenciamento da frota. Dentre os principais parâmetros que são examinados pelo sistema, destacamos: rotação do motor, acelerações (positivas e negativas) sofridas pelo veículo, temperatura de operação do motor, velocidade, distancias percorridas, velocidade na chuva e distancia percorrida na chuva. São apresentados o projeto, a implementação e os resultados experimentais em protótipos do computador de bordo. / Abstract: The objective of the dissertation is to develop a low cost system for the monitoring of automotive vehicles in transportation fleets. It is presented the design ad impementation of a onboard computer with an external portable memory module, as well as the software used to evaluate de recorded data in the memory module. The system allows for an avaluation of how the veihicle is being conducted, indicating not only the route changes, excessive pit-stops time (which were already possible to be detected in the conventional GPS monitoring systems), but it also other information which are valuable for the fleet management. Among the main parameters which are examined by the system, it is worth to mention the follwoing: RPM of the motor, accelerations (posite and negative) experienced by the vehicle, motor's operating temperature, vehicle speed, distances travelled under good weather conditions and speed and distances travelled under rainy weather. / Mestrado / Eletrônica, Microeletrônica e Optoeletrônica / Mestre em Engenharia Elétrica

Software quality has become and persistently remains a big issue among software users and developers. So, the importance of software evaluation cannot be overemphasized. An accepted fact in software engineering is that software must undergo evaluation process during development to ascertain and improve its quality level. In fact, there are too many techniques than a single developer could master, yet, it is impossible to be certain that software is free of defects. Therefore, it may not be realistic or cost effective to remove all software defects prior to product release. So, it is crucial for developers to be able to choose from available evaluation techniques, the one most suitable and likely to yield optimum quality results for different products - it bogs down to choosing the most appropriate for different situations. However, not much knowledge is available on the strengths and weaknesses of the available evaluation techniques. Most of the information related to the techniques available is focused on how to apply the techniques but not on the applicability conditions of the techniques – practical information, suitability, strengths, weaknesses etc. This research focuses on contributing to the available applicability knowledge of software evaluation techniques. More precisely, it focuses on code reading by stepwise abstraction as representative of the static technique, as well as equivalence partitioning (functional technique) and decision coverage (structural technique) as representatives of the dynamic technique. The specific focus of the research is to summarize the results of a series of experiments conducted to investigate the effectiveness of these techniques among other factors. By effectiveness in this research, we mean the potential of each of the techniques to generate test cases capable of revealing software faults in the case of the dynamic techniques or the ability of the static technique to generate abstractions that will aid the detection of faults. The experiments used two versions of three different programs with seven different faults seeded into each of the programs. This work uses the results of the eight different experiments performed and analyzed separately, to explore this fact. The analysis results were pooled together and jointly summarized in this research to extract a common knowledge from the experiments using a qualitative deduction approach created in this work as it was decided not to use formal aggregation at this stage. Since the experiments were performed by different researchers, in different years and in some cases at different site, there were several problems that have to be tackled in order to be able to summarize the results. Part of the problems is the fact that the data files exist in different languages, the structure of the files are different, different names is used for data fields, the analysis were done using different confidence level etc. The first step, taken at the inception of this research was to apply all the techniques to the programs used during the experiments in order to detect the faults. This purpose of this personal experience with the experiment is to be familiarized and get acquainted to the faults, failures, the programs and the experiment situations in general and also, to better understand the data as recorded from the experiments. Afterwards, the data files were recreated to conform to a uniform language, data meaning, file style and structure. A well structured directory was created to keep all the data, analysis and experiment files for all the experiments in the series. These steps paved the way for a feasible results synthesis. Using our method, the technique, program, fault, program – technique, program – fault and technique – fault were selected as main and interaction effects having significant knowledge relevant to the analysis summary result. The result, as reported in this thesis, indicated that the functional technique and the structural technique are equally effective as far as the programs and faults in these experiments are concerned. Both perform better than the code review. Also, the analysis revealed that the effectiveness of the techniques is influenced by the fault type and the program type. Some faults were found to exhibit better behavior with certain programs, some were better detected with certain techniques and even the techniques yield different result in different programs. / I can alternatively be contacted through: qasimbabatunde@yahoo.co.uk

Students learn and retain more when they enjoy the process or avenue of learning. Students have fun learning to spell when visual, auditory, and hands-on learning are included in the process. In addition, the intervention project can be used to support and assist second language learners. The benefits from this intervention project will not only strengthen students' phonemic and spelling foundation, but will also enhance their reading comprehension and writing effectiveness.

This research studies the three market-leading RPA-tools, Automation Anywhere, Blue Prism and UiPath, in order to fill the lack of literature regarding methods for evaluating and comparing RPA-tools. Design science research was performed by designing and creating artefacts in the form of process implementations and an evaluative model. A typical process representing a common area of use was implemented using each of the three RPA-tools, in order to create an evaluative model. Official documentation, along with the three implementations, were studied. Evaluative questions specific to RPA-tool evaluation were created based on a quality model for product quality found in the ISO/IEC 25010 standard. Characteristics dependant on organisational context were not included in the evaluation, in order to create an evaluative model which is not dependant on any specific business environment. The results of the research provide knowledge of (1) how RPA-tools can be implemented and (2) the differences that exist between the three market-leading RPA tools. The research also contributes in the form of a method for investigating and evaluating the RPA-tools. When creating the evaluative model, some of the criteria found in the ISO/IEC 25010 quality model were concluded to be of low relevance and, therefore, not included in the model. By analysing and evaluating the created evaluative model, using a theoretical concept of digital resources and their evaluation, the validity of the evaluative model was reinforced. From an evaluative perspective, this research emphasises the need to appropriate and change existing evaluative methods in order to successfully evaluate the most relevant characteristics of RPA-tools. / Denna forskning studerar de tre marknadsledande RPA-verktygen, Automation Anywhere, Blue Prism och UiPath, för att fylla bristen på litteratur om metoder för utvärdering och jämförelse av RPA-verktyg. Design science research genomfördes genom att utforma och skapa artefakter i form av processimplementeringar och en utvärderingsmodell. En typisk process som representerar ett vanligt användningsområde implementerades med användning av vart och ett av de tre RPA-verktygen för att skapa en utvärderingsmodell. Officiell dokumentation, tillsammans med de tre implementeringarna, studerades. Utvärder-ingsfrågor specifika för RPA-verktygsutvärdering skapades baserat på en kvalitetsmodell för produktkvalitet som finns i ISO/IEC 25010-standarden. Egenskaper som är beroende av organisatoriskt sammanhang ingick inte i utvärderingen för att skapa en utvärderingsmodell som inte är beroende av någon specifik affärsmiljö. Resultaten av forskningen ger kunskap om (1) hur RPA-verktyg kan implementeras och (2) skillnaderna som finns mellan de tre marknadsledande RPA-verktygen. Forskningen bidrar också i form av en metod för att undersöka och utvärdera RPA-verktygen. Vid skapandet av utvärderingsmodellen drogs slutsatsen att några av kriterierna i kvalitetsmodellen i ISO/IEC 25010 var av låg relevans och de är därför inte inkluderade i den resulterande modellen. Genom att analysera och utvärdera den skapade utvärderingsmodellen, med hjälp av ett teoretiskt koncept av digitala resurser och deras utvärdering, förstärktes utvärderingsmodellens validitet. Ur ett utvärderingsperspektiv betonar denna forskning behovet av att anpassa och ändra befintliga utvärderingsmetoder för att framgångsrikt utvärdera de mest relevanta egenskaperna hos RPA-verktyg.