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.

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

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.

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

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.

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

Project Implementation Decision Using Software Development Life Cycle Models: A Comparative Approach

2021 ◽  
Vol 28 (1) ◽  
Author(s):  
M.A. Adeagbo ◽  
J.E.T. Akinsola ◽  
A.A. Awoseyi ◽  
F. Kasali
Keyword(s):  
Life Cycle ◽  
Comparative Analysis ◽  
Software Development ◽  
Cost Estimation ◽  
Comparative Approach ◽  
Project Implementation ◽  
Development Life Cycle ◽  
Software Development Life Cycle ◽  
Waterfall Model ◽  
Spiral Model

Selection of a suitable Software Development Life Cycle (SDLC) model for project implementation is somewhat confusing as there are a lot of SDLC models with similar strengths and weaknesses. Also, the solutions proffered among the researchers so far have been the  qualitative comparative analysis of SDLC models. Hence, this paper proposes a comparative analysis of SDLC models using quantitative approach in relation to strengths and weaknesses of SDLC models. The study adapted comparative analysis and Software Development Life Cycle (SDLC) models features’ classification using ten characteristics such as project complexity, project size, project duration, project with risk, implementation/initial cost, error discovery, associated cost, risk analysis, maintenance and cost estimation. A quantitative measure that employs online survey using experts in software design and engineering, project management and system analysis was carried out for the evaluation of SDLC models. Purposeful Stratified Random Sampling (SRS) technique was used to gather the data for analysis using XLSTAT after pre-processing, taking into consideration both benefit and cost criteria. The overall performance evaluation showed that Spiral-Model is the best followed by V-Model and lastly Waterfall Model with comparative values of 38.63%, 35.76% and 25.61% respectively. As regards cost estimation, Waterfall Model is the most efficient with value of 41%, then V-Model with 31% and lastly Spiral Model with 28%. V-Model has great error recovery capability with value of 45% which is closely followed by Spiral Model with 37% and lastly Waterfall Model with 18%. The study revealed that, a model with efficient risk assurance does not guarantee efficient cost management. In the future work, more characteristics regarding SDLC models shall be considered.

Sign in / Sign up

Export Citation Format

Share Document