• Nuclear Engineering and Technology
• /
• v.51 no.2
• /
• pp.463-478
• /
• 2019

The most important non-functional requirements for dependability of any Embedded Real-Time Safety Systems are safety, availability and reliability requirements. System architecture plays the primary role in achieving these requirements. Compliance with these non-functional requirements should be ensured early in the development cycle with appropriate considerations during architectural design. In this paper, we present an application of system architecture modeling for quantitative assessment of system dependability. We use probabilistic model checker (PRISM), for dependability analysis of the DTMC model derived from system architecture model. In general, the model checking techniques do not scale well for analyzing large systems, because of prohibitively large state space. It limits the use of model checking techniques in analyzing the systems of practical interest. We propose abstraction based compositional analysis methodology to circumvent this limitation. The effectiveness of the proposed methodology has been demonstrated using the case study involving the dependability analysis of safety system of a large Pressurized Water Reactor (PWR).

• The Korean Journal of Archival Studies
• /
• no.18
• /
• pp.139-178
• /
• 2008

The functional requirements standards for electronic records management systems which have been published recently describe the specifications very precisely including not only core functions of records management but also the function of system management and optional modules. The fact that these functional requirements standards seem to be similar to each other in terms of the content of functions described in the standards is linked to the global standardization trends in the practical area of electronic records. In addition, these functional requirements standards which have been built upon with collaboration of archivists from many national archives, IT specialists, consultants and records management applications vendors result in not only obtaining high quality but also establishing the condition that the standards could be the certificate criteria easily. Though there might be a lot of different ways and approaches to benchmark the functional requirements standards developed from advanced electronic records management practice, this paper is showing the possibility and meaningful business cases of gaining useful practical ideas learned from imaging electronic records management practices related to the functional requirements standards. The business cases are explored central functions of records management and the intellectual control of the records such as classification scheme or disposal schedules. The first example is related to the classification scheme. Should the records classification be fixed at same number of level? Should a record item be filed only at the last node of classification scheme? The second example addresses a precise disposition schedule which is able to impose the event-driven chronological retention period to records and which could be operated using a inheritance concept between the parent nodes and child nodes in classification scheme. The third example shows the usage of the function which holds or freeze and release the records required to keep as evidence to comply with compliance like e-Discovery or the risk management of organizations under the premise that the records management should be the basis for the legal compliance. The last case shows some cases for bulk batch operation required if the records manager can use the ERMS as their useful tool. It is needed that the records managers are able to understand and interpret the specifications of functional requirements standards for ERMS in the practical view point, and to review the standards and extract required specifications for upgrading their own ERMS. The National Archives of Korea should provide various stakeholders with a sound basis for them to implement effective and efficient electronic records management practices through expanding the usage scope of the functional requirements standard for ERMS and making the common understanding about its implications.

• The Korean Journal of Archival Studies
• /
• no.37
• /
• pp.239-271
• /
• 2013

Records Management System(RMS) is a system for managing electronic records in records centers. However, RMS cannot content itself with the purpose of introduction and user demands. This is caused by lack of understanding the user's RMS and a review of the lack of detailed features. Therefore, the aim of this study reviews and evaluates a detailed accession function of RMS. Firstly, the study reviewed a detailed function of accession in RMS. Analysing the business processes that each function carried out, it defined functional requirements and investigated functional compliance as the check list which produced by the functional requirements definition. Finally, it surveyed and interviewed public records managers and analyzed the present situation of functional implementation of records accession function. Afterwards, improvement plans and implications were proposed through comparison of global-standard.

• The Journal of Society for e-Business Studies
• /
• v.2 no.2
• /
• pp.89-113
• /
• 1997

Modeling methodology has been widely used for analysis and design of a information system. Specially, under the CALS environments, modeling approach is more important because the enterprise functions are inter-related and information sharing speeds up the business. In this paper, we suggest functional requirements about modeling methodology for CALS by surveying the IDEF0 and ARIS. The former is FIPS 183 and the latter is basic methodology of SAP/R3 which is world-wide ERP system. The proposed functional requirements include all semantics of IDEF0 and adds some features. The first is adding modeling components which are semantic representations. In addition to ICOMs, we add the time and cost component which is required to execute the function. The second is tracing mechanism. When we need some information, we drive the functions related with the information by reverse tracing of the function which produces the information as a output and input. Through the tracing, we find out the bottleneck process or high cost process. This approach guarantees the integrity of data by designating the data ownership. Finally, we suggest the final decomposition level. We call the final decomposed function into unit function which has only one output data. We can combine and reconstruct some of functions such as 'lego block' combination.

• Proceedings of the KSR Conference
• /
• 2007.05a
• /
• pp.1382-1387
• /
• 2007

ERTMS/ETCS is a signalling and control system designed for interoperability between railway networks. In this paper, SysML was used for modeling of the ERTMS/ETCS trackside system. We used use case diagrams and sequence diagrams for requirements analysis and functional analysis. By doing this, we could show that main functions of the ERTMS/ETCS trackside can be described and verified based on scenarios.

• Nonlinear Functional Analysis and Applications
• /
• v.28 no.4
• /
• pp.1069-1086
• /
• 2023

The natural transform is represented by two (p, q)-analogues, and their comparative characteristics are established. To resolve some (p, q)-difference and functional equations, applications are carried out.

• Journal of the Korean Society for Railway
• /
• v.17 no.1
• /
• pp.35-42
• /
• 2014

This paper analyzes the hazard related to train control, the functional requirements for atrain control system(TCS) and the automatic train protection(ATP) functional allocation that ensures the interoperability of a radio communications-based TCS. In addition, the interoperability can be obtained using wireless communications technology standards and standardized functional allocations of TCS performed on the wayside and onboard. Using this information, an integrated operating system for a rail network can be constructed. The functional allocations of TCS that support interoperability, require hazard analysis of TCS and definition of the system requirements. The hazard factors for a TCS are confirmed through setting the train safety space control and train speed limit excess. Furthermore, this paper determines the impact of the hazard factors on the TCS and, defines the functional requirements for the TCS subsystems and the ATP wayside and onboard functional allocations.

• KLA journal
• /
• v.49 no.7
• /
• pp.22-30
• /
• 2008

• International Journal of Knowledge Content Development & Technology
• /
• v.8 no.1
• /
• pp.25-36
• /
• 2018

Research data must be testable. Science is all about verification and testing. To make data testable, tools used to produce, collect, and examine data during the research must be available. Quite often, however, these data become inaccessible once the work is over and the results being published. Hence, information and the related context must be provided on how research data are preserved and how they can be reproduced. Open Science is the international movement for making scientific research data properly accessible for research community. One of its major goals is building data repositories to foster wide dissemination of open data. The objectives of this research are to examine the features of research data, common repository platforms, and community requests for the purpose of designing functional requirements for research data repositories. To analyze the features of the research data, we use data curation profiles available from the Data Curation Center of the Purdue University, USA. For common repository platforms we examine Fedora Commons, iRODS, DataONE, Dataverse, Open Science Data Cloud (OSDC), and Figshare. We also analyze the requests from research community. To design a technical solution that would meet public needs for data accessibility and sharing, we take the requirements of RDA Repository Interest Group and the requests for the DataNest Community Platform developed by the Korea Institute of Science and Technology Information (KISTI). As a result, we particularize 75 requirement items grouped into 13 categories (metadata; identifiers; authentication and permission management; data access, policy support; publication; submission/ingest/management, data configuration, location; integration, preservation and sustainability, user interface; data and product quality). We hope that functional requirements set down in this study will be of help to organizations that consider deploying or designing data repositories.

• Journal of Digital Convergence
• /
• v.17 no.8
• /
• pp.221-228
• /
• 2019

The importance of security for virtualization products has been increased with the activation policy of cloud computing and it is necessary to analyze cyber security threats and develop security requirements for virtualization products to provide with more secure cloud environments. This paper is a preliminary study with the purpose of developing security functional requirements through analyzing security features and cyber security threats as well as comparison of foreign countries' cases for virtualization products. To do this, the paper compares evaluation schemes for virtualization products in US and UK foreign countries, and analyzes the cyber security threats, security objectives and security requirements in both countries. Furthermore, it proposes the essential checking items and processes for developing security functional requirements about security features of virtualization products to contribute to its more secure development and the establishment of related security evaluation standards.