Academic literature on the topic 'Waterfall methodology'
Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles
Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'Waterfall methodology.'
Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.
You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.
Journal articles on the topic "Waterfall methodology":
1
Gidroets, M. O., and L. I. Grishanova. "SOFTWARE DEVELOPMENT METHODOLOGY." System analysis and logistics 4, no. 26 (December 17, 2020): 45–53. http://dx.doi.org/10.31799/2007-5687-2020-4-45-53.
Abstract:
This article discusses the main methodologies for developing software products. The most common cascading and flexible methodologies are characterized. Considered the pros and cons of each methodology. The situations of expedient application of cascade and flexible approaches to software product development are determined. Key words: development methodologies, waterfall model, agile model, project management, planning, software product development.
2
Иванов, A. Ivanov, Иванова, and O. Ivanova. "Cost-Effectiveness of Methodologies to Develop Software for IT-Projects (As Exemplified by the “Waterfall” and the “Agile Development” Methodologies)." Economics 3, no. 2 (April 17, 2015): 30–33. http://dx.doi.org/10.12737/10840.
Abstract:
The paper considers issues related to the choice of more cost-effective
methodologies of developing software needed for implementation of ITprojects.
Also described are the most conventional methodologies of IT-projects
development, along with their main features, specifics and terms of use.
Factors, allowing to opt for the “waterfall” software development methodology
or for the agile development methodology are identified.
3
Nugraha, Abdul Mun’im Taufik, Alvian Yoga Saputra, and Renny Sari Dewi. "Software Development Website Inventaris Pada Pusat Perbelanjaan XYZ." JURIKOM (Jurnal Riset Komputer) 7, no. 1 (February 15, 2020): 28. http://dx.doi.org/10.30865/jurikom.v7i1.1862.
Abstract:
Currently the development of information technology is developing fast and demands to create an application that can solve an existing problem but has not found a solution. In the process of knowing the amount of stock, sometimes it will be difficult if you have to check manually. The application in XYZ shopping center warehouse is based on the need for accurate and accurate information management in managing the status of goods in the warehouse. The methodology used is the waterfall method, this model describes the development of software such as the flow of a waterfall, starting analysis requirements as the beginning of the process up to coding and testing at the end of the process. This application was designed using the SDLC method, by applying the Waterfall model and built using web programming languages, namely WordPress and MySQL for data storage. The result of the application is that the system can display the status of goods and provide the latest reports needed by the car shop manager
4
Mitsuyuki, Taiga, Kazuo Hiekata, Takuya Goto, and Bryan Moser. "Evaluation of Project Architecture in Software Development Mixing Waterfall and Agile by Using Process Simulation." Journal of Industrial Integration and Management 02, no. 02 (June 2017): 1750007. http://dx.doi.org/10.1142/s2424862217500075.
Abstract:
For software development, especially massive software systems, a waterfall process is used traditionally. A waterfall process can be highly effective on the condition that a master plan is fixed and the possibility of changes and uncertain rework is low. However, in software development projects, many kinds of reworks occur corresponding to uncertain requirement changes and program bugs. In addition, with the advent of cloud-based software platforms and continuous development operations, it is possible to develop a software system while operating the system. To respond to this situation, software development projects often adopt an agile process. Agility may allow conditional response to uncertain rework, yet at the same time it may be difficult to control the achievement of known project targets. Recently, many cases of adopting mixed processes including waterfall and agile have been reported in the massive software development projects. In this paper, we argue that the mixed process architecture should be designed, considering the scale of the targeted software project, the culture of organization, the probability of uncertain requirement changes, and so on. This paper proposes a methodology of evaluating the impact of waterfall, agile, and mixed project architectures by using process simulation. A project architectural approach is evaluated with a simulator which includes a software reliability growth model and uncertain rework driven by requirement change and error propagation. The proposed methodology was applied to a development project for a simple shopping website. The results showed that the proposed methodology allows exploration of partial agile adoption depending on the nature of the system development project, including its scale and chances of change. For example, in this paper, if the scale of the project is small, the positive effect of increasing agility by adopting agile processes is low. On the other hand, if the scale of the project is large, the effect of increasing agility by adopting agile process can increase. Furthermore, it became clear that it is important to not apply an agile process blindly, but instead to design a mixed project architecture considering the number of errors and development schedule targets across the project scope.
5
Almeida, Fernando, and Jorge Simões. "Moving from Waterfall to Agile: Perspectives from IT Portuguese Companies." International Journal of Service Science, Management, Engineering, and Technology 10, no. 1 (January 2019): 30–43. http://dx.doi.org/10.4018/ijssmet.2019010103.
Abstract:
This study investigates the main motivations, difficulties and good practices in the migration process of software development models from Waterfall to Agile experienced by IT Portuguese companies. For that, we adopted a quantitative methodology based on multiple case studies that allowed us to explore five research questions. In a first step, we propose to identify the main reasons that motivate the companies to adopt Agile development processes and we intend to characterize this migration process. We also explore a set of good practices that can be followed in this migration process and we suggest a set of measures that can be used to assess the success of projects in an Agile environment. Finally, we explore the organizational and management impacts with the introduction of Agile processes.
6
Balle, Andrea Raymundo, Mírian Oliveira, Carla Curado, and Felipe Nodari. "How do knowledge cycles happen in software development methodologies?" Industrial and Commercial Training 50, no. 7/8 (September 3, 2018): 380–92. http://dx.doi.org/10.1108/ict-04-2018-0037.
Abstract:
Purpose The purpose of this paper is to illustrate how knowledge takes effect in different software development methodologies by relating them to different knowledge cycles. Design/methodology/approach The results were find by conducing a general review about the topics of knowledge cycles and software development methodologies. Findings All software development methodologies have knowledge cycles. In Waterfall methodology, the cycle followed is I-Space. For “code and fix,” there is a parallel with March’s cycle. Scrum shows a parallel with SECI cycle. Among the methodological options, results show there an increase in hierarchy, documentation, processes and explicit knowledge. Research limitations/implications Identified parallels of each methodology with knowledge cycles; established which Scrum artifacts are performed at each stage of SECI, which Waterfall steps correspond to I-Space phases and which activities in “code and fix” deal with exploration and exploitation of knowledge; and features shown increase or decrease according to the adoption of each methodology. Practical implications Results help knowledge sharing implementations and foster inter-team knowledge sharing, with the identification of the correct methodology-cycle match and the personalization of the strategy for each team based on the adopted methodology. Training for knowledge initiatives can be improved by determining how knowledge-sharing activities are incorporated on the determined series of actions established by the methodologies adopted on the firm. Originality/value The identification of how knowledge is generated and shared among teams in each methodology, the optimum pairing of the methodology and the parallels with the other, and the differences that emerge from the adopted knowledge cycle show that software projects are embedded in a knowledge cycle.
7
Bayatmoghadam, Nabiollah, and Ashkan Sami. "Multi-factor analysis of pair programming based on PSP methodology." INTERNATIONAL JOURNAL OF COMPUTERS & TECHNOLOGY 15, no. 4 (February 23, 2016): 6672–80. http://dx.doi.org/10.24297/ijct.v15i4.6922.
Abstract:
In regard with designing software, users play key role. In order to design software, it is necessary to observe standard principles of designation, using templates and using modern methods. Over the decades, using development methods, XP and one of the XP methodologies of paired programming used to design software. These methods have been designed for purpose of enhancing quality of product and rapidresponse to need of market and customer and overcoming weaknesses of traditional methods based on long-term programming and waterfall method. Therefore, every programmer and developer can pass a series of processes for constructing computer software. The processes can be changed daily and efficient processes maynot be effective and useful; although they can be considered as process. The main objective of the present study is multi-factor analysis of pair programming based on PSP methodology. Practical and analytical methodand two PSP methods have been applied for investigations.
8
Ridwan, Muhammad, Iskandar Fitri, and Benrahman Benrahman. "Rancang Bangun Marketplace Berbasis Website menggunakan Metodologi Systems Development Life Cycle (SDLC) dengan Model Waterfall." Jurnal JTIK (Jurnal Teknologi Informasi dan Komunikasi) 5, no. 2 (April 1, 2021): 173. http://dx.doi.org/10.35870/jtik.v5i2.209.
Abstract:
The purpose of designing this marketplace is to take part in enlivening the potential of the e-commerce market or online stores in the Indonesian market. The SDLC methodology is used as a process of making and modifying the system and has structured stages from System planning, System Analysis, System Design, System Implementation, System Testing & System Maintenance. The result of this Marketplace Design is as a forum to make it easier for sellers or shop owners in the fields of Computers, Gadgets, Electronic Games, and the like to market their products.Keywords:Design, Marketplace, Methodology SDLC, Model Watefall.
9
Felicia Sylviana, Sherly Christina, and Sunartie. "APLIKASI PEMESANAN LAUNDRY BERBASIS SMS GATEWAY." Jurnal Teknologi Informasi Jurnal Keilmuan dan Aplikasi Bidang Teknik Informatika 13, no. 2 (October 22, 2019): 12–17. http://dx.doi.org/10.47111/jti.v13i2.248.
Abstract:
Keywords : website, waterfall method, SMS Gateway application
The development of information technology lately has entered almost all areas of our life. One of them in the field of business service provider of washing clothes or usually called the laundry. Each laundry business have its own way to improve their laundry service. In conveying information or promoting the Laundry to the community still using a manual way, and it takes very long time. So, it takes more time to get information. To able overcome these problems it is necessary to build a laundry booking application based sms gateway in Palangka Raya. Methodology The development of this application uses the waterfall methodology, with the following stages, the first stage is the requirements analysis described using UML 2.5 (Unifer Modeling Language), the second stage is design, the third stage is coding and testing, the testing used is using blackbox, the fourth stage is implementation, the fifth stage is maintenance. From the results of application testing, it can be concluded that this application has functioned well by providing features such as features of laundry booking based SMS Gateway and laundry profile information that contains services found in laundry.
10
Enny Dwi Oktaviyani, Licantik Licantik, and Loure Florentina. "SISTEM INFORMASI KEPEGAWAIAN SEBAGAI PENYEDIA INFORMASI PEMILIHAN PEGAWAI PENERIMA PENGHARGAAN SATYA LENCANA KARYA SATYA DI RADIO REPUBLIK INDOSESIA PALANGKA RAYA." Jurnal Teknologi Informasi Jurnal Keilmuan dan Aplikasi Bidang Teknik Informatika 13, no. 1 (October 30, 2019): 18–26. http://dx.doi.org/10.47111/jti.v13i1.280.
Abstract:
Staffing information system (Simpeg) as an information provider of election Officers Work Medal Awardees Satya Lencana In RRI Palangkaraya aims to be a place of useful information provider for submission of award Satya lencana karya satya so that it could be effective, efficient, and accurate by simplifying the existing system. By having this website is expected to handle the process of logging employees so that it can help in the process of registration of a Nobel Prize Medal work of satya.
Methodology in the making of this website using the method waterfall, waterfall method which consists of several parts or stages – stages, namely analysis, design, coding and testing. This methodology was chosen because every step of the development of this website is structured, and clearly documented. The programming language used is PHP and MySQL as a database.
At this stage of testing this website using black box testing. Black-Box Testing to focus on the functional specifications of the program. After doing the testing, can be seen the result of this site that this website can perform its function, namely to manage data, time data family history, history of education, employment, lencan setya, data filing SKP, and PKP
Dissertations / Theses on the topic "Waterfall methodology":
1
Mulbah, Julateh K., and Kahsay Tilahun Gebreslassie. "CO2-efficient retail locations: Building a web-based DSS by the Waterfall Methodology." Thesis, Högskolan Dalarna, Institutionen för information och teknik, 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:du-37741.
Abstract:
Several studies have been carryout on finding optimal locations to minimize CO2 emissions from the last mile distribution perspective. In conjunction with that, there has been no study conducted in Sweden that provides a decision support system to compute the transport consequences of the modifications in the retailer’s store network. This thesis did used the following steps: requirement analysis, system design, implementation and testing to build a prototype decision support system that is to help retailers find optimal locations for a new retail store. This thesis provided a subsequent answer as to which data are needed along with the rightful user interface for said decision support system. Subsequently, this thesis does present a decision support system prototype from which some recommendations were provided as to what skills set and tools are needed for the management and maintenance of said decision support system. The primary data used during this thesis is the Dalarna municipalities, six selected retailer’s stores networks and the Dalarna Road network geo-data (Longitude and latitude). This thesis does conclude that it is possible to integrate an optimization model within the Django framework using a geo data to build a decision support system.
2
Naseem, Junaid, and Wasim Tahir. "Study and analysis of the challenges and guidelines of transitioning from waterfall development model to Scrum." Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-2679.
Abstract:
Software engineering practices have experienced significant changes over the period of past two decades. Keeping in view the competitive market trends, now is the high time for many organizations to shift from traditional waterfall models to more agile technologies like Scrum [22][23]. A change of this magnitude is often not easy to undertake. The reason that both software engineering techniques are different in many respects, organizations require considerable amount of analysis of the whole transitioning process and possible scenarios that may occur along the way. Small and medium organizations are normally very skeptical to the change of this magnitude. The scale of change is not limited to only software processes, in fact, difficult part is to deal with old attitudes and thinking processes and mold them for the new agile based Scrum development. The process of change therefore need to be understood in the first place and then carefully forwarded to the implementation phase.
3
Szuchan, Patrik. "Aplikace agilní metodiky v projektovém řízení." Master's thesis, Vysoké učení technické v Brně. Fakulta podnikatelská, 2020. http://www.nusl.cz/ntk/nusl-417697.
Abstract:
The diploma thesis deals with changes for streamlining project management, software development and work in development teams by introducing the agile Scrum methodology. The beginning of the diploma thesis deals with the theoretical background and basic concepts that are used in other parts of the work. The analytical part analyses the current state of the software division. In the design part, based on the results of the analysis, a proposal for changes in project management is created using the agile methodology, which aims to streamline project management and software development. At the end of the design part, economic evaluations of the design and its benefits for the division are processed.
4
Hellström, Douglas. "Uncertainty management – How to handle project uncertainty : A case study at Rimaster Development." Thesis, KTH, Skolan för industriell teknik och management (ITM), 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-299782.
Abstract:
We know that it is difficult to forecast the future, and the same applies to project management. There are a lot of occurrences that are both predictable and not possible throughout the course of a project. The management of uncertainty is a management method that helps to forecast and adjust to future occurrences. In this context, frameworks and tools have been created to help project managers genuinely understand a project's potential. The study was conducted as a case study at Rimaster Development in Söderhamn and aimed at discovering sources of uncertainty within their project development that affect project performance. The study is built on both quantitative and qualitative data gathering from a workshop, survey, meetings, and interviews from ten different projects of Rimaster. The study had five respondents who contributed with two projects, each of which they had been a part of previously, one classified as uncertain and one as more certain. The data were analyzed with the statistics tool SPSS, where variables were computed based on the empirical findings in the uncertainty survey. The result was then presented through uncertainty attribute matrices to identify how each project performed in relation to customer satisfaction as well as time plan and budget. Here, dependent variables were tested, such as if the uncertainty score (the higher value, the more uncertain is the project) influenced project performance. From the data, two categories of projects could be developed: Higher performing projects and lower performing projects. To this, significant analysis of the performance groups was performed to find parameters that were significantly different between the categories. To capture more data to the thesis, each project was then evaluated through an individual project analysis which consisted of analyzing the data from the survey more closely for each project. The findings from this were then supported with qualitative interviews. The findings in the study suggest that there is a relationship between project uncertainty and lower-performing projects in relationship to time plan and budget. Further, sixteen uncertainty parameters showed to have a significant value in the comparison between higher and lower performing projects. Based upon the data and the analysis of the study, managerial recommendations have been provided to Rimaster on tools and development processes that may assist the organization's uncertainty management and increase their project performance.Det är allmänt känt att det är omöjligt att tydligt förutsäga framtiden och detsamma gäller projektledning. Det finns många händelser som är både oförutsägbara och riskfyllda under ett projektets gång, där osäkerhetshanteringen är en hanteringsmetod som hjälper till att prognostisera och anpassa sig till framtida händelser. Tidigare forskning inom osäkerhetshantering har utvecklat ramar och verktyg för att hjälpa projektledare att verkligen förstå ett projekts potential. Studien genomfördes som en fallstudie vid Rimaster Development i Söderhamn och syftade till att upptäcka källor till osäkerhet inom deras utvecklingsavdelning som påverkar projektets prestanda. Studien bygger på både kvantitativ och kvalitativ datainsamling från en workshop, enkätundersökning, möten och intervjuer från tio olika projekt från Rimaster. Studien enkätundersökning hade fem svarande som bidrog med två projekt som de tidigare hade varit en del av, ett klassificerat som osäkert och ett som mer säkert. Data erhållen from enkäten analyserades med statistikverktyget SPSS där variabler beräknades baserat på empiriska resultat i osäkerhetsundersökningen. Resultatet presenterades sedan genom osäkerhetsattributmatriser för att identifiera hur varje projekt presterade i förhållande till kundnöjdhet samt tidsplan och budget. Här testades beroende variabler som om den osäkerhetspoängen varde projekt erhöll (ju högre värde, desto mer osäkert är projektet) hade en effekt på projektets prestanda. Från analysen kunde två kategorier av projekt utvecklas: projekt med högre prestanda och projekt med lägre prestanda. Utöver detta genomfördes en signifikansanalys av prestationsgrupperna för att hitta parametrar som var signifikanta olika mellan kategorierna. För att samla ytterliga data till avhandlingen utvärderades varje projekt genom en individuell projektanalys som bestod av att analysera data från undersökningen närmare för varje projekt. Resultaten från detta styrktes sedan med kvalitativa intervjuer. Resultaten i studien antyder att det finns ett samband mellan projektosäkerhet och projekt med lägre resultat i förhållande till tidsplan och budget. Vidare visade sig sexton osäkerhetsparametrar ha ett signifikant värde i jämförelsen mellan projekt med högre och lägre resultat. Baserat på analyseringen av den data studien samlat in så har rekommendationer överlämnats till Rimaster om verktyg och utvecklingsprocesser som kan hjälpa organisationens osäkerhetshantering och därmed öka deras projektprestanda.
5
Coetzee, Ziaén. "An interpretive study of the contingent use of systems development methodologies in the telecommunications industry / Z. Coetzee." Thesis, North-West University, 2010. http://hdl.handle.net/10394/5562.
Abstract:
The telecommunication industry is dominating the world. Most recently there have been
technological advancements made in mobile telecommunication. There are currently a few
telecommunication organizations in South Africa. These organizations each have their own unique
approach to service delivery. The strong competitive nature of the telecommunication industry is
taking telecommunications in South Africa to greater heights. All these advancements necessitate the
need for better security and controls of the telecommunications networks. RICA legislation was
brought into effect to accomplish just this. The research focuses on the contingent use of systems
development methodologies in the telecommunication industry in South Africa.
The study determines how these telecommunication organizations choose a systems development
methodology when developing systems. This study looks at how these organizations are currently
implementing system development methodologies to keep up with the changes and competition
within the industry. An interpretive approach was used to conduct the research. Four of the leading
telecommunication organizations in South Africa were studied by using case studies. Each case study
focused on a single telecommunication organization to gain in depth data regarding the use of systems
development methodologies. The case studies were conducted by using structured interviews to gain
data from multiple sources within the organizations. The data was analyzed using ATLAS.ti and a
cross case analysis was done to answer the research questions. The results indicate that there is a
contingent use of systems development methodologies within telecommunication organizations. The
telecommunication organizations each use criteria to determine which systems development
methodology to use. The results of the study indicate that there are different levels of contingency,
and it examines how this is accomplished by each organization individually. Each of the
organizations has a unique approach when selecting systems development methodologies. The
systems development methodologies that are used by the telecommunication organizations are also
tailored in some cases.Thesis (M.Sc. (Computer Science))--North-West University, Potchefstroom Campus, 2011.
6
Haavisto, Felix, Henrik Henriksson, Niklas Hätty, Johan Jansson, Fabian Petersen, David Pop, Viktor Ringdahl, and Sara Svensson. "Modernisering av ett 3D-scanningssystem : Utmaningar och lärdomar av ett projekt." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-130695.
Abstract:
Ett styrsystem för 3D-scanning har moderniserats av en projektgrupp på nio personer. Under utvecklingsarbetet följdes en arbetsprocess som liknade vattenfallsmetoden. Arbetsprocessen fungerade bra, bland annat då projektgruppen utnyttjat både tidigare och nya erfarenheter för att förbättra arbetssättet. Systemet som utvecklades ersätter ett tidigare styrsystem baserat på Matlab, men behåller samma grundläggande uppsättning hårdvara. En avståndskamera, en linjärenhet och ett rotationsbord utgör grunden till systemet. Med hjälp av denna hårdvara möjliggör systemet 3D-scanningar av mindre objekt. Styrsystemet är utvecklat med Python och ROS, Robot Operating System. Valet av ROS ledde till en komplex arkitektur på grund av skillnader i systemkrav hos ROS och hårdvarudrivrutiner. Utan dessa systemkrav tros ROS ha varit ett ypperligt val. Den utvecklade arkitekturen jämförs med en alternativ hypotetisk arkitektur, vilken uppvisade lägre komplexitet och större portabilitet. Den är dock inte lika lättanvänd tillsammans med andra ROS-system. Under utvecklingsarbetet har modularitet, vidareutvecklingsbarhet och robusthet varit i fokus. Även om det fullständiga systemet inte är så robust som önskats så anses de ingående modulerna uppvisa en önskad nivå av robusthet. Systemet uppvisar även en hög grad av modularitet. Den utförligt dokumenterade koden tillsammans med de väl separerade modulerna har lett till att systemet bör vara lätt att vidareutveckla.
Books on the topic "Waterfall methodology":
1
R, Johnson Stephen. Design and testing of a monitoring program for Beaufort Sea waterfowl and marine birds. Herndon, VA: U.S. Dept of Interior, Minerals Management Service, Procurement Operations Branch, 1992.
Book chapters on the topic "Waterfall methodology":
1
Shah, Abad. "OODM." In Information Modeling for Internet Applications, 189–229. IGI Global, 2003. http://dx.doi.org/10.4018/978-1-59140-050-9.ch010.
Abstract:
Today, the Internet and the Web are the most amazingly and dynamically growing computer technologies. The number of users accessing the Web is growing exponentially all over the world. The Web has become a popular environment for new generation of interactive computer applications called Web (or hypermedia) application. The Web applications (WAs) have special characteristics that have made them different from other traditional applications. Hence, many design methodologies for the development of WAs have been proposed. However, most of these methodologies concentrate on the design aspects of applications, and they often do not strictly follow any software development life-cycle model such as the WaterFall software development life-cycle model. In this chapter, we propose an object-oriented design methodology for the development of WAs. The main features of this proposed methodology are that it follows WaterFall model and captures the operations in objects of the applications; thus making the methodology an object-oriented methodology.
2
Etim, Alice S., Chandra Prakash Jaiswal, Marsheilla Subroto, and Vivian E. Collins Ortega. "Managing Information Technology Projects Using Agile Methodology." In Advances in IT Standards and Standardization Research, 123–46. IGI Global, 2021. http://dx.doi.org/10.4018/978-1-7998-3468-7.ch007.
Abstract:
The management of information technology (IT) projects has experienced a shift from predictive and traditional project management methodology to more adaptive practices like Agile. Agile method and its developmental stages are a response to current business-changing trends and computing needs of society. The process assists in accelerating product delivery with rapid feedback and cost-conscious, consecutive iteration, distinguishing it from other traditional practices like the waterfall method. This chapter contributes to the existing literature by discussing agile project management for IT projects, with a specific case of the Africa IT project – the Books for Africa Project (hereafter called, Book Project). The first part of the chapter is used to review the literature on Agile IT projects. The Book Project as a case is an IT project, and it is discussed in detail in the chapter. The chapter concludes with transferable lessons for projects in developing countries, specifically those located in Sub-Saharan Africa.
3
Garling, Richard. "Does an Open Source Development Environment Facilitate Conventional Project Management Approaches and Collaborative Work?" In Information Technology as a Facilitator of Social Processes in Project Management and Collaborative Work, 99–123. IGI Global, 2018. http://dx.doi.org/10.4018/978-1-5225-3471-6.ch006.
Abstract:
Open source software (OSS) is very well known for allowing free access to the source code of the application. The idea is to allow for the creation of a better product. The more people working to make each aspect of an application better, more minds create more ideas, create a better project. OSS runs the internet since all of the protocols—network time protocol (NTP), HTTP, amongst many others—are OSS projects with many years of use. These projects are run by volunteers worldwide. But, none of these projects are run using the traditional methodologies of project management: Waterfall and Agile. This chapter asks: How does an open source development environment facilitate conventional Waterfall project management approaches? and How does an open source development environment facilitate Agile project collaborative work? The method used to determine the answers used surveys and questionnaires involving actual participants in a variety of OSS projects from across the United States (US). The questions asked concerned the organization OSS projects, did they use a particular traditional methodology or some other non-defined method of organization? The answers received by this study centered on non-defined methods of organization; traditional methodologies were considered too restrictive and not agile enough to allow for the freedom cherished by their volunteers.
4
Garling, Richard. "Does an Open Source Development Environment Facilitate Conventional Project Management Approaches and Collaborative Work?" In Research Anthology on Usage and Development of Open Source Software, 239–56. IGI Global, 2021. http://dx.doi.org/10.4018/978-1-7998-9158-1.ch013.
Abstract:
Open source software (OSS) is very well known for allowing free access to the source code of the application. The idea is to allow for the creation of a better product. The more people working to make each aspect of an application better, more minds create more ideas, create a better project. OSS runs the internet since all of the protocols—network time protocol (NTP), HTTP, amongst many others—are OSS projects with many years of use. These projects are run by volunteers worldwide. But, none of these projects are run using the traditional methodologies of project management: Waterfall and Agile. This chapter asks: How does an open source development environment facilitate conventional Waterfall project management approaches? and How does an open source development environment facilitate Agile project collaborative work? The method used to determine the answers used surveys and questionnaires involving actual participants in a variety of OSS projects from across the United States (US). The questions asked concerned the organization OSS projects, did they use a particular traditional methodology or some other non-defined method of organization? The answers received by this study centered on non-defined methods of organization; traditional methodologies were considered too restrictive and not agile enough to allow for the freedom cherished by their volunteers.
Conference papers on the topic "Waterfall methodology":
1
Borges, S. S., R. Barbieri, and P. S. B. Zdanski. "Analysis of the Noise Level Generated by Axial Flow Fan Composed of Radial-Bladed Centrifugal Rotor." In ASME Turbo Expo 2014: Turbine Technical Conference and Exposition. American Society of Mechanical Engineers, 2014. http://dx.doi.org/10.1115/gt2014-26415.
Abstract:
The objective of this work is to present, by means of experimental, analytical and numerical techniques that sound pressure level generated by radial-bladed centrifugal fans of electric motor cooling systems may be expressed by a logarithmical ratio of the peripheral velocity of rotor, volumetric flow and efficiency of the fan. The proposed methodology proved to be efficient and simple in the prediction of generated noise by radial-bladed centrifugal fans of TEFC motors with accuracy of ± 3 dB. In addition, the acoustic resonance mode of the fan cavity were determined by means of numerical simulations, which its results were validated through experiments using waterfall spectrum.