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

This paper is about that case study of the Tube Transportation System that the new transportation system offering passenger and logistic service in a metropolis having plenty of the floating population or between medium-sized cities, and solving large issues like terrible traffic jams and environmental problems etc. in this region. Also it presented that elicitation results of performance parameter and the categorization system of it applying a systematic analysis methodology. By the medium of this paper, It showed that definition, case study, performance parameters, and the categorization system of parameters of a general tube transportation system before developing requirements of a specific tube transportation system. From now on, it will come in pretty handy in systems engineering of activities to establish a concept of a new tube transportation systems and develop requirements.

• Journal of KIISE:Computing Practices and Letters
• /
• v.15 no.3
• /
• pp.167-177
• /
• 2009

This paper is about our experience of developing a context-aware exhibit guide system called MyGuide by applying Simtext development methodology. In particular, we introduce some issues to be considered in development process, the way that we solved them, and other things related to context. In requirements elicitation phase, we reduced the complexity of requirements by separating business logic requirements and context-awareness related requirements. After that, we modeled context, and designed software architecture, classes, and database in sequence during design phase. We considered system requirements and context modeling issues for context modeling because it influences class and database design.

• Electronics and Telecommunications Trends
• /
• v.33 no.5
• /
• pp.24-32
• /
• 2018

With the advent of new convergence services, the requirements of 5G mobile communication systems are being newly derived. The 5G mobile communication system has been evolving to solve requirements that cannot be satisfied with existing 4G mobile communication systems, such as a high user experience transmission rate, short transmission delay, and high connection density. The evolution of a 5G mobile communication system to meet the new requirements is expected to be dominated by the UDN environment in which a number of small cells are concentrated. The 5G wireless backhaul system, which has advantages in terms of initial installation and operation cost, is expected to be an indispensable choice for connecting many small cells and core networks. This paper therefore looks at the frequency band characteristics and requirements applicable to 5G wireless backhaul systems that can accommodate new situations, and introduces key related technologies that can satisfy the 5G wireless backhaul requirements.. In addition, we describe the research and development trends of a 5G wireless backhaul system that is currently under development.

• Journal of the Korea Society of Computer and Information
• /
• v.24 no.3
• /
• pp.65-75
• /
• 2019

Non-Functional Requirements (NFR) play a crucial role during the software development process. Currently, NFRs are considered more important than Functional Requirements and can determine the success of a software system. NFRs can be very complicated to understand due to their subjective manner and especially their conflicting nature. Self-adaptive systems (SAS) are operating in dynamically changing environment. Furthermore, the configuration of the SAS systems is dynamically changing according to the current systems context. This means that the configuration that manages the trade-off between NFRs in this context may not be suitable in another. This is because the NFRs satisfaction is based on a per-context basis. Therefore, one context configuration to satisfy one NFR may produce a conflict with another NFR. Furthermore, current approaches managing Non-Functional Requirements trade-off stops managing them during the system runtime which of concern. To solve this, we propose fragmentizing the NFRs and their alternative solutions in form of Multi-entity Bayesian network fragments. Consequently, when changes occur, our system creates a situation specific Bayesian network to measure the impact of the system's conditions and environmental changes on the NFRs satisfaction. Moreover, it dynamically decides which alternative solution is suitable for the current situation.

• KEPCO Journal on Electric Power and Energy
• /
• v.2 no.2
• /
• pp.269-272
• /
• 2016

Distribution management system or microgrid energy management system plays an important role in monitoring, operation and control of electrical distribution systems by utilizing IT infrastructure. Nowadays, the rapid increase of the distributed resources makes the conventional management system have some additional functionality for the reliable operation due to intermittent renewables and the efficient operation on the economical purpose. In this paper, the brief standard software functional requirements of microgrid energy management system are provided through survey of the recent commercial products of the major vendors, and furthermore the architectures of microgrid energy management system are provided in comparison with major suppliers' microgrid energy management system. The summary of investigation will be able to make the developers and researchers focus on the specific functionality in the real world.

• Nuclear Engineering and Technology
• /
• v.45 no.5
• /
• pp.637-652
• /
• 2013

Instrumentation and control systems in nuclear power plants have been digitalized for the purpose of maintenance and precise operation. This digitalization, however, brings out issues related to cyber security. In the most recent past, international standard organizations, regulatory institutes, and research institutes have performed a number of studies addressing these systems cyber security.. In order to provide information helpful to the system designers in their application of cyber security for the systems, this paper presents methods and considerations to define attack vectors in a target system, to review and select the requirements in the Regulatory Guide 5.71, and to integrate the results to identify applicable technical security control requirements. In this study, attack vectors are analyzed through the vulnerability analyses and penetration tests with a simplified safety system, and the elements of critical digital assets acting as attack vectors are identified. Among the security control requirements listed in Appendices B and C to Regulatory Guide 5.71, those that should be implemented into the systems are selected and classified in groups of technical security control requirements using the results of the attack vector analysis. For the attack vector elements of critical digital assets, all the technical security control requirements are evaluated to determine whether they are applicable and effective, and considerations in this evaluation are also discussed. The technical security control requirements in three important categories of access control, monitoring and logging, and encryption are derived and grouped according to the elements of attack vectors as results for the sample safety system.

• Journal of Korean Society of Industrial and Systems Engineering
• /
• v.40 no.3
• /
• pp.49-58
• /
• 2017

The DQMS (Defence Quality Management System) is a certification system that manages participating companies to improve the quality of munitions. Since Korean Defense Specification (KDS) for DQMS certification that was established by adding military requirements based on the ISO quality standard, many companies complain that they should pay too much effort into the preparation process. However, it is hard to find helpful information on the preparation process because we have been only interested in the effect of DQMS acquisition. The purpose of this paper is to provide helpful information to companies preparing for DQMS certification. We surveyed the degree of difficulty and importance of the DQMS requirements from the companies with certification experience, and performed IDA (Importance-Difficulty analysis) by dividing the companies into the main contractor and the subcontractor. The result of IDA shows that there is a different recognition to the DQMS certification between main-contracting and sub-contracting companies. Subcontractor has more difficulties than main contractor in preparing the DQMS certification. In addition, we are able to identify the difficult and important requirements in the preparation process to the DQMS certification. Both main contractor and subcontractor have difficulty to the requirements related to configuration or validation such as 'customer controls configuration', 'configuration review shall be implemented' and 'design and development validation documentation.' The requirements related to customers are important to main contractor but the subcontractor regards difficult requirements as important ones. The result of this paper would be helpful to both the company preparing for DQMS and the munitions quality assurance agency.

• Journal of KIISE:Computer Systems and Theory
• /
• v.35 no.8
• /
• pp.394-406
• /
• 2008

Even though context is the most important feature in context-aware systems, the existing requirements engineering cannot support methodology for elicitation and specification of contexts. In this paper, we propose a requirements elicitation method and a requirements specification method for context-aware systems. Our requirements elicitation method is a 6-stepped, incremental, and iterative process. At the beginning steps in the process, we identify the requirements for business logic. Afterwards, we gather the requirements for context logic, model contexts, and identify subsystems. For requirements specification, we suggest a context-aware use case diagram, a context diagram for context modeling, and a context-type-use-case-dependency diagram for the traceability of use cases on the change of context types. We also introduce a case study that we apply our approaches to a real system, and a qualitative evaluation of our approaches. Our study will help stakeholders to efficiently elicit requirements for context-aware systems and to specify them clearly.

• Journal of KIISE:Software and Applications
• /
• v.33 no.8
• /
• pp.655-667
• /
• 2006

This paper proposes a method for counting function point using goal and scenario based requirements. Function Point is a software sizing method and widely used as a basis to estimate software development cost. Requirements elicitation and analysis should be performed before function point analysis but function point analysis method doesn't deal with requirements elicitation and analysis. For that reason, Function point extraction method from existing requirements method is needed and if the requirements method has advantage for traceability and elicitation, it is suitable for managing cost. Goal and scenario method is widely used as requirements elicitation and analysis. It has also good traceability. Therefore, this paper discusses a method for extracting function point from requirements text gathered using the goal and scenario based requirements elicitation technique. The proposed method aims to establish and maintain traceability between function point and requirements text. Text based function point extraction guidance rules have been developed. The proposed methodology has been applied to Order Processing System development.

• Journal of Navigation and Port Research
• /
• v.43 no.6
• /
• pp.353-360
• /
• 2019

Technology-driven development of a new system makes it difficult for users and stakeholders to identify or intervene in the development process, resulting in systems with unnecessary functions and poor quality services. Applying the software architecture design process to the initial design of the navigation system platform of autonomous ships enables the development of a system that reflects the required functions and service quality of the stakeholders. The design, which includes all of the subsystems that make up an autonomous ship platform, is close to an enterprise architecture. Thus, we strived to design a navigation system platform suitable for the design range of the software architecture. This study analyzed the definition of functional requirements, and quality attributes by applying the software architecture design procedure. This study was conducted to identify the characteristics of the navigation system and platform needs, and the stakeholders were identified. To derive the functional requirements and constraints of the platform, a quality attributes workshop was held engaging stakeholders, and the results of the analysis of functional requirements and quality attributes were listed. Based on the results of this study, the architect can establish the evidence and technical solutions that are integral for the architecture development, and will facilitate the creation of quality attribute scenarios.