Conceptualizing open agile software development life cycle (OASDLC) model

2015 ◽  
Vol 32 (3) ◽  
pp. 214-235 ◽  
Author(s):  
Subhas C. Misra ◽  
Virender Singh
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Conceptual Model ◽  
Best Practice ◽  
Agile Software Development ◽  
Software Project ◽  
Content Type ◽  
Development Life Cycle ◽  
Software Development Life Cycle ◽  
Agile Software

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).

AMPLA

2021 ◽  
pp. 52-78
Author(s):  
Nuno António Santos ◽  
Nuno Ferreira ◽  
Ricardo J. Machado
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Early Phase ◽  
Agile Software Development ◽  
Architecture Design ◽  
Modeling Process ◽  
Incremental Design ◽  
Development Life Cycle ◽  
Software Development Life Cycle ◽  
Agile Software

Software architecture design, when performed in context of agile software development (ASD), sometimes referred to as “agile architecting,” promotes the emerging and incremental design of the architectural artifact in a sense of avoiding “big design upfront” (BDUF). This chapter presents the Agile Modeling Process for Logical Architectures (AMPLA) method, an approach for supporting the emergence of a candidate (logical) architecture, rather than BDUF, the architecture in an early phase. The architecture then emerges throughout agile iterations, where AMPLA plays a key contribution for providing traceability between models, from the business need to service specifications, ranging from design stages to deployment, hence covering a software development life cycle (SDLC).

Mobile application of BTS tower search build upon location based service (LBS)

2019 ◽  
Vol 36 (3) ◽  
pp. 1-6
Author(s):  
Akbar Siddieq ◽  
Ida Nurhaida
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Mobile Application ◽  
Design Methodology ◽  
Software System ◽  
Location Based Service ◽  
Content Type ◽  
Development Life Cycle ◽  
Analysis Design ◽  
Software Development Life Cycle

Purpose Referring the phenomenon, the researchers create an application to deal with problems faced by the technician team and the vendor in searching the location of BTS tower. Design/methodology/approach This application uses the Software Development Life Cycle (SDLC) methodology which is the process of developing or changing a software system. One of the models owned by SDLC is the waterfall technique. It provides a sequential software flow approach starting from analysis, design, coding, testing and supporting stages. Findings There are some of the technician team and the vendor find difficulties in looking for the position of the BTS tower. As a solution, a facility which enables them to access the location in searching the BTS tower is needed. Originality/value The following is a display of the design results and the implementation of writing code in applications that have been made previously.

scholarly journals Formalization of the prediction and ranking of software development life cycle models

2022 ◽  
Vol 12 (1) ◽  
pp. 534
Author(s):  
Laiali Almazaydeh ◽  
Moath Alsafasfeh ◽  
Reyad Alsalameen ◽  
Shoroq Alsharari
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Software Industry ◽  
Software Project ◽  
Critical Systems ◽  
Critical Factors ◽  
Development Life Cycle ◽  
Software Development Life Cycle ◽  
Software Practitioners ◽  
Selection And Ranking

The study of software engineering professional practices includes the use of the formal methodology in a software development. Identifying the appropriate methodology will not only reduce the failure of software but will also help to deliver the software in accordance with the predetermined budget and schedule. In literature, few works have been developed a tool for prediction of the most appropriate methodology for the specific software project. In this paper, a method for selecting an appropriate software development life cycle (SDLC) model based on a ranking manner from the highest to the lowest scoring is presented. The selection and ranking of appropriate SDLC elaborate the related SDLC’s critical factors, these factors are given different weights according to the SDLC, then these weights are used by the proposed mathematical method. The proposed approach has been extensively experimented on a dataset by software practitioners who are working in the software industry. Experimental results show that, the proposed method represents an applicable tool in predicting and ranking suitable SDLC models on various types of projects, such as: life-critical systems, commercial uses systems, and entertainment applications.

Computable metrics of personal performance in software development teams

2019 ◽  
Author(s):  
Andriy Lishchytovych ◽  
Volodymyr Pavlenko
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Product Quality ◽  
Performance Indicators ◽  
Key Performance Indicators ◽  
Project Manager ◽  
Development Life Cycle ◽  
Software Product ◽  
Software Development Life Cycle

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.

A Systematic Review and Catalog of Security Metric during the Secure Software Development Life Cycle

2020 ◽  
Vol 13 ◽  
Author(s):  
Sampada G.C ◽  
Tende Ivo Sake ◽  
Amrita
Keyword(s):  
Systematic Review ◽  
Life Cycle ◽  
Software Development ◽  
Software Security ◽  
Security Assessment ◽  
Security Metrics ◽  
Development Life Cycle ◽  
Development Processes ◽  
Secure Software Development ◽  
Software Development Life Cycle

Background: With the advancement in the field of software development, software poses threats and risks to customers’ data and privacy. Most of these threats are persistent because security is mostly considered as a feature or a non-functional requirement, not taken into account during the software development life cycle (SDLC). Introduction: In order to evaluate the security performance of a software system, it is necessary to integrate the security metrics during the SDLC. The appropriate security metrics adopted for each phase of SDLC aids in defining the security goals and objectives of the software as well as quantify the security in the software. Methods: This paper presents systematic review and catalog of security metrics that can be adopted during the distinguishable phases of SDLC, security metrics for vulnerability and risk assessment reported in the literature for secure development of software. The practices of these metrics enable software security experts to improve the security characteristics of the software being developed. The critical analysis of security metrics of each phase and their comparison are also discussed. Results: Security metrics obtained during the development processes help to improve the confidentiality, integrity, and availability of software. Hence, it is imperative to consider security during the development of the software, which can be done with the use of software security metrics. Conclusion: This paper reviews the various security metrics that are meditated in the copious phases during the progression of the SDLC in order to provide researchers and practitioners with substantial knowledge for adaptation and further security assessment.

Software Traceability – A Key to Improve Software Evolution

2016 ◽  
Vol 685 ◽  
pp. 881-885
Author(s):  
Alexey Ponomarev ◽  
Hitesh S. Nalamwar
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Software Evolution ◽  
Software Traceability ◽  
Development Life Cycle ◽  
Methods And Techniques ◽  
Software Development Life Cycle

Software traceability is an important part in software development that is getting more and more attention nowadays from organizations and researchers. The paper outlines the importance, different methods and techniques of software traceability. It also explains the need of automating traceability, problems and drawbacks of existing traceability tools, the ongoing challenges facing implementation of traceability in software development life cycle, and finally the paper discusses whether software traceability should be mandated as a key to improve software evolution

Sign in / Sign up

Export Citation Format

Share Document