scholarly journals Agile Methodology for Product Development: A Conceptual Study

Author(s):  
Kajal Singh*

Agile is a software development life cycle (SDLC) methodology that is based on smarter and faster operating principles and techniques. The paper aims to review the agile processes, principles, characteristics, and frameworks for the continuous development of the product while controlling the integration, scope, schedule, cost, quality, resources, risk, procurement, and stakeholder management. Traditional product development methods are not much efficient to adjust the rapid changes of the requirements and provide quality products to the stakeholders. Using agile frameworks, the software development team, customers, and team leaders work more closely to produce high-quality products responding to the changes rapidly. This paper will also present the background analysis of the agile manifesto and will serve as a guide to indicate the characteristics and framework of Agile which places customer satisfaction at the highest priority. Additionally, it will focus on the advantages and disadvantages of the agile projects for faster and frequent delivery of the development.

Author(s):  
Joe Pitt-Francis ◽  
Miguel O Bernabeu ◽  
Jonathan Cooper ◽  
Alan Garny ◽  
Lee Momtahan ◽  
...  

Cardiac modelling is the area of physiome modelling where the available simulation software is perhaps most mature, and it therefore provides an excellent starting point for considering the software requirements for the wider physiome community. In this paper, we will begin by introducing some of the most advanced existing software packages for simulating cardiac electrical activity. We consider the software development methods used in producing codes of this type, and discuss their use of numerical algorithms, relative computational efficiency, usability, robustness and extensibility. We then go on to describe a class of software development methodologies known as test-driven agile methods and argue that such methods are more suitable for scientific software development than the traditional academic approaches. A case study is a project of our own, Cancer, Heart and Soft Tissue Environment, which is a library of computational biology software that began as an experiment in the use of agile programming methods. We present our experiences with a review of our progress thus far, focusing on the advantages and disadvantages of this new approach compared with the development methods used in some existing packages. We conclude by considering whether the likely wider needs of the cardiac modelling community are currently being met and suggest that, in order to respond effectively to changing requirements, it is essential that these codes should be more malleable. Such codes will allow for reliable extensions to include both detailed mathematical models—of the heart and other organs—and more efficient numerical techniques that are currently being developed by many research groups worldwide.


Author(s):  
Ankita Sharma ◽  
Manav Bali

Now a days most of the software companies are able to produce valuable software in a very short span of time with minimum costs and with adjustable environments. For this purpose Agile Methodologies were thus introduced to meet all the requirements of a software development company. In this paper we will discuss the agile technique and SCRUM there advantages and disadvantages. Also we discuss about the dissimilarities and similarities between the new requirements of the software development companies.


2017 ◽  
Vol 16 (7) ◽  
pp. 7047-7064 ◽  
Author(s):  
Ola M.Surakhi ◽  
Amjad Hudaib ◽  
Mohammad AlShraideh ◽  
Mohammad Khanafseh

Software provide services that may come with some vulnerabilities or risks. Attackers perform actions that break security of system through threats and cause a failure. To avoid security vulnerability, there are many security-specific concepts that should be determined as requirements during software development life cycle in order to deliver a strong and secure software. This paper first, survey a number of existing processes, life cycle and methodologies needed for developing secure software based on the related published works. It starts by presenting the most relevant Secure Software Development Lifecycles, a comparison between the main security features for each process is proposed. The results of the comparison will give the software developer with a guideline which will help on selecting the best secure process. Second, the paper list a set of the most widely used specification languages with the advantages and disadvantages for each.


Author(s):  
Samir Abou El-Seoud

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


2018 ◽  
Vol 17 (3) ◽  
pp. 15-25
Author(s):  
Umasankar Saketharaman ◽  
Victor Anandkumar

This study characterises the results of published scientific research in the field of Global Software Product Development (GSD). Based on the analysis of about 22 scholarly articles published between 2001 and 2014, it is observed that in spite of issues and challenges faced in its implementation, GSD is a business necessity. To ensure more successful realisation of the benefits of GSD, co-locating some of the key-roles at global locations along with software development could be exercised. This could have a positive impact on the software product life cycle. This relationship needs to be validated by further research backed with empirical data.      


Author(s):  
Aparna Gupta

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.


Author(s):  
Gagan Gurung ◽  
Rahul Shah ◽  
Dhiraj Prasad Jaiswal

Software Development is one of the most powerful, vital, and the need for an hour in today's generation. Every organization, industries, small firms, institutes, etc. require the software for the functionality of their system and reducing the manual work or the traditional work, which used to be insecure and had more errors. SDLC is all about the minimization of the risk and failure and maximization of the quality of the product. To make the development works in a step by step procedure and precisely SDLC came into existence. The SDLC defines the framework that includes different activities and tasks to be carried out during the software development process. There are many types of SDLC models, which have their advantages and disadvantages and will work as per their needs.


Author(s):  
Andriy Lishchytovych ◽  
Volodymyr Pavlenko

The present article describes setup, configuration and usage of the key performance indicators (KPIs) of members of project teams involved into the software development life cycle. Key performance indicators are described for the full software development life cycle and imply the deep integration with both task tracking systems and project code management systems, as well as a software product quality testing system. To illustrate, we used the extremely popular products - Atlassian Jira (tracking development tasks and bugs tracking system) and git (code management system). The calculation of key performance indicators is given for a team of three developers, two testing engineers responsible for product quality, one designer, one system administrator, one product manager (responsible for setting business requirements) and one project manager. For the key members of the team, it is suggested to use one integral key performance indicator per the role / team member, which reflects the quality of the fulfillment of the corresponding role of the tasks. The model of performance indicators is inverse positive - the initial value of each of the indicators is zero and increases in the case of certain deviations from the standard performance of official duties inherent in a particular role. The calculation of the proposed key performance indicators can be fully automated (in particular, using Atlassian Jira and Atlassian Bitbucket (git) or any other systems, like Redmine, GitLab or TestLink), which eliminates the human factor and, after the automation, does not require any additional effort to calculate. Using such a tool as the key performance indicators allows project managers to completely eliminate bias, reduce the emotional component and provide objective data for the project manager. The described key performance indicators can be used to reduce the time required to resolve conflicts in the team, increase productivity and improve the quality of the software product.


Sign in / Sign up

Export Citation Format

Share Document