Gotowa bibliografia na temat „Computer software development”

Utwórz poprawne odniesienie w stylach APA, MLA, Chicago, Harvard i wielu innych

Wybierz rodzaj źródła:

Zobacz listy aktualnych artykułów, książek, rozpraw, streszczeń i innych źródeł naukowych na temat „Computer software development”.

Przycisk „Dodaj do bibliografii” jest dostępny obok każdej pracy w bibliografii. Użyj go – a my automatycznie utworzymy odniesienie bibliograficzne do wybranej pracy w stylu cytowania, którego potrzebujesz: APA, MLA, Harvard, Chicago, Vancouver itp.

Możesz również pobrać pełny tekst publikacji naukowej w formacie „.pdf” i przeczytać adnotację do pracy online, jeśli odpowiednie parametry są dostępne w metadanych.

Artykuły w czasopismach na temat "Computer software development"

1

Arakawa, Masamoto, Yoshiro Yamada i Kimito Funatsu. "Development of the computer software". Journal of Computer Aided Chemistry 6 (2005): 90–96. http://dx.doi.org/10.2751/jcac.6.90.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
2

MuftiSau, Aftab A. "Development, availability, and use of engineering computer programs". Canadian Journal of Civil Engineering 12, nr 1 (1.03.1985): 43–53. http://dx.doi.org/10.1139/l85-005.

Pełny tekst źródła
Streszczenie:
In the last decade, software engineering has emerged as a discipline very useful for computer application programmers in various engineering fields. In this paper the author considers the programming and management techniques for developing useful and commercially viable engineering software that may be used in the analysis and design of civil engineering projects. The issue of utilizing existing software effectively and efficiently is also discussed. At the conclusion of the presentation, several recommendations are made to encourage engineering software development in Canada. Key words: engineering, software engineering, software, computers, computer service bureaus, software directories.
Style APA, Harvard, Vancouver, ISO itp.
3

Lin, C. Y., i R. R. Levary. "Computer-aided software development process design". IEEE Transactions on Software Engineering 15, nr 9 (1989): 1025–37. http://dx.doi.org/10.1109/32.31362.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
4

Gentleman, W. Morven, i Marceli Wein. "Mass market computer for software development". ACM SIGSMALL/PC Notes 17, nr 3-4 (10.09.1991): 22–28. http://dx.doi.org/10.1145/140738.140760.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
5

Hsia, Pei, i David C. Rine. "Development of computer languages and software". Computer Languages 16, nr 2 (styczeń 1991): 109–11. http://dx.doi.org/10.1016/0096-0551(91)90001-p.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
6

Winzerling, Werner. "Linux und Freie Software". PROKLA. Zeitschrift für kritische Sozialwissenschaft 32, nr 126 (1.03.2002): 37–55. http://dx.doi.org/10.32387/prokla.v32i126.712.

Pełny tekst źródła
Streszczenie:
Since the great success of the operating system Linux, the development of Free and Open Source Software is broad discussed. This is also seen as the beginning of a new economic development. This paper examines, what makes Linux actually so significant for the computer industry. First Linux is critical evaluated and placed opposite the Microsoft operating systems. Than some substantial new influences on the development and production in the computer industry are worked out. On the one hand this are modifications in the production chain of computers and on the other hand network effects (externalization), which proceed from these products. On the basis of this new economic situation the Linux phenomenon is explained and it is shown from which the great importance of Microsoft in the computer industry results at present.
Style APA, Harvard, Vancouver, ISO itp.
7

Han, Su, i Xin Dai Zhang. "Research of the Computer-Aided-Translation Software". Advanced Materials Research 989-994 (lipiec 2014): 4637–42. http://dx.doi.org/10.4028/www.scientific.net/amr.989-994.4637.

Pełny tekst źródła
Streszczenie:
In recent years, with the rapid development of computers, computer-aided-translation software has been used more often, which can improve the efficiency and quality of translation. This paper analyzes the characteristics of the four commonly used computer-aided-translation software at home and abroad--SDL Trados, Déjà Vu, Wordfast and Yaxin in satisfying different users’ needs, points out their characteristics and provides reference for those who are interested in computer-aided-translation technology.
Style APA, Harvard, Vancouver, ISO itp.
8

Schwan, Karsten, i Anita K. Jones. "Flexible software development for multiple computer systems". IEEE Transactions on Software Engineering SE-12, nr 3 (marzec 1986): 385–401. http://dx.doi.org/10.1109/tse.1986.6312881.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
9

Gosbee, John, i Eileen Ritchie. "Human-computer interaction and medical software development". Interactions 4, nr 4 (lipiec 1997): 13–18. http://dx.doi.org/10.1145/259330.259341.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
10

Thomson, Alan J., i Daniel L. Schmoldt. "Ethics in computer software design and development". Computers and Electronics in Agriculture 30, nr 1-3 (luty 2001): 85–102. http://dx.doi.org/10.1016/s0168-1699(00)00158-7.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.

Rozprawy doktorskie na temat "Computer software development"

1

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.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
2

Antia, Yezdi F. "Personal computer development system software architecture". Thesis, Virginia Polytechnic Institute and State University, 1985. http://hdl.handle.net/10919/104287.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
3

Ness, Paul Edward. "Creative software development : an empirical modelling framework". Thesis, University of Warwick, 1997. http://wrap.warwick.ac.uk/3059/.

Pełny tekst źródła
Streszczenie:
The commercial success of software development depends on innovation [Nar93a]. However, conventional approaches inhibit the development of innovative products that embody novel concepts. This thesis argues that this limitation of conventional software development is largely due to its use of analytical artefacts, and that other activities, notably Empirical Modelling and product design, avoid the same limitation by using creative artefacts. Analytical artefacts promote the methodical representation of familiar subjects whereas creative artefacts promote the exploratory representation of novel subjects. The subjects, constraints, environments and knowledge associated with a design activity are determined by the nature of its artefacts. The importance of artefacts was discovered by examining the representation of different kinds of lift system in respect of Empirical Modelling, product design and software development. The artefacts were examined by identifying creative properties, as characterized in the theory of creative cognition [FWS92], together with their analytical counterparts. The processes of construction were examined by identifying generative and exploratory actions. It was found that, in software development, the artefacts were analytical and the processes transformational, whereas, in Empirical Modelling and product design, the artefacts were both creative and analytical, and the processes exploratory. A creative approach to software development using both creative and analytical artefacts is proposed for the development of innovative products. This new approach would require a radical departure from the established ideas and principles of software development. The existing paradigm would be replaced by a framework based on Empirical Modelling. Empirical Modelling can be though of as a situated approach to modelling that uses the computer in exploratory ways to construct artefacts. The likelihood of the new paradigm being adopted is assessed by considering how it addresses the topical issues in software development.
Style APA, Harvard, Vancouver, ISO itp.
4

Algan, Fatih Tuğlular Tuğkan. "Test driven software development/". [s.l.]: [s.n.], 2005. http://library.iyte.edu.tr/tezler/master/bilgisayaryazilimi/T000412.pdf.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
5

Moland, Kathryn J. "An Effective Software Development Methodology for Quality Software Development in a Scheduling Department". NSUWorks, 1997. http://nsuworks.nova.edu/gscis_etd/731.

Pełny tekst źródła
Streszczenie:
The research described in this document represents work performed in the area of software development methodologies as it applied to quality software development in a scheduling department. It addressed traditional methods in software development, current trends in software development, in addition to quality and software development at various companies. The literature suggested a correlation between using a software development methodology and quality software. However, there was limited literature that measured quantitatively the correlation between the effectiveness of the software development methodology and quality software. A software development methodology was developed for the scheduling department of a government contractor company in Aiken, South Carolina based on its needs and emerging technologies. An instrument was utilized to measure the effectiveness of the developed methodology. The methodology was compared with two other methodologies: a standard methodology from the literature and the current method of software development in the scheduling department. A population of computer professionals was divided into three equal groups. Each group was asked to apply the methodology to the case study. Individuals in each group were asked to review the case study and software development methodology. Then using the instrument, the individuals were asked to evaluate the effectiveness of the software development methodology, thereby providing a means for evaluated effectiveness, without conducting years of testing. The responses of the three groups were compared to one another. The results indicated a significantly higher level of approval for those methodologies that guided the development activities, standardized the development process, and identified the development phases and deliverables. It was concluded that utilizing a software development methodology that guides, standardizes, and defines the development phases and deliverables will result in an improved software development process and software quality. Further investigation could validate the findings of this research. The results actually achieved from utilizing the methodology developed for the scheduling department compared with the results achieved from utilizing some other methodology could further validate these research findings. Additional research could examine, over an extended time period, the success of the software development process and software quality of those projects utilizing the methodology described in this dissertation.
Style APA, Harvard, Vancouver, ISO itp.
6

Knapp, Chris H. "Unlocking test-driven development". [Denver, Colo.] : Regis University, 2006. http://165.236.235.140/lib/CKnapp2006.pdf.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
7

Abbas, Noura. "Software quality and governance in agile software development". Thesis, University of Southampton, 2009. https://eprints.soton.ac.uk/158357/.

Pełny tekst źródła
Streszczenie:
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.
Style APA, Harvard, Vancouver, ISO itp.
8

Norman, Michael John. "SSDE : structured software development environment". Master's thesis, University of Cape Town, 1990. http://hdl.handle.net/11427/15899.

Pełny tekst źródła
Streszczenie:
Bibliography: pages 219-230.
Software engineers have identified many problem areas regarding the development of software. There is a need for improving system and program quality at design level, ensuring that design costs remain within the budget, and increasing the productivity of designers. Structured Software Development Environment (SSDE) provides the system designer with an interactive menu-driven environment, and a framework within which he can conveniently express and manipulate his proposed solution. This representation is in terms of both a conceptual model and a detailed software logic definition. Thus SSDE provides tools for both high-level (or logical) and low-level (or physical) design. It allows a user to follow his own preferred methodology rather than restricting him to one specific strategy. SSDE builds and maintains databases that record all design decisions. It provides the system designer with a mechanism whereby systems can easily be modified and new systems can evolve from similar existing systems. There are several auxiliary facilities as productivity aids. SSDE generates PASCAL code for low-level design constructs, ·full documentation of both the high- and low-level designs for inclusion in the project file, as well as a skeleton manual. The system was evaluated by a number of independent users. This exercise clearly demonstrated its success as an aid in expressing, understanding, manipulating and solving software development problems.
Style APA, Harvard, Vancouver, ISO itp.
9

Mäkäräinen, Minna. "Software change management processes in the development of embedded software /". Espoo [Finland] : Technical Research Centre of Finland, 2000. http://www.vtt.fi/inf/pdf/publications/2000/P416.pdf.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
10

Abdullahi, Abdille. "Component-based Software development". Thesis, Växjö University, School of Mathematics and Systems Engineering, 2008. http://urn.kb.se/resolve?urn=urn:nbn:se:vxu:diva-2335.

Pełny tekst źródła
Streszczenie:

Component-based Software development is a promising way to improve quality, time to market and handle the increasing complexity of software management. However, The component-based development is still a process with many problems, it is not well de_ned either from theoretical or practical point of view. This thesis gives a brief overview of Component-Based Software development and starts with brief historical evolution followed by a general explanation of the method. A detailed discussion of the underlying principles like components, component framework and compent system architecture are then presented. Some real world component stadards such as .net framework, CORBA CCM and EJB are given in detail. Finally, simple fille-sharing-program based on Apache's Avalon framework and another one based on .net framework are developed as a case study.

Style APA, Harvard, Vancouver, ISO itp.

Książki na temat "Computer software development"

1

Zelkowitz, Marvin V. Software development. London: Academic Press/Elsevier, 2008.

Znajdź pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
2

Freedman, Jeri. Software development. New York: Cavendish Square, 2015.

Znajdź pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
3

Wells, Timothy D. Dynamic Software Development. London: Taylor and Francis, 2002.

Znajdź pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
4

G, Siegel Stanley, red. Successful software development. Wyd. 2. Upper Saddle River, N.J: Prentice Hall, 2009.

Znajdź pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
5

G, Siegel Stanley, i Donaldson Scott E, red. Successful software development. Wyd. 2. Upper Saddle River, NJ: Prentice Hall PTR, 2001.

Znajdź pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
6

Coad, Peter. Advanced software development. [United States]: TELOS Corp., 1988.

Znajdź pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
7

J, Andriole Stephen, red. Software development tools. Princeton, N.J: Petrocelli Books, 1986.

Znajdź pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
8

D, Klein Ari, red. Computer software engineering research. New York: Nova Science Publishers, 2007.

Znajdź pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
9

Birrell, N. D. A practical handbook for software development. Cambridge: CUP, 1985.

Znajdź pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
10

1948-, Ould Martyn A., red. A practical handbook for software development. Cambridge [Cambridgeshire]: Cambridge University Press, 1985.

Znajdź pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.

Części książek na temat "Computer software development"

1

Dubey, SatyaKesh, Naina Narang, Parmendra Singh Negi i Vijay Narain Ojha. "Software Development". W SpringerBriefs in Electrical and Computer Engineering, 25–34. Singapore: Springer Singapore, 2017. http://dx.doi.org/10.1007/978-981-10-6280-3_4.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
2

Jadhav, Bobby. "Revolutionizing Software Development". W Lecture Notes in Computer Science, 233–37. Berlin, Heidelberg: Springer Berlin Heidelberg, 2002. http://dx.doi.org/10.1007/3-540-38093-0_16.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
3

Weik, Martin H. "software development process". W Computer Science and Communications Dictionary, 1610. Boston, MA: Springer US, 2000. http://dx.doi.org/10.1007/1-4020-0613-6_17654.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
4

Bjørner, Dines. "Software Development Graphs a unifying concept for software development?" W Lecture Notes in Computer Science, 1–9. Berlin, Heidelberg: Springer Berlin Heidelberg, 1986. http://dx.doi.org/10.1007/3-540-17179-7_1.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
5

Kästner, Christian, i Sven Apel. "Feature-Oriented Software Development". W Lecture Notes in Computer Science, 346–82. Berlin, Heidelberg: Springer Berlin Heidelberg, 2013. http://dx.doi.org/10.1007/978-3-642-35992-7_10.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
6

O’Regan, Gerard. "Software Design and Development". W Undergraduate Topics in Computer Science, 101–15. Cham: Springer International Publishing, 2022. http://dx.doi.org/10.1007/978-3-031-07816-3_6.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
7

O’Regan, Gerard. "Software Design and Development". W Undergraduate Topics in Computer Science, 61–74. Cham: Springer International Publishing, 2017. http://dx.doi.org/10.1007/978-3-319-57750-0_4.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
8

Levine, Diane E., John Mason i Jennifer Hadley. "Software Development and Quality Assurance". W Computer Security Handbook, 39.1–39.21. Hoboken, NJ, USA: John Wiley & Sons, Inc., 2015. http://dx.doi.org/10.1002/9781118851678.ch39.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
9

Floyd, Christiane. "Human Questions in Computer Science". W Software Development and Reality Construction, 15–27. Berlin, Heidelberg: Springer Berlin Heidelberg, 1992. http://dx.doi.org/10.1007/978-3-642-76817-0_2.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
10

Baldassarre, Maria Teresa, Vita Santa Barletta, Danilo Caivano i Michele Scalera. "Privacy Oriented Software Development". W Communications in Computer and Information Science, 18–32. Cham: Springer International Publishing, 2019. http://dx.doi.org/10.1007/978-3-030-29238-6_2.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.

Streszczenia konferencji na temat "Computer software development"

1

Han, Dan, Xiaojing Li, Jing Zhang, Guangyu Wang, Hua Deng i Lin Deng. "Research and Application of Software Development Model in Computer Software Development". W ICISS 2022: 2022 the 5th International Conference on Information Science and Systems. New York, NY, USA: ACM, 2022. http://dx.doi.org/10.1145/3561877.3561879.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
2

Liebenberg, Janet, i Vreda Pieterse. "Career Goals of Software Development Professionals and Software Development Students". W CSERC '16: Computer Science Education Research Conference 2016. New York, NY, USA: ACM, 2016. http://dx.doi.org/10.1145/2998551.2998556.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
3

Shao, Bin, i Xin Li. "How to Select Development Language in Computer Software Development". W International Conference on Education, Management and Information Technology. Paris, France: Atlantis Press, 2015. http://dx.doi.org/10.2991/icemit-15.2015.28.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
4

Wu, Jie. "Application and development trend of Computer Software development technology". W 2021 International Conference on Computer, Internet of Things and Control Engineering (CITCE). IEEE, 2021. http://dx.doi.org/10.1109/citce54390.2021.00014.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
5

Mohan Garg, Rachit, i Kapil Kumar. "Metrics for Effective Software Development using Component based Software Engineering". W International Conference on Computer Applications — Computer Applications - II. Singapore: Research Publishing Services, 2010. http://dx.doi.org/10.3850/978-981-08-7304-2_1453.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
6

Far, Behrouz. "Software Reliability Engineering for Agile Software Development". W 2007 Canadian Conference on Electrical and Computer Engineering. IEEE, 2007. http://dx.doi.org/10.1109/ccece.2007.178.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
7

Shi, Yejia. "Application of Computer Software Technology in Plant Protection Software Development". W 2016 2nd International Conference on Materials Engineering and Information Technology Applications (MEITA 2016). Paris, France: Atlantis Press, 2017. http://dx.doi.org/10.2991/meita-16.2017.91.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
8

Rus, Teodor, i Cuong Bui. "Software Development for Non-Expert Computer Users". W Annual International Conference on Cloud Computing and Virtualization (CCV 2010). Global Science and Technology Forum, 2010. http://dx.doi.org/10.5176/978-981-08-5837-7_165.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
9

Hongju, Chen, i Wang Qing. "Computer Software Development Based on Hierarchical Technology". W 2016 Eighth International Conference on Measuring Technology and Mechatronics Automation (ICMTMA). IEEE, 2016. http://dx.doi.org/10.1109/icmtma.2016.48.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
10

Samuel, Selvakumar, Kesava Pillai Rajadorai i Vazeerudeen A. "Software Engineering Strategies for Mobile Software Development In View of Current Development Scenario – A Road Map". W International Conference on Computer Applications — Computer Applications - I. Singapore: Research Publishing Services, 2010. http://dx.doi.org/10.3850/978-981-08-7618-0_1622.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.

Raporty organizacyjne na temat "Computer software development"

1

Okawa, Soshi, Haruo Ishikawa i Yoon-Eui Nahm. Development of Computer Software Tool for Set-Based Design. Warrendale, PA: SAE International, maj 2005. http://dx.doi.org/10.4271/2005-08-0123.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
2

Möllenkamp, Andreas. Paradigms of Music Software Development. Staatliches Institut für Musikforschung, grudzień 2014. http://dx.doi.org/10.25366/2022.99.

Pełny tekst źródła
Streszczenie:
On the way to a more comprehensive and integrative historiography of music software, this paper proposes a survey of the main paradigms of music software development from the 1950s to the present. Concentrating on applications for music composition, production and performance, the analysis focusses on the concept and design of the human-computer-interaction as well as the implicit user.
Style APA, Harvard, Vancouver, ISO itp.
3

Gill, Janet A. Flight Control Computer Development Through Application of Software Safety Technology,. Fort Belvoir, VA: Defense Technical Information Center, październik 1995. http://dx.doi.org/10.21236/ada305293.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
4

Woyna, M. A., i C. R. Carlson. Evaluation of computer-aided software engineering tools for data base development. Office of Scientific and Technical Information (OSTI), luty 1989. http://dx.doi.org/10.2172/5698662.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
5

Luqi. Increasing the Practical Impact of Formal Methods for Computer-Aided Software Development,. Fort Belvoir, VA: Defense Technical Information Center, wrzesień 1995. http://dx.doi.org/10.21236/ada310438.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
6

Striuk, Andrii M. Software engineering: first 50 years of formation and development. [б. в.], grudzień 2018. http://dx.doi.org/10.31812/123456789/2880.

Pełny tekst źródła
Streszczenie:
The article analyzes the main stages of software engineering (SE) development. Based on the analysis of materials from the first SE conferences (1968-1969), it was determined how the software crisis prompted scientists and practitioners to join forces to form an engineering approach to programming. Differences in professional training for SE are identified. The fundamental components of the training of future software engineers are highlighted. The evolution of approaches to the design, implementation, testing and documentation of software is considered. The system scientific, technological approaches and methods for the design and construction of computer programs are highlighted. Analysis of the historical stages of the development of SE showed that despite the universal recognition of the importance of using the mathematical apparatus of logic, automata theory and linguistics when developing software, it was created empirically without its use. The factor that led practitioners to turn to the mathematical foundations of an SE is the increasing complexity of software and the inability of empirical approaches to its development and management to cope with it. The training of software engineers highlighted the problem of the rapid obsolescence of the technological content of education, the solution of which lies in its fundamentalization through the identification of the basic foundations of the industry. It is determined that mastering the basics of computer science is the foundation of vocational training in SE.
Style APA, Harvard, Vancouver, ISO itp.
7

Klymenko, Mykola V., i Andrii M. Striuk. Development of software and hardware complex of GPS-tracking. CEUR Workshop Proceedings, marzec 2021. http://dx.doi.org/10.31812/123456789/4430.

Pełny tekst źródła
Streszczenie:
The paper considers the typical technical features of GPS-tracking systems and their development, as well as an analysis of existing solutions to the problem. Mathematical models for the operation of hardware and software of this complex have been created. An adaptive user interface has been developed that allows you to use this complex from a smartphone or personal computer. Methods for displaying the distance traveled by a moving object on an electronic map have been developed. Atmega162-16PU microcontroller software for GSM module and GPS receiver control has been developed. A method of data transfer from a GPS tracker to a web server has been developed. Two valid experimental samples of GPS-trackers were made and tested in uncertain conditions. The GPS-tracking software and hardware can be used to monitor the movement of moving objects that are within the coverage of GSM cellular networks.
Style APA, Harvard, Vancouver, ISO itp.
8

Forney, Glenn P., i Leonard Y. Cooper. A plan for the development of the generic framework and associated computer software for a consolidated compartment fire model computer code. Gaithersburg, MD: National Bureau of Standards, 1987. http://dx.doi.org/10.6028/nbs.ir.86-3500.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
9

Kiv, Arnold E., Olexandr V. Merzlykin, Yevhenii O. Modlo, Pavlo P. Nechypurenko i Iryna Yu Topolova. The overview of software for computer simulations in profile physics learning. [б. в.], wrzesień 2019. http://dx.doi.org/10.31812/123456789/3260.

Pełny tekst źródła
Streszczenie:
The paper deals with the possibilities of using specialized (virtual labs and simulators, software for natural process simulation) and general (programming languages and libraries, spreadsheets, CAS) software in school researches. Such software as virtual labs, software for natural process simulation, programming languages and libraries in school researches can be used to simulate phenomena that cannot be learned in a school lab (for example, for modeling a radioactive decay or for demonstrating the states of relativistic mechanics). Also, virtual labs in school practice are usually used in those cases where students cannot perform an experiment in real labs. For example, it is convenient for distance learning. The using of programming languages and libraries in physics learning research requires both students’ physics research competencies and programming competencies. That is why using this software in physics classes can hardly be recommended. However, programming languages and libraries can become a powerful tool for the formation and development of research competencies of physics students in extracurricular learning activities. The implementation of the spreadheets and the CAS in school physics researches is the easiest and has its benefits.
Style APA, Harvard, Vancouver, ISO itp.
10

Velychko, Vladyslav Ye, Elena H. Fedorenko i Darja A. Kassim. Conceptual Bases of Use of Free Software in the Professional Training of Pre-Service Teacher of Mathematics, Physics and Computer Science. [б. в.], listopad 2018. http://dx.doi.org/10.31812/123456789/2667.

Pełny tekst źródła
Streszczenie:
The development of education is associated primarily with the use of ICT. A significant experience is already gained in how to use educational computer systems while new forms and methods of learning based on modern information technology are being developed and used. In relation to free software, a period when the quantity should translate into quality and an indicator of such translation is development of the concept of the introduction of free software in educational activities of universities. The proposed concept, let’s take Ukraine as an example, determines the main aim of introduction of free software in the training of pre-service of Mathematics, Physics and Computer Science; defines the objectives, measures, principles, the role and value of free software in the informatization process and results of its implementation.
Style APA, Harvard, Vancouver, ISO itp.
Oferujemy zniżki na wszystkie plany premium dla autorów, których prace zostały uwzględnione w tematycznych zestawieniach literatury. Skontaktuj się z nami, aby uzyskać unikalny kod promocyjny!

Do bibliografii