Siga este link para ver outros tipos de publicações sobre o tema: Software.
Teses / dissertações sobre o tema "Software"
Crie uma referência precisa em APA, MLA, Chicago, Harvard, e outros estilos
Veja os 50 melhores trabalhos (teses / dissertações) para estudos sobre o assunto "Software".
Ao lado de cada fonte na lista de referências, há um botão "Adicionar à bibliografia". Clique e geraremos automaticamente a citação bibliográfica do trabalho escolhido no estilo de citação de que você precisa: APA, MLA, Harvard, Chicago, Vancouver, etc.
Você também pode baixar o texto completo da publicação científica em formato .pdf e ler o resumo do trabalho online se estiver presente nos metadados.
Veja as teses / dissertações das mais diversas áreas científicas e compile uma bibliografia correta.
1
Teixeira, Viviani Corrêa. "Software livre e Movimento Softwrare Livre." Florianópolis, SC, 2008. http://repositorio.ufsc.br/xmlui/handle/123456789/91550.
Texto completo da fonteResumo:
Dissertação (mestrado) - Universidade Federal de Santa Catarina, Centro de Filosofia e Ciências Humanas. Programa de Pós-Graduação em Sociologia Política<br>Made available in DSpace on 2012-10-24T00:10:28Z (GMT). No. of bitstreams: 1
261762.pdf: 553923 bytes, checksum: 4907bc1fe2e42b28fdc7a0fd4e75ee7c (MD5)<br>Na sociedade contemporânea e tecnológica, a luta dos grupos excluídos torna-se cada vez mais evidente. O avanço técnico gerou certas disparidades no campo da informática. Algumas empresas aprisionaram o conhecimento através de copyrights, o que induziu a sociedade civil a ficar refém de um processo de exploração comercial e criou uma divisão entre a comunidade de técnicos ligados à computação. Esse contexto de disputa e luta por novas alternativas para o campo da informática dá origem a um movimento em prol da criação, uso e difusão de softwares alternativos e cooperativos. Esse movimento, conhecido como #Movimento Software Livre", pode ser citado como exemplo de um novo agente de transformação que visa romper com o sistema econômico vigente utilizando-se do potencial das redes, principalmente da Internet. O movimento alcançou vários segmentos da sociedade civil e se encontra entre os movimentos mais representativos da atualidade. Além da luta em que a comunidade tecnológica se empenha pela liberdade de escolha na confecção dos softwares, há a tentativa de conscientizar os usuários de que a migração para um software de código fonte aberto, livre para ser melhorado e adaptado a cada realidade de usuário, pode ser economicamente muito mais viável. Partindo dessas considerações, a presente pesquisa analisou a relação de algumas entidades representantes da sociedade civil organizada com os softwares livre e com o Movimento Software Livre. Mais especificamente, entidades afiliadas à ABONG- Associação Brasileira de Organizações Não Governamental. A escolha do universo da pesquisa deu-se pela forte representatividade que a ABONG exerce no campo da sociedade civil, pois entre as entidades associadas estão incluídos diversos
segmentos dessa sociedade.
In contemporary and technological society, the fight of the excluded groups becomes increasingly evident. The technical development has generated some disparities in the field of information technology. Some companies have hidden ugh copyrights, inducing civil society to be a hostage of a process of commercial exploitation. This behavior also created a mentation among the technical computing community. This context of dispute and fight for new alternatives for information technology gave rise to a movement towardsthe creation, dissemination, and use of alternative and cooperative software, the "Free Software Movement". This movement may be cited as an example of a new transformation agent seeking to break with the existing economic system using the potential of networks, especially the Internet. The movement has affected various segments of civil society, becoming one of its most representative movements. Besides the fight of the scientific and technologic community for freedom of choice in the creation of software, there is an attempt to make the users aware that the migration to an open source code software, free to be improved and adapted to the reality of each user, may be economically more viable. Taking all this into consideration, this research analysed the relation of some entities which represent the civil society with free software and the "Free Software Movement". More specifically, entities affiliated to ABONG (Brazilian Association of Non-Governmental Organizations). The choice of the context for this research has been motivated by the strong representation that ABONG exercises in the field of civil society, because the agencies involved include various segments of this society.
2
Дядечко, Алла Миколаївна, Алла Николаевна Дядечко, Alla Mykolaivna Diadechko, and V. V. Kontchevich. "Software testing and software bugs." Thesis, Видавництво СумДУ, 2011. http://essuir.sumdu.edu.ua/handle/123456789/13487.
Texto completo da fonte
3
Pei, Breivold Hongyu. "Software Architecture Evolution and Software Evolvability." Licentiate thesis, Mälardalen University, School of Innovation, Design and Engineering, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-4540.
Texto completo da fonteResumo:
<p>Software is characterized by inevitable changes and increasing complexity, which in turn may lead to huge costs unless rigorously taking into account change accommodations. This is in particular true for long-lived systems. For such systems, there is a need to address evolvability explicitly during the entire lifecycle, carry out software evolution efficiently and reliably, and prolong the productive lifetime of the software systems.</p><p>In this thesis, we study evolution of software architecture and investigate ways to support this evolution. The central theme of the thesis is how to analyze software evolvability, i.e. a system’s ability to easily accommodate changes. We focus on several particular aspects: (i) what software characteristics are necessary to constitute an evolvable software system; (ii) how to assess evolvability in a systematic manner; (iii) what impacts need to be considered given a certain change stimulus that results in potential requirements the software architecture needs to adapt to, e.g. ever-changing business requirements and advances of technology.</p><p>To improve the capability in being able to on forehand understand and analyze systematically the impact of a change stimulus, we introduce a software evolvability model, in which subcharacteristics of software evolvability and corresponding measuring attributes are identified. In addition, a further study of one particular measuring attribute, i.e. modularity, is performed through a dependency analysis case study.</p><p>We introduce a method for analyzing software evolvability at the architecture level. This is to ensure that the implications of the potential improvement strategies and evolution path of the software architecture are analyzed with respect to the evolvability subcharacteristics. This method is proposed and piloted in an industrial setting.</p><p>The fact that change stimuli come from both technical and business perspectives spawns two aspects that we also look into in this research, i.e. to respectively investigate the impacts of technology-type and business-type of change stimuli.</p>
4
CHRISTOPH, ROBERTO DE HOLANDA. "SOFTWARE ENGINEERING FOR OPEN SOURCE SOFTWARE." PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIRO, 2004. http://www.maxwell.vrac.puc-rio.br/Busca_etds.php?strSecao=resultado&nrSeq=4854@1.
Texto completo da fonteResumo:
Software livres têm despertado bastante atenção, não apenas
devido a popularidade obtida por alguns destes como o Linux
e o Apache, mas também pela forma singular como estes
sistemas são desenvolvidos e sua quantidade de
adeptos. No entanto, em alguns projetos de software livre,
a documentação existente dificulta a entrada de novos
participantes, já que devido a informalidade do
processo de desenvolvimento deste tipo de software, é comum
que a documentação do sistema não receba muita atenção.
Este trabalho colabora para um melhor entendimento do
desenvolvimento de software livres, relacionando-o com as
questões de evolução de software. Será apresentada uma
proposta utilizada no software livre C e L para documentar em
termos da aplicação o código do sistema, utilizando-se do
conceito de cenários. Será mostrado através de um protótipo
que um software seguindo esse padrão proposto pode produzir
uma documentação que torna mais fácil seu entendimento
para novos participantes do projeto.<br>This thesis presents an introduction on the use of the
thermal desorption technique that is based on the direct
heating of the soil, for the remediation of contaminated
areas. Heat propagation through soils can be mathematically
simulated using coupled heat-moisture transfer theories. In
order to make this simulation possible it is necessary to
identify the required parameters: hydraulic conductivity as
a function of volumetric water content, thermal
conductivity as a function of volumetric water content,
volumetric heat capacity, and soil-water characteristic
curve. One technical description of such parameters is
presented. Two different kinds of soils were used, one clay-
sand (CH) and one sandclay (SC). A study physico-chemical
was done talking into consideration the temperature effect
on the soils with X-Ray, electron microscopic investigation,
CTC, Atterberg Limits and at the particle size
distribution. The study was done on pre-heated soils with
temperatures ranging from 20 Celsius Degrees to 300 Celsius Degrees. Equipments and
methodologies have been especially developed for the
study of the thermo-hydraulics proprieties. The laboratory
tests program consisted of hydraulic conductivity,
retention curves and deformability, taking into account
the temperature effects. During the tests it was observed
that all parameters were temperature dependent. The thermal
parameters, thermal conductivity and heat capacity were
studied for both soils.
5
Coppick, John. "Software Metrics for Object-Oriented Software." TopSCHOLAR®, 1990. http://digitalcommons.wku.edu/theses/1920.
Texto completo da fonteResumo:
Within this thesis the application of software complexity metrics in the object-oriented paradigm is examined. Several factors which may affect the complexity of software objects are identified and discussed. The specific applications of Maurice Halstead’s Software Science and Thomas McCabe’s cyclomatic-complexity metric are discussed in detail.
The goals here are to identify methods for applying existing software metrics to objects and to provide a basis of analysis for future studies of the measurement and control of software complexity in the object-oriented paradigm of software development.
Halstead’s length, vocabulary, volume, program levels and effort metrics are defined for objects. A limit for the McCabe cyclomatic complexity of an object is suggested. Also, tools for calculating these metrics have been developed in LISP on a Texas Instruments’ Explorer.
6
DE, Ralf Utermann@Physik Uni-Augsburg. "Software." Universitaet Augsburg, Institut fuer Physik, 1999. http://www.physik.uni-augsburg.de/ci/index.html.
Texto completo da fonte
7
Wirell, Cecilia. "Software." Thesis, Konstfack, Textil, 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:konstfack:diva-6784.
Texto completo da fonte
8
Taipale, T. (Taneli). "Improving software quality with software error prediction." Master's thesis, University of Oulu, 2015. http://urn.fi/URN:NBN:fi:oulu-201512042251.
Texto completo da fonteResumo:
Today’s agile software development can be a complicated process, especially when dealing with a large-scale project with demands for tight communication. The tools used in software development, while aiding the process itself, can also offer meaningful statistics. With the aid of machine learning, these statistics can be used for predicting the behavior patterns of the development process. The starting point of this thesis is a software project developed to be a part of a large telecommunications network. On the one hand, this type of project demands expensive testing equipment, which, in turn, translates to costly testing time. On the other hand, unit testing and code reviewing are practices that improve the quality of software, but require large amounts of time from software experts. Because errors are the unavoidable evil of the software process, the efficiency of the above-mentioned quality assurance tools is very important for a successful software project. The target of this thesis is to improve the efficiency of testing and other quality tools by using a machine learner. The machine learner is taught to predict errors using historical information about software errors made earlier in the project. The error predictions are used for prioritizing the test cases that are most probably going to find an error. The result of the thesis is a predictor that is capable of estimating which of the file changes are most likely to cause an error. The prediction information is used for creating reports such as a ranking of the most probably error-causing commits. Furthermore, a line-wise map of probability of an error for the whole project is created. Lastly, the information is used for creating a graph that combines organizational information with error data. The original goal of prioritizing test cases based on the error predictions was not achieved because of limited coverage data. This thesis brought important improvements in project practices into focus, and gave new perspectives into the software development process<br>Nykyaikainen ketterä ohjelmistokehitys on monimutkainen prosessi. Tämä väittämä pätee varsinkin isoihin projekteihin. Ohjelmistokehityksessä käytettävät työkalut helpottavat jo itsessään kehitystyötä, mutta ne myös säilövät tärkeää tilastotietoa. Tätä tilastotietoa voidaan käyttää koneoppimisjärjestelmän opettamiseen. Tällä tavoin koneoppimisjärjestelmä oppii tunnistamaan ohjelmistokehitystyölle ominaisia käyttäytymismalleja. Tämän opinnäytetyön lähtökohta on ohjelmistoprojekti, jonka on määrä toimia osana laajaa telekommunikaatioverkkoa. Tällainen ohjelmistoprojekti vaatii kalliin testauslaitteiston, mikä johtaa suoraan kalliiseen testausaikaan. Toisaalta yksikkötestaus ja koodikatselmointi ovat työmenetelmiä, jotka parantavat ohjelmiston laatua, mutta vaativat paljon ohjelmistoammattilaisten resursseja. Koska ohjelmointivirheet ovat ohjelmistoprojektin edetessä väistämättömiä, on näiden työkalujen tehokkuus tunnistaa ohjelmointivirheitä erityisen tärkeää onnistuneen projektin kannalta. Tässä opinnäytetyössä testaamisen ja muiden laadunvarmennustyökalujen tehokkuutta pyritään parantamaan käyttämällä hyväksi koneoppimisjärjestelmää. Koneoppimisjärjestelmä opetetaan tunnistamaan ohjelmointivirheet käyttäen historiatietoa projektissa aiemmin tehdyistä ohjelmointivirheistä. Koneoppimisjärjestelmän ennusteilla kohdennetaan testausta painottamalla virheen todennäköisimmin löytäviä testitapauksia. Työn lopputuloksena on koneoppimisjärjestelmä, joka pystyy ennustamaan ohjelmointivirheen todennäköisimmin sisältäviä tiedostomuutoksia. Tämän tiedon pohjalta on luotu raportteja kuten listaus todennäköisimmin virheen sisältävistä tiedostomuutoksista, koko ohjelmistoprojektin kattava kartta virheen rivikohtaisista todennäköisyyksistä sekä graafi, joka yhdistää ohjelmointivirhetiedot organisaatiotietoon. Alkuperäisenä tavoitteena ollutta testaamisen painottamista ei kuitenkaan saatu aikaiseksi vajaan testikattavuustiedon takia. Tämä opinnäytetyö toi esiin tärkeitä parannuskohteita projektin työtavoissa ja uusia näkökulmia ohjelmistokehitysprosessiin
9
Kagdi, Huzefa H. "Mining Software Repositories to Support Software Evolution." Kent State University / OhioLINK, 2008. http://rave.ohiolink.edu/etdc/view?acc_num=kent1216149768.
Texto completo da fonte
10
Kasianenko, Stanislav. "Predicting Software Defectiveness by Mining Software Repositories." Thesis, Linnéuniversitetet, Institutionen för datavetenskap och medieteknik (DM), 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:lnu:diva-78729.
Texto completo da fonteResumo:
One of the important aims of the continuous software development process is to localize and remove all existing program bugs as fast as possible. Such goal is highly related to software engineering and defectiveness estimation. Many big companies started to store source code in software repositories as the later grew in popularity. These repositories usually include static source code as well as detailed data for defects in software units. This allows analyzing all the data without interrupting programing process. The main problem of large, complex software is impossibility to control everything manually while the price of the error can be very high. This might result in developers missing defects on testing stage and increase of maintenance cost. The general research goal is to find a way of predicting future software defectiveness with high precision. Reducing maintenance and development costs will contribute to reduce the time-to-market and increase software quality. To address the problem of estimating residual defects an approach was found to predict residual defectiveness of a software by the means of machine learning. For a prime machine learning algorithm, a regression decision tree was chosen as a simple and reliable solution. Data for this tree is extracted from static source code repository and divided into two parts: software metrics and defect data. Software metrics are formed from static code and defect data is extracted from reported issues in the repository. In addition to already reported bugs, they are augmented with unreported bugs found on “discussions” section in repository and parsed by a natural language processor. Metrics were filtered to remove ones, that were not related to defect data by applying correlation algorithm. Remaining metrics were weighted to use the most correlated combination as a training set for the decision tree. As a result, built decision tree model allows to forecast defectiveness with 89% chance for the particular product. This experiment was conducted using GitHub repository on a Java project and predicted number of possible bugs in a single file (Java class). The experiment resulted in designed method for predicting possible defectiveness from a static code of a single big (more than 1000 files) software version.
11
Lim, Edwin C. "Software metrics for monitoring software engineering projects." Thesis, Edith Cowan University, Research Online, Perth, Western Australia, 1994. https://ro.ecu.edu.au/theses/1100.
Texto completo da fonteResumo:
As part of the undergraduate course offered by Edith Cowan University, the Department of Computer Science has (as part of a year's study) a software engineering group project. The structure of this project was divided into two units, Software Engineering l and Software Engineering 2. ln Software Engineering 1, students were given the group project where they had to complete and submit the Functional Requirement and Detail System Design documentation. In Software Engineering 2, students commenced with the implementation of the software, testing and documentation. The software was then submitted for assessment and presented to the client. To aid the students with the development of the software, the department had adopted EXECOM's APT methodology as its standard guideline. Furthermore, the students were divided into groups of 4 to 5, each group working on the same problem. A staff adviser was assigned to each project group. The purpose of this research exercise was to fulfil two objectives. The first objective was to ascertain whether there is a need to improve the final year software engineering project for future students by enhancing any aspect that may be regarded as deficient. The second objective was to ascertain the factors that have the most impact on the quality of the delivered software. The quality of the delivered software was measured using a variety of software metrics. Measurement of software has mostly been ignored until recently or used without true understanding of its purpose. A subsidiary objective was to gain an understanding of the worth of software measurement in the student environment One of the conclusions derived from the study suggests that teams who spent more time on software design and testing, tended to produce better quality software with less defects. The study also showed that adherence to the APT methodology led to the project being on schedule and general team satisfaction with the project management. One of the recommendations made to the project co-ordinator was that staff advisers should have sufficient knowledge of the software engineering process.
12
Li, Xiang. "The Use of Software Faults in Software Reliability Assessment and Software Mutation Testing." The Ohio State University, 2015. http://rave.ohiolink.edu/etdc/view?acc_num=osu1434394783.
Texto completo da fonte
13
Lindmark, Fanny, and Hanna Kvist. "Security in software : How software companies work with security during a software development process." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-130964.
Texto completo da fonteResumo:
This study is conducted, due to recent interest in privacy and software security, on how a number of software development companies work during a development process to develop secure software to the possible extent. The study is based on four interviews with four software companies located in Linköping, Sweden. The interviews followed a semi-structured format to ensure the possibility to compare the given answers from the companies to each other. This structure was chosen to give each company the liberty to express what they valued and thought were important during a software development process. The aim was to analyze how and if these companies work with security when developing software, and to see what differences and similarities that could be established. We found differences between the companies' perspective of security and on their methods of working. Some valued secure software more than others and performed more measures to ensure it. We also found some similarities on their view on importance of secure software and ways to work with it. The differences and similarities were related to the size of the companies, their resources, the types of products they develop, and the types of clients they have.
14
Jah, Muzamil. "Software metrics : usability and evaluation of software quality." Thesis, University West, Department of Economics and IT, 2008. http://urn.kb.se/resolve?urn=urn:nbn:se:hv:diva-548.
Texto completo da fonteResumo:
<p>It is difficult to understand, let alone improve, the quality of software without the knowledge of its software development process and software products. There must be some measurement process to predict the software development, and to evaluate the software products. This thesis provides a brief view on Software Quality, Software Metrics, and Software Metrics methods that will predict and measure the specified quality factors of software. It further discusses about the Quality as given by the standards such as ISO, principal elements required for the Software Quality and Software Metrics as the measurement technique to predict the Software Quality. This thesis was performed by evaluating a source code developed in Java, using Software Metrics, such as Size Metrics, Complexity Metrics, and Defect Metrics. Results show that, the quality of software can be analyzed, studied and improved by the usage of software metrics.</p>
15
Konuralp, Zeynep. "Software Process Improvement In A Software Development Environment." Master's thesis, METU, 2007. http://etd.lib.metu.edu.tr/upload/12609059/index.pdf.
Texto completo da fonteResumo:
A software process improvement study is presented. The literature on software
development processes and their improvement is reviewed. The current peer review
process at Software Engineering Directorate of the X Company, Ankara, Tü<br>rkiye
(XCOM) is studied and the static software development metrics based on a recent
proposal have been evaluated. The static software metrics based improvement
suggestions and the author&rsquo<br>s improvement suggestions discussed with the senior staff
are compared. An improved peer review process is proposed. The static software
development metrics have been evaluated on the improved process to see the impacts
of the improvements. The improved process has been already implemented at
XCOM and preliminary results have been obtained.
16
Sayyad, Shirabad Jelber. "Supporting software maintenance by mining software update records." Thesis, University of Ottawa (Canada), 2003. http://hdl.handle.net/10393/29004.
Texto completo da fonteResumo:
It is well known that maintenance is the most expensive stage of the software life cycle. Most large real world software systems consist of a very large number of source code files. Important knowledge about different aspects of a software system is embedded in a rich set of implicit relationships among these files. Those relationships are partly reflected in system documentation at its different levels, but more often than not are never made explicit and become part of the expertise of system maintainers. Finding existing relations between source code components is a difficult task, especially in the case of legacy systems.
When a maintenance programmer is looking at a piece of code in a source file, one of the important questions that he or she needs to answer is: "which other files should I know about, i.e. what else might be relevant to this piece of code?". This is an example of a more general Relevance Relation that maps a set of entities in a software system into a relevance value.
How can we discover and render explicit these relationships without looking over the shoulder of a programmer involved in a maintenance task? We turn to inductive methods that are capable of extracting structural patterns or models from data. They can learn concepts or models from experience observed in the past to predict outcomes of future unseen cases.
This thesis lies at the intersection of two research fields, which has been widely ignored by researchers in the machine learning and software engineering communities. It investigates the application of inductive methods to daily software maintenance at the source code level. Therefore in this thesis we first lay out the general idea of relevance among different entities in a software system. Then using inductive learning methods and a variety of data sources used by maintenance programmers, we extract (i.e. learn) what we call a maintenance relevance relation among files in a large legacy system. In effect we learn from past maintenance experience in the form of problem reports and update records, to be able to make predictions that are useful in future maintenance activities. This relation, which is called the Co-update relation, predicts whether updating one source file may require a change in another file.
To learn the Co-update relation we have performed a large number of experiments using syntactic features such as function calls or variable definitions. We have also performed experiments that use text based features such as source code comments and problem reports, and the combination of these features. The results obtained show that while using syntactic features is encouraging in terms of the predictive power of the results of learning, using text based features yields highly accurate models, with precision and recall measures that make these models viable to be used in a real world setting. As part of the contribution of this thesis we also report on challenges encountered in the process and the lessons learned.
17
Zamli, Kamal Zuhairi. "Supporting software processes for distributed software engineering teams." Thesis, University of Newcastle Upon Tyne, 2003. http://hdl.handle.net/10443/2118.
Texto completo da fonteResumo:
Software processes relate to the sequence of steps that must be carried out by humans to pursue the goals of software engineering. In order to have an accurate representation of what these steps actually are, software processes can be modelled using a process modeling language (PML). Some PMLs simply support the specification of the steps, while others enable the process to be executed (or enacted). When enacted, software processes can provide guidance, automation and enforcement of the software engineering practices that are embodied in the model. Although there has been much fruitful research into PMLs, their adoption by industry has not been widespread. While the reasons for this lack of success may be many and varied, this thesis identified two areas in which PMLs may have been deficient: human dimension issues in terms of support for awareness and visualisation; and support for addressing management and resource issues that might arise dynamically when a process model is being enacted. In order to address some of these issues, a new visual PML called Virtual Reality Process Modelling Language (VRPML) has been developed and evaluated. Novel features have been introduced in VRPML to include support for the integration of a virtual environment, and dynamic creation and assignment of tasks and resources at the PML enactment level. VRPML serves as a research vehicle for addressing our main research hypothesis that a PML, which exploits a virtual environment, is useful to support software processes for distributed software engineering teams.
18
Smuts, Matthys. "Software modem for a software defined radio system." Thesis, Stellenbosch : University of Stellenbosch, 2007. http://hdl.handle.net/10019.1/1985.
Texto completo da fonteResumo:
Thesis (MScEng (Electrical and Electronic Engineering))--University of Stellenbosch, 2007.<br>The use of older and slower protocols has become increasingly difficult to justify due to
the rapid pace at which telecommunications are advancing. To keep up to date with the
latest technologies, the communications system must be designed to accommodate the
transparent insertion of new communications standards in all the stages of a system. The
system should, however, also remain compatible with the older standards so as not to
demand an upgrade of the older systems.
The concept of a software defined radio was introduced to overcome these problems. In
a software defined radio system, the functionality of the communications system is defined
in software, which removes the the need for alterations to the hardware during technology
upgrade. To maintain interoperatibilty, the system must be based on a standardised
architecture. This would further allow for enhanced scalability and provide a plug-andplay
feature for the components of the system.
In this thesis, generic signal processing software components are developed to illustrate
the creation of a basic software modem that can be parameterised to comply fully, or
partially, to various standards.
19
Abbas, Noura. "Software quality and governance in agile software development." Thesis, University of Southampton, 2009. https://eprints.soton.ac.uk/158357/.
Texto completo da fonteResumo:
Looking at software engineering from a historical perspective, we can see how software development methodologies have evolved over the past 50 years. Using the right software development methodology with the right settings has always been a challenge. Therefore, there has always been a need for empirical evidence about what worked well and what did not, and what factors affect the different variables of the development process. Probably the most noticeable change to software development methodology in the last 15 years has been the introduction of the word “agile”. As any area matures, there is a need to understand its components and relations, as well as the need of empirical evidence about how well agile methods work in real life settings. In this thesis, we empirically investigate the impact of agile methods on different aspects of quality including product quality, process quality and stakeholders’ satisfaction as well as the different factors that affect these aspects. Quantitative and qualitative research methods were used for this research, including semi-structured interviews and surveys. Quality was studied in two projects that used agile software development. The empirical study showed that both projects were successful with multiple releases, and with improved product quality and stakeholders’ satisfaction. The data analysis produced a list of 13 refined grounded hypotheses out of which 5 were supported throughout the research. One project was studied in-depth by collecting quantitative data about the process used via a newly designed iteration monitor. The iteration monitor was used by the team over three iterations and it helped identify issues and trends within the team in order to improve the process in the following iterations. Data about other organisations collected via surveys was used to generalise the obtained results. A variety of statistical analysis techniques were applied and these suggested that when agile methods have a good impact on quality they also has a good impact on productivity and satisfaction, also when agile methods had good impact on the previous aspects they reduced cost. More importantly, the analysis clustered 58 agile practices into 15 factors including incremental and iterative development, agile quality assurance, and communication. These factors can be used as a guide for agile process improvement. The previous results raised questions about agile project governance, and to answer these questions the agile projects governance survey was conducted. This survey collected 129 responses, and its statistically significant results suggested that: retrospectives are more effective when applied properly as they had more impact when the whole team participated and comments were recorded, that organisation size has a negative relationship with success, and that good practices are related together as when a team does one aspect well, they do all aspects well. Finally, the research results supported the hypotheses: agile software development can produce good quality software, achieve stakeholders’ satisfaction, motivate teams, assures quick and effective response to stakeholder’s requests, and it goes in stages, matures, and improves over time.
20
Volpano, Dennis M. "Software templates /." Full text open access at:, 1986. http://content.ohsu.edu/u?/etd,131.
Texto completo da fonte
21
Tsamis, Alexandros 1976. "Software tectonics." Thesis, Massachusetts Institute of Technology, 2012. http://hdl.handle.net/1721.1/77777.
Texto completo da fonteResumo:
Thesis (Ph. D. in Design and Computation)--Massachusetts Institute of Technology, Dept. of Architecture, 2012.<br>Cataloged from PDF version of thesis.<br>Includes bibliographical references (p. 365-370).<br>The resent shift of attention in the architectural discourse towards issues of ecological design, coupled with the undeniable role of computation, has already cast a new operative role to the notion of environment. Instead of being the passive, conceptualized or historicized context of an architectural object, environment is quite literally becoming the object of design itself. We are moving away from the imposed-preconceived Cartesian object which negotiates through its boundaries its presence within its immediate context. The discipline is already considering an architecture in which architectural form is only an instance of a designed environment. In many respects, this new understanding of environment aspires to be actively designed as a closed system of constant transformation, an autonomous milieu of exchange at all scales and all levels between substances, properties or qualities. The object of investigation in Software Tectonics is how technologies of design and construction allow newly forming propositions about the role of environment in the discipline to become operational tactics in the design practice. SOFTWARE TECTONICS proposes 3 design research projects. VSpace is a computer drawing application for designers. Unlike traditional CAD systems that work primarily by representing boundaries (B-reps), VSpace derives form by the representation and direct manipulation of properties (P-reps) in space. Boundaries and Properties here are considered simultaneously in the same design environment. Castit is a multi axis, Computer Numerically Controlled device that prints 3D objects by dynamically mixing at least two distinct but chemically compatible materials. Dynamic mixing allows for gradient transitions between two or more materials, resulting in objects with anisotropic material properties. CHUNK aims to eliminate a joint as a third mediating member between two building elements with an area of gradient transition. Conceived as a "dynamic insulation" architectural skin, this building technology project challenges the multi-trade and multi-component tectonics of dominant late-industrial building manufacture.<br>by Alexandros Tsamis.<br>Ph.D.in Design and Computation
22
Dartsch, Germán. "Software libre." Bachelor's thesis, Universidad Nacional de Cuyo. Facultad de Ciencias Políticas y Sociales, 2012. http://bdigital.uncu.edu.ar/4514.
Texto completo da fonteResumo:
En el marco de las sociedades de control, en el capitalismo -axiomática, en su oposición a la lógica dominante del software propietario- el movimiento del software libre crea alternativas que ponen en tela de juicio desde la legislación vigente en derechos de autor hasta la dinámica de trabajo actual en la que se sustenta el capitalismo.<br>Fil: Dartsch, Germán. Universidad Nacional de Cuyo. Facultad de Ciencias Políticas y Sociales.
23
Grissino-Mayer, Henri D. "Software Review." Tree-Ring Society, 2001. http://hdl.handle.net/10150/251624.
Texto completo da fonte
24
Grissino-Mayer, Henri D. "Software Review." Tree-Ring Society, 2002. http://hdl.handle.net/10150/262544.
Texto completo da fonte
25
Ramón, B. Santos, and C. Mario Riquelme. "Software academy." Tesis, Universidad de Chile, 2018. http://repositorio.uchile.cl/handle/2250/168493.
Texto completo da fonteResumo:
TESIS PARA OPTAR AL GRADO DE MAGÍSTER EN ADMINISTRACIÓN (MBA)<br>Ramón B., Santos, [Parte I],
Riquelme C., Mario, [Parte II]<br>Actualmente en Chile la brecha entre la oferta y la demanda de profesionales en el sector de
las tecnologías de información continúa creciendo1. Las empresas tienen problemas para
encontrar profesionales especialistas en desarrollo de software que sean capaces de responder
a los cada vez más exigentes requerimientos de la industria.
Software Academy brinda cursos de especialización en desarrollo de software, específicamente
en creación de aplicaciones Android, iOS, Java, .NET y Ruby. Software Academy cuenta con
redes de headhunters que permiten la posibilidad de conectar a los estudiantes con nuevas
oportunidades laborales. Software Academy permite a los estudiantes experimentar y aplicar
los conocimientos adquiridos en un plan de pasantías con empresas del rubro informático.
La evaluación financiera del proyecto considera un período de cinco años, obteniendo como
resultado un VAN positivo de $44.545.726. La tasa interna de retorno es 43,1% y el período de
recuperación de la inversión es de 2,72 años. La inversión inicial es de $14.825.000.
26
Fabbri, Andrea. "La Tecnologia Software Container - Ruolo nell'Ingegneria dei Sistemi Software." Bachelor's thesis, Alma Mater Studiorum - Università di Bologna, 2018. http://amslaurea.unibo.it/15869/.
Texto completo da fonteResumo:
Analisi dell'evoluzione storica della tecnologia dei Software Container. Introduzione e spiegazione delle caratteristiche principali che hanno portato i Software Container a essere una delle tecnologie principali per la virtualizzazione e la distribuzione di software. Infine si è parlato dei vantaggi che i Software Container hanno portato in campo ingegneristico e dei diversi collegamenti con nuove tecnologie come le architetture a microservizi e il cloud.
27
Danielsen, Trond. "Software-Defined GNSS Receiver based on Free Software Components." Thesis, Norwegian University of Science and Technology, Department of Electronics and Telecommunications, 2007. http://urn.kb.se/resolve?urn=urn:nbn:no:ntnu:diva-9621.
Texto completo da fonteResumo:
<p>A acquisition module for the OpenGNSS software receiver has been implemented as GNU Radio module. It has been tested and the functionality has been verified with both simulated and real signal. A number of proposals for future work and modifications to the GNU Radio framework has also been presented.</p>
28
Hauge, Øyvind. "Open Source Software in Software Intensive Industry - A Survey." Thesis, Norwegian University of Science and Technology, Department of Computer and Information Science, 2007. http://urn.kb.se/resolve?urn=urn:nbn:no:ntnu:diva-9653.
Texto completo da fonteResumo:
<p>The use of Open Source Software (OSS) has increased in both the industry and the public sector. The software intensive industry integrates OSS into their products, participates in the development of OSS products, and develops its own OSS products. The understanding of how and why the industry is approaching OSS is so far limited. To help fill this gap, this thesis intends to explore how and why the software intensive industry approaches OSS. This is done by performing an extensive literature study and by executing a web-based survey. This survey is distributed to a near representative sample of companies from the Norwegian software intensive industry and to a convenience sample of participants in the ITEA 2 research program. The research presented here shows that OSS components are widely used in the software intensive industry. Close to 50% of the Norwegian software intensive industry uses OSS in its development. The industry is mainly motivated to use OSS by practical reasons. OSS components provide functionality of high quality and the industry is satisfied with its use of these components. When using OSS, the industry benefits from the availability of source code, and easy access to components and information about these components. Companies participate in OSS projects because they use the software and because of the learning effect of this participation. The participation is however limited. However, some companies provide commercial services related to the OSS projects they participate in. Releasing a product as OSS attracts more users and customers to a product. These community members may contribute with implemented code, feedback, and requirements. There are, however some side-effects related to releasing an OSS product and companies should be aware of these consequences. The main contributions of this thesis are new understanding of how and why companies approach OSS, a reusable research design, and experiences performing survey research.</p>
29
Kanik, Yusuf. "Software Project Scheduling, Software Project Performance Measurement And Control." Master's thesis, METU, 2005. http://etd.lib.metu.edu.tr/upload/12606362/index.pdf.
Texto completo da fonteResumo:
This thesis is about software project scheduling and use of earned value method on software projects.
As a result of the study, a solution for software project scheduling problems is proposed. A mathematical formulation, developed using integer programming method, is at the heart of the solution. Objective of the formulation is to minimize the development costs consisting of direct labor cost, indirect costs and probable penalty costs. The formulation takes the capability and compatibility variances among resources into account whereas contemporary approaches mostly focus on resource availability. Formulation is of type discrete time and takes the time span to be searched as input. Therefore a heuristic approach has been developed for providing time span input to the models developed using the formulation. The heuristic approach has been proven to be calculating a time span that does not hinder achieving the absolute optimum schedule and shortens the solution time of the integer programs. The heuristic approach and problem formulation have been incorporated into a computer program that generates integer programs and heuristic solutions.
This thesis also describes a method for preparing an earned value plan, based on the scheduling solution defined. The method aims to help project managers in determining the status of their projects and deciding whether any corrective action is required or not. Besides the method, approaches for incorporating indirect costs and penalty costs, which are not explicitly discussed in literature, into final cost estimation have been described.
30
Hanssen, Geir Kjetil. "From Agile Software Product Line Engineering Towards Software Ecosystems." Doctoral thesis, Norges teknisk-naturvitenskapelige universitet, Institutt for datateknikk og informasjonsvitenskap, 2010. http://urn.kb.se/resolve?urn=urn:nbn:no:ntnu:diva-11890.
Texto completo da fonteResumo:
Development and evolution of software products is a challenging endeavor and a significant subfield of software engineering. One of the commonly applied approaches to control and manage this process is software product line engineering (SPLE). There exist a few process frameworks where the development of lines of related software products is basically a sum of two processes: the development of reusable assets and the rapid construction of software applications using predeveloped assets. Agile software development (ASD) is another major paradigm, which also has been widely adopted by the industry over the past decade. SPLE and ASD seek to achieve the same goal i.e. rapid and efficient construction of software. However, the former emphasizes extensive up-front investment in the development of assets for later re-use in contrast to ASD, which emphasizes a reactive approach, avoiding up-front planning and development Even though these two approaches may seem to oppose each other, the industry has lately showed great interest in combining them both, aiming to cover the weaknesses of the one with the strengths of the other. In combination with the overall shift in the software industry from closed systems mindset towards open systems, the uptake of some ASD principles (for example active customer engagement, incremental and iterative development, and open information flows) in product line organizations may contribute to the emergence of more flexible software ecosystems. This thesis presents a longitudinal study of a software product line organization, which has adopted an adapted ASD methodology in an SPLE context and to a large extent has successful in gaining benefits from both approaches, developing towards more open yet controlled processes. Data have been collected over a period of approximately five years following the progression from a strictly waterfall oriented approach, via the adoption of the agile method Evo, up to the current combined agile software product line engineering approach. The following research questions have been addressed in this thesis: RQ1: How can software product line engineering and agile software development be combined? RQ2: How does a software ecosystem shape? The main contributions of this work are: C 1. Through a longitudinal study of a software product line organization we provide detailed insight into an industrial case and how they have changed over time. C 2. We have illustrated some of the details of how SPLE and ASD can be combined in practical terms. We describe the current organization, their product line and their agile software product line engineering process. C 3. We have illustrated how the incorporation of some of the central agile principles has enabled a closer cooperation with external actors. C 4. We have explained the emergence and mode of operation of a software ecosystem, and provided a conceptual model of software ecosystems based on our findings. C 5. We have proposed a theory of software ecosystems, rooted in socio-technical theory and the concept of organizational ecology.
31
Almeida, Daniel A. "Investigating software developers' understanding of open source software licensing." Thesis, University of British Columbia, 2017. http://hdl.handle.net/2429/62756.
Texto completo da fonteResumo:
Software provided under open source licenses is widely used, from
forming high-profile stand-alone applications (e.g., Mozilla Firefox)
to being embedded in commercial offerings (e.g., network routers).
Despite the high frequency of use of open source licenses, there has
been little work about whether software developers understand the open
source licenses they use. To help
understand whether or not developers understand the open source
licenses they use, I conducted a survey that posed development
scenarios involving three popular open source licenses (GNU GPL 3.0,
GNU LGPL 3.0 and MPL 2.0) both alone and in combination. The 375
respondents to the survey, who were largely developers, gave answers
consistent with those of a legal expert's opinion in 62% of 42
cases. Although developers clearly understood cases involving one license,
they struggled when multiple licenses were involved. To understand the context in which licensing issues arise in practice, I analyzed real-world questions posed by developers on online question-and-answer communities. The analysis of these questions indicate that licensing issues can constrain software evolution and technical decisions can have an impact on future licensing issues. Finally, I interviewed software developers in industry to understand how developers reason about and handle license incompatibility in practice. The developers I interviewed are cautious of restrictive licenses. To identify potential licensing issues, these developers rely on licensing guidelines provided by their organization and sometimes use specialized tools to automatically detect licensing issues in their projects. When faced with a situation in which a component that suits their needs is not compatible, developers tend to look for alternative components made available by open source communities. They sometimes leverage the technical architecture of their projects to enable the use of components under restrictive licenses and might rewrite the required functionality if necessary. An analysis of
the results indicate a need for tool support to help guide developers in understanding the structure of the code and the technical details of a project while taking into account the exact requirements imposed by the licenses involved.<br>Science, Faculty of<br>Computer Science, Department of<br>Graduate
32
Akhlaq, Usman, and Muhammad Usman Yousaf. "Impact of Software Comprehension in Software Maintenance and Evolution." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2010. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-2176.
Texto completo da fonteResumo:
The need of change is essential for a software system to reside longer in the market. Change implementation is only done through the maintenance and successful software maintenance gives birth to a new software release that is a refined form of the previous one. This phenomenon is known as the evolution of the software. To transfer software from lower to upper or better form, maintainers have to get familiar with the particular aspects of software i.e. source code and documentation. Due to the poor quality of documentation maintainers often have to rely on source code. So, thorough understanding of source code is necessary for effective change implementation. This study explores the code comprehension problems discussed in the literature and prioritizes them according to their severity level given by maintenance personnel in the industry. Along with prioritizing the problems, study also presents the maintenance personnel suggested methodologies for improving code comprehension. Consideration of these suggestions in development might help in shortening the maintenance and evolution time.<br>Usman Akhlaq Mirpur, Azad Kashmir, Pakistan Muhammad Usman Yousaf Bhimber, Azad Kashmir, Pakistan
33
Cappiello, Antonio. "Improving software evolvabilityby exploiting change history and software metrics." Thesis, Mälardalens högskola, Akademin för innovation, design och teknik, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-15251.
Texto completo da fonte
34
Cepa, Vasian. "Attribute enabled software development illustrated with mobile software applications." Saarbrücken VDM, Müller, 2005. http://deposit.d-nb.de/cgi-bin/dokserv?id=2939598&prov=M&dok_var=1&dok_ext=htm.
Texto completo da fonte
35
Cepa, Vasian. "Attributed enabled software development : illustrated with mobile software applications /." Saarbrücken : VDM, Verl. Dr. Müller, 2007. http://deposit.d-nb.de/cgi-bin/dokserv?id=2939598&prov=M&dok_var=1&dok_ext=htm.
Texto completo da fonte
36
Wang, Hui. "Software Defects Classification Prediction Based On Mining Software Repository." Thesis, Uppsala universitet, Institutionen för informationsteknologi, 2014. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-216554.
Texto completo da fonteResumo:
An important goal during the cycle of software development is to find and fix existing defects as early as possible. This has much to do with software defects prediction and management. Nowadays,many big software development companies have their own development repository, which typically includes a version control system and a bug tracking system. This has no doubt proved useful for software defects prediction. Since the 1990s researchers have been mining software repository to get a deeper understanding of the data. As a result they have come up with some software defects prediction models the past few years. There are basically two categories among these prediction models. One category is to predict how many defects still exist according to the already captured defects data in the earlier stage of the software life-cycle. The other category is to predict how many defects there will be in the newer version software according to the earlier version of the software defects data. The complexities of software development bring a lot of issues which are related with software defects. We have to consider these issues as much as possible to get precise prediction results, which makes the modeling more complex. This thesis presents the current research status on software defects classification prediction and the key techniques in this area, including: software metrics, classifiers, data pre-processing and the evaluation of the prediction results. We then propose a way to predict software defects classification based on mining software repository. A way to collect all the defects during the development of software from the Eclipse version control systems and map these defects with the defects information containing in software defects tracking system to get the statistical information of software defects, is described. Then the Eclipse metrics plug-in is used to get the software metrics of files and packages which contain defects. After analyzing and preprocessing the dataset, the tool(R) is used to build a prediction models on the training dataset, in order to predict software defects classification on different levels on the testing dataset, evaluate the performance of the model and comparedifferent models’ performance.
37
Park, In Kyoung, Dan C. Boger, and Michael G. Sovereign. "Software cost estimation through Bayesian inference of software size." Thesis, Monterey, California. Naval Postgraduate School, 1985. http://hdl.handle.net/10945/21547.
Texto completo da fonte
38
Guo, Hong. "Software quality and software process improvement in teleworking environments." Thesis, Southampton Solent University, 2001. http://ssudl.solent.ac.uk/823/.
Texto completo da fonteResumo:
Telework as a swift developing business has attracted great attention from government, company and organisation due to its large benefits for out society. A study was accordingly conducted to investigate its application in the IT industry. Results show that teleworking is widely accepted by and plays an important role in software industry. With the rapid development in computer and telecommunications technology, telework has become increasingly populat and can not be avoided in IT industry. the benefits and problems brought by teleworking in IT industry are then reported in the study. It is found that the big obstruction for telework development in software engineering is still product quality problems. As many researchers have revealed, our society has entered the information society. The demand for more and more software products with better and better quality is increasing. However problems of software quality hinder the development of the IT industry. The recognised reason for this is the inability to manage the software process. Hence, many software process assessment and improvement models have been developed and used successfully in the management of software development in order to acquire improvements in software quality. However, the problem considered here is whether they are suitable for telework software development. To build the necessary ground knowledge for carrying out this project, an extensive analysis of the fundamental methodology and principles of existing software process assessment and improvement models was conducted. The strengths and weaknesses of these models are derived from the analysis. The applicability and adaptability of the models for teleworking environments are also explored. It is found that the existing models are designed for centralised software development. They are not fully suitable but the same functions are applicable for teleworking environments. The results of above discussion lead to the selection and recommendation of SPICE to be used as a baseline for the development of a process approach which meets the need of teleworking software environments. To lay a solid foundation for the development of such approach, two surveys were carried out. Their aims are investigate the current state of telework in IT industry and the applicability of the present models in teleworking environments, and to identify the specific issues which arise in telework. It can be observed from the survey that there are significant differences in software process and management methodologies between telework and conventional single-site work. Special technologies are needed to support telework software development. To provide valuable input in the development of such approach, an in-depth analysis of the specific requirements identified from the survey results in the creation of a set of processes and base practices, which are particularly required by teleworking environments. The SPITE approach, which is a SPICE extension model, is therefore developed as a major contribution to the software industry that fills an important gap in the software process modelling. Good comments have been obtained from a small range of organisations.
39
OLIVEIRA, GLORIA MARIA DE PAULA. "USING SOFTWARE ENGINEERING CONCEPTS TO DEFINE SOFTWARE DEVELOPMENT PROCESSES." PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIRO, 2007. http://www.maxwell.vrac.puc-rio.br/Busca_etds.php?strSecao=resultado&nrSeq=12112@1.
Texto completo da fonteResumo:
PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIRO<br>A qualidade de um produto de software depende fortemente da
qualidade do processo de software utilizado em seu
desenvolvimento. Para auxiliar na definição
de um processo de qualidade, existem diversos modelos de
processo, modelos de maturidade e normas de qualidade.
Entretanto, a tarefa de elaborar ou melhorar o processo de
desenvolvimento de sistemas pode se tornar árdua
devido à grande quantidade de informações disponíveis e
decisões a serem tomadas. Outro grande problema é o risco
de definição de um processo que não seja eficaz, ou seja,
não melhore a qualidade dos sistemas ou somente aumente
a burocracia no desenvolvimento. Esta dissertação apresenta
uma abordagem para definição de processos de
desenvolvimento de sistemas baseada nos conceitos
da análise de sistemas, ressaltando a analogia existente
entre a elaboração de um processo e de um software. Uma das
principais características da abordagem é o enfoque na área
de Gerência de Riscos, visando o controle dos
riscos identificados na definição do processo bem como os
possíveis riscos na execução do processo de desenvolvimento.<br>Software quality depends heavily on the quality of the
process used to develop it. In order to assist the
definition of an adequate process, there are several
process models, maturity models and quality standards.
However, creating or improving a software development
process may be tough due to the large amount of available
information and decisions that have to be made. Another
central problem is the risk of defining an ineffective
process, that is, one that increases the bureaucracy
but doesn`t improve the quality of the systems developed
with its support. This dissertation presents an approach
for defining software development processes based on the
concepts of system analysis, based on the analogy between
software and process elaboration. One of the most important
attributes of this approach is the focus on Risk
Management, considering the identified risks in
the process definition as well the possible risks during
software process execution.
40
Cronje, Johannes Jacobus. "Software architecture design of a software defined radio system." Thesis, Stellenbosch : Stellenbosch University, 2004. http://hdl.handle.net/10019.1/50095.
Texto completo da fonteResumo:
Thesis (MScEng)--University of Stellenbosch, 2004.<br>ENGLISH ABSTRACT: The high pace of technological advancement enables the realisation of ever more advanced
mobile communications standards with more functionality than simple voice
communications. The hardware that is used to implement the radio sections of these
systems generally require long design cycles, much longer than the design cycles of
the other components of a communications system. Another problem is that, once new
communications standards are introduced, the current hardware platforms used in the
terminal equipment becomes obsolete because they can generally not be used with the
new standards. This has serious cost implications for both the service provider and the
consumer, because both parties have to acquire new equipment to be able to use the
new standards.
An elegant solution to the above issues is to use software-defined radio sections to
replace the hardware radio components. New communications standards can then be
supported by simply loading new software onto the equipment, provided the maximum
processing capacity of the processor(s) that the software runs on can accommodate
the bandwidth requirements of that specific standard.
This thesis investigates the ideas behind software defined radio and also describes
the design and implementation of a software architecture that can be used to implement
software defined radios on general-purpose platforms such as personal computers.<br>AFRIKAANSE OPSOMMING: Die hoë tempo van tegnologiese vordering maak dit moontlik om baie gevorderde
mobiele kommunikasie standaarde te implementeer wat meer funksionaliteit bied as
blote spraakkommunikasie. Die hardeware wat gebruik word om die radios van
sulke stelsels te implementeer neem gewoonlik langer om te ontwikkel as die ander
komponente van die stelsels. Die ander probleem is dat hierdie hardeware gewoonlik
nie hergebruik kan word wanneer nuwe kommunikasie standaarde in gebruik geneem
word nie omdat die standaarde nie versoenbaar is nie. Dit het tot gevolg dat beide
die verbruiker en die diensverskaffer groot bedrae geld moet spandeer om die nuwe
tegnologie te kan gebruik.
'n Elegante oplossing vir hierdie probleme is om gebruik te maak van radios waarvan
die funksionaliteit in sagteware gedefiniëer word. Nuwe kommunikasie standaarde
kan dan gebruik word deur slegs die nodige sagteware op die toerusting te laai, solank
die verwerkingskapasiteit van die mikroverwerkers in die stelsel die benodigde bandwydte
kan akkommodeer.
Hierdie tesis ondersoek die konsepte van sagteware-gedefiniëerde radio en beskryf
die ontwerp en implementering van 'n sagteware argitektuur vir die implementering
van sagteware-gedefiniëerde radios op veeldoelige platforms soos persoonlike rekenaars.
41
Kriukov, Illia. "Multi-version software quality analysis through mining software repositories." Thesis, Linnéuniversitetet, Institutionen för datavetenskap och medieteknik (DM), 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:lnu:diva-74424.
Texto completo da fonteResumo:
The main objective of this thesis is to identify how the software repository features influence software quality during software evolution. To do that the mining software repository area was used. This field analyzes the rich data from software repositories to extract interesting and actionable information about software systems, projects and software engineering. The ability to measure code quality and analyze the impact of software repository features on software quality allows us to better understand project history, project quality state, development processes and conduct future project analysis. Existing work in the area of software quality describes software quality analysis without a connection to the software repository features. Thus they lose important information that can be used for preventing bugs, decision-making and optimizing development processes. To conduct the analysis specific tool was developed, which cover quality measurement and repository features extraction. During the research general procedure of the software quality analysis was defined, described and applied in practice. It was found that there is no most influential repository feature and the correlation between software quality and software repository features exist, but it is too small to make a real influence.
42
Waleszonia, Nicholas W. "A SOFTWARE DEVELOPMENT DOCUMENTATION INTERNSHIP WITH BLUESPRING SOFTWARE, INC." Miami University / OhioLINK, 2011. http://rave.ohiolink.edu/etdc/view?acc_num=miami1303179151.
Texto completo da fonte
43
Leardini, Mirko. "Le Software Product Lines nel processo di produzione software." Bachelor's thesis, Alma Mater Studiorum - Università di Bologna, 2011. http://amslaurea.unibo.it/1863/.
Texto completo da fonte
44
Ivanoff, Gregorio Bittar. "Ambientes e organizações virtuais: cultura de segurança e regulação entre o desenvolvimento de programas computacionais e estruturas e processos organizacionais." Universidade de São Paulo, 2006. http://www.teses.usp.br/teses/disponiveis/3/3141/tde-01122006-173728/.
Texto completo da fonteResumo:
Estruturas e processos de desenvolvimento de programas computacionais e estruturas e processos organizacionais que incluem os programas, quando considerados separadamente, resultam em estudos de segurança de programas computacionais que, em geral, levam em conta apenas ambientes e organizações tradicionais. Ambientes e organizações virtuais podem ser utilizados para representar a regulação entre diferentes estruturas e processos, resultando em melhores interpretações sobre o desenvolvimento da segurança de programas computacionais. Esta atividade de pesquisa explora temas de conteúdo, práticas e artefatos como componentes da cultura de segurança em uma organização virtual de pequeno porte voltada para a inovação. Os temas de conteúdo propostos para a organização virtual específica são: adaptabilidade, dependabilidade, compatibilidade, credibilidade, confiança e mobilidade. As práticas e artefatos identificados envolvem, entre outros, a comunicação entre projetistas, desenvolvedores e usuários, a coordenação colaborativa de atividades, a gestão de dependências e o manejo de mudanças e da adaptação. A atividade de pesquisa foi baseada na metodologia Grounded Theory ou Teoria Fundamentada em Dados e identifica como desafios: a falta de adaptação dos programas computacionais a novas circunstâncias do ambiente, a falta de correspondência entre o programa computacional e a realidade, e a falta de credibilidade e confiança nos programas. As conclusões despertam a atenção para a exploração de limites de segurança na relação entre pessoas e programas computacionais, e especificamente, para a mudança de condições perigosas, para a possibilidade da mobilidade virtual em diferentes estruturas e processos, e para a necessidade de apoio à perspectiva de inteligência do ambiente.<br>Software development structures and processes and organizational structures and processes that include the programs, when considered separately, result in studies of software safety and security that, in general, take into account only traditional environments and organizations. Virtual environments and organizations may be utilized to represent the regulation between different structures and processes, resulting in better interpretations of software safety and security development. This research activity explores content themes, practices and artifacts as components of the safety and security culture in a small virtual organization dedicated to innovation. Content themes proposed for the specific virtual organization are: adaptability, dependability, compatibility, credibility, trust and mobility. Practices and artifacts identified involve, among others, the communication between designers, developers and users, the collaborative coordination of activities, the dependencies management and the handling of changes and adaptation. The research activity is based on Grounded Theory methodology and identifies as challenges: the absence of software adaptation to new ambient circumstances, the absence of correspondence between software and reality, and the absence of credibility and confidence in software. Conclusions call the attention to the exploration of safety and security limits to the relation between people and software and specifically, to the change of dangerous conditions, to the possibility of virtual mobility in different structures and processes, and to the necessity of supporting the ambient intelligence perspective.
45
Karvonen, T. (Teemu). "Continuous software engineering in the development of software-intensive products:towards a reference model for continuous software engineering." Doctoral thesis, Oulun yliopisto, 2017. http://urn.fi/urn:isbn:9789526216560.
Texto completo da fonteResumo:
Abstract Continuous software engineering (CSE) has instigated academic debate regarding the rapid, parallel cycles of releasing software and customer experimentation. This approach, originating from Web 2.0 and the software-as-a-service domain, is widely recognised among software-intensive companies today. Earlier studies have indicated some challenges in the use of CSE, especially in the context of business-to-business and product-oriented, embedded systems development. Consequently, research must address more explicit definitions and theoretical models for analysing the prerequisites and organisational capabilities related to the use of CSE. This dissertation investigates various approaches to conducting empirical evaluations related to CSE. The study aims to improve existing models of CSE and to empirically validate them in the context of software companies. The study also aims to accumulate knowledge regarding the use of CSE, as well as its impacts. The case study method is applied for the collection and analysis of empirical data. Twenty-seven interviews are conducted at five companies. In addition, a systematic literature review is used to synthesise the empirical research on agile release engineering practices. Design science research is used to portray the model design and the evaluation process of this dissertation. Three approaches for evaluating CSE are constructed: (1) LESAT for software focuses on enterprise transformation using an organisational self-assessment approach, (2) STH+ extends the “Stairway to Heaven” model and evaluates company practices with respect to evolutionary steps towards continuous experimentation-driven development, and (3) CRUSOE defines 7 key areas and 14 diagnostic questions related to the product-intensive software development ecosystem, strategy, architecture, and organisation, as well as their continuous interdependencies. This dissertation states the relevance of CSE in the context of product-intensive software development. However, more adaptations are anticipated in practices that involve business and product development stakeholders, as well as company external stakeholders<br>Tiivistelmä Jatkuva ohjelmistotuotanto on herättänyt keskustelua nopeasta, samanaikaisesta ohjelmistojulkaisemisesta ja asiakaskokeiluista. Toimintatapa on peräisin Web 2.0 ja software-as-a-service yhteydestä, mutta se tunnetaan nykyään yleisesti ohjelmistoja kehittävissä yrityksissä. Aiemmat tutkimukset ovat osoittaneet haasteita jatkuvan ohjelmistotuotannon käytössä. Erityisesti haasteita on havaittu yritykseltä yritykselle liiketoiminnassa ja tuotepainotteisten sulautettujen järjestelmien yhteydessä. Näin ollen on havaittu tarve tutkimuksen avulla kehittää täsmällisempiä määritelmiä ja teoreettisia malleja, joilla voidaan analysoida jatkuvan ohjelmistotuotannon käyttöön liittyviä edellytyksiä ja organisaatioiden kyvykkyyksiä. Tässä väitöskirjassa tutkitaan malleja, joilla voidaan empiirisesti arvioida jatkuvaa ohjelmistotuotantoa. Tutkimuksella pyritään parantamaan nykyisiä malleja ja arvioimaan niiden käyttöä ohjelmistoyrityksissä. Lisäksi tutkimuksella pyritään kasvattamaan tietoa jatkuvasta ohjelmistotuotannosta ja sen vaikutuksista. Tiedon keräämiseen ja analysointiin käytettiin tapaustutkimus menetelmää. Kaksikymmentäseitsemän haastattelua tehtiin viidessä yrityksessä. Lisäksi tehtiin ketterään ohjelmistojulkaisuun keskittyvä systemaattinen kirjallisuuskatsaus. Väitöskirjassa käytetään Design Science Research menetelmää kuvaamaan tutkimuksen eri vaiheita, joissa malleja suunniteltiin ja arvioitiin. Tutkimuksessa rakennettiin kolme tapaa jatkuvan ohjelmistotuotannon arvioimista varten: (1) LESAT for Software keskittyy organisaation muutoskyvykkyyden arviointiin käyttäen itsearviointimenetelmää, (2) STH+, laajentaa ”Stairway to Heaven” mallia ja arvioi yrityksen käytäntöjä eri evoluutioaskelmilla matkalla kohti kokeilupainotteista tuotekehitystä, (3) CRUSOE määrittelee seitsemän pääaluetta ja 14 kysymystä liittyen tuotekehityksen ekosysteemiin, strategiaan, arkkitehtuuriin, organisointiin sekä näiden välisiin jatkuviin riippuvuuksiin. Väitöskirja osoittaa jatkuvan ohjelmistokehityksen olevan merkityksellinen myös tuotepainotteisessa ohjelmistokehityksessä. Nähtävissä kuitenkin on, että useita nykykäytäntöjä on tarvetta muokata. Erityisesti muokkaustarvetta on tuotekehityksen ja liiketoiminnan sidosryhmiin ja yrityksen ulkoisiin sidosryhmiin liittyvissä käytännöissä
46
Sherwood, Patricia Ann. "Inspections : software development process for building defect free software applied in a small-scale software development environment /." Online version of thesis, 1990. http://hdl.handle.net/1850/10598.
Texto completo da fonte
47
Brophy, Dennis J. O'Leary James D. "Software evaluation for developing software reliability engineering and metrics models /." Monterey, Calif. : Springfield, Va. : Naval Postgraduate School ; Available from National Technical Information Service, 1999. http://handle.dtic.mil/100.2/ADA361889.
Texto completo da fonteResumo:
Thesis (M.S. in Information Technology Management) Naval Postgraduate School, March 1999.<br>"March 1999". Thesis advisor(s): Norman F. Schneidewind, Douglas Brinkley. Includes bibliographical references (p. 59-60). Also available online.
48
Böllert, Kai. "Objektorientierte Entwicklung von Software-Produktlinien zur Serienfertigung von Software-Systemen." [S.l. : s.n.], 2002. http://deposit.ddb.de/cgi-bin/dokserv?idn=974934933.
Texto completo da fonte
49
Achieng, Spance Joy. "SOFTWARE PATENTS : A study on the patentability of software inventions." Thesis, Uppsala universitet, Juridiska institutionen, 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-324267.
Texto completo da fonteResumo:
The primary objective of the thesis will be to focus on patent protection of software under the European Patent Convention, by analyzing the different approaches that the European Patent Office has taken into consideration since the mid-1980s. These approaches are derived from the different decisions that emanate from the Technical Boards of Appeal of the European Patent Office. The thesis will examine the most relevant decisions illustrating the juridical tendencies and basis that have been utilized to decide over the patentability of computer programs. The analysis will conclude with the latest approach taken by the Technical Board of the European Patent Office. The study will examine the patentability requirements of inventions in general established within the European Patent Convention. Sources that will be utilized to carry out this research will include case law, legislation, specialized legal commentary; journals and books. The present study sustains that computer programs may be patented as long as they comply with all the general requirements of an invention prescribed under the European Patent Convention together with the condition established by case law called the technical character requirement. Nevertheless, due to the fact that the Technical Boards of Appeal are not bound by previous case law, the current position could keep evolving as it relies on the stance of the European Patent Office on patentability of computer programs which is seems to be influenced by the changes in the technological world
50
Rönkkö, Kari. "Software Practice from the Inside : Ethnography Applied to Software Engineering." Licentiate thesis, Karlskrona : Blekinge Institute of Technology, 2002. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-00234.
Texto completo da fonteResumo:
Empirical methodologies have recently attracted increasing attention from the broader software engineering community. In particular, organisational issues and the human role in software development have been addressed. Qualitative research approaches have been identified as necessary for understanding human nature. One qualitative methodology which has become increasingly recognised in the software engineering community is ethnography. It is also the qualitative approach that is addressed in this thesis, i.e. ethnography in relation to software engineering. Ethnography emphasises the members point of view in an effort to understand the organisation of a social, cultural and technical setting. Until now, only a handful of ethnographic studies focusing on software engineering have been carried out in accordance with the original conception of ethnography; these studies have traditionally been performed by sociologists. The understanding and application of ethnography by software engineers differ from that of sociologists as it gives up the studied people's point of view in the analysis of data. The thesis is based on two independent ethnographic studies where the ‘inside’ perspective which complies with the original understanding of the methodology is applied. Using these examples as a basis, the relation between ethnography and software engineering research is explored. The objective of this thesis is to promote ‘ethnographic knowledge’ by giving an overview of ethnographic work within software engineering, presenting an original understanding of ethnography, comparing software engineers' understanding of ethnography with the original understanding of ethnography, demonstrating how the different implicit research attitudes of ethnographers and software engineers produce different research discourses, and finally pointing to an opportunity to combine ethnography, which contributes an ‘inside perspective’, with software engineering's need for constant improvement.