Research on Agile Development Methodology of Service-Oriented Personalized Software

2008 ◽  
Author(s):  
Hanning Yuan ◽  
Yanni Han ◽  
Jun Hu
Keyword(s):  
Agile Development ◽  
Development Methodology ◽  
Service Oriented

Agile Software Development Process Applied to the Serious Games Development for Children from 7 to 10 Years Old

2015 ◽  
Vol 8 (2) ◽  
pp. 64-79 ◽  
Author(s):  
Sandra P. Cano ◽  
Carina S. González ◽  
César A. Collazos ◽  
Jaime Muñoz Arteaga ◽  
Sergio Zapata
Keyword(s):  
Serious Games ◽  
User Profile ◽  
Extreme Programming ◽  
Agile Development ◽  
User Centered Design ◽  
Medium Development ◽  
Development Methodology ◽  
Agile Software ◽  
The City

The development of video games is a complex, multidisciplinary process, which involves different areas as well as a greater number of roles than for traditional software. Serious games face process constraints that concern a number of interactive, educational and psychological factors designed to lead to the fulfillment of educational objectives within a specific context. Based on a case study in the city Cali, Colombia, an iterative and incremental process is proposed, focusing on small and medium development for educational serious games and basing itself on two lines of research: agile development methodology and user-centered design (UCD) for children from 7 to 10 years. The agile methodology eXtreme Programming (XP) offers a useful option for the development of serious games as it establishes a continuous communication with all project stakeholders - including the end user - throughout the project, while UCD allows the user profile to be known and identified so that the game will meet the needs and match the capabilities, expectations and motivations of the child.

An efficient effort and cost estimation framework for Scrum Based Projects

2018 ◽  
Vol 7 (4.12) ◽  
pp. 52
Author(s):  
Mohit Arora ◽  
Dr. Sahil Verma ◽  
Dr. Kavita
Keyword(s):  
Cost Estimation ◽  
Process Models ◽  
Agile Development ◽  
Software Systems ◽  
Effort Estimation ◽  
Related Factors ◽  
Inappropriate Use ◽  
Business Units ◽  
Development Methodology ◽  
Soft Computing Techniques

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. 

scholarly journals Using a Low Code Development Environment to Teach the Agile Methodology

2021 ◽  
pp. 191-199
Author(s):  
Mary Lebens ◽  
Roger Finnegan
Keyword(s):  
Higher Education ◽  
Digital Transformation ◽  
Comfort Level ◽  
Agile Development ◽  
Development Environment ◽  
Business World ◽  
Development Platform ◽  
Agile Methodology ◽  
Development Methodology ◽  
Code Development

AbstractThe Agile development methodology is soaring in popularity in the business world. Companies are turning to Agile to develop products quickly and to achieve digital transformation of their organization. Because of this push, companies need employees who understand Agile. Therefore, higher education is obligated to provide an understanding of Agile to students as they enter the workplace. Providing Agile experience to students who are new to programming is difficult because they are so worried about the coding aspects of the assignment, they cannot take time to think about the methodology they are using. The coding crowds out the time needed to get an understanding of how Agile actually works. One remedy for this is to use a low or no-code development platform. With this type of platform students spend less time learning to create apps, freeing them to experience the rituals and roles of Agile. This study examines using the Agile methodology along with the Microsoft Power Apps platform to provide an Agile experience to students. Two course sections were surveyed to learn if students perceived that they acquired a better understanding of Agile and to learn their perceptions of a no-code platform experience. The students completed surveys to ascertain their comfort with the Agile methodology and whether the no-code environment increased their comfort level. The results showed students perceived the no-code platform increased their comfort with using the Agile methodology. The implication is that no-code platforms can be used broadly to help students to gain experience with Agile.

Developing the Product Your Customer Really Wants

2016 ◽  
Vol 29 (3) ◽  
pp. 1-11
Author(s):  
Sondra Ashmore ◽  
Martine Wedlake
Keyword(s):  
Agile Development ◽  
Project Design ◽  
Iterative Approach ◽  
Integrated Development ◽  
Final Project ◽  
Business Partners ◽  
Internal Customers ◽  
Development Methodology ◽  
User Centered Development ◽  
Early Phases

The art of creating software has changed dramatically over the last twenty years, particularly as organizations move from a Waterfall to an Agile development methodology. This study explores the benefits to customers of moving away from traditional Waterfall usability approaches to an integrated development model incorporating elements of Agile, user-centered development, and extended stakeholder feedback from customer councils. Thirty-four customers, seven business partners, and four internal customers participated in a multi-year project where participants were given the option to share product requirements during the early phases of the project, actively engage in monthly project design feedback sessions, or both. Results show that active participation by the customer yields more of their requirements into the final project, especially the high priority requirements. The results suggest that an iterative approach, that is both self-directing and self-correcting, can help teams develop products that are beneficial for both the product and customer.

An Evolutive Component-Based Method for Agile Development of Service Oriented Architectures

2017 ◽  
Vol 9 (3) ◽  
pp. 37-57 ◽  
Author(s):  
Hamza Chehili ◽  
Lionel Seinturier ◽  
Mahmoud Boufaida
Keyword(s):  
Development Process ◽  
Business Processes ◽  
Agile Development ◽  
Service Oriented Architectures ◽  
Development Method ◽  
Service Oriented ◽  
Agile Software Engineering ◽  
Agile Software ◽  
Incremental Process

The adoption of the agile methods' principles has emerged as an effective way to develop service oriented architectures as it paves the way for a better reply to the changing needs of the environment and even the customer. However, these changes may also require the evolution of the development process itself. This paper presents an agile and service-oriented software development method that combines concepts from the Service-Oriented Computing (SOC) domain and the agile software engineering one. This method provides an iterative and incremental process to deliverer business processes, implemented as an assembly of components. This leads to a faster response to the change of needs by reconfiguring the assembly of components. The method is based on a framework that implements its phases as an assembly of components to allow a dynamic reconfiguration of it in case of a development process evolution. Finally, a case study is presented to illustrate the use of the presented method.

Sign in / Sign up

Export Citation Format

Share Document