Journal articles: 'Agility in Software Development'

1

Batra, Dinesh, Weidong Xia, and Shekhar Rathor. "Agility Facilitators for Contemporary Software Development." Journal of Database Management 27, no. 1 (January 2016): 1–28. http://dx.doi.org/10.4018/jdm.2016010101.

Full text

Abstract:

Agile software development generally refers to popular practices that are supposed to adhere to the Agile Manifesto with its values and principles. Empirical studies on agile software development have mainly focused on organizational adoption and impacts of agile practices. Furthermore, the literature on agile software development has mostly centered on small, co-located projects. However, agility is needed for software development projects of varied sizes in different organizations across industries. The general nature of agile values and principles and the procedure-driven nature of specific agile methods make it difficult for organizations to determine what they can do to effectively facilitate agility in their software development process. To bridge that literature gap and based on an evolved grounded-theory approach, this study identifies nine agility facilitators and their corresponding dimensions that extend beyond small, co-located projects to software projects of any size and distribution. These agility facilitators are further grouped into two categories: organizational foundation and project processes. In addition, the authors identify four dimensions of agility. The authors propose a framework that describes the organizational mechanisms through which the nine categories of facilitators lead to software development agility.

APA, Harvard, Vancouver, ISO, and other styles

2

Kettunen, Petri. "Extending Software Project Agility with New Product Development Enterprise Agility." Software Process: Improvement and Practice 12, no. 6 (2007): 541–48. http://dx.doi.org/10.1002/spip.342.

Full text

APA, Harvard, Vancouver, ISO, and other styles

3

Forti, Tiago L. D., Gustavo C. Longhin, Nadia Cazarim da Silva Forti, and João Alberto V. Requena. "Agility based software development for truss design." Rem: Revista Escola de Minas 67, no. 3 (September 2014): 259–64. http://dx.doi.org/10.1590/s0370-44672014000300003.

Full text

Abstract:

This article describes the development of an application for structural analysis of tubular trussed girders. Such structural components are widely used on roofs for which long span components are a necessity, e. g., supermarkets, distribution centers, etc. The application supplies hints to the project engineers as to the most economic solutions for a combination of span, loads, and other characteristics. Software development techniques are also explored. Such techniques can be divided into two large groups. In the first one, which is most widely known and used, software development complies with very rigid planning, where processes are more important than skills. This methodology is known as the Rigorous Development System (RDS). The second group, called Agile Development System (ADS), is conceived as an option for those not aligned with the RDS rules. This text describes the experience of an ADS based software development for truss design. In Section 2, the basis of ADS is presented. Section 3 describes the truss design application and civil engineering related concepts. Section 4 brings an example illustrating the application. Conclusions are in Section 5.

APA, Harvard, Vancouver, ISO, and other styles

4

Balijepally, VenuGopal, Gerald DeHondt, Vijayan Sugumaran, and Sridhar Nerur. "Agility in Software Development and Project Value." Journal of Database Management 28, no. 4 (October 2017): 40–59. http://dx.doi.org/10.4018/jdm.2017100103.

Full text

Abstract:

Agile Development Methods, considered as an alternative to the traditional plan-based methods, have received much attention since their inception. These practices have evolved and developed over time, culminating in 2001 with the Agile Manifesto. Since that time, preferred methodologies, implementations, and best practices have continued to evolve with a focus on doing what works best for the individual company or project. However, the concept of agility in software development has remained quite nebulous, lacking in clarity particularly about its underlying dimensions. In this research the authors conceive agility in terms of four distinct dimensions. Drawing from the theoretical perspective of holographic organization, they develop a model explaining how each of these underlying dimensions of agility contributes to project value in software teams. The authors test the model using survey data collected from industry practitioners and discuss findings.

APA, Harvard, Vancouver, ISO, and other styles

5

Bowen, Jonathan P., Mike Hinchey, Helge Janicke, Martin Ward, and Hussein Zedan. "Formality, Agility, Security, and Evolution in Software Development." Computer 47, no. 10 (October 2014): 86–89. http://dx.doi.org/10.1109/mc.2014.284.

Full text

APA, Harvard, Vancouver, ISO, and other styles

6

de Cesare, Sergio, Mark Lycett, Robert D. Macredie, Chaitali Patel, and Ray Paul. "Examining perceptions of agility in software development practice." Communications of the ACM 53, no. 6 (June 2010): 126–30. http://dx.doi.org/10.1145/1743546.1743580.

Full text

APA, Harvard, Vancouver, ISO, and other styles

7

Varajão, João. "Software Development in Disruptive Times." Queue 19, no. 1 (February 28, 2021): 94–103. http://dx.doi.org/10.1145/3454122.3458743.

Full text

Abstract:

In this project, the challenge was to "deploy software faster than the coronavirus spread." In a project with such peculiar characteristics, several factors can influence success, but some clearly stand out: top management support, agility, understanding and commitment of the project team, and the technology used. Conventional development approaches and technologies would simply not be able to meet the requirements promptly.

APA, Harvard, Vancouver, ISO, and other styles

8

Ortega-Ordóñez, Wilson Alfredo, César Jesús Pardo-Calvache, and Francisco José Pino-Correa. "Systematic mapping on the agility evaluation in software development organizations." ITECKNE 16, no. 1 (June 19, 2019): 64–76. http://dx.doi.org/10.15332/iteckne.v16i1.2162.

Full text

Abstract:

Agile software development approaches provide great benefits for organizations; however, their implementation is subject to many challenges. For organizations is important to know the level of agility achieved and the gaps in their transformation process in order to implement improvements in their processes and take advantage of the agile approaches. Keeping this in mind, this article presents a systematic mapping of the literature about the evaluation of agility in software development organizations. As a result, 18 studies were found, which were analyzed and compared taking into account the type of study, the relationship of the evaluation with the principles and agile values, the defined evaluation criteria, the validation methods used, and the proposed tools. In addition, the factors that influence the assessment of agility and the aspects that motivate the interest in this research stream are exposed.

APA, Harvard, Vancouver, ISO, and other styles

9

Singh, Sukhpal, and Inderveer Chana. "Introducing Agility in Cloud Based Software Development through ASD." International Journal of u- and e- Service, Science and Technology 6, no. 5 (October 31, 2013): 191–202. http://dx.doi.org/10.14257/ijunesst.2013.6.5.17.

Full text

APA, Harvard, Vancouver, ISO, and other styles

10

Tian, Kun. "Adding More Agility to Software Product Line Methods." International Journal of Knowledge and Systems Science 5, no. 4 (October 2014): 17–34. http://dx.doi.org/10.4018/ijkss.2014100102.

Full text

Abstract:

Software Product Line Methods (SPLMs) have been continuously gaining attention, especially in practice, for on one hand, they address diverse market needs while controlling costs by planned systematic reuse in core assets development (domain engineering), and on another hand, they reduce products' time-to-market, achieving a certain level of agility in product development (application engineering). More cost-effective and agile as they are than traditional development methods for producing families of similar products, SPLMs still seem to be heavy weight in nature. In SPLMs, significant up-front commitments are involved in development of a flexible product platform, which will be modified into a range of products sharing common features. Agile Methods (AMs) share similar goals with SPLMs, e.g., on rapidly delivering high quality software that meets the changing needs of stakeholders. However, they appear to differ significantly practices. The purpose of this work is to compare Agile and Software Product line approaches from fundamental goals/principles, engineering, software quality assurance, sand project management perspectives, etc. The results of the study can be used to determine the feasibility of tailoring a software product line approach with Agile practices, resulting in a lighter-weight approach that provides mass customization, reduced time-to-market, and improved customer satisfaction.

APA, Harvard, Vancouver, ISO, and other styles

11

Kettunen, Petri. "Systematizing Software-Development Agility: Toward an Enterprise Capability Improvement Framework." Journal of Enterprise Transformation 2, no. 2 (April 2012): 81–104. http://dx.doi.org/10.1080/19488289.2012.664610.

Full text

APA, Harvard, Vancouver, ISO, and other styles

12

Sheffield, Jim, and Julien Lemétayer. "Factors associated with the software development agility of successful projects." International Journal of Project Management 31, no. 3 (April 2013): 459–72. http://dx.doi.org/10.1016/j.ijproman.2012.09.011.

Full text

APA, Harvard, Vancouver, ISO, and other styles

13

Sadia, Farzana, Imran Mahmud, Eva Dhar, Nusrat Jahan, Syeda Sumbul Hossain, and A. K. M. Zaidi Satter. "Dataset on the influence of software development agility on software firms' performance in Bangladesh." Data in Brief 23 (April 2019): 103741. http://dx.doi.org/10.1016/j.dib.2019.103741.

Full text

APA, Harvard, Vancouver, ISO, and other styles

14

Lacerda, Rogério Tadeu de Oliveira, Ewerton Sacco Calvetti, Mayara Lucia Bernardes, and Júlia Fraga Cargnin Da Silveira. "Research opportunities about measuring agility in software development: a constructivist perspective." Revista de Gestão e Projetos 11, no. 2 (September 10, 2020): 37–63. http://dx.doi.org/10.5585/gep.v11i2.17947.

Full text

Abstract:

Este artigo investiga oportunidades de pesquisa em um processo ágil de desenvolvimento de software sob óticas construtivistas de avaliação de desempenho, com base em um portfólio de 24 artigos científicos relevantes ao tema. O instrumento utilizado para realizar a análise sistêmica foi o método Proknow-C (Knowledge Development Process - Construttivist). Observou-se no portfólio que a avaliação de desempenho para medir a agilidade no contexto de desenvolvimento de software tem se focado praticamente em fatores críticos de sucesso e em modelos inflexíveis que se classificam em níveis de maturidade, mas sem avaliar claramente quanta agilidade é empregada. Este estudo aborda oportunidades de pesquisas relevantes que buscam identificar critérios e construir escalas de desempenho para medir agilidade a partir dos valores e preferências dos tomadores de decisão, que desejam implementar a filosofia ágil, alinhada com a estratégia específica dos objetivos dos tomadores de decisão e utilizando seus recursos, competências e cultura organizacional próprias para melhorar seu processo de desenvolvimento de software.

APA, Harvard, Vancouver, ISO, and other styles

15

Batra, Dinesh, Debra VanderMeer, and Kaushik Dutta. "Extending Agile Principles to Larger, Dynamic Software Projects." Journal of Database Management 22, no. 4 (October 2011): 73–92. http://dx.doi.org/10.4018/jdm.2011100104.

Full text

Abstract:

The article evaluates the feasibility of extending agile principles to larger, dynamic, and possibly distributed software development projects by uncovering the theoretical basis for agile values and principles for achieving agility. The extant literature focuses mainly on one theory – complex adaptive systems – to support agile methods, although recent research indicates that the control theory and the adaptive structuration theory are also applicable. This article proposes that at least three other theories exist that are highly relevant: transaction cost economics, social exchange theory, and expectancy theory. By employing these theories, a rigorous analysis of the Agile Manifesto is conducted. Certain agile values and principles find theoretical support and can be applied to enhance agility dynamic projects regardless of size; some agile principles find no theoretical support while others find limited support. Based on the analysis and the ensuing discussion, the authors propose a framework with five dimensions of agility: process, design, people, outcomes, and adaptation.

APA, Harvard, Vancouver, ISO, and other styles

16

Werder, Karl, and Alexander Maedche. "Explaining the emergence of team agility: a complex adaptive systems perspective." Information Technology & People 31, no. 3 (June 4, 2018): 819–44. http://dx.doi.org/10.1108/itp-04-2017-0125.

Full text

Abstract:

Purpose Agile software development helps software producing organizations to respond to manifold challenges. While prior research focused on agility as a project or process phenomenon, the authors suggest that agility is an emergent phenomenon on the team level. The paper aims to discuss this issue. Design/methodology/approach Using the theory of complex adaptive systems (CASs), the study captures the multiple influencing levels of software development teams (SDTs) and their interplay with self-organization and emergence. The authors investigate three agile SDTs in different contextual environments that participate with four or more different roles each. Findings The results suggest self-organization as a central process when understanding team agility. While contextual factors often provide restriction on self-organization, they can help the team to enhance its autonomy. Research limitations/implications The theoretical contributions result from the development and test of theory grounded propositions and the investigation of mature agile development teams. Practical implications The findings help practitioners to improve the cost-effectiveness ratio of their team’s operations. Originality/value The study provides empirical evidence for the emergence of team agility in agile SDTs. Using the lens of CAS, the study suggests the importance of the team’s autonomy.

APA, Harvard, Vancouver, ISO, and other styles

17

Gumantan, Aditya, and Imam Mahfud. "Pengembangan Alat Tes Pengukuran Kelincahan Mengunakan Sensor Infrared." Jendela Olahraga 5, no. 2 (July 15, 2020): 52–61. http://dx.doi.org/10.26877/jo.v5i2.6165.

Full text

Abstract:

The aim of this development was to develop a product design of measuring tools agility became a software and hardware program as an innovation of stopwacth. There were three items of agility test, such as Dodging run, Bomerang Run and Agility Runing Test.The method that was used were research and development method from Brog and Gral which consisted of ten steps. The subject of this research was the physical education students of Teknokrat Indonesia University which had been evaluated by the experts, a trial, revision and also validated by media experts, material and practice by using the questionnaire which consisted of some questions. The result of the effectiveness of this product showed 85% material expert, 96% media expert, and 85% practicioners.It can be concluded that the development of measuring tools agility was effective to be used for being the basic of developing physical technolgy science.Keywords: Agility, Measuring Agility, Dodging run, Bomerang Run Test, Agility Runing Test , Infrared AbstrakPengembangan ini bertujuan mengembangkan suatu rancangan produk alat ukur kelincahan menjadi software program dan hardware sebagai pembaruan alat ukur stopwacth, dimana ada tiga item tes kelincahan yaitu Dodging run, Bomerang Run Test dan Agility Runing Test. Metode yang digunakan dalam penelitian ini metode penelitian dan pengembangan (Research and Development) dari Borg dan Gall yang terdiri dari sepuluh langkah. Subjek penelitian ini adalah mahasiswa pendidikan olahraga Universitas Teknokrat Indonesia model yang telah di evaluasi ahli, uji coba dan revisi serta divalidasi oleh para ahli media, materi dan praktisi melalui angket yang terdiri dari berbagai macam pertanyaan. Efektifitas produk pengembangan alat ukur kelincahan memilki hasil 85% ahli materi, 96% ahli media dan 85% oleh praktisi, Dengan demikian dapat dinyatakan bahwa pengembangan alat ukur kelincahan efektif digunakan untuk menjadi dasar pengembangan ilmu teknologi olahragaKata kunci: Kelincahan, Alat Ukur Kelincahan, Dodging run, Bomerang Run Test, Agility Runing Test, Infrared

APA, Harvard, Vancouver, ISO, and other styles

18

Pathak, Atul Arun. "Enabling lifelong learning: the key to agility at ThoughtWorks India." Human Resource Management International Digest 25, no. 1 (January 9, 2017): 4–6. http://dx.doi.org/10.1108/hrmid-07-2016-0108.

Full text

Abstract:

Purpose The paper aims to describe the innovative learning culture, practices and processes at ThoughtWorks India (TWI), a software application development company in India. These practices support continual learning and development at the level of employees, project teams and the entire organization. Design/methodology/approach The paper draws upon the unique case of TWI. It describes the need for continual learning at TWI. It then describes how the organization has promoted a culture of continual learning on an individual, team and organizational level. It explains how the learning practices and processes aligns to the project level and organizational goals. Findings Because of the complex and difficult nature of software development projects that TWI takes up regularly, it needs its employees to be at the cutting edge of technological skills and know-how. If this was to be attempted through formal training programs, it would turn out to be extremely expensive and inefficient way of learning for TWI. Instead, TWI relies on on-the-job-learning. It does so through a variety of innovative work practices that are described in the paper. It also achieves its learning goals through a culture that supports continual learning and development of employees. Practical implications The learning related practices, processes and mechanisms used at TWI can be emulated by companies in the software development industry. This will ensure that employees learn and develop their skill-sets all the time and remain at the cutting edge of technological developments. This will help organizations pitch for and successfully deliver difficult and complex software development projects that add very high value to their clients. Social implications The social implications of the approach followed by TWI are positive. Employees are motivated to improve themselves every day. They understand the need for doing so. Also, they appreciate the fact that TWI supports continual learning and development. Knowledge sharing among employees is encouraged through the practices followed almost daily in projects. Originality/value The paper considers a unique set of learning and development practices, processes and mechanisms in TWI, a software development company in India.

APA, Harvard, Vancouver, ISO, and other styles

19

Łukasiewicz, K., and J. Miler. "Improving agility and discipline of software development with the Scrum and CMMI." IET Software 6, no. 5 (2012): 416. http://dx.doi.org/10.1049/iet-sen.2011.0193.

Full text

APA, Harvard, Vancouver, ISO, and other styles

20

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.

Full text

Abstract:

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.

APA, Harvard, Vancouver, ISO, and other styles

21

Horicka, Pavol, and Jaromir Simonek. "Age-related changes of reactive agility in football." Physical Activity Review 9, no. 1 (2021): 16–23. http://dx.doi.org/10.16926/par.2021.09.03.

Full text

Abstract:

The purpose of this investigation is to determine age dynamism of reactive agility in young football players, thus specifying the impact of sport training on the level of reactive agility of players. 112 young male football players playing for the football club in Nitra, Slovakia volunteered to participate in the study. Another goal was to clarify the age dynamics of performances in the monitored groups of football players and to find out the mutual relationship between the two types of agility. Trends in sport performance and relationship of both kinds of agility were observed in 6 teams of different age categories (U11 up to U16). In order to fulfil the aim of the research two different motor tests for running agility (Illinois agility test) and reactive agility (Fitro Agility Check) were selected. For the realization of Fitro Agility Check test, a computer with the necessary hardware and software, and measuring device Fitro Agility Check were used. To evaluate the relationship between the observed variables (Illinois vs FAC), we used Spearman's correlation coefficient rs (-1 ≤ rs ≤ 1) to perform correlation analysis in SSPS statistical software. We used a significance level of 0.01. The results of this study provide evidence of stabilization of performance with the growing age of players at the level of both types of agility and a dynamic increase, especially after the age of 13. Low values of correlation coefficients (from r = - 0.570 to 0.503) indicate indifferent determinants in running and reactive agility. Since low causal-consequential relationship between reactive and running agility was found in the observed football teams, there is a necessity in the sports training to differentiate between specific means for the development of the so-called pre-planned and reactive agility.

APA, Harvard, Vancouver, ISO, and other styles

22

Ortega Ordoñez, Wilson Alfredo, César Jesús Pardo Calvache, and Francisco José Pino Correa. "OntoAgile: an ontology for agile software development processes." DYNA 86, no. 209 (April 1, 2019): 79–90. http://dx.doi.org/10.15446/dyna.v86n209.76670.

Full text

Abstract:

Currently, there is a broad portfolio of agile approaches to software development, however, in many cases their implementation is done informally and without a proper institutionalization of the agile values and principles. Although there are some proposals related to the adoption and assessment of agile approaches, efforts have been made without having a common terminology which has led to confusion and terminological conflict affecting the implementation of these approaches in organizations. This article proposes the ontology called OntoAgile, which aims to suggest a common and consistent terminology that allows sharing the knowledge generated around the implementation of the agile approaches in the software processes in a generic and formal way. Similarly, OntoAgile facilitates the assessment of the agility of the software processes from the identification of the relationships between the elements of the software processes and the agile principles and values. OntoAgile was assessed satisfactorily by three cases of application.

APA, Harvard, Vancouver, ISO, and other styles

23

Sena, James, Jean-Francois Coget, and A. B. (Rami) Shani. "Designing for Agility as an Organizational Capability: Learning from a Software Development Firm." International Journal of Knowledge, Culture, and Change Management: Annual Review 9, no. 5 (2009): 17–36. http://dx.doi.org/10.18848/1447-9524/cgp/v09i05/49740.

Full text

APA, Harvard, Vancouver, ISO, and other styles

24

Gill, Asif Qumer, Brian Henderson-Sellers, and Mahmood Niazi. "Scaling for agility: A reference model for hybrid traditional-agile software development methodologies." Information Systems Frontiers 20, no. 2 (July 16, 2016): 315–41. http://dx.doi.org/10.1007/s10796-016-9672-8.

Full text

APA, Harvard, Vancouver, ISO, and other styles

25

Hasteer, Nitasha, Abhay Bansal, and B. K. Murthy. "Causal Analysis of Software Development Attributes for Cloud Applications." International Journal of Healthcare Information Systems and Informatics 13, no. 4 (October 2018): 66–81. http://dx.doi.org/10.4018/ijhisi.2018100105.

Full text

Abstract:

Cloud computing provides organizations the dynamic capability to deploy applications quickly on self-provision development platforms. In adopting a cloud-computing paradigm, the software development process leverages the use of cloud native features. This article highlights a cloud-based health insurance solution that enables consumers to purchase packages online with the objective of identifying attributes in the context of the development process while analyzing the association among the attributes. Exploratory factor analysis is used to identify the latent attributes. Their associations, in terms of causal relationship analysis, are investigated via DEMATEL. Results of factor analysis imply that agility, availability and adaptability are the underlying factors for cloud application development. The findings of the DEMATEL reveal that co-creative and collaborative development process, which embrace quick discovery and assembly of services in the cloud, are significant attributes that influence other attributes within the context of the cloud-based software development process.

APA, Harvard, Vancouver, ISO, and other styles

26

Bartusevičs, Artūrs, Andrejs Lesovskis, and Viktorija Ponomarenko. "Model-Driven Approach and Library of Reusable Source Code for Automation of IT Operations." Applied Computer Systems 21, no. 1 (May 24, 2017): 5–12. http://dx.doi.org/10.1515/acss-2017-0001.

Full text

Abstract:

Abstract Large software development projects with high levels of agility require several IT operations: software configuration management, bug tracking management, making software builds and deployments. Due to high agility in projects, the starting phases are very chaotic and sometimes in a few days customer is willing to get the first release of software. It means that all IT operations should be automated as soon as possible. The study presents a model-driven approach for automation of IT operations through the reuse of the existing source code. In addition, it presents a method for the development of library of reusable source code. The paper contains a brief description of the model-driven approach, library of source code and meta-models developed for a new methodology. The paper ends with the results of the practical experiments and conclusions on how this approach could be improved in the future.

APA, Harvard, Vancouver, ISO, and other styles

27

Butler, Charles W., Leo R. Vijayasarathy, and Nicholas Roberts. "Managing Software Development Projects for Success: Aligning Plan- and Agility-Based Approaches to Project Complexity and Project Dynamism." Project Management Journal 51, no. 3 (July 4, 2019): 262–77. http://dx.doi.org/10.1177/8756972819848251.

Full text

Abstract:

In general, project complexity and project dynamism are recognized as potent characteristics that influence, usually in a negative way, the outcome of software development projects. However, with respect to the two dominant paradigms for managing software development projects (i.e., plan-based project approach and agility-based project approach), there is less agreement as to which one is better. Emerging research suggests that the preeminence of one approach over another is a matter of fit between the project management approach and the project context, including its complexity and dynamism. We contribute to this line of research by studying the moderating influence of the two project management approaches on the relationship between project complexity and project dynamism on project outcomes. Our analysis of data gathered from a survey of software development professionals shows that managing dynamism is critical for realizing project success, and an agility-based project approach is best suited for mitigating dynamism’s negative effects on project success.

APA, Harvard, Vancouver, ISO, and other styles

28

Mitsuyuki, Taiga, Kazuo Hiekata, Takuya Goto, and Bryan Moser. "Evaluation of Project Architecture in Software Development Mixing Waterfall and Agile by Using Process Simulation." Journal of Industrial Integration and Management 02, no. 02 (June 2017): 1750007. http://dx.doi.org/10.1142/s2424862217500075.

Full text

Abstract:

For software development, especially massive software systems, a waterfall process is used traditionally. A waterfall process can be highly effective on the condition that a master plan is fixed and the possibility of changes and uncertain rework is low. However, in software development projects, many kinds of reworks occur corresponding to uncertain requirement changes and program bugs. In addition, with the advent of cloud-based software platforms and continuous development operations, it is possible to develop a software system while operating the system. To respond to this situation, software development projects often adopt an agile process. Agility may allow conditional response to uncertain rework, yet at the same time it may be difficult to control the achievement of known project targets. Recently, many cases of adopting mixed processes including waterfall and agile have been reported in the massive software development projects. In this paper, we argue that the mixed process architecture should be designed, considering the scale of the targeted software project, the culture of organization, the probability of uncertain requirement changes, and so on. This paper proposes a methodology of evaluating the impact of waterfall, agile, and mixed project architectures by using process simulation. A project architectural approach is evaluated with a simulator which includes a software reliability growth model and uncertain rework driven by requirement change and error propagation. The proposed methodology was applied to a development project for a simple shopping website. The results showed that the proposed methodology allows exploration of partial agile adoption depending on the nature of the system development project, including its scale and chances of change. For example, in this paper, if the scale of the project is small, the positive effect of increasing agility by adopting agile processes is low. On the other hand, if the scale of the project is large, the effect of increasing agility by adopting agile process can increase. Furthermore, it became clear that it is important to not apply an agile process blindly, but instead to design a mixed project architecture considering the number of errors and development schedule targets across the project scope.

APA, Harvard, Vancouver, ISO, and other styles

29

Patil, Madhukar Rajaram, and M. Suresh. "Assessment of Team Agility in Internet of Things Projects." Webology 18, Special Issue 01 (April 29, 2021): 137–48. http://dx.doi.org/10.14704/web/v18si01/web18050.

Full text

Abstract:

Internet of Things (IoT) projects are special kind of Research and Development (R&D) projects. Team agility plays an important role in determining the agility of IoT project organizations. Thus the paper aims to evaluate the team agility level of IoT projects using multi-grade fuzzy and Importance Performance Analysis (IPA).The team agility index is computed using multi-grade fuzzy for the case IoT project is 7.63 which is between the ranges (6-8) which specifies as ‘Highly Agile’. The IPA is applied to identify the weaker attributes to improve the team agility of case IoT project. The framework can be used on a periodic basis to help IoT project managers to improve continuously their team agility level.

APA, Harvard, Vancouver, ISO, and other styles

30

Fayezi, Sajad, and Maryam Zomorrodi. "The role of relationship integration in supply chain agility and flexibility development." Journal of Manufacturing Technology Management 26, no. 8 (October 5, 2015): 1126–57. http://dx.doi.org/10.1108/jmtm-11-2014-0123.

Full text

Abstract:

Purpose – The purpose of this paper is to contribute to the supply chain management literature by presenting the Australian practitioners’ perception of the role of relationship integration in developing supply chain agility and flexibility. Design/methodology/approach – The research takes semi-structured, indepth interviews with ten operations and supply chain practitioners in the Australian manufacturing sector. A systematic qualitative data analysis approach grounded on cross-interview synthesis was used. Findings – Findings contributed into understanding of the manufacturing companies’ implementation of relationship integration with respect to decision trade-offs involved in contract design. Moreover, the findings revealed the significant perceived importance and impact of relationship integration on supply chain agility and flexibility development. This was, however, found to be a function of things such as upstream or downstream focus and organisational size. These findings were expressed in terms of seven propositions. Practical implications – Analysis of the interviews substantiates the criticality of informed allocation of resources to relationship-intensive activities and investments across the supply chain to develop agility and flexibility. International businesses can gain insights into Australian manufacturing businesses’ perception of relationship integration, which can be invaluable for strategic planning to develop agile and flexible supply chains with their Australian partners. Originality/value – This paper takes an original approach to present operations and supply chain practitioners’ perception of manufacturing businesses’ use of relationship integration for supply chain agility and flexibility development.

APA, Harvard, Vancouver, ISO, and other styles

31

Lee and Xia. "Toward Agile: An Integrated Analysis of Quantitative and Qualitative Field Data on Software Development Agility." MIS Quarterly 34, no. 1 (2010): 87. http://dx.doi.org/10.2307/20721416.

Full text

APA, Harvard, Vancouver, ISO, and other styles

32

Jabar, Marzanah A., Norhayati Mohd Ali, Yusmadi Yah Jusoh, Salfarina Abdullah, and S. Mohanarajah. "Adaptive and Dynamic Hybrid Model for Software Project Management: A Review on its Clarity and Usage to Improve Project Success." Applied Mechanics and Materials 892 (June 2019): 38–45. http://dx.doi.org/10.4028/www.scientific.net/amm.892.38.

Full text

Abstract:

Software developers have shown a lot of interest in using agile approaches and methods to manage projects. The Agile Manifesto in 2001 provided a good basis to use this as it formulated its 4 values and 12 principles. Adaptability was a common feature in the Agile Manifesto to make agility happen and there appears a need to combine dynamism to ensure agility takes a more concrete and effective role. Whilst the term adaptability is discussed more often than dynamism by most researchers, the clarity in its meaning needs improvement as the terms are used interchangeably. This paper proposes a useful clarity on its differences and how it should be used. In addition, this approach would also facilitate the current research interest in mixing and combining software development methodologies to create hybrid versions as pure methods (traditional and agile) have not worked well in most software projects.

APA, Harvard, Vancouver, ISO, and other styles

33

Shafiee Kristensen, Saeedeh, Mitra Shafiee, and Sara Shafiee. "ORGANIZATION DESIGN IN MOTION: DESIGNING AN ORGANIZATION FOR AGILITY." Proceedings of the Design Society 1 (July 27, 2021): 2349–58. http://dx.doi.org/10.1017/pds.2021.496.

Full text

Abstract:

AbstractIncreasingly competitive and multifaceted business landscapes and the accelerating pace of innovation require organizations to build in-house capability to evaluate the effectiveness of their design and redesign their organizational structure to drive agile product development. The purpose of this research is to examine how the ability of an organization to implement agile is affected by the organization design. A case study based on 35 semi-structured interviews and field observations at a leading, large-size, Danish software development company was carried out. Adopting the contingency perspective, this paper presents the relevant organizational elements that can increase organizational agility and how the companies can leverage the advantages of the design. Accordingly, it provides a framework that compromises eighteen core organizational practices grouped into four categories (organizational structure and governance, culture and people, IT tools and data infrastructure, and processes) to understand the effect of organization design on agile product development.

APA, Harvard, Vancouver, ISO, and other styles

34

Alruwaili, Fatimah, Muna Alrajhi, and Kawther Saeedi. "How Agile Development and Its Tools Support Digital Transformation." INTERNATIONAL JOURNAL OF COMPUTERS & TECHNOLOGY 18 (February 1, 2019): 7440–50. http://dx.doi.org/10.24297/ijct.v18i0.8060.

Full text

Abstract:

Digital transformation is the enabler for new reform of businesses, socialites and governments. It is also the platform to the 2030 Vision in Saudi Arabia and in many other countries. Agile Manifesto succeeded to manage software development in a rapid and reliable fashion. Furthermore, incremental delivery of software release ensure that software audiences are engaged while delivering the product, their comments are considered in every function and any changes in requirements are based on imperial use of the software. This ensure the delivery of functionalities matching customer demands as well as reduce project failure risk. For this reason, Agility has been adopted in most software companies as a guaranteed and easy way to implement the digital solutions for their companies. This paper examines the characteristics of agile frameworks, such as Scrum and XP, and Agile tools, such as Jira, Agilo, and others, that facilitate digital transformation. Then compare productivity and efficacy of agile frameworks with traditional SDLC methods. The paper is concluded with the features of agile framework that enable digital transformation such as incremental development, flexible requirements and customer engagement.

APA, Harvard, Vancouver, ISO, and other styles

35

Sanatigar, Hoda, Mehraban Hadi Peikani, and Daryoosh Gholamzadeh. "Identifying organizational agility and leadership dimensions using Delphi technique and factor analysis." International Journal of Public Leadership 13, no. 4 (November 13, 2017): 276–94. http://dx.doi.org/10.1108/ijpl-01-2017-0005.

Full text

Abstract:

Purpose The purpose of this paper is to identify the organizational agility components and factors in Iranian’s pension funds as an example of service organizations in the public sector. Design/methodology/approach This study can be categorized in the realm of developmental studies as to its research purposes, and employed the descriptive survey method to collect data using the combination of both qualitative and quantitative methods (exploratory mixed-method design). Findings Finally, a three-level model of organizational agility construct (modeled as 6 components, 23 factors, and 83 indicators) was analyzed and confirmed using confirmatory factor analysis by means of the smart PLS software. Overall, this study provided a new method for the analysis, measurement and development of organizational agility construct in public service organizations in Iran. Originality/value Through using text content analysis and opinion of experts (interviews and Delphi technique), qualitative data were extracted to design an organizational agility model, whereas quantitative data were obtained through a questionnaire to test the model. To determine the validity and reliability of the questionnaire, expert opinions and Cronbach’s α (0.977) were used, respectively.

APA, Harvard, Vancouver, ISO, and other styles

36

Zheng, Mengze, Islam Zada, Sara Shahzad, Javed Iqbal, Muhammad Shafiq, Muhammad Zeeshan, and Amjad Ali. "Key Performance Indicators for the Integration of the Service-Oriented Architecture and Scrum Process Model for IOT." Scientific Programming 2021 (February 2, 2021): 1–11. http://dx.doi.org/10.1155/2021/6613579.

Full text

Abstract:

An important aspect in any business process lifecycle is management of the performance, where performance requirements on business processes are specified as Key Performance Indicators (KPIs) with target values which are to be achieved in a certain analysis period. A KPI is a business metric used to measure and evaluate the individual capability, maturity, complexity, and agility of a business process in the development environment. This study designed four general KPIs for the integration of SOA and scrum to bring further advancement in these approaches for IIoT. The study also identified some common metrics which will give help to software developers and, especially, to those who want to apply SOA and scrum integration. These metrics will play a critical role of bridging the strategy and concepts of improvements with operational activities. The identified KPIs will help to measure the business agility, quality and value, team efficiency, and complexity of scrum- and SOA based projects. Software development organizations can also practice these KPIs to know where to focus their resources to deliver the ultimate business profit. So, software business organizations could better align their business projects and IT investments with the rapid market change and deliveries.

APA, Harvard, Vancouver, ISO, and other styles

37

Singh Patel, Bharat, Cherian Samuel, and S. K. Sharma. "Evaluation of agility in supply chains: a case study of an Indian manufacturing organization." Journal of Manufacturing Technology Management 28, no. 2 (March 6, 2017): 212–31. http://dx.doi.org/10.1108/jmtm-09-2016-0125.

Full text

Abstract:

Purpose The purpose of this paper is to report a case study carried out to assess the agility and identify obstacles to agility in a supply chain. A human perception-based framework is used for the calculation of agility. The case study was carried out in a North India-based manufacturing organization. Design/methodology/approach In this study, the concept of a multi-grade fuzzy logic approach is used. Using this concept, the overall agility index has been determined. The fuzzy logic approach has been used to overcome the disadvantages such as impreciseness and vagueness using a scoring method. Findings From the analysis, it is observed that the organization on which the study was performed is “very agile.” After evaluating the agility level, the fuzzy performance importance index is calculated, which helps to identify the barriers of agility in the supply chain. These barriers help decision makers to implement appropriate improvement measures for improving agility level. Overall, 11 barriers were identified in the study. Research limitations/implications Managers of the contemporary manufacturing organization have to measure the agility level of the organization and identify barriers to agility in order to survive in a competitive environment. The obstacles identified in this study are used to improve the performance of the organization. The enterprise should improve on the weak areas in order to achieve the highest agility level. Originality/value The agile supply chain (ASC) enablers proposed by previous researchers are not sufficient for the evaluation of agility of a supply chain. There are a few more ASC enablers such as customer satisfaction, flexibility and adaptability that also play a vital role in making a supply chain agile. Adding these three ASC enablers, a total of seven ASC enablers along with their attributes are being considered for the development of a conceptual model.

APA, Harvard, Vancouver, ISO, and other styles

38

Bartusevics, Arturs, Leonids Novickis, and Stefan Leye. "Models and Methods of Software Configuration Management." Applied Computer Systems 17, no. 1 (May 1, 2015): 53–59. http://dx.doi.org/10.1515/acss-2015-0008.

Full text

Abstract:

Abstract The paper provides collection of experience of developing models and methods for implementation of software configuration management process. Nowadays, during the age of agility, startup of new software development projects is like an explosion. Sometimes, in a few days a customer is willing to get the first release, but formalized and reusable process for its creating is not ready yet. Software configuration management controls the evolution of software items and supports building and deployment process for product releases. Models and methods for implementation of software configuration management are presented in the paper. Unlike other approaches, the provided models and methods are related to decrease software configuration management implementation time in new projects. The paper provides a simplified use case to illustrate practical application of the mentioned methods and models.

APA, Harvard, Vancouver, ISO, and other styles

39

Mandal, Ardhendu, and S. C. Pal. "Achieving agility through BRIDGE process model: an approach to integrate the agile and disciplined software development." Innovations in Systems and Software Engineering 11, no. 1 (August 23, 2014): 1–7. http://dx.doi.org/10.1007/s11334-014-0239-x.

Full text

APA, Harvard, Vancouver, ISO, and other styles

40

Nadeem, Muhammad Asgher, and Scott Uk-Jin Lee. "Dynamic Agile Distributed Development Method." Mathematics 7, no. 10 (October 13, 2019): 963. http://dx.doi.org/10.3390/math7100963.

Full text

Abstract:

“Agile” is an effective software engineering model with a high trust and acceptance rate among its users. The term agility comes from the concept of rapid development and working in a team for better results and a faster competition rate when compared with any other software engineering model. In this study, an assessment of the different patterns, frameworks, and application program interfaces available for distributed development in an agile model is given. After analyzing the state-of-the-art distributed models, a novel framework of a dynamic agile distributed development method (DADDM) is introduced in this paper. Many researchers have worked on global software development using the agile approach; however, we are presenting the idea of incorporating the agile benefits with dynamic distributed software development. The applicability of the proposed model is checked via two selected parameters: a feasibility study and a business study. The complete DADDM development life cycle is presented in the methodology section. The techniques used in DADDM and team members’ roles and responsibilities in DADDM are defined in this study. This study reflects all pillars of planning, controlling, organizing, and management of leadership. The use of DADDM in distributed agile development encourages future researchers to use this proposed framework for comparison and testing of their models and to check the effectiveness through a comparison with DADDM.

APA, Harvard, Vancouver, ISO, and other styles

41

Yu, Weider D., Ashwini Sathyanarayana Adiga, Srivarsha Rao, and Miby Jose Panakkel. "A SOA Based System Development Methodology for Cloud Computing Environment." International Journal of E-Health and Medical Communications 3, no. 4 (October 2012): 42–63. http://dx.doi.org/10.4018/jehmc.2012100104.

Full text

Abstract:

Service Oriented Architecture (SOA) uses a structural approach to create services which can be reused and shared. SOA provides agility and cost saving in software development, transforming vertical applications to various software components, which can be reused in applications. Cloud computing expands the software service accessibility and usage via Web services. To move successfully into cloud computing, an architecture supporting the cloud capabilities is needed. The cloud provides a good platform for deploying Web services based on SOA. Customer satisfaction, improved collaboration, enhanced end-to-end user security and end-user authentication, and business growth are some long term benefits supported by modern technologies in both of cloud computing and SOA. The objective of the paper is to study the effective process and effort required to design and implement a SOA based system development methodology and applying it to construct a u-Healthcare system to provide healthcare services including accessing medical records of patients on a universal end-to-end basis.

APA, Harvard, Vancouver, ISO, and other styles

42

Berg, Vebjørn, Jørgen Birkeland, Anh Nguyen-Duc, Ilias O. Pappas, and Letizia Jaccheri. "Achieving agility and quality in product development - an empirical study of hardware startups." Journal of Systems and Software 167 (September 2020): 110599. http://dx.doi.org/10.1016/j.jss.2020.110599.

Full text

APA, Harvard, Vancouver, ISO, and other styles

43

Cui, Yanqing, Islam Zada, Sara Shahzad, Shah Nazir, Shafi Ullah Khan, Naveed Hussain, and Muhammad Asshad. "Analysis of Service-Oriented Architecture and Scrum Software Development Approach for IIoT." Scientific Programming 2021 (January 23, 2021): 1–14. http://dx.doi.org/10.1155/2021/6611407.

Full text

Abstract:

Flexibility and change adoption are key attributes for service-oriented architecture (SOA) and agile software development processes. Although the notion of agility is quite visible on both sides, still the integration of the two diverse concepts (architectural framework and development process) should be well thought of before employing them for a software development project. For this purpose, this study is designed to analyze the two diverse software architectural framework and development approaches, that is, SOA and Scrum process model, respectively, and their integrated environment in software project development setup perspective for Industrial Internet of Things (IIoT). This study also analyzes commonalities among Scrum process model and SOA architectural framework to identify compatibility between Scrum and SOA so that the Scrum process can be constructively used for SOA based projects. This study also examines the proper design and setup of Scrum process suitable for large-scale SOA based projects. For this purpose, an SOA based research and development project is selected as a case study using Scrum as the software development process. The project development and deployment perspective include eight core modules that constitute the overall project framework.

APA, Harvard, Vancouver, ISO, and other styles

44

Zheng, Yingqin, Will Venters, and Tony Cornford. "Collective agility, paradox and organizational improvisation: the development of a particle physics grid." Information Systems Journal 21, no. 4 (September 27, 2010): 303–33. http://dx.doi.org/10.1111/j.1365-2575.2010.00360.x.

Full text

APA, Harvard, Vancouver, ISO, and other styles

45

Okoli, Chitu, and Kevin Carillo. "The best of adaptive and predictive methodologies: open source software development, a balance between agility and discipline." International Journal of Information Technology and Management 11, no. 1/2 (2012): 153. http://dx.doi.org/10.1504/ijitm.2012.044071.

Full text

APA, Harvard, Vancouver, ISO, and other styles

46

Rodriguez-Martinez, Laura, Hector Duran-Limon, Manuel Mora, and Francisco Rodriguez. "SOCA-DSEM: A well-structured SOCA development systems engineering methodology." Computer Science and Information Systems 16, no. 1 (2019): 19–44. http://dx.doi.org/10.2298/csis170703035r.

Full text

Abstract:

Service-oriented Software Engineering (SOSE) is a software engineering paradigm focused on Service-oriented Computing Applications (SOCAs), for what SOCA development methodologies are required. Recent studies on SOCA development methodologies revealed theoretical and practical deficiencies. Thus, academicians and practitioners must adapt development methodologies from other paradigms or use the available partial SOCA development methodologies. Also, since the high acceptance of agile approaches, we claim new well-structured and balanced agility-rigor methodologies are required. Then, this paper proposes a new SOCA Development Systems Engineering Methodology, including its description, the explanation of its theoretical foundations and the illustration of its use with a prototype of a running example. Two pilot empirical evaluations on usability metrics are also reported. Findings support both theoretical adequacy and positive perceptions from the evaluators. While further empirical tests are required for gaining more conclusive evidences our preliminary results are encouraging.

APA, Harvard, Vancouver, ISO, and other styles

47

Barros, Jaqueline Dos Santos Valente, Marcos Venicius Malveira de Lima, Aristéia Nunes Sampaio, Suellem M. B. de Moura Rocha, Paulo Moreira Silva Dantas, Shirley Regina De Almeida Batista, and Romeu Paulo Martins Silva. "Analysis of motor capacities in the maturational stages of female adolescents." Journal of Human Growth and Development 27, no. 2 (September 6, 2017): 206. http://dx.doi.org/10.7322/jhgd.125018.

Full text

Abstract:

Introduction: Maturation is a biological phenomenon inherent to the human being that acts alongside environmental factors in its relationship with the development of children and adolescents.Objective: To analyse the motor skills during maturational stages of female adolescents.Methods: This study included 133 female adolescents aged between 10 and 17 years from federal schools in the city of Rio Branco, State of Acre, Brazil. Sexual maturation was evaluated using Tanner’s self-assessment. Motor skills were assessed using the following tests: strength (Jump Test); coordination (Burpee Test); balance (Flamingo Test); flexibility (Sit and Reach Test); agility (Shuttle Run Test). The data were analysed using R software through analysis of variance. The significance level was fixed at 5%.Result: No significant statistical results were found for strength, agility, balance and flexibility, evidencing that maturational advances did not influence these skills. In the coordination variable, significant results were obtained.Conclusion: The results of this study suggest that maturational advancement in adolescents does not influence strength, agility, balance or flexibility. However, it does influence coordination, presenting better performance at stage P2.

APA, Harvard, Vancouver, ISO, and other styles

48

Suteeca, Kittitouch, and Sakgasit Ramingwong. "The Visualization of ISO/IEC29110 on SCRUM under EPF Composer." Information 12, no. 5 (April 28, 2021): 190. http://dx.doi.org/10.3390/info12050190.

Full text

Abstract:

In the midst of an increasingly competitive software industry, very small entities (VSEs) have inevitably faced many challenges. High user expectations, frequent changes of user requirements, and the need for rapid deployment are classic examples of these challenges. Many software companies attempt to implement measures for preventing or solving the aforementioned problems. The use of agile methodologies and the implementation of software development standards are usually perceived to be promising solutions to improve the quality of the software development process. Nevertheless, there are several strong incompatibilities between standards and the Agile approach to software development. For example, the need identified in the standards to create many quality artifacts does not conform to agility philosophies. Since Agile focuses on the working software over the documentation, the use of the Agile with standards can be difficult to implement. Additionally, there has been none guidelines for VSE therefore, an external consultant is usually required. This research analyzes various cases of implementing ISO/IEC29110, a software development standard developed especially for VSEs in Scrum environments. The results of this study provide an Eclipse Process Framework (EPF) for effectively and conveniently implementing this standard in Scrum software development.

APA, Harvard, Vancouver, ISO, and other styles

49

Aarti, Mrs, and M. Karande. "SELECTION OF ENTERPRISE ARCHITECTURE BASED ON AGILE PARAMETERS FOR SCM-BASED CASE STUDY." Scholedge International Journal of Business Policy & Governance ISSN 2394-3351 4, no. 5 (September 21, 2017): 36. http://dx.doi.org/10.19085/journal.sijbpg040501.

Full text

Abstract:

Aim/Purpose: This paper being a review paper shows mapping of enterprise architecture with respect to supply chain domain as per agile parameter so to find the best architecture for the development of the enterprise solution used in SCM company. Background /Methodology: Without EA, companies muddle through. In an agile environment selection of enterprise architecture is difficult even considering different parameters with SCM phases. This is a question and answer based research survey done for finding the mapping of SCM with different EAs were evaluated with 20yrs of experienced five experts. Originality/Value: This paper shows different EA mapped to SCM domain. Tabular format mapping of agile parameter with EA helps to find best EA for developing enterprise solutions even in agile environment. Findings: Comparison of 11 EA with a set of agile parameters shows that TOGAF is the most suitable EA for the development of the enterprise software solution. Systematic and structural working of TOGAF, handles the development in agile situation. Practical implications: Set of agile parameter from different phases of SCM may help practitioners to understand agile environment gives technical and logical gap which needs to consider in developing the software solution. Social implications: Mapping agile parameters at different strategies can help system to withstand in the changing environment with its impact on different operational levels of SCM. Research limitations/implications: Finding the type of agility and amount of agility in the SCM system can be an enhancement of this paper. Even more effective agile parameters affecting agility are the future of SCM.

APA, Harvard, Vancouver, ISO, and other styles

50

Gaševic, Dragan, and Marek Hatala. "Model-Driven Engineering of Service-Oriented Systems." International Journal of Service Science, Management, Engineering, and Technology 1, no. 1 (January 2010): 17–32. http://dx.doi.org/10.4018/jssmet.2010010102.

Full text

Abstract:

Service-oriented architectures (SOA) are an essential platform to provide infrastructures that support widespread collaboration between organizations. These service-oriented systems are a new context for software developers, who must now be equipped with new development methods and technologies. This new context has specific requirements, such as better collaboration and communication between business users and software engineering across organizations and increased agility of the development and maintenance processes to better respond to newly emerged or changed requirements. In this paper, the authors present a research agenda that looks at the use of a novel software engineering discipline—model-driven engineering. By switching the focus from low-level technical details to high-level problem-specific details, model-driven engineering addresses challenges in the development of service-oriented systems. This paper particularly discusses the approach to the development of service-oriented systems based on business process modeling, which integrate business vocabularies and rules in different stages of the development lifecycle. Here, model-driven engineering can provide many promising solutions.

APA, Harvard, Vancouver, ISO, and other styles

Journal articles on the topic 'Agility in Software Development'

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles