• Convergence Security Journal
• /
• v.2 no.2
• /
• pp.77-88
• /
• 2002

A mobile agent system is an infrastructure that supports the mobile agent paradigm. The main challenges encountered in designing this infrastructure are discussed in this paper. After introducing a generic mobile agent system, we discuss the design issues at two levels. System level issues like the provision of agent mobility and security, are mainly encountered in developing the runtime environments for agent execution. Language level issues, such as agent programming models and primitives, arise in providing support for mobile agent programming, mainly at the library level. This paper Identifies such system and language-level issues, and illustrates the different ways developers ate addressing them. We outline the specific challenges addressed by this dissertation, primarily in the area of mobile agent security.

• Proceedings of the Korean Information Science Society Conference
• /
• 2006.06c
• /
• pp.178-180
• /
• 2006

임베디드 시스템이 복잡해지고 Time-to-Market이 요구되면서 HW/SW 통합설계 방법론(codesign)이 제시되었다. 통합설계 과정 중, HW/SW 분할 과정은 시간 성능, 비용, 전력 등의 모든 요구사항을 만족시키기는 불가능하므로 특정 목적함수에 근거한 알고리즘을 이용하여 진행된다. 하지만 고정된 분할 알고리즘을 이용해서는 이해관계자들의 요구사항을 최대한 반영하기 어렵다. 본 논문에서는 이해관계자들의 의견을 최대한 반영하고, 이를 만족시키는 모델을 유도하기 위하여 WinWin negotiation model을 적용된 요구사항 절충을 고려한 HW/SW 분할 방법론을 제안하였다. WinWin 모델을 통해서 도출된 요구사항에 가장 적합한 목적함수를 가지는 분할 알고리즘을 선택하여 HW/SW 분할 과정을 진행하는 방법이다.

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

In order to do requirement-based testing of embedded system, we must have correct requirement specifications. But, natural language requirements of a client have ambiguity, inaccuracy, and inconsistency. To solve these problems, natural language requirements are modeled with modeling language such as UML and Simulink. During a modeling phase, the requirements are rearranged and retranslated in use-case. These activities are disadvantages of modeling. In this paper, we propose the technique, which is how to model a embedded system requirement into a model without rearranging and retranslating. This technique 1) represent a embedded system requirement with graphical language, and 2) model a requirement into a model. Because this technique only describes "what-to-do" of the requirement, this technique is useful to not only the low-level requirements but also the high-level requirements. We show some example systems modeled by REED, which has adopted this technique.

• 시스템엔지니어링워크숍
• /
• s.1
• /
• pp.140-144
• /
• 2003

AGT 시스템은 복잡한 대규모 시스템이며 이 시스템에 도입된 무인운전의 운영 개념은 한국 철도 기술의 환경에서는 처음 시도되는 기술이다. 게다가 신호시스템을 무선 기술을 이용하여 구현해 한다는 요구사항이 추가되어 신호시스템 개발은 더욱 도전적인 문제가 되었다. 이와 같이 실천하기 어려운 요구사항이 많은 무선열차 제어시스템 개발의 위험을 줄이기 위해 시스템공학팀은 전산지원 시스템공학 도구를 사용한 재공학의 개발공정을 수행하도록 하였다. 본 연구에서는 기존의 정적인 데이터모텔에 추가하여 시나리오 기반으로 동적거동 분석을 수행하여 기능 모델을 구축하였고 기능 모델을 토대로 한 시스템 아키텍처를 구성하였다. 특히 기능 요구사항의 취약성을 보완하기 위해 CORE의 FFBD(Functional Flow Block Diagram)기능을 활용하여 열차 운행 중 발생할 수 있는 여러 가지 시나리오를 분석함으로써 기능 모델의 완전성의 기여하였다. 이는 정적인 데이터 흐름 다이아그램(DFD:Data Flow Diagram)이 가지는 한계를 모델 기반 시스템공학 도구에서 지원하는 동적인 기능 분석을 수행하여 보완함으로써 모델의 충실도를 높였음을 의미한다. 이를 통해 기능의 오류를 개념단계에서 최소화함으로써 기술 위험이 높은 제품을 개발할 수 있다는 것을 확인하였다.

• Journal of Industrial Convergence
• /
• v.18 no.2
• /
• pp.95-100
• /
• 2020

Among the customer-oriented data used to comprehend the customer, the user review data has received much attention as it provides insights into customer opinion in a detailed and large-scale manner; many customers have come to rely upon and trust the user reviews. Many application developers are cognizant of the importance of user reviews, so they monitor and respond to these reviews. However, due to the absence of a systematic method, developers have been investing their time and money without clear correlation to the customer satisfaction. Therefore, this paper suggests a systematic method to select user reviews from the application market using the Kano Model that deals with customer satisfaction and service quality, thereby maximizing the customer satisfaction under the given time period and budget. This method is constructed in the following phases: the user review collection and requirement elicitation phase in which the developers collect user reviews from the application market and elicit requirements, the Kano Model application and selection phase in which the Kano Model is applied to the elicited requirements and selection occurs based on the quality type, and the stakeholder review and redefinition phase in which relevant personnel gather to review and redefine requirements from an internal perspective.

• Journal of the Korea Institute of Information Security & Cryptology
• /
• v.14 no.3
• /
• pp.85-100
• /
• 2004

All information system is information security system that enforced security function. To improve qualify of information security system, suity requirement analysis and specification must be Performed by consistently and typically at early requirement analysis step. In this paper, we propose a security requirements analysis and specification model and process by using Misuse Case Model that extends UML's Use Case Model. And, we propose a cost-effective security product selection algorithm that security product is sufficient of all constructed security functional requirements. It may raise quality of information security system that developed through proposed model and process.

• Journal of KIISE:Software and Applications
• /
• v.33 no.2
• /
• pp.186-200
• /
• 2006

Analysis model focuses only on functional requirements and postpones nonfunctional requirements and implementation specific issues until subsequent design activities are undertaken. Based on the analysis models, the design activities are performed by refining and clarifying the analysis models. Thus, the quality of analysis models has a vast impact on the design models. Therefore, much effort should be taken to build correct analysis model. In this paper, we propose a set of structural constraints that analysis models of typical object-oriented development methods should satisfy. Three kinds of constraints are proposed: class related constraints, relation related constraints, and usage related constraints. For each constraint, formal definition and description with OCL are provided. In addition, through a case study with two medium-sired industrial systems, we demonstrated that the proposed approach can help to identify and correct serious deficiencies in object-oriented analysis models.

• 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’.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2008.05a
• /
• pp.355-358
• /
• 2008

현 시대의 IT System은 전산실 직원의 전유물이 아니다. IT System은 Business Goal의 달성을 위한 지렛대 역할을 할 수 있어야 한다. 이를 위해 기존의 요구사항 협상모델을 프로젝트 관리 기반이 아닌 현업의 Business Goal과 연동시켜, 다양한 요구사항들 중 실제적으로 Business Part에 도움이 되는 요구사항을 우선적으로 적용시킬 수 있는 방법을 고민해봐야 할 것이다. 본 논문에서는 IBM Pain Chain을 WinWin negotiation model에 적용해 Business Goal에 직접적인 도움을 줄 수 있는 요구사항 우선순위 결정기법에 대해 연구해보고자 한다.

• KIPS Transactions on Software and Data Engineering
• /
• v.6 no.4
• /
• pp.167-176
• /
• 2017

There are increasing policies and safeguards to prevent various human resource losses with the development of automotive industry. Currently ISO26262 $1^{st}$ edition has been released in 2011 to ensure functional safety of electrical and electronic systems and the $2^{nd}$ edition will be released in the second half of 2016 as part of a trend. The E/E (Electrical & Electronics) system requirements verification is required through walk-through, 인스펙션, semi-formal verification and formal verification in ISO 26262. This paper describe the efficiency of model checking for the E/E system requirements verification by applying the product development project of ASIL (Automotive Safety Integrity Level) D for the electrical parking brake system.