• International Journal of Computer Science & Network Security
• /
• v.22 no.3
• /
• pp.229-235
• /
• 2022

The process of correcting, upgrading, and improving software products after they have been handed over to the consumer is known as software maintenance. Offshore software maintenance outsourcing (OSMO) clients benefit from cost savings, time savings, and improved quality software through OSMO. In most circumstances, the OSMO vendor makes a lot of money but not in all the cases. Especially, when the OSMO project offer is not properly assessed. An efficient outsourcing contract might yield successful outcomes for outsourced projects. But before sending a detailed proposal to bid on the OSMO project the vendor must have to assess the client's project (business offer) requirements. The purpose of this study is to find out common trends within the assessment of a OSMO project. A case study approach along with semi-structured interviews from eight companies concluded ten common practices and several roles. Among these practices, four (code structure, requirements, communication barriers and required infrastructure) were consistent amongst the responses .The findings, limitations and future work are discussed.

• International Journal of Computer Science & Network Security
• /
• v.21 no.2
• /
• pp.130-141
• /
• 2021

This paper is in the intersection of software engineering and system engineering, two intimately intertwined disciplines. A dominating theme in this paper is the integral conceptualization of systems at large, as well as an underlying concern with software systems. In the software development life cycle, challenges still exist in translating requirements into a design artifact and then into an implementation (e.g., coding), then validating the results. From our perspective, software engineering requires an integrating paradigm toward a unified modeling orientation. Many methodologies, languages, and tools exist for facilitating system development processes. This paper is a venture into project development. To focus the materials, we concentrate on Harel's novel (and classic) development environment, which integrates a scenario-based engineering object orientation and statecharts through developing a railcar system. The railcar system is used as a detailed sample of translating requirements into a design artifact and then into an implementation, then validating the result. The project is re-cased as a single integrated modeling endeavor to be contrasted with the scenario and statecharts' development. The result of this scheme is an enriched understanding through experimenting with and contrasting various development methods of software projects.

• Journal of KIISE:Software and Applications
• /
• v.31 no.8
• /
• pp.1010-1026
• /
• 2004

The goal of product line engineering is to support the systematic development of a set of similar software systems by understanding and controlling their common and distinguishing characteristics. The product line engineering is a process that develops reusable core assets and develops a set of software-intensive systems from a common set of core assets in a prescribed way. Currently, many software development technologies are accomplished in context of product line. However, much of the product line engineering research have focused on the reuse of work products relating to the software's architecture, detail design, and code. The product lines fulfill the promise of tailor-made systems built specifically for the needs of particular customers or customer groups. In particular, commonality and variability play central roles in the all product line development processes. These must be treated already during the requirement analysis phase. Requirements in product line engineering are basis of software development just like as traditional system development engineering, and basis of deciding other core assets' property - commonalities and variabilities. However, it is difficult to elicit, analyze and manage correct requirements. Therefore, it is necessary to develop systematic methods which can develop and manage requirement as core asset, which can be stable in anticipative change and can be well adapted to unpredictable change. In this paper, we suggest a method of managing requirements as core asset in product line. Through this method, the reuse of domain requirements can be enhanced. As a result, the cost and time of software development can be reduced and the productivity can be increased.

• The Journal of the Institute of Internet, Broadcasting and Communication
• /
• v.21 no.2
• /
• pp.79-88
• /
• 2021

Scientific software requires a development process different from conventional application software due to its unique characteristics, such as expert-level deep domain knowledge requirements. In this study, we proposed a V & V development process based on RE (Reverse Engineering) and TDD (Test-Driven Development) for software development for science. We also configured a virtual scenario for the actual project, applied it, checked the procedure, and refined it. The development process of this study, suggested for the purpose of developing scientific software, will contribute to the development and application of the software that can provide high quality and high reliability. And This study is expected to serve as an opportunity for the development of scientific software and the spread of research.

• Journal of the Korean Society for Precision Engineering
• /
• v.22 no.4
• /
• pp.136-143
• /
• 2005

Open architecture controller (OAC) is well known technology in factory automation. To better understand the requirements of OAC, authors have discussed the OAC related topics with a number of control experts who represents different segments of the machining industry. There is no common concept that is accepted or used, however, the common ideas for OAC is the control system that is hardware independent, interchangeable, and easily scalable. This paper presents summary of the understaning and requirements of OAC. Based on the requirements of OAC, authors developed the software based PC-CNC. The main focus of the PC-CNC was on the user customization capability and open interface between control networks in manufacturing system. This paper introduces the developed PC-CNC briefly. In addition to introduction of the PC-CNC, to fill the gap between end users and vendors of OAC, this paper presents two applications using OAC. One is a remote monitoring system. The OPC (Ole for Process Control) standard interface was used to monitor the status of open architecture CNC across network. The other is the remote production management module for machine tools using standard database interface.

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

As users of internet-based software applications increase, functional and non-functional problems for software applications are quickly exposed to user reviews. These user reviews are an important source of information for software improvement. User review mining has become an important topic of intelligent software engineering. This study proposes a user review mining method for software improvement. User review data collected by crawling on the app review page is analyzed to check user satisfaction. It analyzes the sentiment of positive and negative that users feel with a machine learning method. And it analyzes user requirement issues through topic analysis based on structural topic modeling. The user review mining process proposed in this study conducted a case study with the a non-face-to-face video conferencing app. Software improvement through user review mining contributes to the user lock-in effect and extending the life cycle of the software. The results of this study will contribute to providing insight on improvement not only for developers, but also for service operators and marketing.

• Journal of the Korean Society of Systems Engineering
• /
• v.5 no.2
• /
• pp.1-9
• /
• 2009

This paper proposes an effective method on the DFILS(Design for Integrated Logistics Support) in ammunition development applying QFD(Quality Function Deployment) method. The goal of this research is to define the Design for ILS approach at the start of the ammunition development and to yield a set of reusable requirements. Based on 000mm High-Explosive(Warship ammunition) development work, a QFD software tool, CUPID, was used to analyze and define the field force's requirements. Additionally, a set of reusable requirements are identified and defined for use during the Design for ILS development phase in the next-generation ammunition development process. These set of requirements that consider both the priority and importance of the VOC(Voice of Customer) will contribute to the early phase of the ammunition development to implement the Design for ILS specialty engineering effort.

• Journal of The Korean Society of Agricultural Engineers
• /
• v.66 no.3
• /
• pp.53-62
• /
• 2024

The purpose of this study is to examine the methodology for applying digital twin technology to pumping station, identify the factors to be determined at each stage, and present its applicability. When analyzing the requirements for developing a digital twin for pumping station, they were categorized into service requirements, IoT device requirements, and gateway requirements, with a total of 39 requirements established. In system design, it was structured according to the principles of modularity, abstraction, stepwise decomposition, and information hiding, allowing the implementation of planned items for diagnosis and operational management. There are difficulties in setting communication-related protocols and applying them in the field due to the complexity of overseeing the entire system with data. Therefore, it is necessary to clarify the purpose of the system, and there are challenges in identifying the characteristics of individual facilities, such as pumps in pumping station, and fully incorporating them into the system process. Thus, the framework of the initial design is crucial for implementing a digital twin.

• Journal of the Korea Safety Management & Science
• /
• v.13 no.4
• /
• pp.9-16
• /
• 2011

Modern systems become more complex and the demand for systems safety goes up sharply. Thus, the proper handling of the safety requirements in the systems design is getting greatly increased attention these days. Hazard analysis has been one of the active areas of research in connection with systems safety. In this paper, we study a subject on how the hazard analysis results can be incorporated in the systems design. To this end we set up a goal on how to systematically generate safety requirements that should reflect hazard analysis results and be implemented in the systems design and development. To do so, we first review the process for systems design and suggest the associated Model. Then the process and results of hazard analysis are analyzed and Modeled particularly with emphasis on the safety data. The resulting data Model incorporating both the hazard analysis and system life cycle is used in the generation of safety requirements. Based on the developed data Model, the generation of the requirements, the construction of requirements DB, and the change management later on is demonstrated through the use of a computer-aided software tool.

• Journal of the Korean Society of Manufacturing Process Engineers
• /
• v.14 no.4
• /
• pp.108-117
• /
• 2015

In this paper, as a previous step of software development, through an analysis step in the basic design process of the FPSO crane, ERD, which could help develop common understanding between its developer and the user, was introduced. From the flowchart of the design process, the overall work flow in its development was understood. Then, after the design process of the crane was divided into many entities, the attributes of each entity were defined and the relationships between the entities were established, followed by ERD creation through the use of IDEF1X notation. The results of the analysis can be readily understood even by users who lack of software knowledge, and then their change requirements can be immediately reflected in the developed system that requires modification.