• Journal of the Korea Society of Computer and Information
• /
• v.16 no.12
• /
• pp.113-120
• /
• 2011

Information system gradually increases the complexity and scale of the project, while if the project fails to occur. To analyze the causes of failure of the project a lack of understanding of your project, unclear requirements and requirements change, etc. of the software development life cycle from requirements analysis phase is to find the source of most. In this paper, a software development project needs analysis derived from the traceability between features and functionality, and development needs throughout the life cycle requirements during the ongoing change management tool was designed to allow. And among those related to the project through consultation with a sufficient consensus to build a common understanding of effective communication will discuss the features required to support.

• Journal of the Korea Society of Computer and Information
• /
• v.25 no.7
• /
• pp.27-37
• /
• 2020

In this paper, we propose the methodology based on data-driven approach using Natural Language Processing and Machine Learning for classifying requirements into functional requirements and non-functional requirements. Through the analysis of the results of the requirements classification, we have learned that the trained models derived from requirements classification with data-preprocessing and classification algorithm based on the characteristics and information of existing requirements that used term weights based on TF and IDF outperformed the results that used stemming and stop words to classify the requirements into functional and non-functional requirements. This observation also shows that the term weight calculated without removal of the stemming and stop words influenced the results positively. Furthermore, we investigate an optimized method for the study of classifying software requirements into functional and non-functional requirements.

• The KIPS Transactions:PartD
• /
• v.9D no.1
• /
• pp.81-90
• /
• 2002

More than 50% of defects and errors in the software development projects are related to the requirements[14]. But the development methodologies can not provide enough supports to the requirements management and changes. In the real world, the requirements keep changing as the requirements at the early development phase are usually incomplete, the developer′s understanding of the problem will be constantly changed during the software process, and new requirements may emerge with the organizational and environmental changes. In this paper, a requirements management process that can be integrated into the development methodologies is proposed to extend the requirements management over the whole development life-cycle and to support the requirements changes at the design/implementation/test phases. To evaluate the proposed process, it was compared to the existing requirements managements processes and models, and examined through a integration test with a widely used development methodology "MaRMI" to show the expected improvements at each development phase.

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

• Journal of the Korean Society of Systems Engineering
• /
• v.14 no.2
• /
• pp.83-88
• /
• 2018

Software has become an integral part of almost any system, triggered by the ever-growing demand for automation and artificial intelligent throughout engineering domains. The complexities of software-centric systems are also increasing, which make software test efforts become essential in software development projects. In this study, we applied systems engineering methodology in generating software test cases. We found out the similarities between requirements analysis and traceability concept of systems engineering and test specification contents of software test. In terms of acceptance test, software test cases could be considered as validation requirements. We also suggested a method to determine test order using a SysML modeling tool.

• Journal of KIISE:Software and Applications
• /
• v.27 no.2
• /
• pp.120-133
• /
• 2000

Major obstruction of using formal methods for hybrid real-time systems in industry is the difficulty that engineers have in understanding and applying the quantitative methods in an abstract requirements phase. While formal methods technology in safety-critical systems can help increase confidence of software, difficulty and complexity in using them can cause another hazard. In order to overcome this obstruction, we propose a framework for qualitative requirements engineering of the hybrid real-time systems. It consists of a qualitative method for requirements specification, called QFM (Qualitative Formal Method), and a safety analysis method for the requirements based on a causality information, called CRSA (Causal Requirements Safety Analysis). QFM emphasizes the idea of a causal and qualitative reasoning in formal methods to reduce the cognitive burden of designers when specifying and validating the software requirements of hybrid safety systems. CRSA can evaluate the logical contribution of the software elements to the physical hazard of systems by utilizing the causality information that is kept during specification by QFM. Using the Shutdown System 2 of Wolsong nuclear power plants as a realistic example, we demonstrate the effectiveness of our approach.

• Journal of KIISE:Software and Applications
• /
• v.27 no.1
• /
• pp.13-23
• /
• 2000

As software becomes more complicated and large-scaled, user's demands become more varied and his expectation levels about software products are raised. Therefore it is very important that a software engineer analyzes user's requirements precisely and applies it effectively in the development step. This paper presents a requirements analysis system that reduces and revises errors of requirements specifications analysis effectively. As this system measures the similarity among requirements documents and sentences, it assists users in analyzing the dependency among requirements specifications and finding the traceability, redundancy, inconsistency and incompleteness among requirements sentences. It also extracts sentences that contain ambiguous words. Indexing method for the similarity measurement combines sliding window model and dependency structure model. This method can complement each model's weeknesses. This paper verifies the efficiency of similarity measure techniques through experiments and presents a proccess of the requirements specifications analysis using the embodied system.

• Journal of the Korean Society of Systems Engineering
• /
• v.14 no.2
• /
• pp.49-57
• /
• 2018

The main objective of this paper is come up with methodology approach for FPGA-based system in verification and validation lifecycle regarding software reliability using system engineering approach. The steps of both reverse engineering and re-engineering are carried out to implement an FPGA-based of safety critical system in Nuclear Power Plant. The reverse engineering methodology is applied to elicit the requirements of the system as well as gain understanding of the current life cycle and V&V activities of FPGA based-system. The re-engineering method is carried out to get a new methodology approach of software reliability, particularly Software Reliability Growth Model. For measure the software reliability of a given FPGA-based system, the following steps are executed as; requirements definition and measurement, evaluation of candidate reliability model, and the validation of the selected system. As conclusion, a new methodology approach for software reliability measurement using software reliability growth model is developed.

• The Journal of Korea Robotics Society
• /
• v.2 no.2
• /
• pp.196-204
• /
• 2007

In this paper, we are looking for requirements of software, hardware and application for use in network-based robots and also directions in building standardization and research activities by reviewing technical status of the robot industries developing robots. The questions are including awareness of RUPI(Robot Unifies Platform Initiative) activities, target market and applications, hardware specifications, software development technologies, and HRI(Human Robot Interaction). The RUPI committee creates standard and drives implementation software for network-based robots through industrial requirements as like of the results. Many robots have been developed and launched services based on RUPI 1.0 standards. Based on this achievement we are expanding RUPI standard to include thin and thick client robots. The results also show that which one is important and urgent technology in the sense of industrial robotic business.

• Journal of the Semiconductor & Display Technology
• /
• v.22 no.1
• /
• pp.88-93
• /
• 2023

In software engineering, requirement analysis is an important task throughout the process and takes up a high proportion. However, factors that fail to analyze requirements include communication failure, different understanding of the meaning of requirements, and failure to perform requirements normally. To solve this problem, we derived actors and behaviors using morpheme analysis and BERT algorithms in the Korean requirement document and constructed them as ontologies. A chatbot system with ontology data is constructed to derive a final system event list through Q&A with users. The chatbot system generates the derived system event list as a requirement diagram and a requirement specification and provides it to the user. Through the above system, diagrams and specifications with a level of coverage complied with Korean requirement documents were created.