Готові списки джерел за темами / Duration of software development

Добірка наукової літератури з теми "Duration of software development"

Автор: Grafiati

Опубліковано: 30 травня 2022

Оновлено: 31 травня 2022

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

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

Зміст

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

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

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

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

Статті в журналах з теми "Duration of software development"

Lee, Sang-Un, and Myeong-Bok Choi. "An Estimating for Practical Software Development Duration." Journal of the Institute of Webcasting, Internet and Telecommunication 12, no. 6 (December 31, 2012): 155–64. http://dx.doi.org/10.7236/jiwit.2012.12.6.155.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Bhardwaj, Mridul, and Ajay Rana. "Key Software Metrics and its Impact on each other for Software Development Projects." International Journal of Electrical and Computer Engineering (IJECE) 6, no. 1 (February 1, 2016): 242. http://dx.doi.org/10.11591/ijece.v6i1.8247.

Повний текст джерела

Анотація:

Every software development project is unique and different from repeatable manufacturing process. Each software project share different challenges related to technology, people and timelines. If every project is unique, how project manager can estimate project in a consistent way by applying his past experience. One of the major challenges faced by the project manager is to identify the key software metrics to control and monitor the project execution. Each software development project may be unique but share some common metric that can be used to control and monitor the project execution. These metrics are software size, effort, project duration and productivity. These metrics tells project manager about what to deliver (size), how it was delivered in past (productivity) and how long will it take to deliver with current team capability (time and effort). In this paper, we explain the relationship among these key metrics and how they statistically impact each other. These relationships have been derived based on the data published in book “Practical Software Estimation” by International Software Benchmarking Group. This paper also explains how these metrics can be used in predicting the total number of defects. Study suggests that out of the four key software metrics software size significantly impact the other three metrics (project effort, duration and productivity). Productivity does not significantly depend on the software size but it represents the nonlinear relationship with software size and maximum team size, hence, it is recommended not to have a very big team size as it might impact the overall productivity. Total project duration only depends on the software size and it does not depend on the maximum team size. It implies that we cannot reduce project duration by increasing the team size. This fact is contrary to the perception that we can reduce the project duration by increasing the project team size. We can conclude that software size is the important metrics and a significant effort must be put during project initiation phases to estimate the project size. As software size will help in estimating the project duration and project efforts so error in estimating the software size will have significant impact on the accuracy of project duration and effort. All these key metrics must be re-calibrated during the project development life cycle.

Стилі APA, Harvard, Vancouver, ISO та ін.

Повний текст джерела

Анотація:

Стилі APA, Harvard, Vancouver, ISO та ін.

Jensen, Samuel J., Pramod M. Paul, A. Ramesh, Anand Mammen Thomas, N. S. Prasad, and A. Kumarasamy. "Development of a Fuel Quantity based Engine Control Unit Software Architecture." Defence Science Journal 69, no. 3 (April 30, 2019): 203–7. http://dx.doi.org/10.14429/dsj.69.14420.

Повний текст джерела

Анотація:

Conventionally diesel engines are controlled in open loop with maps based on engine speed and throttle position wherein fuel quantity is indirectly fixed using the rail pressure and injection duration maps with engine speed and throttle position as the independent variables which are measured by the respective sensors. In this work an engine control unit (ECU) software architecture where fuel quantity is directly specified in relation to the driver demand was implemented by modifying the control logic of a throttle position based framework. A desired fuel quantity for a given engine speed and throttle position was mapped from base line experiments on the reference engine. Injection durations and rail pressure required for this quantity was mapped on a fuel injector calibration test bench. The final calculation of injection duration in the new architecture is calculated using the fuel injector model. This enables determination of fuel quantity injected at any moment which directly indicates the torque produced by the engine at a given speed enabling smoke limited fuelling calculations and easing the implementation of control functions like all-speed governing.

Стилі APA, Harvard, Vancouver, ISO та ін.

Morgenshtern, Ofer, Tzvi Raz, and Dov Dvir. "Factors affecting duration and effort estimation errors in software development projects." Information and Software Technology 49, no. 8 (August 2007): 827–37. http://dx.doi.org/10.1016/j.infsof.2006.09.006.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Golosovskiy, M. S. "Model for Estimation Software Development Effort and Duration on Initiation Project Phase." PROGRAMMNAYA INGENERIA 7, no. 10 (October 2016): 446–55. http://dx.doi.org/10.17587/prin.7.446-455.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Moulla, Donatien Koulla, Alain Abran, and Kolyang. "Duration Estimation Models for Open Source Software Projects." International Journal of Information Technology and Computer Science 13, no. 1 (February 8, 2021): 1–17. http://dx.doi.org/10.5815/ijitcs.2021.01.01.

Повний текст джерела

Анотація:

For software organizations that rely on Open Source Software (OSS) to develop customer solutions and products, it is essential to accurately estimate how long it will take to deliver the expected functionalities. While OSS is supported by government policies around the world, most of the research on software project estimation has focused on conventional projects with commercial licenses. OSS effort estimation is challenging since OSS participants do not record effort data in OSS repositories. However, OSS data repositories contain dates of the participants’ contributions and these can be used for duration estimation. This study analyses historical data on WordPress and Swift projects to estimate OSS project duration using either commits or lines of code (LOC) as the independent variable. This study proposes first an improved classification of contributors based on the number of active days for each contributor in the development period of a release. For the WordPress and Swift OSS projects environments the results indicate that duration estimation models using the number of commits as the independent variable perform better than those using LOC. The estimation model for full-time contributors gives an estimate of the total duration, while the models with part-time and occasional contributors lead to better estimates of projects duration with both for the commits data and the lines of data.

Стилі APA, Harvard, Vancouver, ISO та ін.

Feyeux, M., A. Reignier, M. Mocaer, J. Lammers, D. Meistermann, P. Barrière, P. Paul-Gilloteaux, L. David, and T. Fréour. "Development of automated annotation software for human embryo morphokinetics." Human Reproduction 35, no. 3 (March 2020): 557–64. http://dx.doi.org/10.1093/humrep/deaa001.

Повний текст джерела

Анотація:

Abstract STUDY QUESTION Is it possible to develop an automated annotation tool for human embryo development in time-lapse devices based on image analysis? SUMMARY ANSWER We developed and validated an automated software for the annotation of human embryo morphokinetic parameters, having a good concordance with expert manual annotation on 701 time-lapse videos. WHAT IS KNOWN ALREADY Morphokinetic parameters obtained with time-lapse devices are increasingly used for the assessment of human embryo quality. However, their annotation is time-consuming and can be slightly operator-dependent, highlighting the need to develop fully automated approaches. STUDY DESIGN, SIZE, DURATION This monocentric study was conducted on 701 videos originating from 584 couples undergoing IVF with embryo culture in a time-lapse device. The only selection criterion was that the duration of the video must be over 60 h. PARTICIPANTS/MATERIALS, SETTING, METHODS An automated morphokinetic annotation tool was developed based on gray level coefficient of variation and detection of the thickness of the zona pellucida. The detection of cellular events obtained with the automated tool was compared with those obtained manually by trained experts in clinical settings. MAIN RESULTS AND THE ROLE OF CHANCE Although some differences were found when embryos were considered individually, we found an overall concordance between automated and manual annotation of human embryo morphokinetics from fertilization to expanded blastocyst stage (r2 = 0.92). LIMITATIONS, REASONS FOR CAUTION These results should undergo multicentric external evaluation in order to test the overall performance of the annotation tool. Getting access to the export of 3D videos would enhance the quality of the correlation with the same algorithm and its extension to the 3D regions of interest. A technical limitation of our work lies within the duration of the video. The more embryo stages the video contains, the more information the script has to identify them correctly. WIDER IMPLICATIONS OF THE FINDINGS Our system paves the way for high-throughput analysis of multicentric morphokinetic databases, providing new insights into the clinical value of morphokinetics as a predictor of embryo quality and implantation. STUDY FUNDING/COMPETING INTEREST(S) This study was partly funded by Finox-Gedeon Richter Forward Grant 2016 and NeXT (ANR-16-IDEX-0007). We have no conflict of interests to declare. TRIAL REGISTRATION NUMBER N/A

Стилі APA, Harvard, Vancouver, ISO та ін.

Hill, J., L. C. Thomas, and D. E. Allen. "Experts' estimates of task durations in software development projects." International Journal of Project Management 18, no. 1 (February 2000): 13–21. http://dx.doi.org/10.1016/s0263-7863(98)00062-3.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Prakash, B., and V. Viswanathan. "A Survey on Software Estimation Techniques in Traditional and Agile Development Models." Indonesian Journal of Electrical Engineering and Computer Science 7, no. 3 (September 1, 2017): 867. http://dx.doi.org/10.11591/ijeecs.v7.i3.pp867-876.

Повний текст джерела

Анотація:

Software projects mostly exceeds budget, delivered late and does not meet with the customer’s satisfaction for years. In the past, many traditional development models like waterfall, spiral, iterative, and prototyping methods are used to build the software systems. In recent years, agile models are widely used in developing the software products. The major reasons are – simplicity, incorporating the requirement changes at any time, light-weight approach and delivering the working product early and in short duration. Whatever the development model used, it still remains a challenge for software engineer’s to accurately estimate the size, effort and the time required for developing the software system. This survey focuses on the existing estimation models used in traditional as well in agile software development.

Стилі APA, Harvard, Vancouver, ISO та ін.

Більше джерел

Дисертації з теми "Duration of software development"

Omair, Muhammad. "Challenges in understanding software requirements in agile based offshore development." Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2008. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-3740.

Повний текст джерела

Анотація:

Agile based development seems to become a favorable model for offshore development. It allows both on and offshore team to work in small iterations minimizing the effect of change in software requirements and at the same time developing regular communication between them. However different factors such as physical distance and lack of communication between on and offshore team becomes a hurdle between them leading to misunderstandings about software requirements. This research work gives an insight about these challenges from the software industry by presenting and discussing the responses of four software companies located in different countries, collected through an online questionnaire. The authors found that lack of communication between on and offshore site is seen as a major challenge for better understanding of software requirements. Shorter iterations at the offshore site require more communication with the onshore site. The language problem seems to exist only when both on and offshore site who are non-English speakers communicate in English. Regular long distance meetings would help in better understanding of software requirements. Previous domain and product knowledge is helpful in better understanding of software requirements. This research work would allow different stakeholders within agile based on/offshore setting to better understand these challenges and deal accordingly with them.

Стилі APA, Harvard, Vancouver, ISO та ін.

Ahmedshareef, Zana. "Controlling schedule duration during software project execution." Thesis, University of Brighton, 2015. https://research.brighton.ac.uk/en/studentTheses/819fb81b-e3c1-40ce-bad9-f44308fdbc79.

Повний текст джерела

Анотація:

This thesis describes a method of identifying the influences on schedule delays in projects that develop large software systems. Controlling schedule duration is a fundamental aspect of managing projects because of the financial losses associated with late projects. While challenges with controlling software projects have been investigated, there still seemed to be more to be learned about the interplay of a range of factors during project execution and that affect project duration when developing and integrating software systems within enterprise architecture environment.

Стилі APA, Harvard, Vancouver, ISO та ін.

Karagul, Yasemin. "Factors That Affect The Duration Of Cmmi-based Software Process Improvement Initiatives." Phd thesis, METU, 2009. http://etd.lib.metu.edu.tr/upload/12610733/index.pdf.

Повний текст джерела

Анотація:

Reference models developed for software process improvement (SPI) provide guidelines about what to do while assessing and improving the processes, but they do not answer the questions of how. There have been a number of studies that try to find effective and strategic implementation models or to identify factors that affect the SPI success. However, these studies do not provide answers to questions about the effect of these factors on SPI program duration or accelerated SPI studies. This study aims to investigate the factors that affect CMMI-based SPI duration. It consists of two phases: in the first phase, factors that influence SPI success are identified and hypotheses related to these factors are formulated based on the case studies published in the literature. In the second phase of the study, hypotheses are revised based on the results of the qualitative research conducted in seven companies, six of which have obtained CMMI-Level 3 certification as a consequence of their SPI effort. The study has shown that management commitment and involvement as well as process documentation have had a significant shortening effect on CMMI-based SPI duration, within the context of the studied cases. Software process improvement
CMMI
Success factors
Duration factors. Enter specific words or phrases that are listed in thesis.

Стилі APA, Harvard, Vancouver, ISO та ін.

MacLean, Grant. "Development of a miniature, long-duration GPS tag." Thesis, Heriot-Watt University, 2008. http://hdl.handle.net/10399/2213.

Повний текст джерела

Анотація:

This research concentrates on both weak GPS signal-processing and GPS time error correction in parallel with the development of an innovative GPS tag – “TrackTag”. The technology is aimed at animal tagging applications and therefore has particular challenges. The tag has to be small enough so as not to impact the behaviour of the animal under study as well as robust enough to operate wherever the animal goes. TrackTag‟s architecture differs form that of a conventional GPS receiver in that it uses very short snapshots and there is no processing performed on the tag itself. This enables the tag to operate for over a year on a small battery. Weak signal processing algorithms studied include FFT techniques and conventional correlators for demodulation of the GPS signals using both non-coherent and coherent integration. The techniques developed enabled the tracking of signals down to 24dB-Hz, which is comparable to today‟s best conventional GPS units. However, the algorithms developed during this research achieve such performance using only 76 milliseconds of data while conventional designs require many seconds of data. The performance of the navigation solutions was not compromised in terms of accuracy. A 2dRMS accuracy of 29 metres was observed under forest canopy and the research even demonstrated over 50% success rate in the Amazon Rainforest canopy where conventional GPS tags had never been shown to work. New time correction techniques were also required as it was estimated that a 100ms clock error would result in 100m positional error. Temperature calibration of the RTC crystal was developed as the first step. However, with that, the clock drift over a month could still be up to 5 seconds (2ppm) and so it became clear that for long-duration (>3 months) studies another method for maintaining accuracy was required. Over-determined navigation solutions, and their subsequent position residual error, were used to estimate the time offset with some success. Pattern-matching against WAAS signals offered exceptional performance and was demonstrated on real-world tracking studies that were running concurrently with this research. The accuracy was considered to be limited only by the front-end sample period, i.e. 200 nanoseconds for any given deployment duration.

Стилі APA, Harvard, Vancouver, ISO та ін.

Kurdi, Suparna. "Software development process and strategies used to expedite software development." Thesis, National Library of Canada = Bibliothèque nationale du Canada, 1997. http://www.collectionscanada.ca/obj/s4/f2/dsk2/ftp04/mq22136.pdf.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Kurdi, Suparna Carleton University Dissertation Management Studies. "Software development process and strategies used to expedite software development." Ottawa, 1997.

Знайти повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Johansson, Katrin. "Agile Software Development." Thesis, Linköpings universitet, Institutionen för teknik och naturvetenskap, 2005. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-97920.

Повний текст джерела

Анотація:

Systemutvecklingsföretag är på väg in i en turbulent period. Globaliseringen ger en total konkurrens som kräver snabba anpassningar. Detta ställer krav på reaktionssnabbhet. En framtid där vi slipper ogenomträngliga lösningar ligger nu inom räckhåll. Ett nytt synsätt har börjat ta form och konkurrerar nu ut den gamla, processorienterade synen på systemutveckling. Testdriven utveckling, refactoring och par-programmering är inslag i denna nya mera lättrörliga utvecklingsmetodiken. Detta synsätt går under namnet Agile Software Development. Den studie jag genomfört och som denna uppsats är resultatet av, syftar till att ta reda på hur systemutveckling enligt synsättet agile fungerar i verkligheten och vad det betyder för aktiva systemutvecklare. Resultatet av studien är baserad på en kvalitativ undersökning, i form av intervjuer, som gjorts med tretton systemutvecklare på olika företag runt om i Sverige. Resultatet visar att genom att utveckla mjukvara med en agilemetod, får man en snabbare utvecklingscykel med fokus på störts affärsnytta först. Det ger mer funktioner med högre kvalitet till lägre kostnad. Resultatet visar också att man har en flexiblare syn på utvecklingen och en attityd som välkomnar förändringar när helst dom dyker upp. Ett arbetssätt där förändringar är en del av planeringen.

Стилі APA, Harvard, Vancouver, ISO та ін.

Hellström, Andreas, and Anatoly Chervyakov. "Global Software Development." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik och datavetenskap, 2002. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-1687.

Повний текст джерела

Анотація:

Global Software Development is an area that has been recently highlighted. Translation is usually an issue that people associate with adapting software for a specific country but it is much more than that. Through text representation and data formatting you can go deep into cultural aspects that affect the user interface and even the core functionality. In this thesis we will discuss just how these matters can affect development of global software. To carry out the investigation we analyzed current approaches and references and build up an extended methodology with suggestions to develop global software applications.
Utveckling av globala programvara är ett område som den senaste tiden har uppmärksammats. Översättning är vanligtvis en fråga som människor associerar med att anpassa programvaror för ett specifikt land men det är mycket mer än det. Man kan gå djupare in i kulturella aspekter som kan påverka användargränssnitt och även mjukvarans kärna. I den här uppsatsen diskuterar vi hur dessa aspekter kan påverka utveckling av global programvara. För att genomföra vårt arbete analyserades vi först befintliga metodologier och byggde upp en utökad metodologi med förslag på hur man kan utveckla global programvara.
0737 305407 0708 230374

Стилі APA, Harvard, Vancouver, ISO та ін.

Leinonen, J. (Juho). "Evaluating software development effort estimation process in agile software development context." Master's thesis, University of Oulu, 2016. http://urn.fi/URN:NBN:fi:oulu-201605221862.

Повний текст джерела

Анотація:

This thesis studied effort estimation in software development, focusing on task level estimation that is done in Scrum teams. The thesis was done at Nokia Networks and the motivation for this topic came from the poor estimation accuracy that has been found to be present in software development. The aim of this thesis was to provide an overview of what is the current state of the art in effort estimation, survey the current practices present in Scrum teams working on LTE L2 software component at Nokia Networks Oulu, and then present suggestions for improvement based on the findings. On the basis of the literature review, three main categories of effort estimation methods were found: expert estimation, algorithmic models and machine learning. Universally there did not seem to be a single best method, but instead the differences come from the context of use. Algorithmic models and machine learning require data sets, whereas expert estimation methods rely on previous experiences and intuition of the experts. While model based methods have received a lot of research attention, the industry has largely relied on expert estimation. The current state of effort estimation at Nokia Networks was studied by conducting a survey. This survey was built based on previous survey studies that were found by conducting a systematic literature review. The questions found in the previous studies were formulated into a questionnaire, which was then used to survey the current effort estimation practices present in the participating teams. 41 people out of 100 in the participating teams participated in the survey. Survey results showed that like much of the software industry, the teams in LTE L2 relied on expert estimation methods. Most respondents had encountered overruns in the last sprint and the most often provided reason was that testing related effort estimation was hard. Forgotten subtasks were encountered frequently and requirements were found to be both unclear and to change often. Very few had had any training on effort estimation. There were no common practices for effort data collection and as such, it was mostly not done. By analyzing the survey results and reflecting them on the previous research, five suggestions for improvements were found. These were training in effort estimation, improving the information that is used during effort estimation by collaborating with specification personnel, improving testing related effort estimation by splitting acceptance testing into their own tasks, collecting and using effort data, and using Planning Poker as an effort estimation method, as it fit the context of estimation present in the teams. The study shed light on how effort estimation is done in software industry. Another contribution was the improvement suggestions, which could potentially improve the situation in the teams that participated in the survey. A third contribution was the questionnaire built during this study, as it could potentially be used to survey the current state of effort estimation in also other contexts.

Стилі APA, Harvard, Vancouver, ISO та ін.

Moratilla, Temprado Enrique, and Bendito Enrique Ruz. "Lean Software Development and Agile Methodologies for a small Software development organization." Thesis, Högskolan i Borås, Institutionen Ingenjörshögskolan, 2010. http://urn.kb.se/resolve?urn=urn:nbn:se:hb:diva-20077.

Повний текст джерела

Анотація:

Lean Software Development is a new approach to provide a quality philosophy in software development companies. Lean offers a set of principles that helps companies to identify inefficient processes and waste. Therefore, by applying these principles, we can reduce costs, by shorting development time, incrementing productivity.In this study a software company with seven employees is analyzed. The company develops software and wants to increase its maturity and the quality of its processes. Currently, it has few documented processes. Furthermore, the company want a common way of working for every project. The challenge relies in adapting the set of principles provided by Lean to this particular case of study.We seek to analyze the current situation of the company to find out about the problems and limitations of the current way of working. After that we will state recommendations about the use of Lean combined with Agile practices such as Scrum and XP.As a result we present a proposal for implementation adapted from these philosophies to the needs and characteristics of the company.We have found that there are several ways in which the company can benefit from the implementation of Lean practices in combination with Scrum and XP. The result is a new framework that can be applied for other small software development companies in a similar situation.

Стилі APA, Harvard, Vancouver, ISO та ін.

Більше джерел

Книги з теми "Duration of software development"

Hill, J. Experts' estimates of task durations in software development projects. Edinburgh: University of Edinburgh, Management School, 1998.

Знайти повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Hill, J. Experts' estimation of task durations in software development projects. Edinburgh: Management School, University of Edinburgh, 1998.

Знайти повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

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

Знайти повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

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

Знайти повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Cockburn, Alistair. Agile software development. Boston: Addison-Wesley, 2002.

Знайти повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Ware, Myers, ed. Controlling software development. Los Alamitos, Calif: IEEE Computer Society Press, 1996.

Знайти повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

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

Знайти повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

G, Siegel Stanley, and Donaldson Scott E, eds. Successful software development. 2nd ed. Upper Saddle River, NJ: Prentice Hall PTR, 2001.

Знайти повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

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

Знайти повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

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

Знайти повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Більше джерел

Частини книг з теми "Duration of software development"

Huang, Wei, Lixin Ding, Bin Wen, and Buqing Cao. "Project Scheduling Problem for Software Development with Random Fuzzy Activity Duration Times." In Advances in Neural Networks – ISNN 2009, 60–69. Berlin, Heidelberg: Springer Berlin Heidelberg, 2009. http://dx.doi.org/10.1007/978-3-642-01510-6_8.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Tinbergen, Jan. "The duration of development." In The Global Dimension of Economic Evolution, 153–59. Heidelberg: Physica-Verlag HD, 1996. http://dx.doi.org/10.1007/978-3-642-48870-2_11.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Amasaki, Sousuke, and Chris Lokan. "The Effects of Duration-Based Moving Windows with Estimation by Analogy." In Software Measurement, 14–29. Cham: Springer International Publishing, 2015. http://dx.doi.org/10.1007/978-3-319-24285-9_2.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Paulus, Dietrich W. R., and Joachim Hornegger. "Software Development." In Pattern Recognition of Images and Speech in C++, 31–40. Wiesbaden: Vieweg+Teubner Verlag, 1997. http://dx.doi.org/10.1007/978-3-663-13991-1_3.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Paulus, Dietrich W. R., and Joachim Hornegger. "Software Development." In Pattern Recognition and Image Processing in C++, 32–41. Wiesbaden: Vieweg+Teubner Verlag, 1995. http://dx.doi.org/10.1007/978-3-322-87867-0_3.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Buchanan, W. J. "Software development." In The Complete Handbook of the Internet, 941–68. Boston, MA: Springer US, 2002. http://dx.doi.org/10.1007/978-0-306-48331-8_44.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Constanda, Christian, Dale Doty, and William Hamill. "Software Development." In Boundary Integral Equation Methods and Numerical Solutions, 35–91. Cham: Springer International Publishing, 2016. http://dx.doi.org/10.1007/978-3-319-26309-0_4.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

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

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Hunt, Eleanor Callahan, Sara Breckenridge Sproat, and Rebecca Rutherford Kitzmiller. "Software Development." In The Nursing Informatics Implementation Guide, 276–97. New York, NY: Springer New York, 2004. http://dx.doi.org/10.1007/978-1-4757-4343-2_14.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Lientz, Bennet P. "Software development." In Information Technology Project Management, 295–315. London: Macmillan Education UK, 2011. http://dx.doi.org/10.1007/978-0-230-34500-3_16.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Тези доповідей конференцій з теми "Duration of software development"

Owais, Mohd, and R. Ramakishore. "Effort, duration and cost estimation in agile software development." In 2016 Ninth International Conference on Contemporary Computing (IC3). IEEE, 2016. http://dx.doi.org/10.1109/ic3.2016.7880216.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Lopez-Martin, Cuauhtemoc, Arturo Chavoya, and Maria Elena Meda-Campana. "Use of a Feedforward Neural Network for Predicting the Development Duration of Software Projects." In 2013 12th International Conference on Machine Learning and Applications (ICMLA). IEEE, 2013. http://dx.doi.org/10.1109/icmla.2013.182.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Fabriciuss, Janis, and Lilita Ozola. "Duration of load effects on development of deformations in bolted moment connection." In Research for Rural Development 2020. Latvia University of Life Sciences and Technologies, 2020. http://dx.doi.org/10.22616/rrd.26.2020.034.

Повний текст джерела

Анотація:

Experience saved in the construction industry shows that the timber portal frames with semi-rigid connections at knee joint exhibit permanently increase displacements at the knee and apex point. Normally, timber portal frame with semi-rigid knee joint connection is made with mechanical fasteners located in double circles and cannot be designed without relevant rotation at connection during structures’ exploitation time. The only way to increase connection rigidity is to rise distance from fasteners location at connection, but at the same time, the tension and shear stress become significant at the external section of members. The previous experience is obtained by a model testing showing that deformations at semi-rigid connections are non-linear. These were tests under short-term load and did not disclose creep effects, which can be significant. This study is aimed at the examination of increasing deformations with time under constant static load (creep effects) in semi-rigid dowelled connection. Experimental test models were made and set under long-term load in controlled environmental conditions (heated laboratory room). Results show a significant creep influence to decrease connection stiffness. Corresponding numerical test of orthotropic 3d model by Dlubal RFEM software tools was performed analyzing the value of expected deformations. Results of the numerical test showed that friction between timber elements and extra nuts on bolts can increase connection stiffness. Research results in this stage show that the creep can affect connection stiffness more than expected. Also, experimental test results showed lower deformation values comparing with the ones obtained by the numerical test.

Стилі APA, Harvard, Vancouver, ISO та ін.

ŽIBIENĖ, Gražina, Alvydas ŽIBAS, and Goda BLAŽAITYTĖ. "ASSESSMENT OF HYDROLOGICAL CHANGES IN THE ŠUŠVĖ RIVER." In Rural Development 2015. Aleksandras Stulginskis University, 2015. http://dx.doi.org/10.15544/rd.2015.035.

Повний текст джерела

Анотація:

The construction of dams in rivers negatively affects ecosystems because dams violate the continuity of rivers, transform the biological and physical structure of the river channels, and the most importantly – alter the hydrological regime. The impact on the hydrology of the river can occur through reducing or increasing flows, altering seasonality of flows, changing the frequency, duration and timing of flow events, etc. In order to determine the extent of the mentioned changes, The Indicators of Hydrologic Alteration (IHA) software was used in this paper. The results showed that after the construction of Angiriai dam, such changes occurred in IHA Parameters group as: the water conditions of April month decreased by 31 %; 1-day, 3-days, 7-days and 30-days maximum flow decreased; the date of minimum flow occurred 21 days later; duration of high and low pulses and the frequency of low pulses decreased, but the frequency of high pulses increased, etc. The analysis of the Environmental Flow Components showed, that the essential differences were recorded in groups of the small and large floods, when, after the establishment of the Šušvė Reservoir, the large floods no longer took place and the probability of frequency of the small floods didn’t exceed 1 time per year.

Стилі APA, Harvard, Vancouver, ISO та ін.

Mitchell, Susan M., and Carolyn B. Seaman. "A comparison of software cost, duration, and quality for waterfall vs. iterative and incremental development: A systematic review." In 2009 3rd International Symposium on Empirical Software Engineering and Measurement (ESEM). IEEE, 2009. http://dx.doi.org/10.1109/esem.2009.5314228.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Ustinova, M. E., and A. A. Yashonkov. "APPLICATION OF THE FINITE ELEMENT METHOD FOR MODELING NON-STATIONARY HEAT TRANSFER DURING FOOD DRYING." In STATE AND DEVELOPMENT PROSPECTS OF AGRIBUSINESS Volume 2. DSTU-Print, 2020. http://dx.doi.org/10.23947/interagro.2020.2.218-221.

Повний текст джерела

Анотація:

The article substantiates the possibility of using the finite element method implemented in the ANSYS software package for computer modeling of non-stationary heat transfer. The results of computer simulation of the warm-up period of carrot snack during vacuum drying are presented. The duration of the warm-up period at different ambient temperatures is set.

Стилі APA, Harvard, Vancouver, ISO та ін.

Şaykol, Ediz. "An Economic Analysis of Software Development Process based on Cost Models." In International Conference on Eurasian Economies. Eurasian Economists Association, 2012. http://dx.doi.org/10.36880/c03.00427.

Повний текст джерела

Анотація:

Software development process generally includes requirement analysis, design, implementation, and testing phases. The overall process is called Software Development Life Cycle (SDLC). Each of these steps was executed sequentially in earlier times, i.e. the output of a step is used as the input to the following step. This sequential execution is called waterfall process, and since the total duration of SDLC has been increasing, more dynamic models need to be employed in today’s software engineering methodologies. V-Shaped model, Spiral model, Incremental or iterative software development model, are some examples of these methodologies. On the other hand, due to the increase in the total number of projects for a company and due to the product variability, reusability aspect has entered into the domain. This aspect gained importance in the recent years, leading to the execution of framework-based models and software product line engineering process. In this study, the above methodologies are analyzed from an economic perspective with respect to their cost models. Reusability will require upfront investment, but the gain will be higher as the number of common software items increases, which are determined in commonality/variability analysis phase. Improvements in SDLC might also require organizational changes to adapt new methodologies. These considerations are discussed along with the cost model analysis, and a cost-evaluation criterion is provided in the paper.

Стилі APA, Harvard, Vancouver, ISO та ін.

Salimov, Rail, Javier Torres, Yousif Al Katheeri, Yousef Alhammadi, and Ahmed Abdelrahman. "Automation of Formation Tops Estimation Dramatically Reduces Well Planning Process Duration." In SPE/IADC Middle East Drilling Technology Conference and Exhibition. SPE, 2021. http://dx.doi.org/10.2118/202139-ms.

Повний текст джерела

Анотація:

Abstract Aiming to make the well planning process leaner and agile focusing on duration reduction without compromising quality of deliverables, automation opportunities have been identified within the multi-discipline iterations. The two key criteria considered for the selection of the automation project were: Minimum deployment effort and Maximum value added in efficiency. The initial project objective was to calculate formation tops for a well engineer without requiring the intervention of a geoscientist using commercial software. The methodology utilized is the following: 1. Inputs: Well trajectory and Surfaces. 2. Process: The algorithm finds intersections between surfaces and well trajectory. Surfaces and trajectory are represented as a set of XYZ points. To find the intersection, the software iterates through each point of the trajectory from the top, comparing the depth of the projection to the target surface. The projected depth to the surface is found by 2D interpolation of the surface. Once the trajectory point becomes deeper than the surface projection, the intersection is estimated using geometrical considerations of similar triangles. 3. Deliverables: Estimated formation tops for the given trajectory. 4. Results: Simple in-house developed software enhanced well planning workflow in an Offshore Green Field. The software converted to single executable file and can be run on any device without the open-source software installed. Very accurate results achieved with proposed algorithm with a negligible difference of 0.5 feet with the geoscience traditional software. Well planning duration reduced from average 1 week to 1 or 2 days. The workload for well engineers and the asset team has been dramatically reduced. Reduction of the number of commercial geoscience software licenses required. Way forward: A test with a slightly modified code was used to generate formation tops for more than 400 well in a Long-Term Field Development Plan project for a Brown Field during feasibility study. Upscale to all the Fields within the organization. Improve User Interface for better adoption. Include more formats for both, trajectories, and surfaces. Reduce computing time. This project represents the first initiative in the organization aiming to automate the well planning process. Overall, it represents the beginning of a journey where multiple opportunities for automation can be achieved using an open-source coding software that allows any engineer with little to no experience coding to being able to generate solutions to address daily challenges.

Стилі APA, Harvard, Vancouver, ISO та ін.

Alzoubi, M. F., and Ma’moun Abu-Ayyad. "Development of a Finite Model for Controlling a Mold’s Open/Close Process in an Injection Molding Machine." In ASME 2011 International Mechanical Engineering Congress and Exposition. ASMEDC, 2011. http://dx.doi.org/10.1115/imece2011-62505.

Повний текст джерела

Анотація:

This paper presents a unique approach for integrating a finite element analysis (FEA) model using a dynamic explicit of Abaqus with a nonlinear process of the mold’s open/close phase in an injection molding machine. This opening/closing phase is considered to have one of the highest impacts on reducing an overall cycle duration since it has no impact on the final part quality. Reducing the overall cycle duration has a big positive impact on productivity and enhancing efficiency of the manufacturing processes of injection molding systems. Therefore, one of the objectives of the injection molding manufacturers is increasing efficiency by reducing the time duration of this phase to a possible minimum. In this work, a 3-dimensional (3D) solid model of the mold, toggle mechanism, and hydraulic cylinder were developed and then superimposed with Abaqus software to animate the motion of the movable part of the mold. The position of the movable part of the mold is traced and used as a controlled variable while the inputted force and initial velocity were considered as the manipulated variables. The innovation of this strategy is that the controller structure uses the nonlinear model to update the process variables at every sampling instant while the closed-loop control is executed. This allows the determination of the plant’s variables resulting in a new set of the controller parameters with every sampling instant.

Стилі APA, Harvard, Vancouver, ISO та ін.

Jankauskiene, Dainora, Indrius Kuklys, Lina Kukliene, and Birute Ruzgiene. "Surface modelling of a unique heritage object: use of UAV combined with camera and LiDAR for mound inspection." In Research for Rural Development 2020. Latvia University of Life Sciences and Technologies, 2020. http://dx.doi.org/10.22616/rrd.26.2020.030.

Повний текст джерела

Анотація:

Nowadays, the use of Unmanned Aerial Vehicle flying at a low altitude in conjunction with photogrammetric and LiDAR technologies allows to collect images of very high-resolution to generate dense points cloud and to simulate geospatial data of territories. The technology used in experimental research contains reconstruction of topography of surface with historical structure, observing the recreational infrastructure, obtaining geographic information for users who are involved in preservation and inspection of such unique cultural/ heritage object as are mounds in Lithuania. In order to get reliable aerial mapping products of preserved unique heritage object, such photogrammetric/ GIS procedures were performed: UAV flight for taking images with the camera; scanning surface by LiDAR simultaneously; processing of image data, 3D modelling and generation of orthophoto. Evaluation of images processing results shows that the accuracy of surface modelling by the use of UAV photogrammetry method satisfied requirements – mean RMSE equal to 0.031 m. The scanning surface by LiDAR from low altitude is advisable, relief representation of experimental area was obtained with mean accuracy up to 0.050 m. Aerial mapping by the use of UAV requires to specify appropriate ground sample distance (GSD) that is important for reducing number of images and time duration for modelling of area. Experiment shows that specified GSD of 1.7 cm is not reasonable, GSD size increased by 1.5 time would be applicable. The use of different software in addition for DSM visualization and analysis is redundant action.

Стилі APA, Harvard, Vancouver, ISO та ін.

Звіти організацій з теми "Duration of software development"

Dow, Stephen J. Trainer Software Development. Fort Belvoir, VA: Defense Technical Information Center, October 2001. http://dx.doi.org/10.21236/ada396902.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Baskinger, Patricia J., Larry Ozarow, and Mary C. Chruscicki. Speakeasy Software Development. Fort Belvoir, VA: Defense Technical Information Center, August 1993. http://dx.doi.org/10.21236/ada283816.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Ellison, Robert J. Software Development Environments. Fort Belvoir, VA: Defense Technical Information Center, July 1986. http://dx.doi.org/10.21236/ada181742.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Piercey, R. B. Gammasphere software development. Office of Scientific and Technical Information (OSTI), January 1993. http://dx.doi.org/10.2172/6561547.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Forney, Glenn P., and Walter W. Jones. Software development tools. Gaithersburg, MD: National Institute of Standards and Technology, 1990. http://dx.doi.org/10.6028/nist.ir.4363.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Luqi. Documentation Driven Software Development. Fort Belvoir, VA: Defense Technical Information Center, June 2010. http://dx.doi.org/10.21236/ada532459.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

de Vaulx, Frederic, paul Khouri Saba, Marcus Newrock, and Bertrand Stivalet. Initiating mobile software development :. Gaithersburg, MD: National Institute of Standards and Technology, 2011. http://dx.doi.org/10.6028/nist.ir.7838.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Manna, Zohar. Next Generation Software Development. Fort Belvoir, VA: Defense Technical Information Center, January 2005. http://dx.doi.org/10.21236/ada435087.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Peatman, William C. Nanoelectronic Modeling Software Development. Fort Belvoir, VA: Defense Technical Information Center, March 1998. http://dx.doi.org/10.21236/ada340531.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Hsu, Y. L., Juan F. Reynaud, and Ernst W. Schwiderski. Tidal Atlas Software Development. Fort Belvoir, VA: Defense Technical Information Center, December 1993. http://dx.doi.org/10.21236/ada275251.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

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