• International Journal of Computer Science & Network Security
• /
• 제22권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
• /
• 제21권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.

• 한국정보과학회논문지:소프트웨어및응용
• /
• 제31권8호
• /
• pp.1010-1026
• /
• 2004

소프트웨어 프로덕트 라인 공학의 목표는 일련의 유사한 소프트웨어 시스템의 공통성과 구별되는 특성을 이해하고 제어함으로써 시스템의 체계적인 개발을 지원하는 것이다［1］. 이것은 소프트웨어 개발 시 나오는 산출물들을 핵심 자산으로 만들어 놓고 이를 체계적으로 재사용 할 수 있도록 지원하기 위한 프레임웍 역할을 한다. 현재 많은 기술들이 프로덕트 라인 공학 관련하여 연구되고 있지만, 그 초점이 소프트웨어 아키텍쳐나 상세 설계 또는 코드에 맞추어져 있다［2］. 소프트웨어 프로덕트 라인 공학에서는 컴포넌트의 공급, 조립뿐만 아니라 조립공정까지 특정 요구나 변화에 신속히 적응할 수 있도록 관리하는 것이 중요한데, 이는 요구사항 분석 단계에서부터 이루어져야 한다. 소프트웨어 프로덕트 라인 공학에서 요구사항은 전통적인 시스템 개발에서와 마찬가지로 모든 개발의 기초가 되는 부분이며, 다른 핵심 자산의 공통성과 가변성의 성질을 결정짓게 만들 수 있는 기준이 된다. 그러나 요구사항들을 다 반영하기도 전에 변경이 발생하는 수많은 경험을 해 온 것처럼, 올바른 요구사항을 획득하고 이를 분석, 관리한다는 것은 결코 쉬운 일이 아니다. 특히, 여러 개의 시스템을 개발할 때 사용할 요구사항은 공통성과 가변성의 속성을 가지게 된다. 그러므로 계획할 수 있는 변화에는 충분히 안정적이면서, 반면에 예측하지 못하는 변화에 잘 적응하고 개조될 수 있도록 유연성을 지닌 핵심 요구사항을 개발, 관리하기 위한 체계적인 방법이 필요하다. 본 논문에서는 소프트웨어 프로덕트 라인에서 핵심 자산의 하나인 도메인 요구사항을 관리하는 방법에 대하여 제안한다. 이를 통해 도메인 요구사항에 대한 재사용성을 중대시키고 시스템의 목표를 정확히 세우는 데 투자되는 많은 시간과 노력을 감소시켜 준다. 이는 결과적으로 소프트웨어 개발 시간과 비용을 줄이고, 생산성을 향상시키는 등의 장점을 가져다준다.

• 한국인터넷방송통신학회논문지
• /
• 제21권2호
• /
• pp.79-88
• /
• 2021

과학용 소프트웨어는 전문가 수준의 깊이있는 도메인 지식 요구 등과 같이 고유한 특성들로 인하여 전통적인 응용소프트웨어와는 다른 개발 프로세스가 요구된다. 본 연구에서 우리는 과학용 소프트웨어 개발을 위하여 RE(Reverse Engineering)과 TDD(Test-Driven Development)에 기반한 V&V 개발 프로세스를 제안하였다. 또한 실제 프로젝트에 가상 시나리오를 구성하고 적용하여 절차를 검증하고 정교화 하였다. 과학용 소프트웨어 개발을 목적으로 제안된 본 연구의 개발 프로세스는 고품질, 고 신뢰성을 제공할 수 있는 소프트웨어 개발 및 적용에 기여할 것이다. 또한 본 연구는 과학용 소프트웨어 개발 및 연구의 저변 확산의 계기가 될 것으로 기대된다.

• 한국정밀공학회지
• /
• 제22권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
• /
• 제9권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.

• 시스템엔지니어링학술지
• /
• 제5권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.

• 한국농공학회논문집
• /
• 제66권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.

• 대한안전경영과학회지
• /
• 제13권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.

• 한국기계가공학회지
• /
• 제14권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.