Щоб переглянути інші типи публікацій з цієї теми, перейдіть за посиланням: Software.

Статті в журналах з теми "Software"

Оформте джерело за APA, MLA, Chicago, Harvard та іншими стилями

Оберіть тип джерела:

Ознайомтеся з топ-50 статей у журналах для дослідження на тему "Software".

Біля кожної праці в переліку літератури доступна кнопка «Додати до бібліографії». Скористайтеся нею – і ми автоматично оформимо бібліографічне посилання на обрану працю в потрібному вам стилі цитування: APA, MLA, «Гарвард», «Чикаго», «Ванкувер» тощо.

Також ви можете завантажити повний текст наукової публікації у форматі «.pdf» та прочитати онлайн анотацію до роботи, якщо відповідні параметри наявні в метаданих.

Переглядайте статті в журналах для різних дисциплін та оформлюйте правильно вашу бібліографію.

1

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

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
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.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
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.

Повний текст джерела
Анотація:
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 та ін.
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.

Повний текст джерела
Анотація:
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 та ін.
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.

Повний текст джерела
Анотація:
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 та ін.
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.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
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.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
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.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
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.

Повний текст джерела
Анотація:
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 та ін.
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.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
11

Vaníček, J. "Software quality requirements." Agricultural Economics (Zemědělská ekonomika) 52, No. 4 (February 17, 2012): 177–85. http://dx.doi.org/10.17221/5014-agricecon.

Повний текст джерела
Анотація:
At the present time, the international standards and technical reports for system and software product quality are dispersed in several series of normative documents (ISO/IEC 9126, ISO/IEC 14598, ISO/IEC 12119 etc.). These documents are not purely consistent and do not contain a tools for exact requirements set-ups. As quality is defined as a degree to which the set of inherent characteristic fulfils requirements, the exact requirement formulation is the key point for the quality measurement evaluation. This paper presents the framework for quality requirements for software, which is recommendable to use in the new international standard series ISO/IEC 250xx developed on the SQuaRE (Software Quality Requirements and Evaluation) standardisation research project. The main part of this contribution was presented on the conference Agrarian Perspectives XIV, organised by the Czech University of Agriculture in Prague, September 20 to 21, 2005.
Стилі APA, Harvard, Vancouver, ISO та ін.
12

Aksatha, Mrs D. Seema Dev, and M. Blessing Marshal. "Software Piracy Protection." International Journal of Trend in Scientific Research and Development Volume-3, Issue-3 (April 30, 2019): 243–46. http://dx.doi.org/10.31142/ijtsrd21705.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
13

Tharmaseelan, Janani. "Cohesive Software Design." International Journal of Trend in Scientific Research and Development Volume-3, Issue-3 (April 30, 2019): 955–57. http://dx.doi.org/10.31142/ijtsrd22900.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
14

Gupta, Karan, and Anita Goel. "Software Engineering for Tagging Software." International Journal of Software Engineering & Applications 4, no. 4 (July 31, 2013): 65–76. http://dx.doi.org/10.5121/ijsea.2013.4406.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
15

Amirat, Abdelkrim, Halima Bahi, Mourad Oussalah, and Ahcene Menasria. "Software connector as software process." International Journal of Simulation and Process Modelling 17, no. 4 (2021): 231. http://dx.doi.org/10.1504/ijspm.2021.10046773.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
16

Menasria, Ahcene, Mourad Oussalah, Abdelkrim Amirat, and Halima Bahi. "Software connector as software process." International Journal of Simulation and Process Modelling 17, no. 4 (2021): 231. http://dx.doi.org/10.1504/ijspm.2021.122503.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
17

Nagel, Stuart. "Software Review: Creativity-Aiding Software." Social Science Computer Review 19, no. 3 (August 2001): 376–78. http://dx.doi.org/10.1177/089443930101900313.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
18

Hurlburt, George, and Jeffrey Voas. "Software is Driving Software Engineering?" IEEE Software 33, no. 1 (January 2016): 101–4. http://dx.doi.org/10.1109/ms.2016.22.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
19

Rakhmawati, Nur Aini. "SOFTWARE OPEN SOURCE, SOFTWARE GRATIS?" JUTI: Jurnal Ilmiah Teknologi Informasi 5, no. 1 (January 1, 2006): 13. http://dx.doi.org/10.12962/j24068535.v5i1.a201.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
20

Power, Lee. "Software Integration without Integrated Software." OCLC Micro 1, no. 5 (May 1985): 13–15. http://dx.doi.org/10.1108/eb055753.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
21

Charette, R. N. "Why software fails [software failure." IEEE Spectrum 42, no. 9 (September 2005): 42–49. http://dx.doi.org/10.1109/mspec.2005.1502528.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
22

Lindner, Felix "FX." "Software security is software reliability." Communications of the ACM 49, no. 6 (June 2006): 57–61. http://dx.doi.org/10.1145/1132469.1132502.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
23

Kittlaus, Dipl Inform Hans-Bernd. "Software-Engineering und Software-Fabrik." Informatik-Spektrum 26, no. 1 (January 1, 2003): 8–12. http://dx.doi.org/10.1007/s00287-002-0278-9.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
24

Broy, Manfred. "Software-Engineering und Software-Fabrik." Informatik-Spektrum 26, no. 1 (January 1, 2003): 13–16. http://dx.doi.org/10.1007/s00287-002-0279-8.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
25

Clark, Ruth C. "Software: Wanted: Desktop software reviews." Performance + Instruction 27, no. 6 (July 1988): 45. http://dx.doi.org/10.1002/pfi.4170270611.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
26

Leach, Ronald J. "Software metrics and software maintenance." Journal of Software Maintenance: Research and Practice 2, no. 2 (June 1990): 133–42. http://dx.doi.org/10.1002/smr.4360020204.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
27

Rossi, Jandira Ferreira de Jesus, Luis Carlos Passarini, and Leandro Innocentini Lopes de Faria. "Aplicação do software Zotero para apoiar a prática de Inteligência CompetitivaThe application of Zotero software as a tool to support the practice of Competitive Intelligence." RDBCI: Revista Digital de Biblioteconomia e Ciência da Informação 10, no. 1 (July 10, 2012): 1. http://dx.doi.org/10.20396/rdbci.v10i1.1893.

Повний текст джерела
Анотація:
Existem softwares que podem ser aplicados às várias fases do ciclo de Inteligência Competitiva – IC, como por exemplo, os que fazem a garimpagem de informações. Porém esses softwares são deficientes quando se trata de atividades realizadas entre as fases da coleta e análise que necessitam da leitura humana de documentos. Em geral, um software não consegue analisar dados puramente qualitativos nas fases do ciclo de IC. Por essa razão é de suma importância estudar softwares que tenham cunho colaborativo para saber até onde podem ser efetivos na prática de IC. Este artigo relata a aplicação do software Zotero por coletores e analistas de IC. Para averiguar seu apoio foi realizado um experimento simulando-o em um projeto de inteligência competitiva dividido em duas partes: sem o uso do software e com o uso do software. A simulação teve a participação de duas equipes locadas em diferentes pontos tendo a comunicação somente via web. O resultado indicou que com o uso do software foi possível comprovar que efetivamente o Zotero auxilia coletores e analistas em suas atividades.Abstract There are softwares which can be applied to various stages of the cycle of Competitive Intelligence - CI, such as, the ones which can sort the information. However, these softwares are defficient when it comes to activities to be carried out between the stages of collection and analysis which require the human reading of documents. Generally, a software cannot analize purely qualitative data in the stages of CI. Therefore, it is of paramount importance to study softwares which have a collaborative nature to know how far it can be effective in the practice of CI. This article reports the applicaiton of the software Zotero by CI collectors and analists. To assess its support, an simulating experiment was conducted in a CI project divided into two parts: one without the use of the software and the other with the use of the softwared. Two teams, located in different points and being connected only via web, participated in the simulation. The result indicated that with the use of the software it was possible to prove that Zotero effectivelly helps collectors and analysts in their activities.
Стилі APA, Harvard, Vancouver, ISO та ін.
28

Khan, Mohd Kamran. "LITERATURE REVIEW ON SOFTWARE COMPLEXITY, SOFTWARE USABILITY AND SOFTWARE DELIVERABILITY." International Journal of Advanced Research in Computer Science 9, no. 2 (April 20, 2018): 438–41. http://dx.doi.org/10.26483/ijarcs.v9i2.5853.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
29

Sudhaman, Parthasarathy. "Evaluating software quality using software metrics for a software product." International Journal of Information Systems and Change Management 5, no. 2 (2011): 180. http://dx.doi.org/10.1504/ijiscm.2011.041514.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
30

Notkin, David. "Software, Software Engineering and Software Engineering Research: Some Unconventional Thoughts." Journal of Computer Science and Technology 24, no. 2 (March 2009): 189–97. http://dx.doi.org/10.1007/s11390-009-9217-4.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
31

Phanthanithilerd, Nattapon, and Nakornthip Prompoon. "Verifying Software Requirements Characteristics Based on Rules Defined from Software Component Relationships." Lecture Notes on Software Engineering 4, no. 1 (2016): 27–33. http://dx.doi.org/10.7763/lnse.2016.v4.219.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
32

Frankel, James. "Software." Music Educators Journal 92, no. 5 (May 2006): 29. http://dx.doi.org/10.2307/3878495.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
33

Silva, Fabio. "Software." Journal of Skyscape Archaeology 7, no. 2 (February 18, 2022): 325–26. http://dx.doi.org/10.1558/jsa.22285.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
34

Bauer, William I. "Software." Music Educators Journal 92, no. 2 (November 2005): 25–26. http://dx.doi.org/10.2307/3400191.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
35

Huffman, Valarie. "Software." Music Educators Journal 92, no. 1 (September 2005): 28. http://dx.doi.org/10.2307/3400221.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
36

McEndree, Heather. "Software." Music Educators Journal 92, no. 4 (March 2006): 22. http://dx.doi.org/10.2307/3401105.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
37

Kersten, Fred. "Software." Music Educators Journal 92, no. 3 (January 2006): 22. http://dx.doi.org/10.2307/3401133.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
38

Kano, Yutaka, James L. Arbuckle, Roderick P. McDonald, Colin Fraser, Peter M. Bentier, Karl G. Jöreskog, G. Arminger, Michael W. Browne, and James H. Steiger. "Software." Behaviormetrika 24, no. 1 (January 1997): 85–125. http://dx.doi.org/10.2333/bhmk.24.85.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
39

DEAN, J. MICHAEL. "Software." Annals of Internal Medicine 103, no. 5 (November 1, 1985): 817. http://dx.doi.org/10.7326/0003-4819-103-5-817.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
40

Porter, Stephen. "Software." Health Informatics 2, no. 3 (September 1996): 160. http://dx.doi.org/10.1177/146045829600200312.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
41

TÜTÜNCÜ, Özkan. "Open Source Softwares and Jamovi Statistical Software." Anatolia: Turizm Araştırmaları Dergisi, December 1, 2023, 95–105. http://dx.doi.org/10.17123/atad.1404447.

Повний текст джерела
Анотація:
Bu çalışmada açık ve kapalı kaynak kodlu işletim sistemleri ve programlar değerlendirilmektedir. Bu kapsamda açık kaynak kodlu-Jamovi ve kapalı kaynak kodlu-SPSS istatistiksel yazılımları karşılaştırmalı olarak incelenmiştir. Açık kaynak kodlu işletim sistemleri ve istatistiksel yazılımlar daha şeffaf ve ücretsiz olsalar da araştırmalarda kapalı kaynak kodlu işletim sistemleri ve yazılımların egemen olduğu görülmektedir. Bilim insanları her zaman araştırmalarında şeffaflık, bağımsızlık ve tarafsızlığı savunmaktadır. Bununla birlikte, işletim sistemlerinin ve istatistiksel yazılımlarının seçiminde şeffaflığı ve tarafsızlığı göz ardı edebilmektedirler.
Стилі APA, Harvard, Vancouver, ISO та ін.
42

"Software: Software." Analytical Chemistry 68, no. 1 (January 1996): 41A. http://dx.doi.org/10.1021/ac961806d.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
43

"Software: Software." Analytical Chemistry 68, no. 7 (April 1996): 261A. http://dx.doi.org/10.1021/ac961887d.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
44

"Software: Software." Analytical Chemistry 68, no. 9 (May 1996): 319A. http://dx.doi.org/10.1021/ac961917c.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
45

"Software: Software." Analytical Chemistry 68, no. 13 (July 1996): 427A. http://dx.doi.org/10.1021/ac961981u.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
46

"Software: Software." Analytical Chemistry 68, no. 15 (August 1996): 485A. http://dx.doi.org/10.1021/ac962015e.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
47

"Software: Software." Analytical Chemistry 68, no. 17 (September 1996): 555A. http://dx.doi.org/10.1021/ac9620573.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
48

"Software: Software." Analytical Chemistry 68, no. 19 (October 1996): 617A. http://dx.doi.org/10.1021/ac962088y.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
49

"Software: Software." Analytical Chemistry 68, no. 23 (December 1996): 741A. http://dx.doi.org/10.1021/ac962164x.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
50

"Software: Software." Analytical Chemistry 69, no. 1 (January 1997): 37A. http://dx.doi.org/10.1021/ac9715074.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
Ми пропонуємо знижки на всі преміум-плани для авторів, чиї праці увійшли до тематичних добірок літератури. Зв'яжіться з нами, щоб отримати унікальний промокод!

До бібліографії