Готові списки джерел за темами / Agile software process models

Зміст

  1. Статті в журналах
  2. Дисертації
  3. Книги
  4. Частини книг
  5. Тези доповідей конференцій
  6. Звіти організацій

Добірка наукової літератури з теми "Agile software process models"

Автор: Grafiati
Опубліковано: 10 березня 2023

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

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

Ознайомтеся зі списками актуальних статей, книг, дисертацій, тез та інших наукових джерел на тему "Agile software process models".

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

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

Статті в журналах з теми "Agile software process models"

1

Ünver, Mahmut. "Software Process Models and Agile Method Applicability in Industry." International Journal of Trend in Scientific Research and Development Volume-3, Issue-1 (December 31, 2018): 1285–89. http://dx.doi.org/10.31142/ijtsrd20238.

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

Jain, Parita, Arun Sharma, and Laxmi Ahuja. "Software Maintainability Estimation in Agile Software Development." International Journal of Open Source Software and Processes 9, no. 4 (October 2018): 65–78. http://dx.doi.org/10.4018/ijossp.2018100104.

Повний текст джерела
Анотація:
Agile methodologies have gained wide acceptance for developing high-quality products with a quick and flexible approach. However, until now, the quality of the agile process has not been validated quantitatively. Quality being important for the software system, there is a need for measurement. Estimating different quality factors will lead to a quality product. Also, agile software development does not provide any precise models to evaluate maintainability. Therefore, there is a need for an algorithmic approach that can serve as the basis for estimation of maintainability. The article proposes an adaptive neuro-fuzzy inference system (ANFIS) model for estimating agile maintainability. Maintainability is one of the prominent quality factors in the case of agile development. The proposed model has been verified and found to be effective for assessing the maintainability of agile software.
Стилі APA, Harvard, Vancouver, ISO та ін.
3

Silas, Faki Agebee, Musa Yusuf, and Anah Hassan Bijik. "Hybridization of Class Responsibility Collaborators Model (HCRCM) with Function Point to enhance Project Estimation Cost in Agile Software Development." Circulation in Computer Science 2, no. 6 (July 20, 2017): 20–24. http://dx.doi.org/10.22632/ccs-2017-252-32.

Повний текст джерела
Анотація:
Estimating software cost in an agile system in terms of effort is very challenging. This is because the traditional models of software cost estimation do not completely fit in the agile development process. This paper presents a methodology to enhance the cost of project estimation in agile development. The hybridization adopts Class Responsibility Collaborators models with function point thereby boosting the agile software development estimation process. The study found out that adopting the Hybridized Class Responsibility Collaborator with function point has great improvement on cost estimation in agile software development.
Стилі APA, Harvard, Vancouver, ISO та ін.
4

A. Haraty, Ramzi, and Gongzhu Hu. "Software process models: a review and analysis." International Journal of Engineering & Technology 7, no. 2.28 (June 22, 2018): 390. http://dx.doi.org/10.14419/ijet.v7i2.28.14537.

Повний текст джерела
Анотація:
Modeling of software process has been a very challenging problem and constantly debated in the software development community in the past 30+ years, largely due to the complex nature of the software development process that involves not only the technical knowledge and skills but also many other factors, such as human, management, quality assessment, and cost. Although the situations of creating software differ greatly from one case to another, there are some common themes shared by many of the situations, and hence various software process models have been emerged to address these common themes. In this paper, we present a review of the software process models commonly used in practice, from traditional to agile, and assessment of these models with metrics and case studies.
Стилі APA, Harvard, Vancouver, ISO та ін.
5

A. Haraty, Ramzi, and Gongzhu Hu. "Software process models: a review and analysis." International Journal of Engineering & Technology 7, no. 2.29 (May 22, 2018): 325. http://dx.doi.org/10.14419/ijet.v7i2.29.13206.

Повний текст джерела
Анотація:
Modeling of software process has been a very challenging problem and constantly debated in the software development community in the past 30+ years, largely due to the complex nature of the software development process that involves not only the technical knowledge and skills but also many other factors, such as human, management, quality assessment, and cost. Although the situations of creating software differ greatly from one case to another, there are some common themes shared by many of the situations, and hence various software process models have been emerged to address these common themes. In this paper, we present a review of the software process models commonly used in practice, from traditional to agile, and assessment of these models with metrics and case studies.
Стилі APA, Harvard, Vancouver, ISO та ін.
6

van Driel, Willem Dirk, Jan Willem Bikker, Matthijs Tijink, and Alessandro Di Bucchianico. "Software Reliability for Agile Testing." Mathematics 8, no. 5 (May 13, 2020): 791. http://dx.doi.org/10.3390/math8050791.

Повний текст джерела
Анотація:
It is known that quantitative measures for the reliability of software systems can be derived from software reliability models, and, as such, support the product development process. Over the past four decades, research activities in this area have been performed. As a result, many software reliability models have been proposed. It was shown that, once these models reach a certain level of convergence, it can enable the developer to release the software and stop software testing accordingly. Criteria to determine the optimal testing time include the number of remaining errors, failure rate, reliability requirements, or total system cost. In this paper, we present our results in predicting the reliability of software for agile testing environments. We seek to model this way of working by extending the Jelinski–Moranda model to a “stack” of feature-specific models, assuming that the bugs are labeled with the features they belong to. In order to demonstrate the extended model, two use cases are presented. The questions to be answered in these two cases are: how many software bugs remain in the software and should one decide to stop testing the software?
Стилі APA, Harvard, Vancouver, ISO та ін.
7

Koch, Stefan, and Gerhard Turk. "Human Resource Related Problems in Agile and Traditional Software Project Process Models." International Journal of Information Technology Project Management 2, no. 2 (April 2011): 1–13. http://dx.doi.org/10.4018/jitpm.2011040101.

Повний текст джерела
Анотація:
This paper explores the impacts associated with different software process models on the staff. The main research question addressed is whether any process model leads to a higher satisfaction of staff, and less human resource related problems, including staff turnover or increased stress levels. This issue is empirically investigated using a set of projects from 15 different software developing companies. Agile-oriented models are not necessarily limited to small projects, but both groups showed nearly identical distributions for team size and duration. Interestingly, rigid-type models tend to exhibit higher effort estimations, and lower correctness in these estimations. Also customer satisfaction is slightly lower. With regard to human resource issues, the differences are not major overall, but there are some noticeable exceptions. In general, satisfaction and acceptance are higher at lower stress and overtime levels for agile-type project participants, but, interestingly and contrary to theory, people wish for more responsibility. Agile-type projects also enjoy some advantages in information sharing and communication, and in some quality aspects. Rigid-type projects show considerable higher abilities to cope with absence of personnel.
Стилі APA, Harvard, Vancouver, ISO та ін.
8

Rasheed, Aqsa, Bushra Zafar, Tehmina Shehryar, Naila Aiman Aslam, Muhammad Sajid, Nouman Ali, Saadat Hanif Dar, and Samina Khalid. "Requirement Engineering Challenges in Agile Software Development." Mathematical Problems in Engineering 2021 (May 8, 2021): 1–18. http://dx.doi.org/10.1155/2021/6696695.

Повний текст джерела
Анотація:
Agile software development has large success rate due to its benefits and promising nature but natively where the size of the project is small. Requirement engineering (RE) is crucial as in each software development life cycle, “Requirements” play a vital role. Though agile provides values to customer’s business needs, changing requirement, and interaction, we also have to face impediments in agile, many of which are related to requirement challenges. This article aims to find out the challenges being faced during requirement engineering of agile projects. Many research studies have been conducted on requirement challenges which are somehow biased, no suggestions are given to improve the agile development process, and the research does not highlight large-scale agile development challenges. Hence, this article covers all the challenges discussed above and presents a comprehensive overview of agile models from requirement engineering perspective. The findings and results can be very helpful for software industry to improve development process as well as for researchers who want to work further in this direction.
Стилі APA, Harvard, Vancouver, ISO та ін.
9

Sharma, Nidhi, and Manoj Wadhwa. "eXSRUP: Hybrid Software Development Model Integrating Extreme Programing, Scrum & Rational Unified Process." TELKOMNIKA Indonesian Journal of Electrical Engineering 16, no. 2 (November 1, 2015): 377. http://dx.doi.org/10.11591/tijee.v16i2.1627.

Повний текст джерела
Анотація:
<p>Software industries are progressively adopting the agile development practices of customized models such as Extreme Programming (XP) or Scrum or Rational Unified Process (RUP). Scrum and Extreme Programming (XP) are frequently used agile models, whereas Rational Unified Process (RUP) is one popular classic plan driven software development methodology. Both agile and plan driven models have their own merits &amp; demerits such as XP has good engineering practices, team collaboration and on the other hand weak documentation, poor performance in medium &amp; large scale projects. Scrum is based on project management practices. RUP model has some limitations such as impractical for small and fast paced projects, tendency to be over budgeted, condemn rapid changes in requirements. This research paper based on proposes hybrid framework eXSRUP by combining strengths of Scrum, XP and RUP by suppressing their limitations to produce high quality software.</p>
Стилі APA, Harvard, Vancouver, ISO та ін.
10

Rindell, Kalle, Sami Hyrynsalmi, and Ville Leppänen. "Fitting Security into Agile Software Development." International Journal of Systems and Software Security and Protection 9, no. 1 (January 2018): 47–70. http://dx.doi.org/10.4018/ijsssp.2018010103.

Повний текст джерела
Анотація:
Security objectives in software development are increasingly convergent with the business objectives, as requirements for privacy and the cost of security incidents call for more dependable software products. The development of secure software is accomplished by augmenting the software development process with specific security engineering activities. Security engineering, in contrast to the iterative and incremental software development processes, is characterized by sequential life cycle models: the security objectives are thus to be achieved by conflicting approaches. In this study, to identify the incompatibilities between the approaches, the security engineering activities from Microsoft SDL, the ISO Common Criteria and OWASP SAMM security engineering models are mapped into common agile software development processes, practices and artifacts.
Стилі APA, Harvard, Vancouver, ISO та ін.
Більше джерел

Дисертації з теми "Agile software process models"

1

Sabar, Suneel. "Software Process Improvement and Lifecycle Models in Automotive Industry." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2011. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-69640.

Повний текст джерела
Анотація:
The quality of a product depends on the quality of the underlying process is a well known fact. Software development organizations have been struggling to decrease their cost, increase their ROI, reduce time-to-market, and enhance the quality of their products. This all depends upon the improvement in the processes they are following inside their organizations. A number of software process improvement models exist in market, e.g., CMMI, SPICE and Automotive SPICE. But before an organization can improve its development and management processes, it is very important to know whether it is following the right processes. There exist a number of software development process models, mainly categorized into Traditional and Agile, which provide the step-by-step guidance to develop and manage the software projects.The current thesis presents a study of software process improvement models in automotive industry, their weaknesses and strengths and presents a comparison of how do they relate to each other. This thesis also explores some software development models which are more famous in automotive industry, and the applicability of process improvement models in conjunction with the Agile software development models. A case study was performed at an automotive software supplier organization to investigate the experience of combining Agile practices with organization’s company-tailored software development model that was incorporating Automotive SPICE standards.
Стилі APA, Harvard, Vancouver, ISO та ін.
2

Ittner, Jan. "Software assisted tailoring of process descriptions." Saarbrücken VDM Verlag Dr. Müller, 2006. http://d-nb.info/987892932/04.

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

Huo, Ming Computer Science &amp Engineering Faculty of Engineering UNSW. "A systematic framework of recovering process patterns from project enactment data as inputs to software process improvement." Publisher:University of New South Wales. Computer Science & Engineering, 2009. http://handle.unsw.edu.au/1959.4/43683.

Повний текст джерела
Анотація:
The study of the software development process is a relatively new research area but it is growing rapidly. This development process, also called 'the software life cycle' or 'the software process', is the methodology used throughout the industry for the planning, design, implementation, testing and maintenance that takes place during the creation of a software product. Over the years a variety of different process models have been developed. From the numerous process models now available, project managers need validation of the choice he/she has made for a software development model that he/she believes will provide the best results. Yet the quality software so sought after by software project managers can be enhanced by improving the development process through which it is delivered. Well tested, reliable evidence is needed to assist these project managers in choosing and planning a superior software process as well as for improving the adopted software process. While some guidelines for software process validation and improvement have been provided, such as CMMI, quantitative evidence is, in fact, scarce. The quantitative evidence sometimes may not be able to be obtained from high level processes that refer to a planned process model, such as a waterfall model. Furthermore, there has been little analysis of low level processes. These low level processes refer to the actions of how a development team follow a high level software process model to develop a software product. We describe these low level processes as project enactment. Normally there is a gap between the high level software process and the project enactment. In order to improve this software development process, this gap needs to be identified, measured and analyzed. In this dissertation, we propose an approach that examines the deviation between a planned process model and the project enactment of that plan. We measure the discrepancy from two aspects: consistency and inconsistency. The analytical results of the proposed approach, which include both qualitative and quantitative data, provide powerful and precise evidence for tailoring, planning and selecting any software process model. The entire approach is composed of four major phases: 1) re-presentation of the planned process model, 2) pre-processing the low level process data, 3) process mining, and 4) analysis and comparison of the recovered process model and planned process model. We evaluate the proposed approach in three case studies: a small, a medium, and a large-sized project obtained from an industrial software development organization. The appropriate data on low level processes is collected and our approach is then applied to these projects individually. From each case study we then performed a detailed analysis of the inconsistencies that had surfaced as well as the consistencies between the plan and the enactment models. An analysis of the inconsistencies revealed that several 'agile' practices were introduced during the project's development even though the planned process model was initially based on 'ISO-12207' instead of the 'agile' method. In addition, our analysis identifies the patterns in the process that are frequently repeated. The outcome of the case studies shows that our approach is applicable to a range of software projects. The conclusions derived from these case studies confirmed that our approach could be used to enhance the entire software development process, including tailoring and assessment.
Стилі APA, Harvard, Vancouver, ISO та ін.
4

Koutsoumpos, Vasileios, and Iker Marinelarena. "Agile Methodologies and Software Process Improvement Maturity Models, Current State of Practice in Small and Medium Enterprises." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-4284.

Повний текст джерела
Анотація:
Abstract—Background: Software Process Improvement (SPI) maturity models have been developed to assist organizations to enhance software quality. Agile methodologies are used to ensure productivity and quality of a software product. Amongst others they are applied in Small and Medium – sized Enterprises (SMEs). However, little is known about the combination of Agile methodologies and SPI maturity models regarding SMEs and the results that could emerge, as all the current SPI models are addressed to larger organizations and all these improvement models are difficult to be used by Small and Medium – sized firms. Combinations of these methodologies could lead to improvement in the quality of the software products, better project management methodologies and organized software development framework. Objectives: The aim of this study is to identify the main Agile methodologies and SPI maturity models applied in SMEs, the combinations of these methodologies, and the results that could emerge. Through these combinations, new software development frameworks are proposed. What is more, the results of this study can be used as a guide with the appropriate combination for each SME, as a better project management methodology or as improvement in the current software engineering practices. Methods: A Systematic Literature Review was conducted, resulting in 71 selected relevant papers ranging from 2001 to 2013. Besides, a survey has been performed from June 2013 to October 2013, including 49 participants. Results: Seven Agile methodologies and six different SPI maturity models were identified and discussed. Furthermore, the combination of eight different Agile methodologies and Software Process Improvement maturity models is presented, and as well as their benefits and drawbacks that could emerge in Small and Medium – sized firms. Conclusion: The majority of the Agile methodologies and SPI maturity models are addressed to large or very large enterprises. Thus, little research has been conducted for SMEs. The combinations of the Agile methodologies and SPI maturity models are usually performed in experimental stages. However, it has been observed that such type of combination could present numerous benefits, which can also be applicable in SMEs as well. The combinations that are most common are the CMMI and XP, CMMI and Scrum, CMMI and Six Sigma, and the PRINCE2 and DSDM.
0034-636835645
Стилі APA, Harvard, Vancouver, ISO та ін.
5

Dreiseitel, Jiří. "Agilní metody vývoje software." Master's thesis, Vysoké učení technické v Brně. Fakulta informačních technologií, 2015. http://www.nusl.cz/ntk/nusl-264956.

Повний текст джерела
Анотація:
The thesis deals with basic principles of agile software development and describes their advantages compared to the traditional approach. Siemens, s.r.o in Brno uses combination of Scrum and Kanaban as part of organizational processes, therefore the thesis focuses mainly on the method Scrum, Kanban, Scrum-ban and compares these methods with each other. The thesis also analyzes the existing project and results were consulted with the representative of the Siemens company together with the proposals for improvement. JIRA plugin was designed and implemented base on our mutual agreement. This module extends the current tool for analyzing agile projects, this leads to better support of decision making in the context of agile processes. Benefits and further upgrades are consulted at the end of the thesis.
Стилі APA, Harvard, Vancouver, ISO та ін.
6

Laanti, M. (Maarit). "Agile Methods in large-scale software development organizations:applicability and model for adoption." Doctoral thesis, Oulun yliopisto, 2013. http://urn.fi/urn:isbn:9789526200347.

Повний текст джерела
Анотація:
Abstract Agile methods have proven to be beneficial in small organizations, and there has also been growing interest in using these methods in large organizations. This dissertation analyzes what agility and agile development are and creates a framework for using those methods in large organizations. The work starts with a Concept Analysis of Agile Software Development and agile-in-large. The theoretical part also reflects the necessary background of Complex Adaptive Systems, Lean Thinking, and Learning Organizations. Then a model of an Agile Enterprise is defined and a Framework for Organizational Development and putting Agile Methods into use in large software development organizations is presented. Large development organizations consist of many levels. It is not enough to use Agile Methods on a certain level only, e.g., on the lowest level, but all levels need to change and adapt to the new way of working. Failure to do so leads to several unwanted consequences, which are described. One possible large-scale Agile Framework is described and analyzed. The usage of Agile Methods on a large scale is validated by quantitative studies. The level of success of using an Agile Framework on a large scale is dictated by how much the same framework for operation is shared within the organization, as partial transformation leads to confusion. But smaller successes can lead into organizational learning. The framework that is proposed can be used to further enhance agility. In this way large-scale agility can be seen as a never-ending series of systematic improvements of the enterprises’ Agile Aspects
Tiivistelmä Tämä väitöskirja tarkastelee suurten organisaatioiden tarpeisiin sopivien ketterien prosessimallien mallinnusta ja käyttöä. Ketterät menetelmät on todettu hyödyllisiksi pienissä ohjelmistoyrityksissä, joten myös isoissa yrityksissä on herännyt kiinnostus ketteriä menetelmiä kohtaan. Työ alkaa ketterien menetelmien käsiteanalyysillä, ja jatkuu määrittelemällä mitä ketteryys laajassa mittakaavassa on. Teoriaosuus käsittelee taustatiedot kompleksisista sopeutuvista järjestelmistä, lean-ajattelusta ja oppivista organisaatioista tarvittavin osin. Tämän jälkeen määritellään ketterän yrityksen käsite ja esitetään malli laajamittaiselle ketteryydelle. Suurissa kehitysorganisaatioissa on monta tasoa. Ei riitä, että ketteriä menetelmiä käytetään vain jollakin (yleensä alimmalla) tasolla, vaan kaikkien organisaation tasojen täytyy sopeutua uuteen toimintatapaan. Mikäli näin ei tapahdu, saattaa tuloksena olla joukko ei-toivottavia seurauksia, jotka on myös kuvattu tässä työssä. Työssä on esitetty ja analysoitu mahdollinen malli suuren yrityksen ketteryyden toteuttamiseksi. Ketterien menetelmien käyttö isossa yrityksessä on validoitu kvantitatiivisin menetelmin. Isoissa yrityksissä ketteristä menetelmistä saatu hyöty on sidottu siihen miten hyvin koko organisaatio pystyy noudattamaan samaa ketterää toiminnan mallia – osittainen toimintatavan muutos johtaa toimintatapojen konflikteihin. Kuitenkin myös osittaiset onnistumiset voivat johtaa organisaation oppimiseen. Esitettyä mallia voidaan käyttää kehitettäessä toimintatapaa entisestään ketterämpään suuntaan. Tällä tavalla suuren organisaation ketteryys voidaan nähdä jatkuvana sarjana systemaattisia toimintatavan parannuksia, joista jokainen johtaa entistä ketterämpään toimintatapaan
Стилі APA, Harvard, Vancouver, ISO та ін.
7

Nascimento, Gustavo Vaz. "Um modelo de referência para o desenvolvimento ágil de software." Universidade de São Paulo, 2007. http://www.teses.usp.br/teses/disponiveis/55/55134/tde-07052008-170413/.

Повний текст джерела
Анотація:
A crescente procura por software de qualidade vem causando grande pressão sobre as empresas que trabalham com desenvolvimento de software. As entregas de produtos de software dentro do prazo e custo previstos vêm se tornando, a cada dia, um diferencial importante nesse ramo de atividade. Nesse sentido, as empresas procuram por metodologias que propiciem o desenvolvimento de produtos com qualidade, e que respeitem o custo e prazo previstos. Em resposta a essas necessidades, surgiu uma nova classe de metodologias de desenvolvimento de software, conhecidas como metodologias ágeis. Este trabalho apresenta um estudo realizado sobre as principais características existentes nessa nova classe de metodologias. Uma análise permitiu a identificação de semelhanças e diferenças existentes entre elas, o que possibilitou a criação de um modelo de referência para o desenvolvimento ágil de software. O modelo foi utilizado em uma avaliação de processo baseada no modelo de avaliação da ISO/IEC 15504. A avaliação permitiu a identificação de forças e fraquezas no processo avaliado e possibilitou a definição de ações de melhoria para que o processo avaliado se assemelhasse à um processo de desenvolvimento ágil. Palavra-chave: Metodologia ágil de desenvolvimento. Modelo de referência. Processo de desenvolvimento de software. Avaliação de processo de software
The vast demand for software with quality is causing a great pressure on the companies which work with software development. The delivery of software products within the schedule and cost is becoming, every day, an important issue in this area. Therefore, companies are seeking for methodologies to develop products with quality, within the timetable and the cost. Considering these needs, it became a new class of software development methodologies, known as agile methodologies. This research shows a work done upon the main existing characteristics in this new class of methodologies. An analysis allowed the identification of the existing similarities and differences among them, which it made possible to create a new reference model for agile software development. The agile model was used in process assessment based on assessment model from ISO/IEC 15504. The assessment alowed a identification of power and weakness on the process and alowed a definition of improvement action to the process with the intention of to approach the agile development process
Стилі APA, Harvard, Vancouver, ISO та ін.
8

Ress, Ana Paula Pereira de Moraes. "Um estudo sobre a integração CMMI e desenvolvimento ágil." Universidade de São Paulo, 2013. http://www.teses.usp.br/teses/disponiveis/3/3136/tde-14102014-151014/.

Повний текст джерела
Анотація:
É possível notar no trabalho diário das empresas que a pressão por diminuir o prazo de entrega dos softwares ainda é uma realidade. Neste contexto, empresas adotam técnicas de desenvolvimento ágil de software, implementando entregas constantes e estabelecendo ciclos iterativos e curtos no processo de desenvolvimento de software. Mas, se por um lado estas técnicas visam inovar e reduzir tempo de desenvolvimento, por outro, as empresas sentem-se pressionadas a adotar a forma tradicional de manter a qualidade de software. Neste ponto, o CMMI se apresenta como um modelo de maturidade de reconhecimento mundial e é classificado na abordagem tradicional por pregar grande formalismo e foco no processo. A abordagem ágil coloca que os indivíduos e suas interações têm maior importância que os processos e as ferramentas e que ser adaptável às mudanças é mais importante do que seguir a rigor o planejado. Ao integrar estes dois modelos de abordagens distintas espera-se que as práticas ágeis possam ajudar organizações maduras a se tornarem mais flexíveis. Com o intuito de averiguar esta integração, utilizou-se o método de pesquisa de estudo de caso, de modo a se aprofundar nas empresas que possuem certificação CMMI e decidiram adotar o modelo de desenvolvimento ágil. O objetivo é levantar como estas empresas resolveram os pontos de conflito da abordagem tradicional e ágil, de modo a se tornarem mais eficazes. O estudo ainda contém um quadro de integração CMMI versus desenvolvimento ágil de modo a elencar os pontos que merecem maior atenção e esforço de adaptação, visando a concretização da integração.
It\'s possible to notice in the daily work of companies that pressure by decreasing the delivery of software is still a reality. It is in this context that companies adopt the techniques of agile software development, implementing and establishing constant deliveries and short iterative cycles in the process of software development. But if on the one hand these techniques aim to innovate and reduce development time, on the other, companies feel pressured to adopt the traditional way of maintaining the quality of software. At this point, the CMMI is presented as maturity model worldwide recognition, classified in the traditional approach for preaching extensive formalism and focus on the process, as the agile approach puts individuals and their interactions is more important than processes and tools, where being adaptable changes is more important than following the strict what was planned. By integrating these two models of different approaches, it is expected that agile practices can help organizations mature to become more flexible. In order to investigate this integration is that this study uses the research method of case study so as to deepen the companies that have decided to adopt CMMI and agile development model. The goal is to raise as these companies solved the trouble spots of the traditional approach and agile in order to become more effective. The study also contain a framework for integrating CMMI vs. Agile development in order to list the points that deserve more attention and effort to adapt in order to achieve integration.
Стилі APA, Harvard, Vancouver, ISO та ін.
9

Cintra, Caroline Carbonell. "A implementação de um processo de engenharia de requisitos baseado no Processo Unificado da Rational (RUP) alcançando nível 3 de Maturidade da Integração de Modelos de Capacidade e Maturidade (CMMI) incluindo a utilização de práticas de métodos ágeis." reponame:Biblioteca Digital de Teses e Dissertações da UFRGS, 2006. http://hdl.handle.net/10183/8128.

Повний текст джерела
Анотація:
Este trabalho descreve a definição e institucionalização de um processo de engenharia de requisitos que está em conformidade com as áreas de processo do CMMI (Capability Maturity Model) de Gerência de Requisitos e Desenvolvimento de Requisitos e cujos componentes (atividades, papéis, produtos de trabalho) são baseados em RUP (Rational Unified Process). A principal contribuição deste estudo é a definição de um processo de engenharia de requisitos baseado em abordagens de desenvolvimento diferenciadas, que foi implantado em uma organização específica, com foco em praticidade, eficiência e retorno do investimento. A implantação do processo em projetos reais permitiu sua experimentação, avaliação e refinamento, validando as alternativas de integração utilizadas para empregar as abordagens de desenvolvimento escolhidas. Complementando o processo proposto, como decorrência do foco em eficiência, são consideradas possibilidades de emprego de práticas de métodos ágeis na execução do processo, com o intuito de aumentar a produtividade do mesmo, sustentando sua garantia de qualidade. O processo proposto é descrito, do método de concepção aos passos envolvidos e artefatos gerados em cada atividade. Também são comentadas as etapas e áreas de trabalho envolvidas na institucionalização do trabalho.
This research depicts the definition and institutionalization of a requirements engineering process which is in conformance to CMMI (Capability Maturity Model) Requirements Management and Requirements Development process areas. The proposed process components (activities, roles, work products) are based on Rational Unified Process (RUP) process framework. The proposed process main contribution is the definition of a requirements engineering process, leveraging such diverse development approaches, which was implemented in a specific organization, focusing on practicality, efficiency and return on investment. Implementing such process in real projects has promoted its experimentation, evaluation and refinement, validating the integration alternatives used to bring together the chosen development approaches. The possibility of employing agile methods practices through the process execution is discussed, aiming at increasing the process productivity, while assuring product quality. The proposed process details are described, from method conception to each activity steps and generated artifacts. The process institutionalization phases and work areas are also commented.
Стилі APA, Harvard, Vancouver, ISO та ін.
10

Řezáč, Jakub. "Zdokonalování procesů vývoje software." Master's thesis, Vysoké učení technické v Brně. Fakulta informačních technologií, 2009. http://www.nusl.cz/ntk/nusl-236682.

Повний текст джерела
Анотація:
This master's thesis is oriented on software development processes improvement techniques. It presents modern approaches of process development and analyses problems of their management and usage in various life cycle phases. In connection with these techniques it brings draft of support tool, which increases automatization of processes development with pertinent cooperation with other tools, as one of presumptions of improvement of their quality.
Стилі APA, Harvard, Vancouver, ISO та ін.
Більше джерел

Книги з теми "Agile software process models"

1

editor, Margaria-Steffen Tiziana 1964, ed. Process design for natural scientists: An agile model-driven approach. Heidelberg: Springer, 2014.

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

Salo, Outi. Enabling software process improvement in agile software development teams and organisations. [Espoo, Finland]: VTT Technical Research Centre of Finland, 2006.

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

Colomo-Palacios, Ricardo. Agile estimation techniques and innovative approaches to software process improvement. Hershey, PA: Information Science Reference, 2014.

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

Proudlock, Kimberley. Software process models: Establishing a sound approach to the software development process. Portsmouth: Portsmouth Polytechnic, School of Information Science, 1991.

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

Essential Scrum: A practical guide to the most popular agile process. Upper Saddle River, NJ: Addison-Wesley, 2012.

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

Ita, Richardson, and Ó. hAodha Mícheál 1969-, eds. Agile development in the Irish software industry: Models for change. Newcastle upon Tyne, UK: Cambridge Scholars Pub., 2009.

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

Hafedh, Mili, and SpringerLink (Online service), eds. Agile Business Rule Development: Process, Architecture, and JRules Examples. Berlin, Heidelberg: Springer-Verlag Berlin Heidelberg, 2011.

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

Lester, Neil. Assisting the software reuse process through classification and retrieval of software models. [s.l: The Author], 2000.

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

service), SpringerLink (Online, ed. Business Process Models. Change Management. Berlin, Heidelberg: Springer Berlin Heidelberg, 2013.

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

International Software Process Workshop (5th 1989 Kennebunkport, Me.). Proceedings of the 5th International Software Process Workshop: "Experience with software process models", Kennebunkport, Maine, USA, October 10-13, 1989. Edited by Perry Dewayne E, Rocky Mountain Institute of Software Engineering., Association for Computing Machinery, and IEEE Computer Society. Los Alamitos, Calif: IEEE Computer Society Press, 1990.

Знайти повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
Більше джерел

Частини книг з теми "Agile software process models"

1

Schmitt, Anna, Sven Theobald, and Philipp Diebold. "Comparison of Agile Maturity Models." In Product-Focused Software Process Improvement, 661–71. Cham: Springer International Publishing, 2019. http://dx.doi.org/10.1007/978-3-030-35333-9_52.

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

Visconti, Marcello, and Curtis R. Cook. "An Ideal Process Model for Agile Methods." In Product Focused Software Process Improvement, 431–41. Berlin, Heidelberg: Springer Berlin Heidelberg, 2004. http://dx.doi.org/10.1007/978-3-540-24659-6_31.

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

Bonacin, Rodrigo, Maria Cecília Calani Baranauskas, and Marcos Antônio Rodrigues. "An Agile Process Model for Inclusive Software Development." In Enterprise Information Systems, 807–18. Berlin, Heidelberg: Springer Berlin Heidelberg, 2009. http://dx.doi.org/10.1007/978-3-642-01347-8_67.

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

Poth, Alexander, Mario Kottke, and Andreas Riel. "Evaluation of Agile Team Work Quality." In Agile Processes in Software Engineering and Extreme Programming – Workshops, 101–10. Cham: Springer International Publishing, 2020. http://dx.doi.org/10.1007/978-3-030-58858-8_11.

Повний текст джерела
Анотація:
Abstract The maturity of organizations is measured with process assessment models like the ISO/IEC 33001. The product quality is aligned with internal and external product quality charactersitics based on models like the ISO/IEC 25010. With the shift from the Tailorism-driven process orientation to a more people centric organization, the two dimensions process and product quality have to be extened by the people or team quality dimension. The presented approach offers aspects for agile Team Work Quality (aTWQ), as well as related measurement indicators. The approach is evaluated in the large enterprise context of the Volkswagen AG. The indicators of aTWQ have been integrated and established in the agile tool box for a sustainable agile transition of the company.
Стилі APA, Harvard, Vancouver, ISO та ін.
5

Lamsellak, Hajar, Houda Metthahri, Mohammed Ghaouth Belkasmi, and Mohammed Saber. "Pre-planning Process Model in Agile Global Software Development." In Innovations in Smart Cities Applications Volume 5, 393–400. Cham: Springer International Publishing, 2022. http://dx.doi.org/10.1007/978-3-030-94191-8_31.

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

Zorzetti, Maximilian, Ingrid Signoretti, Eliana Pereira, Larissa Salerno, Cassiano Moralles, Cássio Trindade, Michele Machado, Ricardo Bastos, and Sabrina Marczak. "A Practice-Informed Conceptual Model for a Combined Approach of Agile, User-Centered Design, and Lean Startup." In Product-Focused Software Process Improvement, 142–50. Cham: Springer International Publishing, 2020. http://dx.doi.org/10.1007/978-3-030-64148-1_9.

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

Hayashi, Kengo, and Mikio Aoyama. "A Portfolio-Driven Development Model and Its Management Method of Agile Product Line Engineering Applied to Automotive Software Development." In Product-Focused Software Process Improvement, 88–105. Cham: Springer International Publishing, 2020. http://dx.doi.org/10.1007/978-3-030-64148-1_6.

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

Tuncel, Doruk, Christian Körner, and Reinhold Plösch. "Setting the Scope for a New Agile Assessment Model: Results of an Empirical Study." In Lecture Notes in Business Information Processing, 55–70. Cham: Springer International Publishing, 2021. http://dx.doi.org/10.1007/978-3-030-78098-2_4.

Повний текст джерела
Анотація:
AbstractAgile software development methods have been increasingly adopted by many organizations at different organizational levels. Whether named agile adoption, agile transition, agile transformation, digital transformation or new ways of working, the success of embracing this change process mostly remains uncertain. This is primarily because there are many ways of evaluating success. Based on the existing agile assessment models, we developed a model of principles with associated practice clusters that serves as a core for a new agile assessment model that is capable of assessing agile organizations at different scale. Towards our ultimate goal to establish a lightweight, context-sensitive agile maturity model, we validated our initial findings in an expert interview study to identify improvement points, and ensure the at hand model’s applicability, coherence and relevance. The results of the interview study show that the structure as well as the content of our assessment model fits with the experts’ expectations and experience.
Стилі APA, Harvard, Vancouver, ISO та ін.
9

Ito, Takayuki, Naoki Fukuta, and Mark Klein. "An Approach to Sharing Business Process Models in Agile-Style Global Software Engineering." In Studies in Computational Intelligence, 155–70. Berlin, Heidelberg: Springer Berlin Heidelberg, 2011. http://dx.doi.org/10.1007/978-3-642-21375-5_13.

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

Salameh, Abdallah, and Julian M. Bass. "Spotify Tailoring for Architectural Governance." In Agile Processes in Software Engineering and Extreme Programming – Workshops, 236–44. Cham: Springer International Publishing, 2020. http://dx.doi.org/10.1007/978-3-030-58858-8_24.

Повний текст джерела
Анотація:
Abstract Organisations usually tailor Agile methods to fit their needs best. Spotify has developed its own Agile culture to facilitate software development for hundreds of developers across multiple cities. The Spotify model has become influential among agile proponents and hence formed the basis of methods used in other organisations. We have identified a lack of research into agile architecture using the Spotify model. To explore How can architectural governance increase the autonomy of teams when using the Spotify model?, an intervention embedded case study was conducted in a multinational FinTech organisation, using the Spotify model. New processes were introduced by developing and evaluating an approach to Agile architectural governance. This approach incorporates a structural change and a change management process. We conducted 6 semi-structured open-ended interviews and direct observations of Agile practices. The collected data was analysed using Thematic Analysis and informed by some Grounded Theory techniques. The practitioners in our study report benefits of this evaluated approach. These benefits include transforming architectural based decision into decentralised based decision-making, strengthening the autonomy of squads through aligning architectural based decisions, sharing the architectural knowledge among the squads, and other benefits. We identify the characteristics and benefits of our evaluated approach to Agile architectural governance using the Spotify model. Also, we identify guidelines and challenges for those wishing to adopt this approach.
Стилі APA, Harvard, Vancouver, ISO та ін.

Тези доповідей конференцій з теми "Agile software process models"

1

Nyfjord, Jaana, and Mira Kajko-Mattsson. "Commonalities in Risk Management and Agile Process Models." In International Conference on Software Engineering Advances (ICSEA 2007). IEEE, 2007. http://dx.doi.org/10.1109/icsea.2007.22.

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

Maqsood, H., and Andrea Bondavalli. "Agility of Security Practices and Agile Process Models: An Evaluation of Cost for Incorporating Security in Agile Process Models." In 15th International Conference on Evaluation of Novel Approaches to Software Engineering. SCITEPRESS - Science and Technology Publications, 2020. http://dx.doi.org/10.5220/0009356403310338.

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

Fontana, Rafaela Mantovani, Sheila Reinehr, and Andreia Malucelli. "Progressive Outcomes: is it a handy approach to support agile methods process improvement?" In XIV Simpósio Brasileiro de Qualidade de Software. Sociedade Brasileira de Computação - SBC, 2015. http://dx.doi.org/10.5753/sbqs.2015.15216.

Повний текст джерела
Анотація:
While software engineering relies on reference models, such as CMMI-DEV, to improve its processes and gain maturity; agile teams that wish to sustain agility demand other guidelines to drive improvements. To address this need, in a previous study we have proposed the Progressive Outcomes Framework as a result of a research about how real agile teams evolve in agility. Although we could describe agile maturing mechanisms, we lacked a perception of how handy out approach would be to guide improvements. The objective of this study was, thus, to identify agile practitioners’ perception about the framework. We performed a survey with agile practitioners in Brazilian conferences and analyzed collected data using descriptive statistics. Results show that agile practitioners feel comfortable in following non- prescriptive guidelines, but they still lack guidance on how to improve in agility.
Стилі APA, Harvard, Vancouver, ISO та ін.
4

Fontana, Rafaela Mantovani, Sheila Reinehr, and Andreia Malucelli. "Maturity in Agile Software Development." In XV Simpósio Brasileiro de Qualidade de Software. Sociedade Brasileira de Computação - SBC, 2016. http://dx.doi.org/10.5753/sbqs.2016.15149.

Повний текст джерела
Анотація:
This paper summarizes the main objectives, research approach, and contributions of the doctoral dissertation named as “Maturity in Agile Software Development”. It was developed in the Graduate Program in Informatics of the Pontifical Catholic University of Parana, from 2013 to 2015. The study was ́developed with the objective to characterize maturity in agile software development, as a means to guide agile teams in software process improvements. Our results contribute to the software engineering body of knowledge by showing a picture of maturity in agile teams that goes beyond defining and controlling processes, as usually stated by reference models.
Стилі APA, Harvard, Vancouver, ISO та ін.
5

De Silva, Ian J., Sanjai Rayadurgam, and Mats P. E. Heimdahl. "A reference model for simulating agile processes." In ICSSP '15: International Conference on Software and Systems Process 2015. New York, NY, USA: ACM, 2015. http://dx.doi.org/10.1145/2785592.2785615.

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

Montenegro, Carlos, Rodrigo Fonseca, and Andres Larco. "IT process improvement: Developing an agile model using the DSR approach." In 2016 International Conference on Software Process Improvement (CIMPS). IEEE, 2016. http://dx.doi.org/10.1109/cimps.2016.7802807.

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

"Enhance Your Model-driven Modernization Process with Agile Practices." In 1st International Workshop in Software Evolution and Modernization. SciTePress - Science and and Technology Publications, 2013. http://dx.doi.org/10.5220/0004588800950102.

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

Doherty, Bernard, Andrew Jelfs, Aveek Dasgupta, and Patrick Holden. "Defect Analysis in Large Scale Agile Development: Quality in the Agile Factory Model." In 2016 Joint Conference of the International Workshop on Software Measurement and the International Conference on Software Process and Product Measurement (IWSM-MENSURA). IEEE, 2016. http://dx.doi.org/10.1109/iwsm-mensura.2016.034.

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

Alfonso, Maria Isabel, and Antonio Botia. "An Iterative and Agile Process Model for Teaching Software Engineering." In Proceedings. 18th Conference on Software Engineering Education & Training. IEEE, 2005. http://dx.doi.org/10.1109/cseet.2005.5.

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

Sadaf, Sameera, Shama Iqbal, Aliya Saba, and Md KamarMohsin. "An extended adaptive process model for agile software development methodology." In 2017 International Conference on Intelligent Computing, Instrumentation and Control Technologies (ICICICT). IEEE, 2017. http://dx.doi.org/10.1109/icicict1.2017.8342770.

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

Звіти організацій з теми "Agile software process models"

1

Krhutová, Lenka, Petr Šaloun, Kamila Vondroušová, Marcela Dabrowská, Zdeněk Velart, David Andrešič, and Miroslav Paulíček. Výzkum a vývoj podpůrných sítí a informačních systémů pro neformální pečující o osoby po cévních mozkových příhodách. Ostravská univerzita, 2021. http://dx.doi.org/10.15452/vsouhrntacr.2021.

Повний текст джерела
Анотація:
The summary research report describes and summarizes the goals, course and results of the TAČR–VISNEP project. The aim of the experimental development project was to create an information system (IS) for informal carers (ICs) for a person after stroke using modern information technologies in the technical and non-technical spheres of research. IS will allow users to obtain relevant, timely and interconnected information on support networks to prevent their possible social isolation and exclusion, physical and psychological exhaustion, health disorders and other risk factors in their difficult life situation. The purpose of IS is to contribute to improved awareness of ICs support systems across other long-term care providers, in particular public administration, general practitioners etc. The intent of the project was to create and verify a pilot model of IS in Moravian-Silesian Region, which can subsequently be applied in other regions and / or other target ICs groups. The presented results of the project are based on data obtained by research procedures of qualitative and quantitative methodology in the process of agile software development.
Стилі APA, Harvard, Vancouver, ISO та ін.
2

Klasky, Hilda B., Paul T. Williams, and Bennett Richard Bass. Proposal: Application of Agile Software Development Process in xLPR. Office of Scientific and Technical Information (OSTI), November 2012. http://dx.doi.org/10.2172/1062630.

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

Scacchi, Walt. Models of Software Evolution: Life Cycle and Process. Fort Belvoir, VA: Defense Technical Information Center, October 1987. http://dx.doi.org/10.21236/ada236120.

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

Penedo, Maria H. PSEE Architecture Report. Architectures and Models for Next Generation Process-based Software Engineering Environments. Fort Belvoir, VA: Defense Technical Information Center, February 1995. http://dx.doi.org/10.21236/ada291268.

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

Nguyen, Ba Nghiep, Xiaoshi Jin, Jin Wang, Jay Phelps, Charles L. Tucker III, Vlastimil Kunc, Satish K. Bapanapalli, and Mark T. Smith. Implementation of New Process Models for Tailored Polymer Composite Structures into Processing Software Packages. Office of Scientific and Technical Information (OSTI), February 2010. http://dx.doi.org/10.2172/973410.

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

Hadgu, Teklu, Brandon Keith Reynolds, Gordon John Appel, and Jason P. Garland. FY 18 Status Report on the Computing Systems for the Yucca Mountain Project TSPA-LA Models and Inventory of Software used for Process Models. Office of Scientific and Technical Information (OSTI), December 2018. http://dx.doi.org/10.2172/1489540.

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

TRW SYSTEMS GROUP REDONDO BEACH CA. PSEE Architecture Report. PSEE Architecture Report Attachment - Section 11. Architectures and Models for Next Generation Process-Based Software Engineering Environments. Fort Belvoir, VA: Defense Technical Information Center, February 1995. http://dx.doi.org/10.21236/ada293112.

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

Markova, Oksana M., Serhiy O. Semerikov, Andrii M. Striuk, Hanna M. Shalatska, Pavlo P. Nechypurenko, and Vitaliy V. Tron. Implementation of cloud service models in training of future information technology specialists. [б. в.], September 2019. http://dx.doi.org/10.31812/123456789/3270.

Повний текст джерела
Анотація:
Leading research directions are defined on the basis of self-analysis of the study results on the use of cloud technologies in training by employees of joint research laboratory “Сloud technologies in education” of Kryvyi Rih National University and Institute of Information Technology and Learning Aids of the NAES of Ukraine in 2009-2018: cloud learning technologies, cloud technologies of blended learning, cloud-oriented learning environments, cloud-oriented methodological systems of training, the provision of cloud-based educational services. The ways of implementation SaaS, PaaS, IaaS cloud services models which are appropriate to use in the process of studying the academic disciplines of the cycles of mathematical, natural science and professional and practical training of future specialists in information technology are shown, based on the example of software engineering, computer science and computer engineering. The most significant advantages of using cloud technologies in training of future information technology specialists are definite, namely, the possibility of using modern parallel programming tools as the basis of cloud technologies. Conclusions are drawn; the direction of further research is indicated: designing a cloud-oriented learning environment for future specialists in computer engineering, identifying trends in the development of cloud technologies in the professional training and retraining of information technology specialists, developing a methodology for building the research competencies of future software engineering specialists by using cloud technologies.
Стилі APA, Harvard, Vancouver, ISO та ін.
9

Holub, Oleksandr, Mykhailo Moiseienko, and Natalia Moiseienko. Fluid Flow Modelling in Houdini. [б. в.], November 2020. http://dx.doi.org/10.31812/123456789/4128.

Повний текст джерела
Анотація:
The modern educational environment in the field of physics and information technology ensures the widespread use of visualization software for successful and deep memorization of material. There are many software for creating graphic objects for presentations and demonstrations, the most popular of which were analyzed. The work is devoted to the visualization of liquids with different viscosity parameters. The article describes the development of a fluid model in the form of a particle stream. The proposed methodology involves using the Houdini application to create interactive models. The developed model can be used in the educational process in the field of information technology.
Стилі APA, Harvard, Vancouver, ISO та ін.
10

Zhylenko, Tetyana I., Ivan S. Koziy, Vladyslav S. Bozhenko, and Irina A. Shuda. Using a web application to realize the effect of AR in assessing the environmental impact of emissions source. [б. в.], November 2020. http://dx.doi.org/10.31812/123456789/4408.

Повний текст джерела
Анотація:
Revolutionary technologies of nowadays are virtual and augmented reality. Humanity's concern for nature may be affected by their ability to combine reality with the simulated effects of human impact on the environment. An urgent task today is creating software applications to assess the impact of human activities on the environment. Recently, most scientists have been trying to model the impact of various factors on environmental change today and for decades using information technology. Visual models are very impressive and they also make a deep impression on the psychological state of the person. This forces people to use natural resources wisely. In this article we have considered the sequential process of building and implementing models for assessing the impact of pollutants from a stationary emission source. We have created a software product that helps to show visually how the emissions of a chemical plant are spreading to the surrounding city. The harmfulness to the city of the cloud into which emissions are converted can also be calculated by the program. We have implemented a number of functions responsible for emission modeling, taking into account different conditions.
Стилі APA, Harvard, Vancouver, ISO та ін.
Також вас можуть зацікавити розширені добірки на тему "Agile software process models" для конкретних типів джерел:
Статті в журналах Дисертації Книги
Ми пропонуємо знижки на всі преміум-плани для авторів, чиї праці увійшли до тематичних добірок літератури. Зв'яжіться з нами, щоб отримати унікальний промокод!

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