A CRITICAL ANALYSIS AND COMPARISON OF AGILE WITH TRADITIONAL SOFTWARE DEVELOPMENT PROCESS

Author(s):  
Priyanka Kataria ◽  
Shweta Shrivas ◽  
Ishita Shukla ◽  
A. Hemlata

During the past years, new software development approaches were introduced to suit within the new trend of the software development corporations. Most Software Corporation’s today aim to provide valuable software in short period of time with marginal prices and among unstable, ever-changing environments. Agile methodology focuses on the challenges of unpredictability of the real world by relying on individuals and their creative thinking instead of method. In this paper we tend to explore about the current agile methods, strengths and weaknesses of agile strategies and numerous problems with their relevancy. We have conjointly enclosed comparison between traditional software development process and agile software development process. This paper also includes brief discussion about the benefits and problems associated with these methodologies by performing case study of two corporations.

Author(s):  
Yerramalli Subramaniam ◽  
Avik Pal ◽  
Arindam Dey

Given that Agile software development is preferred methodology for products and services in life science industry, in this chapter we will describe how to adopt Agile software development process and still be compliant. We will focus on few Agile methodologies and provide details on what design controls we can adopt in order for the product and process to be compliant. We will also focus on some of the tools that can be used to help put such design and process control in place where we can have complete transparency and traceability.


2017 ◽  
Vol 10 (13) ◽  
pp. 143 ◽  
Author(s):  
Jayasudha R ◽  
Viswanathan V ◽  
Shanthi P

The concept of reuse is applied in one of the agile development methodologies called the scrum. Sprint is a single functionality and the result at the end of the sprint functionality is derived as the shippable or bugs. This paper makes an attempt to use the concept of reuse in the agile software development to meet the dynamic change of customer requirements in banks. A banking project is created using both waterfall model and scrum model, and the knowledge gained is stored in the ontology-based repository for the first time. Again, the same project is created for different vendors using the ontology-based repository. The result shows that maximum sprint is reused and all the knowledge gained is stored in the form of ontology. This ontology helps identify the shippable component of each sprint which is a small executable functionality. This leads to less cost and time to deliver the product. The main aim is to increase the availability of the reusable artifacts, which lead to increase the reusability of the developer. The experimental results show improvements in the performance of retrieving the components for the software development.  


Author(s):  
Andreza Vieira ◽  
Franklin Ramalho

The Model-Driven Development (MDD) approach shifts the focus on code to models in the software development process. In MDD, model transformations are elements that play an important role. MDD-based projects evolve along their lifecycle in a way that changes in their transformations are frequent. Before applying changes it is important to measure their impacts within the transformation. However, currently no technique helps practitioners in this direction. We propose an approach to measure the change impact in ATL model transformations. Based on static analysis, it detects the elements impacted by a change and calculates the change impact value through three metrics we defined. By using our approach, practitioners can (i) save effort and development time since the elements impacted with the change are automatically detected and (ii) better schedule and prioritize changes according to the impact value. To empirically evaluate our approach we conducted a case study.


2020 ◽  
Vol 14 ◽  
pp. 8-13
Author(s):  
Tomasz Bławucki ◽  
Siarhei Ramanovich ◽  
Maria Skublewska-Paszkowska

The article presents a comparison in terms of hardware requirements of applications that supports the agile software development processes. For research purposes, popular mobile and internet applications supporting agile software development were chosen. In order to determine the significance of individual technical requirements for end-users, a series of research experiments, based on scenarios of typical and boundary use was conducted. In addition to research, the application supporting agile software development process was implemented. The results of research were recorded by specialized monitoring and profiling tools. The results of performed work are presented in tabular form.


2019 ◽  
Author(s):  
Alexandra Terrill ◽  
Justin J. MacKenzie ◽  
Maija Reblin ◽  
Jackie Tyne Einers ◽  
Jesse Ferraro ◽  
...  

BACKGROUND Individuals with disability and their partners, who often provide care, are both at risk for depression and lower quality of life. Mobile health (mHealth) interventions are promising to address barriers for mental health care. Rehabilitation researchers and software development researchers must collaborate effectively with each other, and with clinical and patient stakeholders to ensure successful mHealth development. OBJECTIVE To aid researchers interested in mHealth software development by describing the collaborative process between a team of rehabilitation researchers, software development researchers, and stakeholders. Thus, we provide a framework (conceptual model) for other teams to replicate in order to build a web-based mHealth app for individuals with physical disability. METHODS Rehabilitation researchers, software development researchers, and stakeholders (people with physical disabilities and clinicians) are involved in an iterative software development process. The overall process to develop an mHealth intervention includes initial development meetings and a co-design method called “designbox”, in which the needs and key elements of the app are discussed. Based on the objectives outlined, a prototype is developed and goes through scoping iterations with feedback from stakeholders and end-users. The prototype is then tested by users to identify technical errors and gather feedback on usability and accessibility. RESULTS Illustrating the overall development process, we present a case study based on our experience developing an app (SupportGroove) for couples coping with spinal cord injury. Examples of how we addressed specific challenges are also included. For example, feedback from stakeholders resulted in development of app features for individuals with limited functional ability. Initial designs lacked accessibility design principles made visible by end-users. Solutions included large text, single-click, and minimal scrolling to facilitate menu navigation for individuals using eye-gaze technology. Prototype testing allowed further refinement and demonstrated high usability and engagement with activities in the app. Qualitative feedback indicated high levels of satisfaction, accessibility, and confidence in potential utility. We also present key lessons learned about working in a collaborative interdisciplinary team. CONCLUSIONS mHealth promises to help overcome barriers to mental health intervention access. However, the development of these interventions can be challenging because of the disparate and often siloed expertise required. By describing the mHealth software development process and illustrating it with a successful case study of rehabilitation researchers, software development researchers, and stakeholders collaborating effectively, our goal is to help other teams avoid challenges we faced and benefit from our lessons learned. Ultimately, good interdisciplinary collaboration will benefit individuals with disabilities and their families. CLINICALTRIAL n/a


Sign in / Sign up

Export Citation Format

Share Document