scholarly journals Understanding SDLC using CI/CD pipeline

2020 ◽  
Vol 9 (6) ◽  
pp. 22-25
Keyword(s):  
Development Process ◽  
Software Systems ◽  
High Quality ◽  
Continuous Integration ◽  
Software Products ◽  
Development Life Cycle ◽  
Development Processes ◽  
Recent Addition ◽  
Software Development Life Cycle ◽  
Feedback Time

Development of complex and quality software necessitates the use of a development model, so that the development process is efficient, reliable and faster. Software development life cycle (SDLC) is a well-defined and wellorganized process used to plan, develop, deploy and maintain high quality software systems. DevOps is one recent addition to SDLC that ensures that the development and operations team collaborate to accelerate the deployment and delivery of higher quality software products. This paper throws a light on how development processes are accelerated using DevOps tactics like continuous integration and deployment (CI/CD) pipelines. however, there are several factors that prevent the organizations from using these approaches. Discovering the evolution of DevOps and its continuous practices, gives a thorough understanding of the importance of the DevOps culture. Manual deployment and testing increase the feedback time of a commit operation. The paper discusses various tools available in the DevOps community that can be used to automate various stages of continuous integration and deployment pipeline, so that the feedback time is reduced.

ECSE

2014 ◽  
pp. 296-309 ◽  
Author(s):  
Sakgasit Ramingwong ◽  
Lachana Ramingwong
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Engineering Students ◽  
Major Influence ◽  
Engineering Construction ◽  
Software Products ◽  
Development Life Cycle ◽  
Critical Issues ◽  
Development Processes ◽  
Software Development Life Cycle

Software development is uniquely different especially when compared to other engineering processes. The abstractness of software products has a major influence on the entire software development life cycle, which results in a number of uniquely important challenges. This chapter describes and discusses Engineering Construction for Software Engineers (ECSE), an effective workshop that helps software engineering students to understand some of these critical issues within a short period of time. In this workshop, the students are required to develop a pseudo-software product from scratch. They could learn about unique characteristics and risks of software development life cycle as well as other distinctive phenomenon through the activities. The workshop can still be easily followed by students who are not familiar with certain software development processes such as coding or testing.

ECSE

2017 ◽  
pp. 191-205
Author(s):  
Sakgasit Ramingwong ◽  
Lachana Ramingwong
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Engineering Students ◽  
Major Influence ◽  
Engineering Construction ◽  
Software Products ◽  
Development Life Cycle ◽  
Critical Issues ◽  
Development Processes ◽  
Software Development Life Cycle

Software development is uniquely different especially when compared to other engineering processes. The abstractness of software products has a major influence on the entire software development life cycle, which results in a number of uniquely important challenges. This chapter describes and discusses Engineering Construction for Software Engineers (ECSE), an effective workshop that helps software engineering students to understand some of these critical issues within a short period of time. In this workshop, the students are required to develop a pseudo-software product from scratch. They could learn about unique characteristics and risks of software development life cycle as well as other distinctive phenomenon through the activities. The workshop can still be easily followed by students who are not familiar with certain software development processes such as coding or testing.

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 Securing Software Systems - A Survey

2020 ◽  
Author(s):  
Yong Weixiong ◽  
Kohei Dozono ◽  
Robin Lee ◽  
Alvin Kon Soon Seng ◽  
Fatima tuz Zahra
Keyword(s):  
Development Process ◽  
User Behavior ◽  
Development Stage ◽  
Security And Privacy ◽  
Software Systems ◽  
Privacy Concerns ◽  
Policy Awareness ◽  
Secure Software ◽  
Different Types ◽  
Development Processes

This paper aims to discuss the standard guidelines of the development process of secure software and will give justification on different types and ways of the software development processes. Additionally, a survey is conducted, the aim of which is to observe user behavior towards software system usage, user attitude in terms of privacy and policy awareness, security and privacy concerns. This is followed by discussion on how to secure software systems in development stage.

Open Source Software Systems

2010 ◽  
pp. 439-459
Author(s):  
R. B. Lenin ◽  
S. Ramaswamy ◽  
Liguo Yu ◽  
R. B. Govindan
Keyword(s):  
Software Development ◽  
Software Systems ◽  
The Internet ◽  
Development Projects ◽  
Work Processes ◽  
High Quality ◽  
Software Products ◽  
Geographic Boundaries ◽  
Doing Business ◽  
Development Costs

Complex software systems and the huge amounts of data they produce are becoming an integral part of our organizations. We are also becoming increasingly dependent on high quality software products in our everyday lives. These systems ‘evolve’ as we identify and correct existing defects, provide new functionalities, or increase their nonfunctional qualities - such as security, maintainability, performance, etc. Simultaneously, more software development projects are distributed over multiple locations (often globally) and are often several millions of dollars in development costs. Consequently, as the Internet continually eliminates geographic boundaries, the concept of doing business within a single country has given way to companies focusing on competing in an international marketplace. The digitalization of work and the reorganization of work processes across many organizations have resulted in routine and/or commodity components being outsourced.

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.

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

scholarly journals Rancang Bangun Aplikasi Ensiklopedia Kesehatan Berbasis Android

2018 ◽  
Vol 1 (1) ◽  
pp. 1-4
Author(s):  
Ferdiyani Haris
Keyword(s):  
Software Development ◽  
Research Method ◽  
Software Systems ◽  
Development Method ◽  
A Value ◽  
Development Life Cycle ◽  
The World ◽  
The Media ◽  
Software Development Life Cycle ◽  
Software Development Model

In the world of health, many health terms are difficult to understand. The health encyclopedia book is one of the media that presents an explanation of these terms. But in its use, the printed book is less effective and efficient because of limited space and time. So we need a media that explains health terms that are mobile so that they can be used whenever and wherever. This application was designed and implemented for the Android operating system. The system created aims to display definitions and images of health terms. The research method used is the research and development method. While for the development of software systems using the Software Development Life Cycle (SDLC) waterfall software development model. Based on the results of the response to application users conducted with a questionnaire resulting in a value of 88.9% stated very well.

Sprint Backlog Estimating and Planning Using Planning Poker Technique in Agile Scrum Framework

2018 ◽  
Vol 8 (5) ◽  
pp. 109
Author(s):  
Abdelelah Elgasim Babiker ◽  
Adil Mahmoud ◽  
Alameen Abdalrahman
Keyword(s):  
Software Development ◽  
Development Process ◽  
Relative Mass ◽  
Planning Techniques ◽  
Team Members ◽  
Development Framework ◽  
User Stories ◽  
Development Life Cycle ◽  
Relative Value ◽  
Software Development Life Cycle

Today and during the recent years, Agile Product Development Framework has been common used framework for software development particularly, Scrum is the most widely known methodology under the umbrella of agile, including many sprints to manage the development process of software. One of the most important terms in each scrum sprint is the planning and estimation phase. Many techniques to plan the sprint backlog and specify the required time and resources to perform each single backlog item. As some of planning techniques as Planning Poker, T-Shirt Sizes and Relative Mass Valuation. Planning Poker is considered an effective and powerful technique according to its algorithm of work which evolves the whole team members estimation to user stories backlog. Planning Poker gets the backlog items and input and gives the well estimated tasks and output. Planning Poker helps the product owners and scrum team to successfully estimate the work that ensures working Relative Value Points Return On Investment goals specified since the beginning of the software development life cycle phases. The importance of Planning Poker is in giving the optimum estimation with consideration to high priority backlog items and user stories.

Problems, Threats in Software Development Life Cycle and Their Analysis

2018 ◽  
pp. 61-82
Author(s):  
Deepika Rana ◽  
Manisha Malhotra
Keyword(s):  
Supply Chain ◽  
Life Cycle ◽  
Software Development ◽  
Knowledge Base ◽  
Software Systems ◽  
Development Face ◽  
Development Life Cycle ◽  
Software Development Life Cycle ◽  
Software Services ◽  
Automated Tool

Managerial and commercialization approach that operate software systems continue to look for assurance that software they acquire should have security attributes they hope for. Methods used to assess the security of software development are software design, coding, testing, and support and consideration of security as well. Researchers of software development face many issues which remain constant and very frequent as there was no development in earlier phase of software development to avoid threats and loopholes in the software. Researchers analyze existing methods and their efficiency for software development within an open-source software supply chain. These efforts yielded valuable insights for an automated tool and knowledge base that has the potential for overcoming some of the major and in practice limitations of secure development on a wider scale. As a summarized development of software services along with authenticated approach is mandatory to make its usage on wider expands.

Sign in / Sign up

Export Citation Format

Share Document