Увійти

Готові списки джерел за темами / Software development methodologies / Статті в журналах

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

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

Автор: Grafiati

Опубліковано: 4 червня 2021

Оновлено: 13 лютого 2022

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

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

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

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

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

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

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.

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

Анотація:

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.

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

2

Kacmar, Charles J., Denise J. McManus, Evan W. Duggan, Joanne E. Hale, and David P. Hale. "Software Development Methodologies in Organizations." Information Resources Management Journal 22, no. 3 (July 2009): 16–39. http://dx.doi.org/10.4018/irmj.2009070102.

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

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

3

Soobia.et.al., Saeed. "Analysis of Software Development Methodologies." International Journal of Computing and Digital Systems 8, no. 5 (January 9, 2019): 445–60. http://dx.doi.org/10.12785/ijcds/080502.

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

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

4

Conger, Sue. "Software Development Life Cycles and Methodologies." International Journal of Information Technologies and Systems Approach 4, no. 1 (January 2011): 1–22. http://dx.doi.org/10.4018/jitsa.2011010101.

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

Анотація:

Information Systems as a discipline has generated thousands of research papers, yet the practice still suffers from poor-quality applications. This paper evaluates the current state of application development, finding practice wanting in a number of areas. Changes recommended to fix historical shortcomings include improved management attention to risk management, testing, and detailed work practices. In addition, for industry’s move to services orientation, recommended changes include development of usable interfaces and a view of applications as embedded in the larger business services in which they function. These business services relate to both services provided to parent-organization customers as well as services provided by the information technology organization to its constituents. Because of this shift toward service orientation, more emphasis on usability, applications, testing, and improvement of underlying process quality are needed. The shift to services can be facilitated by adopting tenets of IT service management and user-centered design and by attending to service delivery during application development.

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

5

Alsaqqa, Samar, Samer Sawalha, and Heba Abdel-Nabi. "Agile Software Development: Methodologies and Trends." International Journal of Interactive Mobile Technologies (iJIM) 14, no. 11 (July 10, 2020): 246. http://dx.doi.org/10.3991/ijim.v14i11.13269.

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

Анотація:

<p>Software engineering is a discipline that undergone many improvements that aims to keep up with the new advancements in technologies and the modern business requirements through developing effective approaches to reach the final software product, agile software development is one of these successful approaches. Agile software development is a lightweight approach that was proposed to overcome the convolutional development methods’ limitations and to reduce the overhead and the cost while providing flexibility to adopt the changes in requirements at any stage, this is done by managing the tasks and their coordination through a certain set of values and principles.</p><p>In this work, a comprehensive review that outlines the main agile values and principles, and states the key differences that distinguish agile methods over the traditional ones are presented. Then a discussion of the most popular agile methodologies; their life cycles, their roles, and their advantages and disadvantages are outlined. The recent state of art trends that adopts agile development especially in cloud computing, big data, and coordination are also explored. And finally, this work highlights how to choose the best suitable agile methodology that must be selected according to the task at hand, how sensitive the product is and the organization structure.</p>

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

6

Kumar, Rakesh, Priti Maheshwary, and Timothy Malche. "Inside Agile Family Software Development Methodologies." International Journal of Computer Sciences and Engineering 7, no. 6 (June 30, 2019): 650–60. http://dx.doi.org/10.26438/ijcse/v7i6.650660.

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

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

7

Chandra, Vishal. "Comparison between Various Software Development Methodologies." International Journal of Computer Applications 131, no. 9 (December 17, 2015): 7–10. http://dx.doi.org/10.5120/ijca2015907294.

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

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

8

Jovanovic, Aca, Filip Jovanovic, Ljiljana Miletic, and Ivana Beric. "Application of agile methodologies in software development." Tehnika 71, no. 6 (2016): 896–900. http://dx.doi.org/10.5937/tehnika1606896j.

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

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

9

Al-Zewairi, Malek, Mariam Biltawi, Wael Etaiwi, and Adnan Shaout. "Agile Software Development Methodologies: Survey of Surveys." Journal of Computer and Communications 05, no. 05 (2017): 74–97. http://dx.doi.org/10.4236/jcc.2017.55007.

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

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

10

Zakrzewski, Pawel, Janusz Narkiewicz, and Darren Brenchley. "Safety Critical Software Development Methodologies in Avionics." Transactions on Aerospace Research 2020, no. 2 (June 1, 2020): 59–71. http://dx.doi.org/10.2478/tar-2020-0011.

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

Анотація:

AbstractThis article summarizes avionics safety-critical software development methodologies and implications of the DO-178C standard from an Agile application perspective. We explain the safety-critical software categorization. It also outlines the main differences and advantages of different approaches to the development process, from Waterfall through the V-model to Iterative and Incremental. Agile principles are explained as well as a Scrum – which is a popular framework in the non-safety-critical software industry. The application of Agile, for safety-critical software considerations, is based on the practical knowledge of the authors, and looks at the potential solution from a DO-178C standard, size of the project, scalability, and organizational culture points of view. Definition of the Agile type of framework, consistent with the certification process and existing standards, has been highlighted as a potential game-changer for the avionics industry.

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

11

Gonzalez-Perez, Cesar, and Brian Henderson-Sellers. "Templates and Resources in Software Development Methodologies." Journal of Object Technology 4, no. 4 (2005): 173. http://dx.doi.org/10.5381/jot.2005.4.4.a5.

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

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

12

Gonzalez-Perez, Cesar, and Brian Henderson-Sellers. "Modelling software development methodologies: A conceptual foundation." Journal of Systems and Software 80, no. 11 (November 2007): 1778–96. http://dx.doi.org/10.1016/j.jss.2007.02.048.

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

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

13

Lindstrom, Lowell, and Ron Jeffries. "Extreme Programming and Agile Software Development Methodologies." Information Systems Management 21, no. 3 (June 2004): 41–52. http://dx.doi.org/10.1201/1078/44432.21.3.20040601/82476.7.

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

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

14

Mishra, Alok, and Deepti Mishra. "A curriculum for agile software development methodologies." ACM SIGSOFT Software Engineering Notes 36, no. 3 (May 5, 2011): 1–2. http://dx.doi.org/10.1145/1968587.1968608.

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

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

15

Wasserman, Anthony I. "Modern software development methodologies and their environments." Computer Physics Communications 38, no. 2 (October 1985): 119–34. http://dx.doi.org/10.1016/0010-4655(85)90079-7.

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

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

16

Matharu, Gurpreet Singh, Anju Mishra, Harmeet Singh, and Priyanka Upadhyay. "Empirical Study of Agile Software Development Methodologies." ACM SIGSOFT Software Engineering Notes 40, no. 1 (February 6, 2015): 1–6. http://dx.doi.org/10.1145/2693208.2693233.

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

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

17

Gonzalez-Perez, Cesar, Tom McBride, and Brian Henderson-Sellers. "A Metamodel for Assessable Software Development Methodologies." Software Quality Journal 13, no. 2 (June 2005): 195–214. http://dx.doi.org/10.1007/s11219-005-6217-7.

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

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

18

Gbaranwi, Barima Precious, Ojekudo, and Nathaniel Akpofure. "A Comparative Analysis of Software Development Methodologies." International Journal of Research and Innovation in Applied Science 06, no. 05 (2021): 159–66. http://dx.doi.org/10.51584/ijrias.2021.6513.

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

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

19

Deepak Dahiya, and Pooja Jain. "Enterprise Systems Development: Impact of Various Software Development Methodologies." International Journal of Advancements in Computing Technology 2, no. 4 (October 31, 2010): 77–87. http://dx.doi.org/10.4156/ijact.vol2.issue4.8.

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

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

20

Lytvynov, V. V., I. V. Bogdan, A. О. Zadorozhnyi, and I. V. Bilous. "Task prioritization methods in flexible software development methodologies." Mathematical machines and systems 2 (2020): 70–78. http://dx.doi.org/10.34121/1028-9763-2020-2-70-78.

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

Анотація:

The modern task prioritization methods that are used in flexible software development methodologies are discussed in the paper. Very flexible development methodologies such as Scrum, Kunban and others are currently the most popular because they allow making adjustments to it at any stage of a project, to improve the quality of the created product through daily monitoring of its creation and quickly release the first versions of the software. All task prioritization methods that are used in software projects de-velopment including flexible methodologies are divided into those that take into account the point of view of the development team and those that are based on various quantitative assessments, among which various metrics, expert opinions, points of view of those who are interested in the project, availa-ble classifications etc. Among the considered prioritization methods, which take into account the opin-ion of the development team, there are such popular and actively used nowadays methods, as MoSCoW, story map (User story mapping) and proactive improvement. Among the considered methods, based on quantitative assessment, is Kano's model, the method based on the creation of evaluation sheets, the method for estimating relative priorities for a set of functions offered by Carl Wigers and the method of structuring quality functions (Quality Function Deployment). Depending on the features of the project, customer requirements, the wishes of the development team and the other objective or subjective fac-tors, the project can use one or several prioritization methods at the same time or the combination of them. In addition, some of the considered methods can be used in short-term planning, the others – in the long-term, but there are those that can be used at each stage.

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

21

Tegegne, Esubalew Workineh, Pertti Seppänen, and Muhammad Ovais Ahmad. "Software development methodologies and practices in start‐ups." IET Software 13, no. 6 (December 2019): 497–509. http://dx.doi.org/10.1049/iet-sen.2018.5270.

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

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

22

Boehm-Davis, Deborah A., and Lyle S. Ross. "Program design methodologies and the software development process." International Journal of Man-Machine Studies 36, no. 1 (January 1992): 1–19. http://dx.doi.org/10.1016/0020-7373(92)90050-u.

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

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

23

Saeedi, Kawther, and Anna Visvizi. "Software Development Methodologies, HEIs, and the Digital Economy." Education Sciences 11, no. 2 (February 13, 2021): 73. http://dx.doi.org/10.3390/educsci11020073.

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

Анотація:

Progressing digitalization of business, economy, and the society places higher education institutions (HEIs) in the center of the debate on how to effectively respond to challenges and opportunities that are thus triggered. Several facets of this process and corresponding challenges exist, including the complex question of how to match students’ skills and competencies with the demands and expectations of the industry. From a different angle, considering the changing nature of work, HEIs are responsible for equipping future employees with skills necessary to work in virtual, distributed, culturally diverse, and frequently global, teams. In the domain of software development, i.e., the backbone of the digital world, the challenge HEIs need to face is paramount. For this reason, the way software development is taught at HEIs is crucial for the industry, for the economy, for the students, and for the HEIs. As there is a tendency in the industry to embrace the scrum method and seek employees equipped with skills necessary for the scrum methodology use, it is necessary to ensure that HEIs offer the students the opportunity to get exposed to scrum. By querying the challenges of switching to agile software development methodologies in senior capstone projects, this paper makes a case that software development and software development methodology form the thrust of a multi-stakeholder ecosystem that defines today’s digital economy and society. In this context, the added value of this paper rests in the elaboration of a method enabling HEIs to move toward scrum in senior projects.

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

24

Prof. Prashant Keswani, Prof Sapana Desai,. "Software Testing Methodologies: A Information Review." International Journal on Recent and Innovation Trends in Computing and Communication 9, no. 2 (February 28, 2021): 01–05. http://dx.doi.org/10.17762/ijritcc.v9i2.5455.

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

Анотація:

In today’s Complex era, the need for simplest software application has increased massively. The quality of such a handy application along with adequate testing is the biggest challenge one can face. Software Testing is an integral part of any software development which has to be followed right from the sapling phase of development. This paper focuses on testing methodologies which are used prior along with testing techniques for quality assurance and best of the quality.

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

25

Gómez-Sanz, Jorge J., and Rubén Fuentes-Fernández. "Understanding Agent-Oriented Software Engineering methodologies." Knowledge Engineering Review 30, no. 4 (September 2015): 375–93. http://dx.doi.org/10.1017/s0269888915000053.

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

Анотація:

AbstractFor many years, the progress in agent-oriented development has focused on tools and methods for particular development phases. This has not been enough for the industry to accept agent technology as we expected. Our hypothesis is that the Agent-Oriented Software Engineering (AOSE) community has not recognized the kind of development methods that industry actually demands. We propose to analyze this hypothesis starting with a more precise definition of what an AOSE methodology should be. This definition is the first step for a review of the current progress of an illustrative selection of methodologies, looking for missing elements and future lines of improvement. The result is an account of how well the AOSE community is meeting the software lifecycle needs. It can be advanced that AOSE methodologies are far from providing all the answers industry requires and that effort has grounded mainly in requirements, design, and implementation phases.

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

26

Khan, Rashid Ali, Muhammad Faisal Abrar, Samad Baseer, Muhammad Faran Majeed, Muhammad Usman, Shams Ur Rahman, and You-Ze Cho. "Practices of Motivators in Adopting Agile Software Development at Large Scale Development Team from Management Perspective." Electronics 10, no. 19 (September 24, 2021): 2341. http://dx.doi.org/10.3390/electronics10192341.

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

Анотація:

Agile software development methodologies have become the most popular software development methods in the last few years. These methodologies facilitate rapid development. The low cost and prioritized user satisfaction make these methodologies more attractive. These methodologies were also intended for small scale developmental teams. Therefore, challenges were encountered when these methodologies were used in large-scale development teams. This study was based on the identification of factors which were discovered in our previous study. Some of the factors included “leadership strong commitment and team autonomy”, “cooperative organizational culture”, and “team competency—agile development expertise”. A total of 147 practices were identified in this study via a systematic literature review. These practices will help practitioners and project managers to adopt agile software methodologies and encourage them to the enhance them.

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

27

De Cesare, Sergio, Chaitali Patel, Nicola Iacovelli, Antonio Merico, and Mark Lycett. "Tailoring Software Development Methodologies in Practice: A Case Study." Journal of Computing and Information Technology 16, no. 3 (2008): 157. http://dx.doi.org/10.2498/cit.1000898.

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

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

28

Shah, Abad. "A Framework for the Prototype-based Software Development Methodologies." Journal of King Saud University - Computer and Information Sciences 13 (2001): 111–31. http://dx.doi.org/10.1016/s1319-1578(01)80006-9.

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

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

29

Sauer, Stefan, and Amelie Tihlarik. "NEW SOFTWARE DEVELOPMENT METHODOLOGIES BETWEEN DIVERSITY AND GENDER STEREOTYPES." Review of Business Research 20, no. 1 (June 1, 2020): 5–18. http://dx.doi.org/10.18374/rbr-20-1.1.

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

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

30

Sousa, Kenia, Jean Vanderdonckt, Brian Henderson-Sellers, and Cesar Gonzalez-Perez. "Evaluating a graphical notation for modelling software development methodologies." Journal of Visual Languages & Computing 23, no. 4 (August 2012): 195–212. http://dx.doi.org/10.1016/j.jvlc.2012.04.001.

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

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

31

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.

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

Анотація:

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.

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

32

Connors, Danny T. "Software development methodologies and traditional and modern information systems." ACM SIGSOFT Software Engineering Notes 17, no. 2 (April 1992): 43–49. http://dx.doi.org/10.1145/130840.130843.

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

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

33

Ramsin, Raman, and Richard F. Paige. "Process-centered review of object oriented software development methodologies." ACM Computing Surveys 40, no. 1 (February 2008): 1–89. http://dx.doi.org/10.1145/1322432.1322435.

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

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

34

Bates, Andrew. "Implement your DAM solution using Agile software development methodologies." Journal of Digital Asset Management 3, no. 4 (August 2007): 173–76. http://dx.doi.org/10.1057/palgrave.dam.3650087.

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

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

35

Mutschler, Richard, Oliver Trost, and Jürgen Crepin. "Agile Methodologies in the Development of Automotive Embedded Software." ATZelectronics worldwide 15, no. 7-8 (July 2020): 44–49. http://dx.doi.org/10.1007/s38314-020-0225-z.

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

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

36

Nicolaysen, Torstein, Richard Sassoon, Maria B. Line, and Martin Gilje Jaatun. "Agile Software Development." International Journal of Secure Software Engineering 1, no. 3 (July 2010): 71–85. http://dx.doi.org/10.4018/jsse.2010070105.

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

Анотація:

In this article, the authors contrast the results of a series of interviews with agile software development organizations with a case study of a distributed agile development effort, focusing on how information security is taken care of in an agile context. The interviews indicate that small and medium-sized agile software development organizations do not use any particular methodology to achieve security goals, even when their software is web-facing and potential targets of attack. This case study confirms that even in cases where security is an articulated requirement, and where security design is fed as input to the implementation team, there is no guarantee that the end result meets the security objectives. The authors contend that security must be built as an intrinsic software property and emphasize the need for security awareness throughout the whole software development lifecycle. This paper suggests two extensions to agile methodologies that may contribute to ensuring focus on security during the complete lifecycle.

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

37

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 та ін.

38

Machado, Ricardo J., Flávio R. Wagner, and Rick Kazman. "Introduction to special issue: model-based development methodologies." Innovations in Systems and Software Engineering 5, no. 1 (February 10, 2009): 1–3. http://dx.doi.org/10.1007/s11334-009-0076-5.

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

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

39

Iyawa, Gloria E., Marlien E. Herselman, and Alfred Coleman. "Customer Interaction in Software Development: A Comparison of Software Methodologies Deployed in Namibian Software Firms." Electronic Journal of Information Systems in Developing Countries 77, no. 1 (November 2016): 1–13. http://dx.doi.org/10.1002/j.1681-4835.2016.tb00560.x.

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

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

40

РУДНИЧЕНКО, Н. Д. "FLEXIBLE METHODOLOGIES EFFICIENCY RESEARCH IN PRACTICE OF MODERN SOFTWARE DEVELOPMENT COMPANIES." Transport development, no. 1(1) (September 27, 2017): 171–77. http://dx.doi.org/10.33082/td.2017.1-1.20.

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

Анотація:

The results of research on the effectiveness of the use of flexible software development methodologies in the practice of modern companies are presented. The results of the survey on the use of project management methodologies, as well as the results of the cost analysis of 9 different projects are presented. The peculiarities of various agile development methodologies are revealed at their practical application.

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

41

M.M.Safwan, M., Thavarajah G., Vijayarajah N., K. Senduran, and C. D. Manawadu. "An Empirical Study of Agile Software Development Methodologies: A Sri Lankan PerspectiveAn Empirical Study of Agile Software Development Methodologies: A Sri Lankan Perspective." International Journal of Computer Applications 84, no. 8 (December 18, 2013): 1–7. http://dx.doi.org/10.5120/14593-2832.

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

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

42

Dingsøyr, Torgeir, Sridhar Nerur, VenuGopal Balijepally, and Nils Brede Moe. "A decade of agile methodologies: Towards explaining agile software development." Journal of Systems and Software 85, no. 6 (June 2012): 1213–21. http://dx.doi.org/10.1016/j.jss.2012.02.033.

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

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

43

Zhang, Xihui, Tao Hu, Hua Dai, and Xiang Li. "Software Development Methodologies, Trends and Implications: A Testing Centric View." Information Technology Journal 9, no. 8 (November 1, 2010): 1747–53. http://dx.doi.org/10.3923/itj.2010.1747.1753.

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

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

44

Abou El-Seoud, Samir. "A Comparison of Various Software Development Methodologies: Feasibility and Methods of Integration." International Journal of Recent Contributions from Engineering, Science & IT (iJES) 4, no. 4 (December 30, 2016): 50. http://dx.doi.org/10.3991/ijes.v4i4.6547.

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

Анотація:

<p class="Abstract">System development methodologies which have being used in the academic and commercial environments during last two decades have advantages and disadvantages. Researchers had tried to identify objectives, scope …etc. of the methodologies by following different approaches. Each approach has its Limitation, specific interest, coverage …etc. In this paper, we tried to perform a comparative study of those methodologies which are popular and commonly used in banking and commercial environment. We tried in our study to determine objectives, scope, tools and other features of the methodologies. We also, tried to determine how and to what extent the methodologies incorporate the facilities such as project management, cost benefit analysis, documentation …etc. One of the most important aspects of our study was how to integrate the methodologies and develop a global methodology which covers the complete span of the software development life cycle? A prototype system which integrates the selected methodologies has been developed. The developed system helps analysts and designers how to choose suitable tools or to obtain guidelines on what to do in a particular situation. The prototype system has been tested during the development of a software for an ATM “Auto Teller Machine” by selecting and applying SASD methodology during software development. This resulted in the development of high quality and well documented software system.</p>

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

45

Introne, J., R. Laubacher, and T. Malone. "Enabling Open Development Methodologies in Climate Change Assessment Modeling." IEEE Software 28, no. 6 (November 2011): 56–61. http://dx.doi.org/10.1109/ms.2011.115.

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

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

46

Et.al, Javed Iqbal. "The Effects of Agile Methodologies on Software Project Management in Pakistani Software Companies." Turkish Journal of Computer and Mathematics Education (TURCOMAT) 12, no. 3 (April 11, 2021): 1717–27. http://dx.doi.org/10.17762/turcomat.v12i3.996.

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

Анотація:

Agile methodologies are always tends to increase the quality of software and also handling the complex software projects. However, the software companies in Pakistan have recently felt the disparity of producing successful software. In this context, an extensive survey has been conducted in 52 prominent software development companies of Pakistan to identify this remedy and the motivation behind this production discrepancy. It is revealed from the survey that there is a lack of empirical evidence in the relationship of agile methodologies with the effective and progressive management of software project management factors including, schedule, scope, risk, budget, quality and resources. Therefore, the proposed study delivers an extensive statistical comparison to determine the effectiveness of agile methodologies in terms of their effects on the project management factors. The results suggest that in general all agile methodologies play a significant role towards the successful software development in the software company. However, Extreme Programming, Scrum, Kanban and Agile modeling are the main determinants of production disparity among software companies. Furthermore, it is determined that the quality factor has a positive correlation with the rest of the factors. It is also found that the budget factor has significantly correlated with other five factors, while rest of the factors has insignificant correlation. We have also compared agile methodologies in terms of project management factors, which specify that each agile methodology has its own importance and effect with respect to managing different factors of project management.

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

47

Ceja, Jesús Manuel Olivares, and Emilio Buendía Cervantes. "Software Development Integrating Methodology with Epistemology Promoting Knowledge Production." International Journal of Technology and Educational Marketing 4, no. 1 (January 2014): 106–15. http://dx.doi.org/10.4018/ijtem.2014010109.

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

Анотація:

Currently, many specialties should be mastered to produce software, consequently they fall in different levels of knowledge: project, system, program, or routine. This consideration was obtained through an epistemological approach in software development. Therefore, this article develops this consideration for students learning software production. The epistemological approach compliments the methodologies used during software generation. The main focus in this proposal is on applying learning principles, combining both the epistemological approach and methodologies to promote student knowledge production for software development. The implementation of the proposal provides students with a framework that prepares them to face software development problems with different levels of complexity. Evaluation is based on verifying which of the different epistemological categories the student masters.

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

48

Zayat, Wael, and Ozlem Senvar. "Framework Study for Agile Software Development Via Scrum and Kanban." International Journal of Innovation and Technology Management 17, no. 04 (June 2020): 2030002. http://dx.doi.org/10.1142/s0219877020300025.

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

Анотація:

This paper provides a systematic comparison between two well-known Agile methodologies: Scrum, which is a framework of doing projects by allocating tasks into small stages called sprints, and Kanban, which is a scheduling system to manage the flow of work by means of visual signals. In this regard, both methodologies were reviewed to explore similarities and differences between them. Then, a focus group survey was performed to specify the preferable methodology for product development according to various parameters in the project environment including project complexity, level of uncertainty, and work size with consideration of output factors like quality, productivity, and delivery. Results show the flexibility of both methodologies in approaching Agile objectives, where Scrum emphasizes on the corporation of the customer and development teams with a focus on particular skills such as planning, organization, presentation, and reviewing which makes it ideal for new and complex projects where a regular involvement of the customer is required, whereas Kanban is more operative in continuous-flow environments with a steady approach toward a system improvement.

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

49

ZHOU, Zhi-Ying. "Perfect Ball in Nature—On Software Development Methodologies for Distributed Systems." Journal of Software 16, no. 12 (2005): 2166. http://dx.doi.org/10.1360/jos162166.

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

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

50

Onokoy, Lyudmila, and Jurijs Lavendels. "Evolution and Development Prospects of Information System Design Methodologies." Applied Computer Systems 23, no. 1 (May 1, 2018): 63–68. http://dx.doi.org/10.2478/acss-2018-0008.

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

Анотація:

Abstract The article investigates different approaches to the design of information systems. Much attention is paid to comparative analysis of criteria for selecting methodologies for software development, and also to not well-known methodology of DevOps (Development & Operation) [1], [2], which aims at consolidation of software developers (Development) and IT professionals’ (Operation) efforts, and automation of implementation process. In conclusion, based on the retrospective analysis and practical experience, the authors formulate regularities and prospects of information systems design methodology development.

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

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