• Journal of the Korea Computer Industry Society
• /
• v.4 no.4
• /
• pp.517-522
• /
• 2003

As the Software development condition is changed into enlargement and complex, requirements generated in each step of Software development life cycle has important effects on the technique and management area. In this thesis, We propose so engineering approach for effective and systematic process and activities including Requirements acquisition and management based on activities proposed with Requirements Engineering and CMM that my special emphasis is putted on Software qualify improvement through the reduction of software development cost and danger.

• Journal of Platform Technology
• /
• v.11 no.5
• /
• pp.3-15
• /
• 2023

Requirements traceability link information is the basis for determining whether requirement change requested throughout the software development life cycle should be reflected in the system. Setting up complete requirements traceability links requires considerable effort. However, the commensurate benefits can be obtained in later development or further maintenance phases. For this reason, setting up and managing requirements traceability links in the software development phase are tasks that cause considerable resistance to developers. This study proposes a method for generating requirement traceability links in business applications. The key feature of the proposed method is that the traceability link from the requirements element, which is the basis of the corresponding element to the analysis element, is automatically established at the same time the elements of the analysis model are identified. This can be a way to reduce developer effort while increasing the efficiency of the traceability model. A case study on a Course Registration System demonstrates the feasibility of applying the proposed requirements traceability management method to actual software development.

• Journal of KIISE:Software and Applications
• /
• v.30 no.5_6
• /
• pp.503-514
• /
• 2003

In conventional development methodologies, requirements are considered to be not changing after analysis phase, and requirements specifications are used for the next step system design purpose. But in the real world, requirements can be changed and modified throughout the development life cycle according to end-user's more understanding about the target system, new IT technologies, changes of customer environment and market situation, and so on. So there needs a requirements change management process that can extend requirements management over the entire development life cycle and can support managing changes to the requirements after design phase. In this paper, a requirements change management process that can be integrated into conventional development methodologies is proposed to support the extension of requirements life cycle and managing changes to the requirements after design phase. This process was evaluated through an verification test with a widely used development methodology‘MaRMI’.

• Journal of the Korea Institute of Information Security & Cryptology
• /
• v.32 no.6
• /
• pp.1183-1192
• /
• 2022

Information and Information processing systems must maintain a certain level of security during the total life cycle of Information. To maintain a certain level of security, security management processes are applied to software, automobile development, and the U.S. federal government information system over a life cycle, but theme of no similar security management process in Korea. This paper proposes a Korean-style security risk management framework to maintain a certain level of security in the total life cycle of information and information processing system in the defense sector. By applied to the defense field, we intend to present the direction of defense security work in the future and induce an shift in security paradigm.

• KIPS Transactions on Software and Data Engineering
• /
• v.8 no.12
• /
• pp.465-472
• /
• 2019

Today, in many area the rise of software necessity there has been increasing the issue of the impotance of Good Software. Our reality in software industrial world has been happening to frequently change requirements at any stage of software life cycle. Furthermore this frequent changing will be increasing the design complexity, which will result in being the lower quality of software against our purpose the original design goals. To solve this problem, we suggest how to improve software design through refactoring based on reverse engineering. This is our way of diverse approaches to visually identify bad smell patterns in source code. We expect to improve software quality through refactoring on even frequently changing requirements.

• Korean Journal of Computational Design and Engineering
• /
• v.16 no.2
• /
• pp.92-103
• /
• 2011

The construction industry consists of various and massive architectural information as an architectural process includes a variety of design stages with cooperation of many disciplines. A Building Information Modeling (BIM) serves as a shared knowledge resource for information about a facility forming a reliable basis for decisions during its life-cycle from inception onward. building SMART has developed Industry Foundation Classes (IFC) standard for interoperability of BIM based information. Several software tools are already IFC-compliant. However, there are a lot of problems related to efficient interoperability of software owing to the lack of guide regarding the software usage and insufficiency IFC interfaces of software. The purpose of this study is to suggest efficient IFC support interface development methodologies of existing IFC certified software. The scope of this study is interoperability test for open BIM based quality assurance. To achieve this purpose, the authors have classified subject of open BIM based quality assurance and investigated IFC certification process and certified software. In addition, the authors have exported and imported via IFC files using different IFC interfaces in the software for interoperability of architectural objects and their properties. Finally, the authors have suggested IFC support interface development methodologies and hereafter direction for efficient interoperability of IFC certified software based on open BIM.

• Journal of Information Processing Systems
• /
• v.17 no.5
• /
• pp.972-988
• /
• 2021

At present, DevOps environments are getting popular in software organizations due to better collaboration and software productivity over traditional software process models. Software artefacts in DevOps environments are vulnerable to frequent changes at any phase of the software development life cycle that create a continuous integration continuous delivery pipeline. Therefore, software artefact traceability management is challenging in DevOps environments due to the continual artefact changes; often it makes the artefacts to be inconsistent. The existing software traceability related research shows limitations such as being limited to few types of artefacts, lack of automation and inability to cope with continuous integrations. This paper attempts to overcome those challenges by providing traceability support for heterogeneous artefacts in DevOps environments using a prototype named SAT-Analyser. The novel contribution of this work is the proposed traceability process model consists of artefact change detection, change impact analysis, and change propagation. Moreover, this tool provides multi-user accessibility and is integrated with a prominent DevOps tool stack to enable collaborations. The case study analysis has shown high accuracy in SAT-Analyser generated results and have obtained positive feedback from industry DevOps practitioners for its efficacy.

• International Journal of Computer Science & Network Security
• /
• v.23 no.8
• /
• pp.199-203
• /
• 2023

Influential trend that widely reflected the software engineering industry is service oriented architecture. Vendors are migrating towards cloud environment to benefit their organization. Companies usually offer products and services with a goal to solve problems at customer end. Because customers are more interested in solution of their problem rather than focusing on products or services. In software industry the approach in which customers' problems are solved by providing services is known as software as a service. However, software development life cycle encounters enormous changes when migrating software from product model to service model. Enough research has been done on the overall development process but a limited work has been done on the factors that influence requirements elicitation process. This paper focuses on those changes that influence requirement elicitation process and proposes a systematic methodology for transformation of software from product to service model in a successful manner. The paper then elaborates the benefits that inherently come along with elicitation process in cloud environment. The paper also describes the problems during transformation. The paper concludes that requirement engineering process turn out to be more profitable after transformation of traditional software from product to service model.

• The Transactions of the Korea Information Processing Society
• /
• v.3 no.4
• /
• pp.846-854
• /
• 1996

In this paper, we propose a solution to the software maintenance problem that is a primary factor of software crisis. We surveyed and analyzed the current software maintenance problems through questionnaires and interviews. As a result, we defined the software maintenance management life cycle and established a fundamental strategies to solve the software maintenance problems efficiently. We also designed a software maintenance management support systems to construct an automated software maintenance management tool. Furthermore, tp improve the formalization and reliability of the software maintenance management procedure, we defined acost predictive model using a fixed-single parameter based on comprehensive program size for the source code and delivered effort(person/month). We elaborated the model by considering an experience level of maintainer, a skill- level defined by the manager, and a reliability level required by the model of maintenance management.

• IE interfaces
• /
• v.17 no.spc
• /
• pp.122-130
• /
• 2004

Since the cost of software maintenance occupies about 50~75% in a general successful organization, the software maintenance plays an important role in software life cycle. In particular, if the managed system needs to be operated in a long term or the system is very large and complex, then the maintenance is especially more important. Software maintenance is defined as software modification activities after customer delivery, such as improvement of performance or functionality, error correction, adaptation to environmental changes, etc. In this paper, software cost estimation models are proposed, that is based on productivity of manpower in maintenance projects. In order to do this, the activities of maintenance are classified into function change, non-function change, user support and application operation. The proposed models are constructed and verified based on the real size and cost information of projects in the real world. The approach in this paper is to discriminate the heterogeneous activities in maintenance projects, and then to calculate the respective cost of each discriminated activity. By using the proposed models, the total cost of maintenance project is summed from the costs of four activities. In addition the number of conflicts between owner and order receiver about the amount of cost will be reduced and the reasonable cost estimation system will be established.