Relevant bibliographies by topics / Software

Contents

  1. Journal articles
  2. Dissertations / Theses
  3. Books
  4. Book chapters
  5. Conference papers
  6. Reports

Academic literature on the topic 'Software'

Author: Grafiati
Published: 4 June 2021
Last updated: 31 August 2024

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'Software.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Journal articles on the topic "Software"

1

Zeidman, Bob. "Software v. Software." IEEE Spectrum 47, no. 10 (October 2010): 32–53. http://dx.doi.org/10.1109/mspec.2010.5583460.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Voas, J. "Software's secret sauce: the "-ilities" [software quality]." IEEE Software 21, no. 6 (November 2004): 14–15. http://dx.doi.org/10.1109/ms.2004.54.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Mamoriya, Alka. "Open-Source Software and Proprietary Software for Library Automation." Journal of Advanced Research in Library and Information Science 08, no. 02 (July 9, 2021): 1–3. http://dx.doi.org/10.24321/2395.2288.202101.

Full text
Abstract:
By using library automation software the work gets done easily and quickly. There is no error in library housekeeping operation and solve many issues like stock verification, bibliography, OPAC search operation easily by library automation software. Open-source software is Open bibliog. library management software, KOHA, Avanti. Proprietary software is e-Granthalaya, SOUL, TLSS, and Libsys. By using any software handling library housekeeping and administrative work is very easy and reduces duplication. Many modules are available in software for library operation and each has its unique quality by which the work can be done easily.
APA, Harvard, Vancouver, ISO, and other styles
4

Mamoriya, Alka. "Open-Source Software and Proprietary Software for Library Automation." Journal of Advanced Research in Library and Information Science 08, no. 02 (July 9, 2021): 1–3. http://dx.doi.org/10.24321/2395.2288.202101.

Full text
Abstract:
By using library automation software the work gets done easily and quickly. There is no error in library housekeeping operation and solve many issues like stock verification, bibliography, OPAC search operation easily by library automation software. Open-source software is Open bibliog. library management software, KOHA, Avanti. Proprietary software is e-Granthalaya, SOUL, TLSS, and Libsys. By using any software handling library housekeeping and administrative work is very easy and reduces duplication. Many modules are available in software for library operation and each has its unique quality by which the work can be done easily.
APA, Harvard, Vancouver, ISO, and other styles
5

Mamoriya, Alka. "Open-Source Software and Proprietary Software for Library Automation." Journal of Advanced Research in Library and Information Science 08, no. 02 (July 9, 2021): 1–3. http://dx.doi.org/10.24321/2395.2288.202101.

Full text
Abstract:
By using library automation software the work gets done easily and quickly. There is no error in library housekeeping operation and solve many issues like stock verification, bibliography, OPAC search operation easily by library automation software. Open-source software is Open bibliog. library management software, KOHA, Avanti. Proprietary software is e-Granthalaya, SOUL, TLSS, and Libsys. By using any software handling library housekeeping and administrative work is very easy and reduces duplication. Many modules are available in software for library operation and each has its unique quality by which the work can be done easily.
APA, Harvard, Vancouver, ISO, and other styles
6

Pineda Ballesteros, Eliécer, Freddy Reynaldo Tellez Acuña, and Javier Medina Cruz. "Software requirements: prototyping, legacy software, and document analysis." Ingeniería y Desarrollo 37, no. 2 (March 24, 2020): 327–45. http://dx.doi.org/10.14482/inde.37.2.1053.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Habli, Ibrahim, Richard Hawkins, and Tim Kelly. "Software safety: relating software assurance and software integrity." International Journal of Critical Computer-Based Systems 1, no. 4 (2010): 364. http://dx.doi.org/10.1504/ijccbs.2010.036605.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Munson, John C. "Software faults, software failures and software reliability modeling." Information and Software Technology 38, no. 11 (November 1996): 687–99. http://dx.doi.org/10.1016/0950-5849(96)01117-2.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Bahrami, Mehdi, and Mohammad Bahrami. "A Review of Software Architecture for Collaborative Software’s." Advanced Materials Research 433-440 (January 2012): 2372–76. http://dx.doi.org/10.4028/www.scientific.net/amr.433-440.2372.

Full text
Abstract:
Software architecture has emerged as an important sub-discipline of software engineering; particularly in the realm of large system development. Collaboration software applications are inherently cooperative, requiring many software applications to coordinate their efforts to produce a software system application. Integral to this effort is developing shared understanding surrounding multiple artifacts, each artifact embodying its own model, over the entire development process. This focus on model collaboration embedded within a larger process is what distinguishes collaboration research in software engineering from broader collaboration research. This article first review a list of goals for software architecture, then collaboration software application, several possible future directions for collaboration in software engineering is presented. The article concludes by noting a problem in performing research on collaborative systems.
APA, Harvard, Vancouver, ISO, and other styles
10

Rine, David. "Software perfective maintenance: Including retrainable software in software reuse." Information Sciences 75, no. 1-2 (December 1993): 109–32. http://dx.doi.org/10.1016/0020-0255(93)90116-4.

Full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "Software"

1

Teixeira, Viviani Corrêa. "Software livre e Movimento Softwrare Livre." Florianópolis, SC, 2008. http://repositorio.ufsc.br/xmlui/handle/123456789/91550.

Full text
Abstract:
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
Made available in DSpace on 2012-10-24T00:10:28Z (GMT). No. of bitstreams: 1 261762.pdf: 553923 bytes, checksum: 4907bc1fe2e42b28fdc7a0fd4e75ee7c (MD5)
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.
APA, Harvard, Vancouver, ISO, and other styles
2

Дядечко, Алла Миколаївна, Алла Николаевна Дядечко, Alla Mykolaivna Diadechko, and V. V. Kontchevich. "Software testing and software bugs." Thesis, Видавництво СумДУ, 2011. http://essuir.sumdu.edu.ua/handle/123456789/13487.

Full text
APA, Harvard, Vancouver, ISO, and other styles
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.

Full text
Abstract:

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.

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.

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.

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.

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.

APA, Harvard, Vancouver, ISO, and other styles
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.

Full text
Abstract:
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.
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.
APA, Harvard, Vancouver, ISO, and other styles
5

Coppick, John. "Software Metrics for Object-Oriented Software." TopSCHOLAR®, 1990. http://digitalcommons.wku.edu/theses/1920.

Full text
Abstract:
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.
APA, Harvard, Vancouver, ISO, and other styles
6

DE, Ralf Utermann@Physik Uni-Augsburg. "Software." Universitaet Augsburg, Institut fuer Physik, 1999. http://www.physik.uni-augsburg.de/ci/index.html.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Wirell, Cecilia. "Software." Thesis, Konstfack, Textil, 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:konstfack:diva-6784.

Full text
APA, Harvard, Vancouver, ISO, and other styles
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.

Full text
Abstract:
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
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
APA, Harvard, Vancouver, ISO, and other styles
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.

Full text
APA, Harvard, Vancouver, ISO, and other styles
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.

Full text
Abstract:
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.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Books on the topic "Software"

1

Rucker, Rudy v. B. Software. New York: Avon Books, 1997.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
2

Books, Time-Life, ed. Software. Amsterdam: Time-Life, 1986.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
3

BOOKS, Editors of TIME-LIFE. Software. Amsterdam: Time-Life, 1986.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
4

Books, Time-Life, ed. Software. Amsterdam: Time-Life Books, 1986.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
5

Books, Time-Life, ed. Software. Alexandria, Va: Time-Life Books, 1990.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
6

Rucker, Rudy v. B. Software. London: Roc, 1985.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
7

Rucker, Rudy v. B. Software. Harmondsworth: Penguin, 1985.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
8

Books, Time-Life, ed. Software. Alexandria, Va: Time-Life Books, 1985.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
9

Abran, Alain. Software Metrics and Software Metrology. Hoboken, NJ, USA: John Wiley & Sons, Inc., 2010. http://dx.doi.org/10.1002/9780470606834.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

library, Wiley online, ed. Software metrics and software metrology. Hoboken, N.J: Wiley, 2010.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Book chapters on the topic "Software"

1

Werdich, Martin. "Software Software." In FMEA - Einführung und Moderation, 113–20. Wiesbaden: Vieweg+Teubner Verlag, 2012. http://dx.doi.org/10.1007/978-3-8348-2217-8_6.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

O’Regan, Gerard. "Software Metrics Software Metrics." In Introduction to Software Quality, 151–83. Cham: Springer International Publishing, 2014. http://dx.doi.org/10.1007/978-3-319-06106-1_10.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Abts, Dietmar, and Wilhelm Mülder. "Software." In Grundkurs Wirtschaftsinformatik, 51–92. Wiesbaden: Vieweg+Teubner Verlag, 1998. http://dx.doi.org/10.1007/978-3-322-93946-3_3.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Abts, Dietmar, and Wilhelm Mülder. "Software." In Grundkurs Wirtschaftsinformatik, 53–80. Wiesbaden: Vieweg+Teubner Verlag, 2002. http://dx.doi.org/10.1007/978-3-322-94284-5_3.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Abts, Dietmar, and Wilhelm Mülder. "Software." In Grundkurs Wirtschaftsinformatik, 57–103. Wiesbaden: Vieweg+Teubner Verlag, 2001. http://dx.doi.org/10.1007/978-3-322-94323-1_3.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Miettinen, Kaisa. "Software." In Nonlinear Multiobjective Optimization, 233–37. Boston, MA: Springer US, 1998. http://dx.doi.org/10.1007/978-1-4615-5563-6_8.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Borgeest, Kai. "Software." In Elektronik in der Fahrzeugtechnik, 177–234. Wiesbaden: Vieweg+Teubner, 2010. http://dx.doi.org/10.1007/978-3-8348-9337-6_7.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Klaus, Dembowski. "Software." In Raspberry Pi – Das Handbuch, 33–54. Wiesbaden: Springer Fachmedien Wiesbaden, 2013. http://dx.doi.org/10.1007/978-3-658-03167-1_3.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Abts, Dietmar, and Wilhelm Mülder. "Software." In Grundkurs Wirtschaftsinformatik, 55–87. Wiesbaden: Springer Fachmedien Wiesbaden, 2017. http://dx.doi.org/10.1007/978-3-658-16379-2_3.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Li, Jinghai, Wei Ge, Wei Wang, Ning Yang, Xinhua Liu, Limin Wang, Xianfeng He, Xiaowei Wang, Junwu Wang, and Mooson Kwauk. "Software." In From Multiscale Modeling to Meso-Science, 403–29. Berlin, Heidelberg: Springer Berlin Heidelberg, 2013. http://dx.doi.org/10.1007/978-3-642-35189-1_11.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "Software"

1

Deprez, Jean-Christophe, Fredédéric Fleurial Monfils, Marcus Ciolkowski, and Martín Soto. "Defining Software Evolvability from a Free/Open-Source Software." In Third International IEEE Workshop on Software Evolvability 2007. IEEE, 2007. http://dx.doi.org/10.1109/software-evolvability.2007.6.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Reitz, Markus. "Software Evolvability by Component-Orientation." In Second International IEEE Workshop on Software Evolvability. IEEE, 2006. http://dx.doi.org/10.1109/software-evolvability.2006.13.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Kagdi, Huzefa, and Jonathan Maletic. "Software-Change Prediction: Estimated+Actual." In 2006 Second International IEEE Workshop on Software Evolvability (SE'06). IEEE, 2006. http://dx.doi.org/10.1109/software-evolvability.2006.14.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

"Introduction to Software Evolvability 2006." In Second International IEEE Workshop on Software Evolvability. IEEE, 2006. http://dx.doi.org/10.1109/software-evolvability.2006.4.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Sampaio, Alberto. "Software Phenetics, Phylogeny and Evolution." In Third International IEEE Workshop on Software Evolvability 2007. IEEE, 2007. http://dx.doi.org/10.1109/software-evolvability.2007.13.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Laddaga, Robert. "Self Adaptive Software Problems and Projects." In 2006 Second International IEEE Workshop on Software Evolvability (SE'06). IEEE, 2006. http://dx.doi.org/10.1109/software-evolvability.2006.10.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Meng, Wen Jun, Juergen Rilling, Yonggang Zhang, Rene Witte, Sudhir Mudur, and Philippe Charland. "A Context-Driven Software Comprehension Process Model." In Second International IEEE Workshop on Software Evolvability. IEEE, 2006. http://dx.doi.org/10.1109/software-evolvability.2006.1.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Yu, Liguo, Srini Ramaswamy, and John Bush. "Software Evolvability: An Ecosystem Point of View." In Third International IEEE Workshop on Software Evolvability 2007. IEEE, 2007. http://dx.doi.org/10.1109/software-evolvability.2007.12.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Ernst, Neil A., and John Mylopoulos. "Tracing software evolution history with design goals." In Third International IEEE Workshop on Software Evolvability 2007. IEEE, 2007. http://dx.doi.org/10.1109/software-evolvability.2007.19.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Arcelli, Francesca, and Luca Christina. "Enhancing Software Evolution through Design Pattern Detection." In Third International IEEE Workshop on Software Evolvability 2007. IEEE, 2007. http://dx.doi.org/10.1109/software-evolvability.2007.7.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Reports on the topic "Software"

1

Choquette, Gary. PR-000-SOFTWARE PRCI Software Catalog. Chantilly, Virginia: Pipeline Research Council International, Inc. (PRCI), August 2020. http://dx.doi.org/10.55274/r0011749.

Full text
Abstract:
This document provides a high-level summary of all research deliverables involving software developed with the support of PRCI. Some of these applications were written for older operating systems and may not work on current computer platforms. Many of the applications will work on current operating systems if suitable backward compatibility parameters are set for the application.
APA, Harvard, Vancouver, ISO, and other styles
2

Pollock, G. M. Software attribute visualization for high integrity software. Office of Scientific and Technical Information (OSTI), March 1998. http://dx.doi.org/10.2172/671984.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Thompson, Kelly Glen. Software Testing - Auditing Software Quality Assurance Plans. Office of Scientific and Technical Information (OSTI), June 2017. http://dx.doi.org/10.2172/1364571.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Waite, William W., and Anthony M. Sloane. Software Synthesis via Domain-Specific Software Architectures. Fort Belvoir, VA: Defense Technical Information Center, September 1992. http://dx.doi.org/10.21236/ada451709.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Eslinger, S. Software Acquisition and Software Engineering Best Practices. Fort Belvoir, VA: Defense Technical Information Center, November 1999. http://dx.doi.org/10.21236/ada371477.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Kaufman, Gordon M. Stochastic Software Reliability: Modeling of Software Failures. Fort Belvoir, VA: Defense Technical Information Center, November 1996. http://dx.doi.org/10.21236/ada329608.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

SECRETARY OF THE AIR FORCE WASHINGTON DC. Software Management. Fort Belvoir, VA: Defense Technical Information Center, July 2000. http://dx.doi.org/10.21236/ada404975.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Carrington, David Bradley. KIVA Software. Office of Scientific and Technical Information (OSTI), April 2015. http://dx.doi.org/10.2172/1177537.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Sauers, Aaron G. Software Management. Office of Scientific and Technical Information (OSTI), January 2017. http://dx.doi.org/10.2172/1460399.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Ruhl, Mary K., and Mary T. Gunn. Software reengineering. Gaithersburg, MD: National Institute of Standards and Technology, 1991. http://dx.doi.org/10.6028/nist.sp.500-193.

Full text
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Software' for particular source types:
Journal articles Dissertations / Theses Books
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography