• International Journal of Computer Science & Network Security
• /
• v.23 no.6
• /
• pp.107-114
• /
• 2023

Successful implementations of DevOps practices significantly improvise software efficiency, collaboration and security. Most of the organizations are adopting DevOps for faster and quality software delivery. DevOps brings development and operation teams together to overcome all kind of communication gaps responsible for software failures. It relies on different sets of alternative tools to automate the tasks of continuous integration, testing, delivery, deployment and monitoring. Although DevOps is followed for being very reliable and responsible environment for quality software delivery yet it lacks many quantifiable aspects to prove it on the top of other traditional and agile development methods. This research evaluates quantitative performance of DevOps and traditional/ agile development methods based on software metrics. This research includes three sample projects or code repositories to quantify the results and for DevOps integrated selective tool chain; current research considers our earlier proposed and implemented DevOps hybrid model of integrated automation tools. For result discussion and validation, tabular and graphical comparisons have also been included to retrieve best performer model. This comparative and evaluative research will be of much advantage to our young researchers/ students to get well versed with automotive environment of DevOps, latest emerging buzzword of development industries.

• Journal of the Korea Academia-Industrial cooperation Society
• /
• v.16 no.4
• /
• pp.2744-2748
• /
• 2015

This paper analyzes the effect on productivity by measuring Function Point per MM(man-month) in a software development project and code inspection which performed in Agile methodology, and introduce the method of applying MDA/MDD technology in the e-government standard framework project. MDA/MDD which recently raising its head is technology that increase software development productivity through automatic transformation form abstract model into lower abstract model, or from model to code. but, many Lessons obtained through the case studies, the analysis suggests a limited effect measurements. In this study, efficient development methodology and utilizing a e-government framework to measure the effectiveness of the MDD to the new measures through a case study applied to real information system development process. In addition to, managing information modeling through integrated repository presents a traceability and visibility.

• ETRI Journal
• /
• v.42 no.6
• /
• pp.965-975
• /
• 2020

This paper proposes a new framework for the development and deployment of honeypots for evolving malware threats. As new technological concepts appear and evolve, attack surfaces are exploited. Internet of things significantly increases the attack surface available to malware developers. Previously independent devices are becoming accessible through new hardware and software attack vectors, and the existing taxonomies governing the development and deployment of honeypots are inadequate for evolving malicious programs and their variants. Malware-propagation and compromise methods are highly automated and repetitious. These automated and repetitive characteristics can be exploited by using embedded reinforcement learning within a honeypot. A honeypot for automated and repetitive malware (HARM) can be adaptive so that the best responses may be learnt during its interaction with attack sequences. HARM deployments can be agile through periodic policy evaluation to optimize redeployment. The necessary enhancements for adaptive, agile honeypots require a new development and deployment framework.

• Journal of the Korea Institute of Information and Communication Engineering
• /
• v.7 no.6
• /
• pp.1351-1359
• /
• 2003

Extreme programming is the most representative methodology among agile software development methodologies which is agile in business environment which change fast. As software industry is matured, usability of software quality characteristics is emphasized gradually, but effort to obtain usability in extreme programming is insufficient. To improve usability of extreme programming, in this thesis, a software life cycle is defined by six phase as exploration, planning, iterations to release, productionizing, maintenance, and death phase. In this thesis, an extreme programming process which can improve usability is proposed by definition of 11 activities including integration testing and acceptance testing for usability testing, The proposed process is validated with four aspects. The proposed process is enhanced to support acceptance testing activity. The proposed extreme programming process is able to support CMM level 4 and quality assurance practice of CMM.

• Journal of Digital Convergence
• /
• v.11 no.8
• /
• pp.95-108
• /
• 2013

Agile development methods regards an interaction among software developers, operating softwares, and cooperation with customers as its main value. Most of the developing processes undergo a procedure called tailoring to meet the relevant project. Yet, in reality, projects run in disorder due to their overlap with other methods and management processes. As a result, the advantages of agile process cannot be fully used. So, the information system audit has an important role to detect these problems and improve the qualities of agile application projects. Also, researches should be conducted on Agile-based Iformation System Audit Model in order to enhance the effectiveness of agile projects. This paper suggests a model for an information system audit that applied agile developing methods. This model proposes audit domains and check lists for agile-based information system. In order to verify the suitability of the suggested model, more than 89.3% of the checklists were verified as suitable in all domains.

• The Journal of the Institute of Internet, Broadcasting and Communication
• /
• v.16 no.1
• /
• pp.155-162
• /
• 2016

In recent years, hoping the interaction of individuals and rather than software development process and tools, and customers want software that works first, rather than a comprehensive document, in cooperation with the customer, rather than the developer negotiate a contract, to each other stick to the plan I think even more so than the value that corresponds to the change. In view of this, software development is given the autonomy and motivation to project team rather than process-oriented and have a passion and vision and human relations oriented management approach is required. In recent years, increasing the productivity benefits of agile development processes, improved quality, efficiency and customer satisfaction as is demonstrated in the methodology selected to promote the project, attention was given to the experts. Contemporary demands with regard to the methodology chosen to meet your needs, in this paper in the organization, and to solve the problems of product-based Cross functional team proposed methodology Feature Team model, this model is an organizational Cross functional team and the team is not the outcome (product) basis, were examined for the model that points to progress the development across multiple product as a functional unit, value-plan through the driven agile technique-based model and proposed a difference. And the domain analysis, required extraction by conventional JAD (joint application development) meeting the targets for the object-oriented modeling, in modeling and organize, review, aware in advance and the UML Structure and Behavior Diagrams and proposed to proceed with the project.

• Information Systems Review
• /
• v.13 no.1
• /
• pp.61-74
• /
• 2011

Software industry still has many deep-seated problems. As a natural consequence, it may have to learn from best practices in more mature industry like manufacturing. An example is 'lean' software development which is defined as translation of 'lean manufacturing' principles to the software development domain. The principles include 'eliminate waste' and 'amplify learning.' It was much asserted that these principles are worth applying. Not much study, however, was done on how to practically implement these principles into software development practice. In this study we attempt to present a method in which project lead time and software defects are regarded as major targets of management and are visualized using Cumulative Flow Diagram. We further applied this method on actual projects. The result confirms that agile is positively effective on reducing wastes.

• The Bulletin of The Korean Astronomical Society
• /
• v.44 no.2
• /
• pp.79.3-79.3
• /
• 2019

GMACS is one of the first light instruments for the Giant Magellan Telescope (GMT). The development of GMACS control software follows Agile software development process, and the design of the software is based on the Unified Model Language (UML). In this poster, we present the architecture of the GMACS software and the development processes. As an example of the software development, we show the software of the Slit Mask Exchange Mechanism Prototype (SMEM-P) which is part of the GMACS Device Control Package (DCP).

• Proceedings of the KIEE Conference
• /
• 2001.11c
• /
• pp.311-314
• /
• 2001

The objectives of this paper include the development of an agile prototype of SFFS, the $CAFL^{VM}$(Computer Aided fabrication of Lamination for Various Material), which is suitable for the multi-item and small-quantity production and various material fabrication. This paper includes remodeling of the layer slices for the 2D cutting, supplementing information of the layer slices and developing process conditions to fabricate products of various shape. And also includes developing control hardware as well as software by enhancing BOF of the manipulator to 3 degree for the precise 2D cutting. It will generate optimal layer trajectory considering the dynamic characteristics of the laser beam. The system can be used as a competitive agile protype system in terms of various materials, fabrication speed, and accuracy by CAD modeling precise layer slicing, material development, robot path control, and optimization of the support structure.

• KIISE Transactions on Computing Practices
• /
• v.21 no.2
• /
• pp.115-120
• /
• 2015

The Testing Frontier Capability Assessment Model (TCAM) is based on ISO/IEC 9126, TMMi and TPI. Since ISO/IEC 9126, TMMi and TPI were made over 10 years ago, TCAM faces the problem that it can not assess and analyze the capability of small businesses that employ new software development methods or processes, for example Agile, TDD(Test Driven Development), App software, and Web Software. In this paper, a method to improve the problem is proposed. The paper is composed of the following sections: 1) ISO/IEC 9126, ISO/IEC 25010 and ISO/IEC/IEEE 29119 part 2 review 2) TCAM review 3) software product quality perspective comparison, and analysis between ISO/IEC 9126, ISO/IEC 25010 and TCAM 4) comparison, and analysis between ISO/IEC/IEEE 29119 part2 and TCAM and 5) proposal for the improvement of TCAM.