• Journal of the Korea Computer Industry Society
• /
• 제4권4호
• /
• pp.517-522
• /
• 2003

As the Software development condition is changed into enlargement and complex, requirements generated in each step of Software development life cycle has important effects on the technique and management area. In this thesis, We propose so engineering approach for effective and systematic process and activities including Requirements acquisition and management based on activities proposed with Requirements Engineering and CMM that my special emphasis is putted on Software qualify improvement through the reduction of software development cost and danger.

• Journal of Navigation and Port Research
• /
• 제43권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 Korea Society of Computer and Information
• /
• 제24권7호
• /
• pp.19-29
• /
• 2019

Requirements traceability is regarded as one of the important quality attributes in software requirements engineering field. If requirements traceability is guaranteed then we can trace the requirements' life throughout all the phases, from the customers' needs in the early stage of the project to requirements specification, deployment, and maintenance phase. This includes not only tracking the development artifacts that accompany the requirements, but also tracking backwards from the development artifacts to the initial customer requirements associated with them. In this paper, especially, we dealt with the traceability between functional requirements and non-functional requirements. Among many Information Retrieval (IR) techniques, we decided to utilize Latent Semantic Indexing (LSI) and Latent Dirichlet Allocation (LDA) in our research. Ultimately, we conducted an experiment on constructing traceability by using two techniques and analyzed the experiment results. And then we provided a comparative study between two IR techniques in constructing traceability between functional requirements and non-functional requirements.

• Journal of the Korea Society of Computer and Information
• /
• 제16권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.

• The KIPS Transactions:PartD
• /
• 제11D권7호
• /
• pp.1459-1466
• /
• 2004

As the area of software application is increased. the software is becoming larger and more complex. In addition, development of the high quality software within the limits of the budget is strongly demanded. Many methodologies, such as software process improvement, object-ori-ented development, requirement-engineering, and software metrics have been introduced in the software development process in order to attain such objectives. Among those techniques. Requirements-Engineering gives basic guideline to develop high quality software. In other word. in order to develop high quality software, requirements should be elicited, and described. And with proper reviews and management. the quality of requirements can be improved. In this paper, quantitative measurement method that is based on IEEE Std-830-1998 for the require-ment-specifications is proposed.

• KSII Transactions on Internet and Information Systems (TIIS)
• /
• 제10권3호
• /
• pp.1404-1415
• /
• 2016

Because of the properties of software such as invisibility, complexity, and changeability, software configuration management (SCM) for software artifacts generated during software life-cycle has been used for guarantee of the quality of the software. However, the existing SCM system has only focused on code artifacts and software development document artifacts such as Software Requirements Specification (SRS), Software Design Description (SDD), and Software Test Description (STD). Moreover, software research-oriented project comes out late the code artifacts and the software development document artifacts. Therefore, there is a need for trace and management of software research document artifacts composed of highly abstracted non-functional requirements like 'the purpose of the project', 'the objectives', and 'the progress' before generation of the code artifacts and the software development document artifacts for a long time. Nevertheless, the existing SCM system cannot trace and manage them. In this paper, we propose content-based configuration management system comprised of the relevance link generation phase and content-based testing phase to trace and manage them. The preliminary application results show applicability and feasibility of the proposed system.

• International Journal of Internet, Broadcasting and Communication
• /
• 제15권3호
• /
• pp.219-230
• /
• 2023

With the development of autonomous driving technology, as the use of software in vehicles increases, the complexity of the system increases and the difficulty of development increases. Developments that meet ISO 26262 must be carried out to reduce the malfunctions that may occur in vehicles where the system is becoming more complex. ISO 26262 for the functional safety of the vehicle industry proposes to consider functional safety from the design stage to all stages of development. Specifically at the software level, the requirements to be complied with during development and the requirements to be complied with during verification are defined. However, it is not clearly expressed about specific design methods or development methods, and it is necessary to supplement development guidelines. The importance of analysis and verification of requirements is increasing due to the development of technology and the increase of system complexity. The vehicle industry must carry out developments that meet functional safety requirements while carrying out various development activities. We propose a process that reflects the perspective of system engineering to meet the smooth application and developmentrequirements of ISO 26262. In addition, the safety analysis/verification FMEA processforthe safety of the proposed ISO 26262 function was conducted based on the FCAS (Forward Collision Avoidance Assist System) function applied to autonomous vehicles and the results were confirmed. In addition, the safety analysis/verification FMEA process for the safety of the proposed ISO 26262 function was conducted based on the FCAS (Forward Collision Avoidance Assist System) function applied to the advanced driver assistance system and the results were confirmed.

• International Journal of Internet, Broadcasting and Communication
• /
• 제15권2호
• /
• pp.218-226
• /
• 2023

In Korea, we still use function point based cost estimations for software size and cost of a project. The current problem is that we make difficultly calculating function points with requirements and also have less accurate. That is, it is difficult for non-experts to analyze requirements and calculate function point values with them, and even experts often derive different function points. In addition, all stakeholders strongly make the validity and accuracy of the function point values of the project before /after the development is completed. There are methods for performing function point analysis using source code [1][2][3][4] and some researchers [5][6][7] attempt empirical verification of function points about the estimated cost. There is no research on automatic cost validation with source code after the final development is completed. In this paper, we propose automatically how to calculate Function Points based on natural language requirements before development and prove FP calculation based on the final source code after development. We expect validation by comparing the function scores calculated by forward engineering and reverse engineering methods.

• Journal of the Korea Society of Computer and Information
• /
• 제21권10호
• /
• pp.115-123
• /
• 2016

In this paper, we propose a Model Driven Development using UML(Unified Modeling Language) in an efficient Combat System Software development methods. UML is managed by the OMG (Object Management Group) as a Unified Modeling Language. Recently, In developing the software for the system, development time is contrary to a short, while it must meet a number of requirements of our customers. If you develop a non-efficient software early, the structure of the software become more complex in proportion to the number of requirements. As a result, a serious problem in the system, such as an increase in defective products due to the lowering of the reliability and communication problems between the developer has occurred. To overcome those problems, the aim of this paper is to develop a reusable high efficient Combat System Software by applying Model-Centric Development (Not Code-Centric Development). If Combat System Software development method using the UML proposed in this paper is used, easy communication among developers can help reduce the serious errors in systems. Also, it has the advantage that the future needs of software maintenance/repair become easy by using high readability object Model.

• Nuclear Engineering and Technology
• /
• 제27권1호
• /
• pp.84-95
• /
• 1995

Application of computer software to safety-critical systems is on the increase. To be successful, the software must be designed and constructed to meet the functional and performance requirements of the system. For safety reason, the software must be demonstrated not only to meet these requirements, but also to operate safely as a component within the system. For longer-term cost consideration, the software must be designed and structured to ease future maintenance and modifications. This paper present a software engineering process for the production of safety-critical software for a nuclear power plant The presentation is expository in nature of a viable high quality safety-critical software development. It is based on the ideas of a rational design process and on the experience of the adaptation of such process in the production of the safety-critical software for the Shutdown System Number Two of Wolsong 2, 3 & 4 nuclear power generation plants. This process is significantly different from a conventional process in terms of rigorous software development phases and software design techniques. The process covers documentation, design, verification and testing using mathematically precise notations and highly reviewable tabular format to specify software requirements and software design. These specifications allow rigorous, stepwise verification of software design against software requirements, and code against software design using static analysis. The software engineering process described in this paper applies the principle of information-hiding decomposition in software design using a modular design technique so that when a change is' required or an error is detected, the affected scope can be readily and confidently located. It also facilitates a sense of high degree of confidence in the ‘correctness’ of the software production, and provides a relatively simple and straightforward code implementation effort.