• IE interfaces
• /
• v.6 no.1
• /
• pp.47-54
• /
• 1993

Sequential Numbering System(SNS) is one of the production and inventory management system, which is more effective and practical to minor enterprises than Material Requirement Planning (MRP) system or Just-in-Time(JIT) system. The purpose of the paper is the structured analysis of SNS as the first phase of software development. Data Flow Diagram(DFD), Data Dictionary(DD), and Mini-Specs are used to analyze the system through the second level. The result can be exploited to SNS software design and programming.

• Proceedings of the Korean Society for Quality Management Conference
• /
• 1998.11a
• /
• pp.43-50
• /
• 1998

The cause of software crisis is that software quality and productivity can not meet the requirement of software market. In order to resolve the software crisis, there are many approaches to be proposed. Software reuse is one of the high potential approaches to improve software quality and productivity. Some high-tech countries (like USA, Japan) have proposed and studied the topics of software reuse in 1970 and got several results. In software development procedure, the products of detailed design and implement phases are simple, definite and suitable for reuse. In this paper, the necessary documents of reusable software component will be proposed, and how to select and evaluate the software components with high reuse potential and high quality will be discussed and recommended.

• Journal of Computing Science and Engineering
• /
• v.11 no.1
• /
• pp.9-23
• /
• 2017

NuDE 2.0 (Nuclear Development Environment 2.0) is a formal-method-based software development, verification and safety analysis environment for safety-critical digital I&Cs implemented with programmable logic controller (PLC) and field-programmable gate array (FPGA). It simultaneously develops PLC/FPGA software implementations from one requirement/design specification and also helps most of the development, verification, and safety analysis to be performed mechanically and in sequence. The NuDE 2.0 now consists of 25 CASE tools and also includes an in-depth solution for indirect commercial off-the-shelf (COTS) software dedication of new FPGA-based digital I&Cs. We expect that the NuDE 2.0 will be widely used as a means of diversifying software design/implementation and model-based software development methodology.

• The Transactions of the Korea Information Processing Society
• /
• v.7 no.10
• /
• pp.3075-3085
• /
• 2000

According to distributed, large-caled environment of software development and operation, the elicitation and specivication of correct and complete requrement is the most important factor for the system. In addition contiuous and dramatic systerm canging requests in cooperative environment with internet require more efficient, requirement management. In this paper we detine the specification architecture and techruques for requrements, so that we improve the efficiency ofnatural language-based requirement speciticationand management in a cooperatie work environment. Also, we propose a software requirement engineering process model and environment based on requirements in a CSC@(Computer Supported Cjooperative Work) environment, therefore transfer them into analysis phase.

• Journal of KIISE:Software and Applications
• /
• v.34 no.5
• /
• pp.419-430
• /
• 2007

It is very important to track whether software is properly developed according to requirements. This study suggests a method to track requirements by using a tracking table. In this study, the tracking table indicates why such requirements are included by detailing the content of requests for proposals and proposals. The table also facilitates verification of the consistency between outputs and the integrity by having ID codes of each requirement mapped to each output. Furthermore, as this study was conducted, it was found that some factors were required to be added or supplemented to the outputs at the requirement gathering stage of MaRMI-Ⅲ v.4.0 methodology. Thus, this study seeks to present this additional result along with the enhanced tracking table. By verifying outputs, the tracking table presented in this study will help to reduce all kinds of risks and problems that may occur in software development due to the lack of management of requirements. In addition, the output of the requirement-gathering stage of MaRMI-Ⅲ v.4.0 methodology will be improved/supplemented according to the creation of tracking tables; this will increment the applicability of the MaRMI-III methodology.

• Journal of Information Technology Services
• /
• v.5 no.1
• /
• pp.177-190
• /
• 2006

Since their first inception a few decades ago, software components have received much attention mainly due to their alleged benefits of quality and productivity improvement. Despite this, it is yet to be agreed upon what and how components should be designed. This paper aims to bridge the gap by proposing a collaborative process where the voice of the customer is captured and documented by employing the event and entity models. These requirement elements (WHAT) are cross-tabulated in three relation matrices in accordance with the weights provided by the business users. The requirements are fed into the algorithm invented by the authors to optimize the component grouping (HOW). This collaborative process has been successfully validated at an enterprise wide software development project. The process was effective to help the users more actively involved in the design of the system and made the whole process faster and more adaptive to the changes.

• Korean Journal of Computational Design and Engineering
• /
• v.13 no.2
• /
• pp.121-130
• /
• 2008

The concept of integrated product information has been universalized so that many manufacturing industries have applied the concept to their production system. The field of PDM (Product Data Management), which is one of the core components of the integrated product information, is not an exception. Therefore, various PLM (Product Lifecycle Management) software providers are in process of suggesting the PDM solutions. As the PDM solution is widely adopted in the manufacturing industries, the successful application of the solution has been gathering more strength in manipulation of the product information. However, the standardized implementation methodology is stuck in the basic level contrast with the enhanced PDM's functionality and capability. Present study refers to the application of UML (Unified Modeling Language), which is an object oriented modeling description, to PDM system development procedure. The advantage of UML is its efficiency and effectiveness in handling complex requirement often found in PDM implementation works. This paper shows the integration of PDM and UML proposes a philosophy for the support of requirement analysis throughout the full implementation of PDM system.

• Journal of KIISE
• /
• v.44 no.9
• /
• pp.893-907
• /
• 2017

In safety-critical systems, software defects may have serious consequences. Therefore, defects should be considered during the requirements specification process, which is the first step of a software development lifecycle. Stakeholder requirements that are usually written in natural language are difficult to derived, and there may also be defects due to ambiguity and inaccuracy. To address these issues, we propose a requirement specification method using a standardized Boilerplate and a GSN Model. The Boilerplate is a semi-standard language that follows a predefined format. Due to its ability to provide a consistent representation of the requirements, boilerplate helps stakeholders avoid ambiguities about what they mean and to define the exact meaning of the requirement. Meanwhile, GSN is recognized notation to prepare a Safety Case to prove to authorities that a system is safe. It can be expressed as a functional goal, e.g., Safety Evidence, etc. The proposed study allows an analyst to easily identify a fault from the early stage of the software development lifecycle. The Boilerplate and GSN Model are designed to specify the requirements of safety critical systems and to prove safety conformity through a connection with Safety Evidence. In addition, the proposed approach is also useful to develop secure software by correcting deficiencies in the requirements found during this process.

• Asia pacific journal of information systems
• /
• v.4 no.2
• /
• pp.83-130
• /
• 1994

Software development of large scale program such as Operating System or University Total Information System is lengthy and costly process. In order to reduce cost, time and risk, there is currentry general acceptance of the need for Software Reuse System during the whole development cycles. In this paper, (from a practical point of view), the problem of existing reuse system methodology is analyzed and an implement method of software reuse system is presented. Also using this method Application Program Reuse System(APRS) which supports all phase of software life cycles is designed and implemented. This application program reuse system which is based on common language is considerably shown to reduce communication Error of requirement specification between systems analyst and end-user.

• Korean Management Science Review
• /
• v.9 no.1
• /
• pp.31-40
• /
• 1992

The size of software collection at any organization is increasing rapidly with the use of computer becomes popular for various applications. This trend points out the importance of proper 'catalog'or 'directory' for software collections, however, only 'title list' is found in practice. The problem of no proper directory with software collection would be more serious than the problem with book collection since browsing is not possible with softwares. Many of the expensive softwares will be a waste of money to purchase and to hold if no catalog about them is provided. In this paper the difficulties in applying AACR2 to software cataloging and the most important characteristic of computer software are discussed as well as presenting the necessity of localized information due to the requirement of a machine to be used, the difficulty using subject-based-call-number scheme, an expected way of searching software to design a location indicator, software qualifications to be cataloged, and so on. In addition, an analysis of randomly selected softwares after a cataloging practice is followed.