scholarly journals Software Development Life Cycle Models-A Comparative Study

2020 ◽  
pp. 30-37
Author(s):  
Gagan Gurung ◽  
Rahul Shah ◽  
Dhiraj Prasad Jaiswal
Keyword(s):  
Software Development ◽  
Small Firms ◽  
Development Process ◽  
Software Development Process ◽  
Advantages And Disadvantages ◽  
Step Procedure ◽  
Development Life Cycle ◽  
Software Development Life Cycle ◽  
Traditional Work

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.

scholarly journals Comparative Study of Different SDLC Models

2021 ◽  
Vol 9 (11) ◽  
pp. 73-80
Author(s):  
Aparna Gupta
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Development Process ◽  
Cost Effective ◽  
Software Development Process ◽  
Application Development ◽  
Advantages And Disadvantages ◽  
Development Life Cycle ◽  
Software Development Life Cycle ◽  
Life Cycle Models

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.

scholarly journals Tailoring effective requirement's specification for ingenuity in Software Development Life Cycle.

2021 ◽  
Vol 12 (3) ◽  
pp. 3338-3344
Author(s):  
Naveen N Kulkarni Et.al
Keyword(s):  
Best Practices ◽  
Software Development ◽  
Natural Language ◽  
Development Process ◽  
Object Oriented ◽  
Software Development Process ◽  
Software Documentation ◽  
Development Life Cycle ◽  
Software Development Life Cycle ◽  
Software Requirement Specification

Software Requirements Engineering (SRE) process define software manuscripts with sustaining Software Requirement Specification (SRS) and its activities. SRE comprises many tasks requirement analysis, elicitation, documentation, conciliation and validation. Natural language is most popular and commonly used to form the SRS document. However, natural language has its own limitations wrt quality approach for SRS. The constraints include  incomplete, incorrect, ambiguous, and inconsistency. In software engineering, most applications are object-oriented. So requirements are unlike problem domain need to be developed. So software  documentation is completed in such a way that, all authorized users like clients, analysts, managers, and developers can understand it. These are the basis for success of any planned project. Most of the work is still dependent on intensive human (domain expert) work. consequences of the project success still depend on timeliness with tending errors. The fundamental quality intended for each activity is specified during the software development process. This paper concludes critically with best practices in writing SRS. This approach helps to mitigate SRS limitation up to some extent. An initial review highlights capable results for the proposed practices

Managing Tacit Knowledge for a Software Development Process: A Case Study

2012 ◽  
Vol 11 (01) ◽  
pp. 1250001
Author(s):  
David P. Stevens ◽  
Sonya H. Y. Hsu ◽  
Zhiwei Zhu
Keyword(s):  
Software Development ◽  
Tacit Knowledge ◽  
Development Process ◽  
Explicit Knowledge ◽  
Software Development Process ◽  
Development Life Cycle ◽  
Managerial Implications ◽  
Software Development Life Cycle ◽  
Why Questions

The acquisition and management of knowledge is increasingly more important in today's economy because of the large proportion of the workforce eligible for retirement in the next 10 years. Companies have long understood that reusing explicit knowledge in the form of policies, documentation and procedures produces tremendous savings, reduces variability, decreases costs, and improves overall quality. Unfortunately, a considerable portion of corporate knowledge is tacit or known at a non-verbal level, and does not lend itself to reuse. This research examines "how" and "why" questions regarding a specific process used for managing and sharing tacit knowledge related to the software development life cycle. The issues related to acquiring, preserving and disseminating the tacit knowledge are discussed in detail, and the advantages and managerial implications of the results of the method are described, together with implications for knowledge workers and managers in other industries.

scholarly journals Integrasi Database M-Learning (Mobile Learning) Menggunakan Content Manajemen System Moodle Untuk Pengelolaan Konten Akademik

2017 ◽  
Vol 1 (2) ◽  
Author(s):  
Ade Andri Hendriadi ◽  
Deden Wahidin
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Mobile Learning ◽  
Management System ◽  
Development Process ◽  
Software Development Process ◽  
Development Tools ◽  
Development Life Cycle ◽  
Software Development Life Cycle ◽  
Android Development

Abstrak Pengembangkan aplikasi m-learning (mobile learning) yang terintegrasi dengan sebuah LMS (Learning Management System) Moodle dan untuk kemudian diimplementasikan sebagai fasilitas pendukung perkuliahan. Tahapan penelitian menggunakan metode pengembangan perangkat lunak SDLC (Software Development Life Cycle) dengan model USDP (Unified Software Development Process). Aplikasi m-learning yang dikembangkan pada penelitian ini bersifat client yang penggunaanya lebih ditujukan untuk mahasiswa (student). Aplikasi yang dikembangkan berjalan pada platform android. Penulisan kode program menggunakan bahasa pemrograman Java menggunakan IDE Eclipse. Pengembangan aplikasi juga menggunakan beberapa Development tools diantaranya Android SDK (Software Development Kit) dan ADT (Android Development Tools) sebagai alat bantu berupa emulator android. Proses integrasi antara LMS Moodle dengan aplikasi m-learning menggunakan bahasa pemrograman PHP (HyperText Preprocessor). Dari hasil implementasi yang dilakukan aplikasi m-learning dinilai baik untuk digunakan sebagai fasilitas pendukung belajar dalam perkuliahan Keywords: Mobile learning, Moodle LMS, USDP

scholarly journals The Importance of Ethical Hacking Tools and Techniques in Software Development Life Cycle

2021 ◽  
Vol 10 (3) ◽  
pp. 2042-2049
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Development Process ◽  
Software Security ◽  
Research Work ◽  
Cyber Attacks ◽  
Software Development Process ◽  
Development Life Cycle ◽  
Software Development Life Cycle ◽  
Tools And Techniques

Ethical hackers are using different tools and techniques to encounter malicious cyber-attacks generated by bad hackers. During the software development process, development teams typically bypass or ignore the security parameters of the software. Whereas, with the advent of online web-based software, security is an essential part of the software development process for implementing secure software. Security features cannot be added as additional at the end of the software deployment process, but they need to be paid attention throughout the SDLC. In that view, this paper presents a new, Ethical Hacking -Software Development Life Cycle (EH-SDLC) introducing ethical hacking processes and phases to be followed during the SDLC. Adopting these techniques in SDLC ensures that consumers find the end-product safe, secure and stable. Having a team of penetration testers as part of the SDLC process will help you avoid incurring unnecessary costs that come up after the data breach. This research work aims to discuss different operating systems and tools in order to facilitate the secure execution of the penetration tests during SDLC. Thus, it helps to improve the confidentiality, integrity, and availability of the software products.

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.

scholarly journals DevOps phases across Software Development Lifecycle

2021 ◽  
Author(s):  
Mayank Gokarna
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Implementation Strategy ◽  
Quality Of Services ◽  
Comprehensive Collection ◽  
Development Lifecycle ◽  
Development Life Cycle ◽  
Software Development Lifecycle ◽  
Software Development Life Cycle

DevOps is the combination of cultural mindset, practices, and tools that increases a team's ability to release applications and services at high velocity. The development and operations teams always have a conflict around the scope of responsibility. With these differences the quality and speed of delivery across software Development Life Cycle is negatively impacted. DevOps is about removing the barriers between two traditionally delimited teams, development and operations. With DevOps, these two teams work together to optimize both the productivity of developers and the reliability of operations. They strive to communicate frequently, increase efficiencies, and improve the quality of services they provide. They take full ownership for their services, often beyond where their stated roles or titles have traditionally been scoped. Transitioning to DevOps requires a change in culture and mindset first. It is quite difficult to persuade a whole company to change its culture at once. This paper aims to bring different phases of software development lifecycle into DevOps implementation strategy and presents a comprehensive collection of leading tools used across Software Development life Cycle to automate and integrate different stages of software delivery. This paper also highlights on DevOps practices which span across different phases of the Software Development Lifecycle and how those can be implemented with different tools available.

scholarly journals Quality of the Software Development Process

1983 ◽  
Vol 16 (18) ◽  
pp. 145-152 ◽  
Author(s):  
K. Frühauf ◽  
H. Sandmayr
Keyword(s):  
Software Development ◽  
Development Process ◽  
Software Development Process

scholarly journals Penerapan Metode Rational Unified Process (RUP) Dalam Pengembangan Sistem Informasi Medical Check Up Pada Citra Medical Centre

2020 ◽  
Vol 2 (1) ◽  
pp. 76-88
Author(s):  
Ririn Perwitasari ◽  
Royana Afawani ◽  
Sri Endang Anjarwani
Keyword(s):  
Software Development ◽  
Development Process ◽  
System Development ◽  
Medical Center ◽  
Development Method ◽  
Development Life Cycle ◽  
Project Risks ◽  
Unified Process ◽  
Software Development Life Cycle ◽  
Time Required

The Rational Unified Process (RUP) method is an iterative and incremental software development method that focuses on architecture. The RUP method will be used in the development of a medical check-up information system on a Citra medical center because this method is proactively able to resolve the project risks associated with the client's evolving requirements requiring careful change request management. Less time is required for integration as the process of integration goes on throughout the software development life cycle and the development time required is less due to using of components over and over. RUP involves The client’s in The system development process, so the result will be accordance with client  wishes. The system built is expected to make it easier for employees to manage patient data from anywhere and anytime.

Sign in / Sign up

Export Citation Format

Share Document