Щоб переглянути інші типи публікацій з цієї теми, перейдіть за посиланням: Agile software process models.
Статті в журналах з теми "Agile software process models"
Оформте джерело за APA, MLA, Chicago, Harvard та іншими стилями
Ознайомтеся з топ-50 статей у журналах для дослідження на тему "Agile software process models".
Біля кожної праці в переліку літератури доступна кнопка «Додати до бібліографії». Скористайтеся нею – і ми автоматично оформимо бібліографічне посилання на обрану працю в потрібному вам стилі цитування: APA, MLA, «Гарвард», «Чикаго», «Ванкувер» тощо.
Також ви можете завантажити повний текст наукової публікації у форматі «.pdf» та прочитати онлайн анотацію до роботи, якщо відповідні параметри наявні в метаданих.
Переглядайте статті в журналах для різних дисциплін та оформлюйте правильно вашу бібліографію.
1
Ünver, Mahmut. "Software Process Models and Agile Method Applicability in Industry." International Journal of Trend in Scientific Research and Development Volume-3, Issue-1 (December 31, 2018): 1285–89. http://dx.doi.org/10.31142/ijtsrd20238.
Повний текст джерела
2
Jain, Parita, Arun Sharma, and Laxmi Ahuja. "Software Maintainability Estimation in Agile Software Development." International Journal of Open Source Software and Processes 9, no. 4 (October 2018): 65–78. http://dx.doi.org/10.4018/ijossp.2018100104.
Повний текст джерелаАнотація:
Agile methodologies have gained wide acceptance for developing high-quality products with a quick and flexible approach. However, until now, the quality of the agile process has not been validated quantitatively. Quality being important for the software system, there is a need for measurement. Estimating different quality factors will lead to a quality product. Also, agile software development does not provide any precise models to evaluate maintainability. Therefore, there is a need for an algorithmic approach that can serve as the basis for estimation of maintainability. The article proposes an adaptive neuro-fuzzy inference system (ANFIS) model for estimating agile maintainability. Maintainability is one of the prominent quality factors in the case of agile development. The proposed model has been verified and found to be effective for assessing the maintainability of agile software.
3
Silas, Faki Agebee, Musa Yusuf, and Anah Hassan Bijik. "Hybridization of Class Responsibility Collaborators Model (HCRCM) with Function Point to enhance Project Estimation Cost in Agile Software Development." Circulation in Computer Science 2, no. 6 (July 20, 2017): 20–24. http://dx.doi.org/10.22632/ccs-2017-252-32.
Повний текст джерелаАнотація:
Estimating software cost in an agile system in terms of effort is very challenging. This is because the traditional models of software cost estimation do not completely fit in the agile development process. This paper presents a methodology to enhance the cost of project estimation in agile development. The hybridization adopts Class Responsibility Collaborators models with function point thereby boosting the agile software development estimation process. The study found out that adopting the Hybridized Class Responsibility Collaborator with function point has great improvement on cost estimation in agile software development.
4
A. Haraty, Ramzi, and Gongzhu Hu. "Software process models: a review and analysis." International Journal of Engineering & Technology 7, no. 2.28 (June 22, 2018): 390. http://dx.doi.org/10.14419/ijet.v7i2.28.14537.
Повний текст джерелаАнотація:
Modeling of software process has been a very challenging problem and constantly debated in the software development community in the past 30+ years, largely due to the complex nature of the software development process that involves not only the technical knowledge and skills but also many other factors, such as human, management, quality assessment, and cost. Although the situations of creating software differ greatly from one case to another, there are some common themes shared by many of the situations, and hence various software process models have been emerged to address these common themes. In this paper, we present a review of the software process models commonly used in practice, from traditional to agile, and assessment of these models with metrics and case studies.
5
A. Haraty, Ramzi, and Gongzhu Hu. "Software process models: a review and analysis." International Journal of Engineering & Technology 7, no. 2.29 (May 22, 2018): 325. http://dx.doi.org/10.14419/ijet.v7i2.29.13206.
Повний текст джерелаАнотація:
Modeling of software process has been a very challenging problem and constantly debated in the software development community in the past 30+ years, largely due to the complex nature of the software development process that involves not only the technical knowledge and skills but also many other factors, such as human, management, quality assessment, and cost. Although the situations of creating software differ greatly from one case to another, there are some common themes shared by many of the situations, and hence various software process models have been emerged to address these common themes. In this paper, we present a review of the software process models commonly used in practice, from traditional to agile, and assessment of these models with metrics and case studies.
6
van Driel, Willem Dirk, Jan Willem Bikker, Matthijs Tijink, and Alessandro Di Bucchianico. "Software Reliability for Agile Testing." Mathematics 8, no. 5 (May 13, 2020): 791. http://dx.doi.org/10.3390/math8050791.
Повний текст джерелаАнотація:
It is known that quantitative measures for the reliability of software systems can be derived from software reliability models, and, as such, support the product development process. Over the past four decades, research activities in this area have been performed. As a result, many software reliability models have been proposed. It was shown that, once these models reach a certain level of convergence, it can enable the developer to release the software and stop software testing accordingly. Criteria to determine the optimal testing time include the number of remaining errors, failure rate, reliability requirements, or total system cost. In this paper, we present our results in predicting the reliability of software for agile testing environments. We seek to model this way of working by extending the Jelinski–Moranda model to a “stack” of feature-specific models, assuming that the bugs are labeled with the features they belong to. In order to demonstrate the extended model, two use cases are presented. The questions to be answered in these two cases are: how many software bugs remain in the software and should one decide to stop testing the software?
7
Koch, Stefan, and Gerhard Turk. "Human Resource Related Problems in Agile and Traditional Software Project Process Models." International Journal of Information Technology Project Management 2, no. 2 (April 2011): 1–13. http://dx.doi.org/10.4018/jitpm.2011040101.
Повний текст джерелаАнотація:
This paper explores the impacts associated with different software process models on the staff. The main research question addressed is whether any process model leads to a higher satisfaction of staff, and less human resource related problems, including staff turnover or increased stress levels. This issue is empirically investigated using a set of projects from 15 different software developing companies. Agile-oriented models are not necessarily limited to small projects, but both groups showed nearly identical distributions for team size and duration. Interestingly, rigid-type models tend to exhibit higher effort estimations, and lower correctness in these estimations. Also customer satisfaction is slightly lower. With regard to human resource issues, the differences are not major overall, but there are some noticeable exceptions. In general, satisfaction and acceptance are higher at lower stress and overtime levels for agile-type project participants, but, interestingly and contrary to theory, people wish for more responsibility. Agile-type projects also enjoy some advantages in information sharing and communication, and in some quality aspects. Rigid-type projects show considerable higher abilities to cope with absence of personnel.
8
Rasheed, Aqsa, Bushra Zafar, Tehmina Shehryar, Naila Aiman Aslam, Muhammad Sajid, Nouman Ali, Saadat Hanif Dar, and Samina Khalid. "Requirement Engineering Challenges in Agile Software Development." Mathematical Problems in Engineering 2021 (May 8, 2021): 1–18. http://dx.doi.org/10.1155/2021/6696695.
Повний текст джерелаАнотація:
Agile software development has large success rate due to its benefits and promising nature but natively where the size of the project is small. Requirement engineering (RE) is crucial as in each software development life cycle, “Requirements” play a vital role. Though agile provides values to customer’s business needs, changing requirement, and interaction, we also have to face impediments in agile, many of which are related to requirement challenges. This article aims to find out the challenges being faced during requirement engineering of agile projects. Many research studies have been conducted on requirement challenges which are somehow biased, no suggestions are given to improve the agile development process, and the research does not highlight large-scale agile development challenges. Hence, this article covers all the challenges discussed above and presents a comprehensive overview of agile models from requirement engineering perspective. The findings and results can be very helpful for software industry to improve development process as well as for researchers who want to work further in this direction.
9
Sharma, Nidhi, and Manoj Wadhwa. "eXSRUP: Hybrid Software Development Model Integrating Extreme Programing, Scrum & Rational Unified Process." TELKOMNIKA Indonesian Journal of Electrical Engineering 16, no. 2 (November 1, 2015): 377. http://dx.doi.org/10.11591/tijee.v16i2.1627.
Повний текст джерелаАнотація:
<p>Software industries are progressively adopting the agile development practices of customized models such as Extreme Programming (XP) or Scrum or Rational Unified Process (RUP). Scrum and Extreme Programming (XP) are frequently used agile models, whereas Rational Unified Process (RUP) is one popular classic plan driven software development methodology. Both agile and plan driven models have their own merits & demerits such as XP has good engineering practices, team collaboration and on the other hand weak documentation, poor performance in medium & large scale projects. Scrum is based on project management practices. RUP model has some limitations such as impractical for small and fast paced projects, tendency to be over budgeted, condemn rapid changes in requirements. This research paper based on proposes hybrid framework eXSRUP by combining strengths of Scrum, XP and RUP by suppressing their limitations to produce high quality software.</p>
10
Rindell, Kalle, Sami Hyrynsalmi, and Ville Leppänen. "Fitting Security into Agile Software Development." International Journal of Systems and Software Security and Protection 9, no. 1 (January 2018): 47–70. http://dx.doi.org/10.4018/ijsssp.2018010103.
Повний текст джерелаАнотація:
Security objectives in software development are increasingly convergent with the business objectives, as requirements for privacy and the cost of security incidents call for more dependable software products. The development of secure software is accomplished by augmenting the software development process with specific security engineering activities. Security engineering, in contrast to the iterative and incremental software development processes, is characterized by sequential life cycle models: the security objectives are thus to be achieved by conflicting approaches. In this study, to identify the incompatibilities between the approaches, the security engineering activities from Microsoft SDL, the ISO Common Criteria and OWASP SAMM security engineering models are mapped into common agile software development processes, practices and artifacts.
11
Gahroee, Tayebe Mohamadi, Taghi Javdani Gandomani, and Mohammadreza Soltan Aghaei. "The main pillars of Agile consolidation in newly Agile teams in Agile software development." Indonesian Journal of Electrical Engineering and Computer Science 26, no. 2 (May 1, 2022): 1216. http://dx.doi.org/10.11591/ijeecs.v26.i2.pp1216-1226.
Повний текст джерелаАнотація:
<span>Many software companies and teams use Agile methods as their main development approach. These methods promise higher team productivity, faster product delivery, a more flexible development process, and greater customer satisfaction. Nevertheless, a review of the literature shows that adapting to these methods, known as Agile transition, is not as easy as expected. However, several frameworks and models have been proposed to facilitate the Agile transition process. The challenging issue after the transition to agility is the behavior of companies and teams after the Agile transition and how to maintain agility in the long run. Very little research has been done on this issue, which has largely expressed concern. The present study tries to explore the hidden aspects of the transition to agility and provide a solution for Agile consolidation in newly Agile software teams. In this regard, using the grounded theory approach, the basic theory of Agile consolidation in these teams has been presented. Preliminary findings of the study indicate important factors that play an important role in Agile consolidation. Identification of challenges, facilitators, organizational culture structure, and human roles in Agile consolidation is the most important initial findings of this study.</span>
12
H. Kulkarni, Rajesh, P. Padmanabham, Manasi Harshe, K. K. Baseer, and Pallavi Patil. "Investigating Agile Adaptation for Project Development." International Journal of Electrical and Computer Engineering (IJECE) 7, no. 3 (June 1, 2017): 1278. http://dx.doi.org/10.11591/ijece.v7i3.pp1278-1285.
Повний текст джерелаАнотація:
Agile methodologies adaptation in software companies is an accepted norm.Rapid application development and efficient deliverables being the premise. The changing business needs, cost effectiveness and timely delivery are catered to by agile methods. Different software development models are in the literature and also are being used by the industry. Few companies have adopted agile, few are gearing up for and few are in transition. We investigated agile presence in a software company.Project management is an evolving art with innovative methods being added up.The aim of this paper is to tease about project management challenges, agile, agile transition in companies and a comparison of conventional software engineering practices with agile process model.This paper takes stock of the current status of quality in software projects and to add on quality process improvement strategies. The results presented here are after a qualitative interview study with one cross function team using streamline development framework in agile development.
13
Srivastava, Abhishek, P. K. Kapur, Deepti Mehrotra, and Rana Majumdar. "Modelling Fault Detection Using SRGM in Agile Environment and Ranking of Models." Journal of Cases on Information Technology 21, no. 2 (April 2019): 1–20. http://dx.doi.org/10.4018/jcit.2019040101.
Повний текст джерелаАнотація:
Today's software applications deployed in an enterprise to cater to the complex business processes, integrate various business units and address requirements of a global customer base. The traditional methodology of software engineering succumbs to the changing need of customer and technology advancement. On the behest of the customer, a software system should be designed in a way that it goes in concert with the present user needs. Agile methodology targets complex systems with its iterative, incremental, and evolutionary approach. There are numerous factors attributing towards the successful implementation of agile methodology. This led to adopting an approach of agile based on ‘lean' principles over the traditional software development life cycle (SDLC) approach. Collaborative work is done with the project team on a priority list. The implementation is done through “SCRUM” an empirical framework for learning. It has multiple sprints which are deliverable products. This idea has substantially reduced the ‘time to market' as the customer can decide which features of the software they would like to be delivered on a priority basis. To model trends of fault detection in each sprint, a growth model of software reliability is used. This research article presents a framework to analyze and measure the cumulative errors in an Agile Testing Process, the authors have applied modeling on various SRGMs to prove acceptability in an agile development process and finally compares these models using the Mahalanobis Distance Formula for Model ranking. The Mahalanobis distance criteria is easy to compute and that can be utilized to get the ranks and select the best model in view of an arrangement of contributing criteria.
14
Arcos-Medina, Gloria, Alejandra Oñate-Andino, and Danilo Pástor. "Structural Analisys of CMMI with the Software Development Process, Project Portfolio Management and PMBOK." KnE Engineering 1, no. 2 (January 30, 2018): 223. http://dx.doi.org/10.18502/keg.v1i2.1497.
Повний текст джерелаАнотація:
Abstract. CMMI is one of the most used models in the software industry to certify the quality of its processes and products, reduces or eliminates rework, increases product and process reuse, reduces costs due to multiple evaluations and process improvement programs. On the other hand, companies that develop software apply traditional models or agile models, which manage the software development process. They also apply development standards such as ISO/IEC 12207 as well as project portfolio management standards and project management standards. The purpose of this paper is to relate the traditional and agile software development processes, project portfolio management and PMBOK with the CMMI standard. The results of this work allow us to determine the aspects that are missing from these standards and the best practices to reach a high level of CMMI maturity. It is concluded that for a company it is important to apply both agile processes and traditional processes, as well as all the standards that contribute improving the management of its projects. None of these practices and norms are opposed to the CMMI process areas, but rather are complemented to achieve a high level of quality in the final product and in achieving the objectives of the company.
15
Sahraoui, Sofiane, Noor Al-Nahas, and Rania Suleiman. "An Agile Perspective on Open Source Software Engineering." International Journal of Open Source Software and Processes 4, no. 3 (July 2012): 52–65. http://dx.doi.org/10.4018/ijossp.2012070105.
Повний текст джерелаАнотація:
Open source software (OSS) development has been a trend parallel to that of agile software development, which is the highly iterative development model following conventional software engineering principles. Striking similarities exist between the two development processes as they seem to follow the same generic phases of software development. Both modes of development have less emphasis on planning and design and a more prominent role for implementation during the software engineering process. This article expounds on this connection by adopting an agile perspective on OSS development to emphasize the similarities and dissimilarities between the two models. An attempt is first made to show how OSS development fits into the generic agile development framework. Then, the article demonstrates how the development process of Mozilla and Apache as two of the most famous OSS projects can be recast within this framework. The similarity discussed and illustrated between agile and OSS development modes is rather limited to the mechanics of the development processes and do not include the philosophies and motivations behind development.
16
Santos, Nuno António, Jaime Pereira, Nuno Ferreira, and Ricardo J. Machado. "Using Logical Architecture Models for Inter-Team Management of Distributed Agile Teams." International Journal of Information Technologies and Systems Approach 15, no. 1 (January 2022): 1–17. http://dx.doi.org/10.4018/ijitsa.289996.
Повний текст джерелаАнотація:
Projects at large-scale have been adopting agile practices in order to optimize how a group of teams deliver software, however has facing issues when dealing with work items that are dependent on each other, need for well-defined interfaces and shared understanding of the existing knowledge. Systems thinking and modeling can have important contributions in managing a process with this nature. This article proposes a design framework, called logical architecture-based distributed agile team management (LADATM), that uses logical architecture models to serve as the basis for the delivery of work items to distributed agile teams, support the identification of boundaries, dependencies and coordination needs, and derive an agile team product backlog. By performing Design Science Research (DSR) cycles, this article introduces the constructs of the LADATM framework. Afterwards, it demonstrates - using a research project - how it provided a systematized approach for process mananagement decision support for agile teams based in requirements models and through shared understanding.
17
Gupta, Aparna. "Comparative Study of Different SDLC Models." International Journal for Research in Applied Science and Engineering Technology 9, no. 11 (November 30, 2021): 73–80. http://dx.doi.org/10.22214/ijraset.2021.38736.
Повний текст джерелаАнотація:
Abstract: The Software Development Life Cycle (SDLC) refers to a methodology with clearly defined processes for creating highquality software which are cost effective and reliable. This method of software developing process is quite systematic and structural. SDLC defines the framework that has different activities and tasks to be administered during the software development process. Software development process is quite complex, and to do it without any proper planning would be inefficient. So, we use these SDLC models to make the Software development process simple and systematic. There are various software development life cycle models that are used in the software development process, all having their own advantages and limitations. In this paper, we have included six of these SDLC models - Waterfall Model, Spiral Model, V Model, Agile Model, Iterative Model and Rapid Application Development (RAD) Model. These Software Development processes have their own Advantages and Disadvantages, and the main purpose of this paper is to explain these models and know the difference between them. Keywords: Software Development life cycle, Models, Risk Analysis, Framework, SRS.
18
B, Prakash, and Viswanathan V. "Distributed Cat Modeling Based Agile Framework for Software Development." International Journal of Engineering Education 2, no. 1 (June 15, 2020): 20–32. http://dx.doi.org/10.14710/ijee.2.1.20-32.
Повний текст джерелаАнотація:
Software development is a hectic process that requires keen understanding and effective model such that the developed software inherits good quality, reliability, and achieves customer satisfaction towards achieving the goals effectively. The effective operation of the software is enabled by modifying the operating modules of the software through a model, like agile. In this paper, the catastrophic and distributed computing models are integrated into the software development step. The proposed model is termed as Distributed Cat model that is developed with the aim to handle the risk factors engaged in various developing stages of the agile model. The risk factors that affect the communication, planning, release, design, coding and testing modules of the agile modules are deeply learned and executed such that the risk factors are tackled by various modules present in the proposed Distributed Cat model. The effectiveness of the proposed model is analyzed based on the performance metrics, such as Index of Integration (IoI) and Usability Goals Achievement Metric (UGAM), for which five products including the hotel management system, Customer relationship Management system (CRM), Rainfall prediction system, Temperature monitoring system, and meta-search system, are employed and analyzed. The analysis is progressed using the parameters, like mean difference, variance, standard devaiation, correlation. The analysis proves that the proposed model offered a great deviation after applying the proposed model contributing a high degree of performance in software development.
19
Sadia Kousar, Sundus Munir, and Afrozah Nadeem. "A Non-Parametric Comparison between Advances Software Engineering Process Model." Lahore Garrison University Research Journal of Computer Science and Information Technology 1, no. 4 (December 29, 2017): 75–81. http://dx.doi.org/10.54692/lgurjcsit.2017.010417.
Повний текст джерелаАнотація:
Software development process provides detailed guideline for development testing and maintenance of software products. It deals with the risks associated withsoftware development and a road map to manage its complexities. In other words, software development processes are considered as optimized solution specific to any particular software product development. There are many software process models available in literature. This research performs a non-parametric comparison between formal process model, agile process model and agent based process model to aid software community in developing quality software product.
20
Fotariya, Mr Anuj, and Mr Omprakash Mandge. "Systematic Review of Agile Methodologies for Software Development." International Journal for Research in Applied Science and Engineering Technology 10, no. 6 (June 30, 2022): 1771–74. http://dx.doi.org/10.22214/ijraset.2022.44143.
Повний текст джерелаАнотація:
Abstract: With the increase in complexity and innovation in IT products and services, developing them, that to by the shared efforts of team members brings in the need of some standardized development model or approach. Due to several advantages of agile methodologies over the traditional waterfall based models, it is the preferred choice. Many a times, a single agile method is also not enough to meet the current scenario of product development. We therefore propose a Competitor Driven Development (CDD) model, a hybrid agile process model for IT product development by abstracting practices from Extreme Programming (XP) and Feature Driven Reuse Development (FDRD) agile methods. This model is based on self-realizing requirements generation for Product development by keeping an eye watch on competitor’s upcoming launch of the product and market response to it rather than customer explicitly specifying the requirements. This development model can be generally used by the organizations who intend to develop IT product for mass targeted customers rather than an individual or an organization.
21
Almeida, Fernando, Jorge Simões, and Sérgio Lopes. "Exploring the Benefits of Combining DevOps and Agile." Future Internet 14, no. 2 (February 19, 2022): 63. http://dx.doi.org/10.3390/fi14020063.
Повний текст джерелаАнотація:
The combined adoption of Agile and DevOps enables organizations to cope with the increasing complexity of managing customer requirements and requests. It fosters the emergence of a more collaborative and Agile framework to replace the waterfall models applied to software development flow and the separation of development teams from operations. This study aims to explore the benefits of the combined adoption of both models. A qualitative methodology is adopted by including twelve case studies from international software engineering companies. Thematic analysis is employed in identifying the benefits of the combined adoption of both paradigms. The findings reveal the existence of twelve benefits, highlighting the automation of processes, improved communication between teams, and reduction in time to market through process integration and shorter software delivery cycles. Although they address different goals and challenges, the Agile and DevOps paradigms when properly combined and aligned can offer relevant benefits to organizations. The novelty of this study lies in the systematization of the benefits of the combined adoption of Agile and DevOps considering multiple perspectives of the software engineering business environment.
22
Khaled Al Ghanmi, Nora, and Nor Shahida Mohd Jamail. "Integrating Scrum development process with UX design flow." Bulletin of Electrical Engineering and Informatics 9, no. 6 (December 1, 2020): 2630–36. http://dx.doi.org/10.11591/eei.v9i6.2484.
Повний текст джерелаАнотація:
Nowadays, Agile software development practices are being widely adapted all over the world. Scrum is one of the most known Agile models, it satisfies the business needs and put the main focus on the product. One common challenge for the development of customer-facing products is having a good user experience. This paper presents integrating Scrum development process with user experience design flow. In this study, papers relating to the topic of user experience (UX) process integration with Agile development process, how to measure it and how to improve it, from the year 2010 onwards are reviewed. This is to identify how organizations can integrate UX design flow and Scrum development and get the benefits of both. The conducted review identifies a number of limitations in the existing integrations efforts. A proposed process model to resolve these limitations is presented. Along with our experience in implementing it on an ongoing software development project. The results of applying this process, its impact on the project outcomes quality and the employees’ satisfaction with the process are discussed. The goal of this study is to aid organizations in integrating UX design into their development process.
23
Rodríguez-Hernández, V., M. C. Espino-Gudiño, J. L. González-Pérez, J. Gudiño-Bazaldúa, and Victor Castano. "Assessing quality in software development: An agile methodology approach." Journal of Advanced Computer Science & Technology 4, no. 2 (June 9, 2015): 225. http://dx.doi.org/10.14419/jacst.v4i2.4173.
Повний текст джерелаАнотація:
<p>A novel methodology, result of 10 years of in-field testing, which makes possible the convergence of different types of models and quality standards for Engineering and Computer Science Faculties, is presented. Since most software-developing companies are small and medium sized, the projects developed must focuson SCRUM and Extreme Programming (XP), opposed to a RUP, which is quite heavy, as well as on Personal Software Process (PSP) and Team Software Process (TSP), which provide students with competences and a structured framework. ISO 90003:2004 norm is employed to define the processes by means of a quality system without new requirements or changing the existing ones. Also, the model is based on ISO/IEC 25000 (ISO (IEC 9126 – ISO/IEC 14598)) to allow comparing software built by different metrics.</p>
24
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.
Повний текст джерелаАнотація:
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.
25
Nasiri, Samia, Amina Adadi, and Mohammed Lahmer. "Automatic generation of business process models from user stories." International Journal of Electrical and Computer Engineering (IJECE) 13, no. 1 (February 1, 2023): 809. http://dx.doi.org/10.11591/ijece.v13i1.pp809-822.
Повний текст джерелаАнотація:
In this paper, we propose an automated approach to extract business process models from requirements, which are presented as user stories. In agile software development, the user story is a simple description of the functionality of the software. It is presented from the user's point of view and is written in natural language. Acceptance criteria are a list of specifications on how a new software feature is expected to operate. Our approach analyzes a set of acceptance criteria accompanying the user story, in order, first, to automatically generate the components of the business model, and then to produce the business model as an activity diagram which is a unified modeling language (UML) behavioral diagram. We start with the use of natural language processing (NLP) techniques to extract the elements necessary to define the rules for retrieving artifacts from the business model. These rules are then developed in Prolog language and imported into Python code. The proposed approach was evaluated on a set of use cases using different performance measures. The results indicate that our method is capable of generating correct and accurate process models.
26
Pang, Chung-Yeung. "An Agile Architecture for a Legacy Enterprise IT System." International Journal of Organizational and Collective Intelligence 6, no. 4 (October 2016): 65–97. http://dx.doi.org/10.4018/ijoci.2016100104.
Повний текст джерелаАнотація:
Back in the 1970s, applications mainly comprised programs written in COBOL. Many of these applications are still in operation. To meet new business demands, new applications that have to collaborate with existing programs need to be developed. It is possible to have an agile software architecture that enables easy development, extension and maintenance in COBOL. Such an architecture, and the agile development process, are presented in this article. The architectural design is a combination of the layered, component-based and service-oriented architectural patterns. It also includes features such as the centralized control of the business process, plug-and-play autonomous COBOL modules and context container for storing state data. A model-driven approach is used in the agile development process. Application models include UML class diagrams, state charts and activity diagrams from which various software artefacts and COBOL codes are generated. The architecture and development approaches were first introduced in 2004 and have been successfully applied to 13 applications since then.
27
Henriques, Vaughan, and Maureen Tanner. "A Systematic Literature Review of Agile Maturity Model Research." Interdisciplinary Journal of Information, Knowledge, and Management 12 (2017): 053–73. http://dx.doi.org/10.28945/3666.
Повний текст джерелаАнотація:
Background/Aim/Purpose: A commonly implemented software process improvement framework is the capability maturity model integrated (CMMI). Existing literature indicates higher levels of CMMI maturity could result in a loss of agility due to its organizational focus. To maintain agility, research has focussed attention on agile maturity models. The objective of this paper is to find the common research themes and conclusions in agile maturity model research. Methodology: This research adopts a systematic approach to agile maturity model research, using Google Scholar, Science Direct, and IEEE Xplore as sources. In total 531 articles were initially found matching the search criteria, which was filtered to 39 articles by applying specific exclusion criteria. Contribution:: The article highlights the trends in agile maturity model research, specifically bringing to light the lack of research providing validation of such models. Findings: Two major themes emerge, being the coexistence of agile and CMMI and the development of agile principle based maturity models. The research trend indicates an increase in agile maturity model articles, particularly in the latter half of the last decade, with concentrations of research coinciding with version updates of CMMI. While there is general consensus around higher CMMI maturity levels being incompatible with true agility, there is evidence of the two coexisting when agile is introduced into already highly matured environments. Future Research: Future research direction for this topic should include how to attain higher levels of CMMI maturity using only agile methods, how governance is addressed in agile environments, and whether existing agile maturity models relate to improved project success.
28
Nidagundi, Padmaraj, and Leonids Novickis. "Introduction to Lean Canvas Transformation Models and Metrics in Software Testing." Applied Computer Systems 19, no. 1 (May 1, 2016): 30–36. http://dx.doi.org/10.1515/acss-2016-0004.
Повний текст джерелаАнотація:
Abstract Software plays a key role nowadays in all fields, from simple up to cutting-edge technologies and most of technology devices now work on software. Software development verification and validation have become very important to produce the high quality software according to business stakeholder requirements. Different software development methodologies have given a new dimension for software testing. In traditional waterfall software development software testing has approached the end point and begins with resource planning, a test plan is designed and test criteria are defined for acceptance testing. In this process most of test plan is well documented and it leads towards the time-consuming processes. For the modern software development methodology such as agile where long test processes and documentations are not followed strictly due to small iteration of software development and testing, lean canvas transformation models can be a solution. This paper provides a new dimension to find out the possibilities of adopting the lean transformation models and metrics in the software test plan to simplify the test process for further use of these test metrics on canvas.
29
Misra, Subhas C., and Virender Singh. "Conceptualizing open agile software development life cycle (OASDLC) model." International Journal of Quality & Reliability Management 32, no. 3 (March 2, 2015): 214–35. http://dx.doi.org/10.1108/ijqrm-08-2013-0127.
Повний текст джерелаАнотація:
Purpose – Software development life cycle (SDLC) has always been the core methodology for any software engineer that depicts the entire development process which an organization is bound to utilize to achieve successful software. The purpose of this paper is to bring forth a conceptual model after analysing the best practices in SDLC, and extracting the best out of agile methodologies and the open source software, thereby bringing forward an optimised structure. Design/methodology/approach – The OASDLC is hypothesized specifically for “Brihaspati” project and is formulated keeping in mind the gaps and limitations posed by existing SDLC models. OASDLC is further put to test for achieving lower costs and efforts involved. The tests are further substantiated by means of hypothesis validation through execution of a survey based research. Findings – It has been observed that the present conceptual model further optimizes the efforts involved while adopting such a practice. Originality/value – This paper proposes a novel SDLC model so as to achieve a best practice for a software project. On analysing the issues involved such as tight budget and timelines, it led the authors to formulate a newer concept “Open Agile Software Development Life Cycle model” (OASDLC).
30
Dave, Chitrak Vimalbhai. "An Efficient Framework for Cost and Effort Estimation of Scrum Projects." International Journal for Research in Applied Science and Engineering Technology 9, no. 11 (November 30, 2021): 1478–87. http://dx.doi.org/10.22214/ijraset.2021.39030.
Повний текст джерелаАнотація:
Abstract: Software Process Models from its inception instill standardization and creates a generic culture of developing software for various IT industries. A great paradigm shift has been observed in terms of embracing Agile Development methodology as a viable development methodology in cross key business units. There is a buffet of agile methodologies comes under the umbrella of ASD, out of which Scrum got the highest popularity and acceptability index. Agile based software development is the need of immediate environment. There is an increasing demand for significant changes to software systems to meet ever-changing user requirements and specifications. As Agile is volatile, so effort estimation is challenging and still striving for perfection to decide size, effort, cost, duration and schedule of projects with minimum error. This cause sensitizes potential researchers all across the globe to start working on addressing the issue of inaccurate predication of efforts. The gap between estimated and actual effort is because of limited or no inclusion of various estimation factors like people and project related factors, inappropriate use of size metric and cost drivers, ignorance of testing effort, team member’s inability to understand user story size and complexity etc. This paper attempts to bridge the gap of estimated and actual effort by the use of soft computing techniques thus taking the research to advance frontier area in terms ofestimation. Keywords: Cost Estimation, Effort Estimation, Scrum, Machine Learning, Agile Software Development
31
Arora, Mohit, Dr Sahil Verma, and Dr Kavita. "An efficient effort and cost estimation framework for Scrum Based Projects." International Journal of Engineering & Technology 7, no. 4.12 (October 4, 2018): 52. http://dx.doi.org/10.14419/ijet.v7i4.12.20992.
Повний текст джерелаАнотація:
Software Process Models from its inception instill standardization and creates a generic culture of developing software for various IT industries. A great paradigm shift has been observed in terms of embracing Agile Development methodology as a viable development methodology in cross key business units. There is a buffet of agile methodologies comes under the umbrella of ASD, out of which Scrum got the highest popularity and acceptability index. Agile based software development is the need of immediate environment. There is an increasing demand for significant changes to software systems to meet ever-changing user requirements and specifications. As Agile is volatile, so effort estimation is challenging and still striving for perfection to decide size, effort, cost, duration and schedule of projects with minimum error. This cause sensitizes potential researchers all across the globe to start working on addressing the issue of inaccurate predication of efforts. The gap between estimated and actual effort is because of limited or no inclusion of various estimation factors like people and project related factors, inappropriate use of size metric and cost drivers, ignorance of testing effort, team member’s inability to understand user story size and complexity etc. This paper attempts to bridge the gap of estimated and actual effort by the use of soft computing techniques thus taking the research to advance frontier area in terms of estimation.
32
Bonino, Maria Belen, Ana Garis, and Daniel Riesco. "FORMAL MODELING AND ANALYSIS OF ENTITY FRAMEWORK USING ALLOY." International Journal of Software Engineering and Computer Systems 7, no. 2 (August 30, 2021): 9–18. http://dx.doi.org/10.15282/ijsecs.7.2.2021.2.0085.
Повний текст джерелаАнотація:
Formal methods provide multiple benefits when applied in the software development process. For instance, they enable engineers to verify and validate models before working on their implementation, leading to earlier detection of design defects. However, most of them lack flexibility to be applied in agile software development projects. Alloy is a lightweight formal modeling language with a friendly tool that facilitates the agile approaches application. Unfortunately, its industrial adoption is hampered by the lack of methods and tools for current software development frameworks, such as Entity Framework. This platform is usually chosen by agile projects following the code-first approach that allows automatic generation of a database from domain classes coded in the C# language. We present a new method and tool for the formal specification and analysis of Entity Framework projects with Alloy. The proposal allows engineers to start the software development using Alloy for modeling, validation and verification, automatically translate Alloy specifications to C# domain classes and then generate the corresponding database with Entity Framework. We validate our approach with a real case study: an application required by a gas supplier company.
33
Alavandhar, Jai Vigneshwar, and Oksana Ņikiforova. "Several Ideas on Integration of SCRUM Practices within Microsoft Solutions Framework." Applied Computer Systems 21, no. 1 (May 24, 2017): 71–79. http://dx.doi.org/10.1515/acss-2017-0010.
Повний текст джерелаАнотація:
Abstract In order to develop and deliver a software project successfully, any software development organisation has to follow a well-known and recognised software engineering process for successful delivery and maintenance of the software. However, when the organisation is willing to follow a new software development process, the success rate of adopting a new software engineering process is a question mark. In the paper, we aim at studying and comparing two software engineering processes, which are based on different paradigms or models, and proposing a hybrid methodology, which integrates advantages of both compared methods. They are Microsoft Solutions Framework as a representative for an iterative methodology and SCRUM for agile software development. The comparative analysis will help a software development company to make the transition easier from Microsoft Solutions Framework to SCRUM or vice versa.
34
Alam, Intakhab, Nadeem Sarwar, and Iram Noreen. "Statistical analysis of software development models by six-pointed star framework." PLOS ONE 17, no. 4 (April 1, 2022): e0264420. http://dx.doi.org/10.1371/journal.pone.0264420.
Повний текст джерелаАнотація:
Software Development Process Model (SDPM) develops software according to the needs of the client within the defined budget and time. There are many software development models such as waterfall, Iterative, Rapid Application Development (RAD), Spiral, Agile, Z, and AZ model. Each development model follows a series of steps to develop a product. Each model has its strengths and weaknesses. In this study, we have investigated different software development process models using the six-pointed star framework. Six-point star is a framework of project management industry standards maintained by Project Management Body of Knowledge (PMBOK). A survey is designed to evaluate the performance of well-known software process models in the context of factors defined by the six-point star framework. The survey is conducted with experienced users of the software industry. The statistical analysis and comparison of results obtained by the survey are further used to examine the effectiveness of each model for the development of high-quality software concerning lightweight and heavyweight methodologies for small, medium and large scale projects. After exploring the results of all factors of the six-pointed star model, we conclude that lightweight methodology easily handles small-scale projects. The heavyweight methodology is suitable for medium and large-scale projects, whereas the AZ model, which is one of the latest models, works efficiently with both small-scale and large-scale categories of projects.
35
Kankaanhuhta, Ville, Tuula Packalen, and Kari Väätäinen. "Digital Transformation of Forest Services in Finland—A Case Study for Improving Business Processes." Forests 12, no. 6 (June 13, 2021): 781. http://dx.doi.org/10.3390/f12060781.
Повний текст джерелаАнотація:
This case study introduces an innovation and development concept for agile software tools for the improvement of the productivity and customer experience of forest services. This need was recognized in the context of the opening of forest data and the development of service platforms for a forest-based bioeconomy in Finland. The forest services that were studied covered a continuum from a single type of work, e.g., soil preparation and young stand management through timber procurement, to comprehensive forest property management services. The study concentrated on the needs of micro-, small, and medium-sized enterprises (SMEs), which provide either retail- or business to business (B2B) services as sub-contractors. In addition, the challenges and bottlenecks in service processes detected by other stakeholders were considered. The prevailing service processes were conceptually modelled in order to search for opportunities for improvements in business and ecosystem services, i.e., agile software concepts. For example, we examined whether it would be possible to create opportunities for flexible operational models for precision, resilience, and protection of valuable microsites in forests. These software concepts were developed and evaluated in co-operation with the stakeholders in a co-creative workshop. The technological feasibility and commercial viability of the concepts, as well as the desirability for the customer were considered. The results of this business development process—i.e., agile software concepts and their anticipated benefits—were provided for further evaluation. In addition to the practical implications of this kind of innovation process tested, the potential of these kinds of agile tools for the further development of knowledge-intensive service processes was further discussed.
36
Dave, Chitrak Vimalbhai. "Estimation Approaches of Machine Learning in Scrum Projects: A Review." International Journal for Research in Applied Science and Engineering Technology 9, no. 11 (November 30, 2021): 1110–18. http://dx.doi.org/10.22214/ijraset.2021.38977.
Повний текст джерелаАнотація:
Abstract: It is inevitable for any successful IT industry not to estimate the effort, cost, and duration of their projects. As evident by Standish group chaos manifesto that approx 43% of the projects are often delivered late and entered crises because of over budget and less required functions. Improper and inaccurate estimation of software projects leads to a failure, and therefore it must be considered in true letter and spirit. When Agile principle-based process models (e.g. Scrum) came into the market, a significant change can be seen. This change in culture proves to be a boon forstrengthening the collaboration betweendeveloper and customer.Estimation has always been challenging in Agile as requirements are volatile. This encourages researchersto work on effort estimation. There are many reasons for the gap between estimated and actual effort, viz., project, people, and resistance factors, wrong use of cost drivers, ignorance of regression testing effort, understandability of user story size and its associated complexity, etc. This paperreviewed the work of numerous authors and potential researchers working on bridging the gap of actual and estimated effort. Through intensive and literature review, it can be inferred that machine learning models clearly outperformed non-machine learning and traditional techniques of estimation. Keywords: Machine Learning, Scrum, Scrum Projects, Effort Estimation, Agile Software Development
37
Fotache, Marin, Gabriela Mesnita, Florin Dumitriu, and Georgiana Olaru. "A Few Insights Into Romanian Information Systems Analysts and Designers Toolbox." Timisoara Journal of Economics and Business 10, no. 1 (June 1, 2017): 1–18. http://dx.doi.org/10.1515/tjeb-2017-0001.
Повний текст джерелаАнотація:
Abstract Information Systems (IS) analysts and designers have been key members in software development teams. From waterfall to Rational Unified Process, from UML to agile development, IS modelers have faced many trends and buzzwords. Even if the topic of models and modeling tools in software development is important, there are no many detailed studies to identify for what the developers, customers and managers decide to use the modeling and specific tools. Despite the popularity of the subject, studies showing what tools the IS modelers prefer are scarce, and quasi-non-existent, when talking about Romanian market. As Romania is an important IT outsourcing market, this paper investigated what methods and tools Romanian IS analysts and designers apply. In this context, the starting question of our research focuses on the preference of the developers to choose between agile or non-agile methods in IT projects. As a result, the research questions targeted the main drivers in choosing specific methods and tools for IT projects deployed in Romanian companies. Also, one of the main objectives of this paper was to approach the relationship between the methodologies (agile or non-agile), diagrams and other tools (we refer in our study to the CASE features) with other variables/metrics of the system/software development project. The observational study was conducted based on a survey filled by IS modelers in Romanian IT companies. The data collected were processed and analyzed using Exploratory Data Analysis. The platform for data visualization and analysis was R.
38
Peldžius, Stasys, and Saulius Ragaišis. "Tarpinio programų kūrimo proceso modelio reikalavimai." Informacijos mokslai 56 (January 1, 2011): 138–45. http://dx.doi.org/10.15388/im.2011.0.3143.
Повний текст джерелаАнотація:
Įmonės, siekdamos sėkmingai įgyvendinti programų kūrimo projektus – pateikti rezultatus laiku, neviršydamos biudžeto, ir kad klientai būtų patenkinti jų kokybe, renkasi programų kūrimo proceso modelius, pagal kuriuos gali įvertinti savo programų kūrimo procesą ir jį gerinti. Šiuo metu pasaulyje populiariausi programų kūrimo proceso modeliai yra ISO/IEC 15504 ir CMMI. Įmonėms prasminga turėti įvertinimus pagal abu šiuos proceso modelius, bet kiekvienas įmonės vertinimas brangus tiek finansiniu, tiek laiko požiūriu, todėl būtų naudinga gauti įvertinimus pagal skirtingus modelius, atliekant tik vieną vertinimą. Norėdamos apibrėžti ir (ar) pagerinti savo programų kūrimo procesą, įmonės renkasi įvairius programų sistemų inžinerijos metodus, pavyzdžiui, XP, Scrum, DSDM, RUP. Įmonei svarbu žinoti, ką pasirinktas metodas jai gali duoti: kokį proceso gebėjimą ir (ar) brandą jis gali užtikrinti. Šias aktualias problemas išspręstų tarpinis programų kūrimo proceso modelis, kuris leistų įmonėms atlikti įvertinimą pagal vieną proceso modelį ir gauti rezultatus pagal kelis modelius, taip pat žinoti, kokį proceso gebėjimą ir (ar) brandą gali užtikrinti pasirinktas programų sistemų inžinerijos metodas. Straipsnyje pateikiamas pirmasistokio modelio kūrimo žingsnis – apibrėžiami tokio modelio reikalavimai.Requirements of Transitional Software Process ModelStasys Peldžius, Saulius Ragaišis SummaryMost of the software development projects face the following problems: projects are delayed; they overrun the budget; customers are dissatisfied with the quality of the software delivered. This phenomenon is so widespread that it is even called a software crisis. It has been understood that software process maturity is closely related to project success and the quality of a software product, so various software process models have been introduced. Organizations want to get all the advantages of the different process models that stimulate their harmonization and the investigation of process improvement in multimodel environments. Organizations seek to get their capability/maturity assessment according to several process models by conducting only a single assessment. This could be achieved by the transitional software process model. Organizations employ different software development methodologies, but they are unable to assess how they affect their process without implementation. The transitional model helps to assess the capability/maturity according to ISO/IEC 15504 and CMMI which could be ensured by agile or other software development methodologies. Similar ideas have been introduced in the unified SEPRM model. A detailed review of the deficiencies that led to its unpopularity is made. The paper presents the requirements for the transitional software process model.
39
Kettunen, Janne, and Miguel A. Lejeune. "Technical Note—Waterfall and Agile Product Development Approaches: Disjunctive Stochastic Programming Formulations." Operations Research 68, no. 5 (September 2020): 1356–63. http://dx.doi.org/10.1287/opre.2019.1977.
Повний текст джерелаАнотація:
When engaging in the development of new products, the primary objective of start-up companies is to generate a specified return level quickly and with high confidence. Achieving this goal is complicated because of uncertainties in projects’ returns and durations. In the study titled, “Waterfall and Agile Product Development Approaches: Disjunctive Stochastic Programming Formulations,” Kettunen and Lejeune develop new disjunctive chance-constrained programming models that capture this goal. The first static model reflects the traditional waterfall product development process, whereas the second one is dynamic and depicts the agile product development process. Kettunen and Lejeune design a novel reformulation method and a decomposition algorithm and use them on a new product development problem encountered by a U.S.-based software start-up company. The results reveal that high confidence in reaching a certain return can be achieved by investing in projects with a longer development time and higher risk. Additionally, overlooking the capability to make dynamic decisions, as allowed by the agile approach, leads to overestimating the time needed to obtain the targeted return.
40
Kryvstun, T. V., M. O. Slabinoha, and Ya I. Zayachuk. "WEB-ORIENTED SYSTEM FOR MONITORING AND MANAGEMENT OF AGILE METHODOLOGY PROJECTS." METHODS AND DEVICES OF QUALITY CONTROL, no. 1(46) (June 28, 2021): 132–37. http://dx.doi.org/10.31471/1993-9981-2021-1(46)-132-137.
Повний текст джерелаАнотація:
The work is devoted to the development of a web-based support system for monitoring the implementation and management of small projects implemented according to the agile methodology (in particular, in the field of information technologies). Monitoring the implementation of projects is an important factor in their success, which in turn has a positive impact on the company's profits and the economy as a whole. Existing solutions in the field of project management were analyzed: the main models of project management were considered, as well as the main software tools for their implementation, their advantages and disadvantages. The task of developing a web-based system for monitoring and project management according to the Agile methodology was formed. The software tools for the system implementation were selected and the database structure was designed. The software of the server part was implemented using the architecture "model - view - controller", for which UML-diagrams of the relevant components of the system were developed. The developed server software uses a software interface with response to requests in JSON format, which allows you to further develop in addition to the web interface and mobile applications. The web interface implemented by the Angular framework implements basic functions for users and system administrators, such as entity management, authorization and registration, and includes an analytical tool for monitoring project performance, namely the burn-out chart. The developed software will be useful for small projects that use Agile methodologies, both partially and completely, and which do not require complex tools that require a long setup process. Implementing this system as a web-based application allows you to use it from both desktop computers and mobile devices.
41
França, Mauro Borges, Alexandre Cardoso, Edgard Afonso Lamounier Junior, and Camila Tavares Mota. "Agile Short Unified Process - ASUP: Uma metodologia híbrida apoiada na adaptação do framework Scrum e do modelo Unified Process." RISTI - Revista Ibérica de Sistemas e Tecnologias de Informação, no. 46 (June 30, 2022): 71–86. http://dx.doi.org/10.17013/risti.46.71-86.
Повний текст джерелаАнотація:
Encontrar uma metodologia de desenvolvimento de software que seja aderente às características de fábricas de software é um grande desafio para pesquisadores. Neste sentido, este trabalho apresenta uma metodologia híbrida, denominada Agile Short Unified Process - ASUP. A proposta tem como base elementos extraídos do framework Scrum inseridos nas quatro fases do Unified Process - UP: Concepção, Elaboração, Construção e Transição. Em cada fase encontra-se um ciclo de vida representada e tipificada com todos os seus elementos. Para avaliar a eficiência, o ASUP foi aplicado em quatro projetos de duas instituições federais de educação profissional - IFTM e IFNMG. Após a aplicação da metodologia, alguns apontamentos foram realizados pelas equipes como forma de feedback e suas percepções finais foram de ganhos significativos nas atividades de gerenciamento dos projetos. Por fim, nas duas instituições, a metodologia foi aprovada e deixou de ser apenas sugestiva para ser considerada aplicável em outros projetos.
42
Buladaco, Mark Van, and Jennifer Sabugaa. "An Agile Prototyping Approach on the Design of the Purchase Request and Financial Tracking System." International Journal of Computing Sciences Research 6 (January 31, 2022): 913–24. http://dx.doi.org/10.25147/ijcsr.2017.001.1.83.
Повний текст джерелаАнотація:
Purpose – This paper focuses on designing a purchase request and financial tracking system to better support the government agencies in fast, easy management and better understand a more comprehensive strategy for its financial activities. Method – It employs an agile prototyping approach for fast and cost-effective turnaround. UML approach was utilized for designing process models and data models. Results – The prototypes allow you to observe real user behavior as they interact with your design and obtain detailed feedback about your designs, alternatives, and ideas before implementing them. Various process and data models are designed and presented in this paper with exact and comprehend steps for the programmers to follow during the software development life cycle (SDLC). Conclusion – Making the developed models as the government's guide in engaging and embracing emerging technological innovations would impact the purchase request processes and financial tracking management quality. These models will certainly provide new knowledge, theories, and methods for the experts who will put these prints into action or implementation and other researchers who wish to seek facts relevant to purchase requests and financial tracking of government transactions. Recommendations – It is recommended to utilize this design to develop the software in a purchase request and financial tracking in government agencies in the Philippines. It is also recommended to consider adding PR Mapping; aside from tracking the PR through status, they could suggest adding the PR mapping to track the PR, upload other documents that require in their purchase request, and adding machine learning algorithms to predict the budget allocation of each office for the next incoming years. Research Implications – This paper's results will eventually be significant in the development of a purchase request system for different government agencies in the Philippines.
43
Mohan, Prajval, Pranav Narayan, Mythili Thirugnanam, and Supratim Sarkar. "XPS-MoSCoW." International Journal of Software Innovation 10, no. 1 (January 2022): 1–15. http://dx.doi.org/10.4018/ijsi.297989.
Повний текст джерелаАнотація:
This paper presents a thorough analysis of the existing SCRUM model and the Extreme programming model for software testing and deployment and proposes a new hybrid model for software development. On reviewing the various static agile models, we concluded that the development process of the SCRUM model focused on the management aspect of software testing and deployment. In the case of Extreme programming, the engineering practices are applied to the project itself. No model effectively focuses on balancing management as well as the engineering practices of the software deployment cycle. In this paper, we have proposed an improved model called the XPS-MoSCoW Hybrid programming model that carefully integrates the features of both the SCRUM and Extreme programming models. The tasks executed using our hybrid model are prioritized using the MoSCoW prioritization rules, in which tasks with higher priorities enter first into the sprint backlog. Looking at the implementational results of this model when deployed in a startup, it is eminent how our hybrid model surpasses these static models.
44
Kuhrmann, Marco, Philipp Diebold, and Jürgen Münch. "Software process improvement: a systematic mapping study on the state of the art." PeerJ Computer Science 2 (May 23, 2016): e62. http://dx.doi.org/10.7717/peerj-cs.62.
Повний текст джерелаАнотація:
Software process improvement (SPI) has been around for decades: frameworks are proposed, success factors are studied, and experiences have been reported. However, the sheer mass of concepts, approaches, and standards published over the years overwhelms practitioners as well as researchers. What is out there? Are there new trends and emerging approaches? What are open issues? Still, we struggle to answer these questions about the current state of SPI and related research. In this article, we present results from an updated systematic mapping study to shed light on the field of SPI, to develop a big picture of the state of the art, and to draw conclusions for future research directions. An analysis of 769 publications draws a big picture of SPI-related research of the past quarter-century. Our study shows a high number of solution proposals, experience reports, and secondary studies, but only few theories and models on SPI in general. In particular, standard SPI models like CMMI and ISO/IEC 15,504 are analyzed, enhanced, and evaluated for applicability in practice, but these standards are also critically discussed, e.g., from the perspective of SPI in small-to-medium-sized companies, which leads to new specialized frameworks. New and specialized frameworks account for the majority of the contributions found (approx. 38%). Furthermore, we find a growing interest in success factors (approx. 16%) to aid companies in conducting SPI and in adapting agile principles and practices for SPI (approx. 10%). Beyond these specific topics, the study results also show an increasing interest into secondary studies with the purpose of aggregating and structuring SPI-related knowledge. Finally, the present study helps directing future research by identifying under-researched topics awaiting further investigation.
45
Hou, Li, Qi Liu, Kiran Saeed, Saqib Ali Haidery, M. Irfan Uddin, and Hizbullah Khattak. "Enhancement of the Capability Maturity Model for Improving the Quality of Software Projects in Developing Countries." Scientific Programming 2021 (May 29, 2021): 1–10. http://dx.doi.org/10.1155/2021/9982227.
Повний текст джерелаАнотація:
Business process modeling was suggested by academia and implemented by the industry to trigger device requirements. Maturity models of software processes are also similar in the software industry. Therefore, business software requirement engineering approaches-based process should aim to fulfil with the maturity models. Although researchers in the area of Software Engineering, Project Management, and Business Intelligent have addressed planning and execution and a lot of research still needs to be done, in this study, we focused on doing a questionnaire based on different prominent universities, major companies, and software houses. The purpose of the questionnaire was to dig out the main factors that negatively affect software houses and their products and services, especially in the medical field. A questionnaire was generated to accomplish these reasons, and interviews were conducted to extract the key explanation why software developers and software houses in developing countries are not familiar with the CMMI (Capability Maturity Model Integration) model for medical software projects. This analysis attempted to figure out why the tech enterprises of developing countries are behind foreign competitors. We aimed to determine why software developers do not meet the international requirements for software. The novelty of the research is that attempts were made to strengthen the new approach by adding agile at level 3 to keep the local software industry appropriate and reveal the requirements for medical software life cycle study, because accurate decision support is really necessary for healthcare systems.
46
Atoum, Issa. "A Spiral Software Engineering Model to Inspire Innovation and Creativity of University Students." International Journal of Engineering Pedagogy (iJEP) 9, no. 5 (November 22, 2019): 7. http://dx.doi.org/10.3991/ijep.v9i5.10993.
Повний текст джерелаАнотація:
Youth, especially students in universities, have tremendous energy that could be utilized to support their universities’ visions and their societies. However, students face several problems -for reasons related to their personalities, monetary support, and mentoring. During incubation, an idea goes several steps to crystallize, develop, and then be evaluated to gain success. However, the innovation process is agile, unstable, and subject to the risk of failure. Therefore, this paper proposes a spiral software model, called iSpiral, starting from student ideas and ending with creative operational projects. The proposed model was compared with selected models over a set of innovative criteria. The proposed iSpiral model was found more general and actionable, especially over agility and control criteria. The proposed iSpiral model was applied to a series of interrelated student ideas. The proposed model switched unmanaged and risky initiatives into active-inspired projects.
47
Dragičević, Zoran, and Saša Bošnjak. "THE ROLE OF AGILE SOFTWARE ARCHITECT IN THE AGE OF DIGITAL DISRUPTION AND TRANSFORMATION." Balkans Journal of Emerging Trends in Social Sciences 3, no. 2 (December 2020): 148–62. http://dx.doi.org/10.31410/balkans.jetss.2020.3.2.148-162.
Повний текст джерелаАнотація:
The consequence of the increasing development and use of digital technologies, in every segment of society, is the emergence of digital disruption - a powerful external pressure that is changing the way business is done in all industries. Businesses are responding to digital disruption by digital transformation, which involves organizational change, redefining and aligning digital and business strategies, new business models, increased agility of software development and delivery processes, migration and/or integration of legacy systems using cloud-based platforms and ecosystems. In such a context, one of the key responsibilities of a software architect is to maintain the agility of the organization by defending the flexibility of digital strategy and IT resources so that the enterprise is able to transform and respond adequately and rapidly to the effects of digital disruption. In this regard, the question arises as to how digital disruption and business transformation affect the change in the role, importance, competence and agility of a software architect, especially in the context of the development of complex business software systems. This paper aims to present the role of an agile software architect in the era of digital disruption and transformation, by integrating the results of theoretical and empirical research. A systematic literature review identifies the role, importance, and competencies of a software architect in implementing agile architecture. In other hand, empirical research, based on a case study in a large enterprise, provides a better understanding of the importance of software architect for aligning business and digital strategy, as well as its contribution to increasing the agility of the process of developing, delivering and integrating complex business software systems.
48
López Herrera, Gloria Yolanda, and Juan Carlos Jiménez Sanz. "Best practices for requirements identification, specification, and validation to guide software implementation and maintenance processes for applications in an electricity supply company." Sistemas y Telemática 13, no. 35 (December 3, 2015): 53–76. http://dx.doi.org/10.18046/syt.v13i35.2152.
Повний текст джерелаАнотація:
The objective of this project is to identify and adapt the best practices for the identification, specification, and validation of requirements that guide the software implementation and maintenance processes in applications of an electric company. We performed this identification through the study and analysis of the actual state of the topic in Colombia, particularly within electric companies and supported by the theoretical examples of requirements engineering. Both the examples and the methodological models identified as best practices —such as RUP, agile development (focused on Scrum), CMMI, use cases and use cases 2.0, PMI —focused on the management of the scope and stakeholders—, and BABOK support the understanding of this topic. The result is a process that collects models to improve the requirements for new developments and for the handling of change requests and incidents/emergencies, obtaining positive evaluations by expert judgement in a pilot experiment.
49
Eljayar, Ali, and Jeff S. Busch. "Agile-Stage-Gate Approach: Exploratory Research on the Structure, Roles, and Responsibilities." Athens Journal of Τechnology & Engineering 8, no. 1 (January 20, 2021): 39–90. http://dx.doi.org/10.30958/ajte.8-1-3.
Повний текст джерелаАнотація:
One of the most prominent methodologies gaining recognition in recent years is the Agile-Stage-Gate approach. The relatively new hybrid model is a combination of the Stage-Gate and the Agile-Scrum models. Several companies already using the Stage-Gate process have recently adopted the Agile-Stage-Gate approach to improve product development and project management. However, each of these companies has added their adjustments and modifications to the new approach in order to accommodate their specialized needs and to achieve the goals that are unique to their company. Therefore, no fixed structure or standardized features have been explicitly assigned to this hybrid approach. Instead, each company has added on different features and manipulated the new approach to fit whatever needs arise from moment to moment. This ambiguity leads to the question of whether the structure, roles, and responsibilities of this new approach can be defined and if so, how these clear and consistent definitions can improve productivity, efficiency, communication and market response time. The purpose of this study is to explore the structure, roles, and responsibilities within this new approach and to identify patterns that emerge during the product development and project management processes. The research questions presented were administered and examined through a qualitative survey. Fifty-two complete responses were collected from experienced individuals who have varying degrees of experience with the Agile-Stage-Gate approach. These findings revealed many similarities and differences between the structure, roles, and responsibilities of this approach, which were also dependent on the product and project type being considered. The most apparent similarities between roles and responsibilities were found in the case of software products and new product development projects. The Agile-Stage-Gate approach has also had a significant and undeniable impact on team communication and performance and was shown to improve overall quality and productivity. Keywords: agile, stage-gate, customer, scrum, sprint, hybrid, ideation, combination products, backlog, retrospective
50
Yang, Chen, and Yan Liu. "Enhancements to Neural Language Model for Generating System Configuration Code: A Study with Maven Dependency." Applied Sciences 12, no. 16 (August 21, 2022): 8347. http://dx.doi.org/10.3390/app12168347.
Повний текст джерелаАнотація:
Thanks to the widespread application of software frameworks, OTS components, DSLs, and new-generation software building and construction systems, leveraging system configuration code to assist in development is increasingly common, especially in agile software development. In software system implementation, the system configuration code is used to separate configuration items from the underlying logic, of which Maven dependency code is a typical example. To improve software productivity, developers often reuse existing dependency libraries. However, the large quantity, rapid iteration, and various application scenarios exacerbate the challenge for researchers to reuse the library efficiently and appropriately. Proper reuse of Maven dependencies requires correct importation, which is the research priority of this article; putting it into practical usage at the functional level is the next step. In order to overcome this barrier, researchers have proposed a number of recommendation and intelligent generation models based on deep learning algorithms and code learning strategies. We first introduce an enhancement path for the generation model in order to propose novel models that are more targeted than previous studies. We propose EMGSCC (Enhanced Model for Generating System Configuration Code), which generates accompanying dependency libraries based on the libraries already employed by the current system. EMGSCC uses content-based attention to cope with dependency language features and integrate additional domain information. Finally, we evaluate EMGSCC on the DDDI dataset with extra domain information, and findings show that improvement varies from 1% to 8% on all metrics compared with the baseline. We show empirical evidence of our enhancement path for generating system configuration code based on neural language models, and continuous improvement in this direction would yield promising results.