• Journal of Information Processing Systems
• /
• v.6 no.1
• /
• pp.91-106
• /
• 2010

The rapid growth of communication and globalization has changed the software engineering process. Security has become a crucial component of any software system. However, software developers often lack the knowledge and skills needed to develop secure software. Clearly, the creation of secure software requires more than simply mandating the use of a secure software development lifecycle; the components produced by each stage of the lifecycle must be correctly implemented for the resulting system to achieve its intended goals. This study demonstrates that a more effective approach to the development of secure software can result from the integration of carefully selected security patterns into appropriate stages of the software development lifecycle to ensure that security designs are correctly implemented. The goal of this study is to provide developers with an Integrated Security Development Framework (ISDF) that can assist them in building more secure software.

• Korean Journal of Computational Design and Engineering
• /
• v.13 no.4
• /
• pp.314-322
• /
• 2008

This paper introduces an integration of Product Data Management (PDM) and Software Configuration Management (SCM). PDM and SCM have supported development of mechanical products and software products respectively. The importance of software components in the current products increases rapidly since the software enables the products to satisfy various customer requirements efficiently. Therefore the current product development needs enhanced product data management that can control both the hardware and software data seamlessly. This paper proposes an extended product data model for integrating SCM into PDM. The extension enables PDM document management to support the version control for software development. It also enables engineers to control both the software and hardware parts as integrated data objects during product configuration and engineering change management. The proposed model is implemented by using a commercial Product Lifecycle Management (PLM) system and a development of a network based robot system is tested by the implemented product development environment.

• Nuclear Engineering and Technology
• /
• v.38 no.3
• /
• pp.259-276
• /
• 2006

As the use of digital systems becomes more prevalent, adequate techniques for software specification and analysis have become increasingly important in nuclear power plant (NPP) safety-critical systems. Additionally, the importance of software verification and validation (V&V) based on adequate specification has received greater emphasis in view of improving software quality. For thorough V&V of safety-critical systems, V&V should be performed throughout the software lifecycle. However, systematic V&V is difficult as it involves many manual-oriented tasks. Tool support is needed in order to more conveniently perform software V&V. In response, we developed four kinds of computer aided software engineering (CASE) tools to support system specification for a formal-based analysis according to the software lifecycle. In this work, we achieved optimized integration of each tool. The toolset, NuSEE, is an integrated environment for software specification and V&V for PLC based safety-critical systems. In accordance with the software lifecycle, NuSEE consists of NuSISRT for the concept phase, NuSRS for the requirements phase, NuSDS for the design phase and NuSCM for configuration management. It is believed that after further development our integrated environment will be a unique and promising software specification and analysis toolset that will support the entire software lifecycle for the development of PLC based NPP safety-critical systems.

• Journal of the Korea Institute of Information Security & Cryptology
• /
• v.24 no.1
• /
• pp.171-182
• /
• 2014

Common Criteria is a scheme that minimize IT products's vulnerabilities in accordance with the evaluation assurance level. SSDLC(Secure Software Development Lifecycle) is a methodology that reduce the weakness that can be used to generate vulnerabilities of software development life cycle. However, Common Criteria does not consider certificated IT products's vulnerabilities after certificated it. So, it can make a problem the safety and reliability of IT products. In addition, the developer and the evaluator have the burden of duplicating evaluations of IT products that introduce into the government business due to satisfy both Common Criteria and SSDLC. Thus, we researched the relationship among the Common Criteria, the static code analysis tools, and the SSDLC. And then, we proposed how to combine SSDLC into Common Criteria.

• International journal of advanced smart convergence
• /
• v.12 no.2
• /
• pp.187-192
• /
• 2023

Currently, our society is showing many changes due to the influence of information and communication technology (ICT). At the center of these information and communication technologies are software, intelligence, and sensing technologies. The software-related industry is steadily developing due to various software development policies implemented by the government and related organizations. Software development is desirable, but on the other hand, some negative aspects are also appearing. In this study, we proposed an objective way to infer the progress of software development for reasonable resolution of cases when a dispute related to the progress of development occurred during the software development process. The proposed solution was based on the waterfall model. The outputs generated in each process of the waterfall model are contents excluded from subjectivity. Therefore, it can be used as an objective method for calculating software development progress.

• The KIPS Transactions:PartD
• /
• v.15D no.4
• /
• pp.523-530
• /
• 2008

There are many defects that cause the process improvement of lifecycle problems during software development. This paper propose the management method of risk items that removes and manages the lifecycle problems as well. For the similar projects, we can estimate defects and prepare to solve them by using domain expert knowledge and the state analysis of defect items, which can greatly improve the software process. This research provides solution of management of risk items problem and detection of defect transition and its prevention and causes that happen on software development. Also, In this paper propose to making quantity of degree and transition phase.

• International journal of advanced smart convergence
• /
• v.9 no.4
• /
• pp.167-172
• /
• 2020

In the 4th industrial revolution, there are many projects for diverse software applications of smart city environments. Most of the stakeholders focus on considering software quality for their developed software. Nobody doesn't guarantee requirement satisfaction after complete development. At this time, we can only work on user acceptance testing for requirement satisfaction on frequently changing requirements. Why keeps the requirement traceability? This traceability is to identify risks related to requirements, to assure correct software development based on customer requirements. To solve this, we are researching how to implement requirement traceability across each artifact's relationship to each activity of a whole development lifecycle.

• Journal of Internet Computing and Services
• /
• v.5 no.4
• /
• pp.95-113
• /
• 2004

RUP(Rational Unified Process) is a development process which is based on object-oriented, use case centric, architecture centric, and iterative approach. Public projects performed previously adopt waterfall lifecycle model for development of large scale software. However, recently various projects adopt an iterative approach to minimize risks of a project and to enhance quality of software. But few research result on practices of RUP as the subprocess of system development process is available. This paper presents a system development process which uses RUP as the subprocess for a subset of the system. Thus we introduce a tailored RUP for K-CIS(Korean Core Instrumentation System). Moreover, we assess the application result of K-CIS with typical waterfall lifecycle model and RUP. We believe that the results of our work are useful for tailoring a system development process with RUP, reducing risks of development, and enhancing the quality of a final product.

• Journal of information and communication convergence engineering
• /
• v.4 no.1
• /
• pp.23-27
• /
• 2006

The discipline of software performance is very broad; it influences all aspects of the software development lifecycle, including architecture, design, deployment, integration, management, evolution and servicing. Thus, the complexity of software is an important aspect of development and maintenance activities. Much research has been dedicated to defining different software measures that capture what software complexity is. In most cases, the description of complexity is given to humans in forms of numbers. These quantitative measures reflect human-seen complexity with different levels of success. Software complexity growth has been recognized to be beyond human control. In this paper, we have focused our discussion on the increasing software complexity and the issue with the problems being faced in managing this complexity. This increasing complexity in turn affects the software productivity, which is declining with increase in its complexity.

• Journal of Information Processing Systems
• /
• v.9 no.1
• /
• pp.69-88
• /
• 2013

Agile methods are highly attractive for small projects, but no agile method works well as a standalone system. Therefore, some adaption or customization is always required. In this paper, the Agile Framework for Small Projects (AFSP) was applied to four industry cases. The AFSP provides a structured way for software organizations to adopt agile practices and evaluate the results. The framework includes an extended Scrum process and agile practices, which are based on agility and critical success factors in agile software projects that are selected from Scrum, XP, FDD, DSDM and Crystal Clear. AFSP also helps software managers and developers effectively use agile engineering techniques throughout the software development lifecycle. The case study projects were evaluated on the basis of risk-based agility factors, the agility of the adopted practices, agile adoption levels, and the degree of the agile project success. The analysis of the results showed that the framework used in the aforementioned cases was effective.