• The KIPS Transactions:PartD
• /
• 제10D권5호
• /
• pp.763-772
• /
• 2003

Design patterns are known widely by the techniques to improve software qualify. The design patterns are efficient solutions for problems occurring frequently in software development. Recently there are wide researches for design patterns to find them and to verify usability for them. But there are very few researches to define systematic development approaches about constructing application using design patterns. In this paper, we propose an approach for the pattern-oriented software development process using incremental composition for design patterns. For this proposal, first we define a development process using design patterns, propose technique for incremental composition for design patterns and view ports for software in the process. Also we deal with the problem of efficient traceability and maintenance to design patterns in the software system. And we use a feedback framework system as an illustrative example to show how the process can be used to develop the pattern-oriented software. In the development of software, the systematic development approach and usage increase efficiency to develop the system by using design experience and technique early in the development lifecycle. Therefore the system will assure the high stability and reusability and offer the low cost and time for development.

• Journal of KIISE
• /
• 제44권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.

• The KIPS Transactions:PartD
• /
• 제9D권1호
• /
• pp.75-80
• /
• 2002

Putnam develops SLIM (Software LIfecycle Management) model based upon the assumption that the manpower utilization during software project development is followed by a Rayleigh distribution. To obtain the manpower distribution, we have to be estimate the total development effort and difficulty ratio parameter. We need a way to accurately estimate these parameters early in the requirements and specification phase before investment decisions have to be made. Statistical tests show that system attributes are highly correlation (redundant) so that Putnam discards one and get a parameter estimator from the other attributes. But, different statistical method has different system attributes and presents different performance. To select the principle system attributes, this paper uses the principle component analysis (PCA) instead of Putnam's method. The PCA's results improve a 9.85 percent performance more than the Putnam's result. Also, this model seems to be simple and easily realize.

• The Transactions of the Korea Information Processing Society
• /
• 제4권7호
• /
• pp.1719-1732
• /
• 1997

In the software development process, various development product are made in each phase of lifecycle. Formless software is visualized by products, and quality management is implemented by management for products. But, because standardization for products which is made in the development process is not established practically, developers use different development methodologies or documentation specifications. Therefore the reality is that quality evaluation is not implemented along standardized methodology or systematic process. In this paper, we constructed quality management system and designed and implemented analysis phase quality evaluation toolkit. We constructed quality external and internal character to evaluate software quality for quality management and constructed relational metrics and system of qualitative quantitative evaluation element items and, under these systems, we constructed quality evaluation toolkit and Implemented functions and evaluated products.

• Journal of the Korea Convergence Society
• /
• 제10권12호
• /
• pp.71-80
• /
• 2019

DevOps is a combining which means giving a diverse environments for software development and operations through whole software lifecycle. The key value of the proposed DevOps platform is the fast and stable service capability for a software development and operation environment. To do this, the DevOps gives pre-embedded 7 programming languages-Java, C/C++, Python, PHP, Ruby, Node.js, goLang and 7 service frameworks - Korea eGov Framework, Spring, Struts, Django, Laravel, Rails, Express. With the DevOps platform, it is possible to develop a software and also to build and distribute operation packages directly with the Linux containers. In this paper, the performance evaluation for a compile time, a distribution time and a processing capability is will be also proved. Though the performance evaluation, this paper shows capabilities of the proposed DevOps for Cloud services with commercial service level, prospectively.

• Journal of KIISE:Software and Applications
• /
• 제41권7호
• /
• pp.469-480
• /
• 2014

Software Product Line (SPL) is a software development paradigm that guarantees high productivity, reduced cost, and shorter time-to-market by systematically planning and reusing commonality and variability. In order to maximize the benefits of SPL engineering, testing should be integrated into the SPL engineering lifecycle processes that consist of domain engineering and application engineering and should be performed with as little test efforts as possible. This paper proposes a systematic software product line test cases derivation method using combinatorial test design. By applying combinatorial test design to product line test cases derivation and exploiting commonality between products at the same time, the number of generated test cases is dramatically reduced with the result that they can be effectively reused by the products of the given product line. Case studies conducted in this paper show the efficacy of our method compared with other methods that use only commonality or combinatorial design or neither of them in terms of the number of derived test cases.

• The Korean Journal of Health Service Management
• /
• 제7권3호
• /
• pp.203-212
• /
• 2013

Medical devices separated by a committee of the International Electrotechnical Commission IEC TC (Technical Committee) 62 medical electrical equipment being promoted by the International standards. Actually, a lot of standards were existed, but many national and international standards for medical devices were lacking in practical standards that can be applied to their development. Most international standards were focused in electrical and mechanical safety of medical devices. Therefore, there were few practical standards which contain essential performance evaluation. Although medical device regulations do not enforce a fixed lifecycle model, activities are presented in a sequential manner, thus hinting at a waterfall process. Meanwhile, for a decade or more, software teams have benefitted from agile development methods. Several medical device manufacturers have adopted agile practices while keeping development in compliance with regulations, but conflicts arise and decisions have to be taken in favor of agility or formality. However, if there are new practical standards of medical devices, it must be possible to promote the medical devices industry in their nation. To do this, there is a need to develop a new standard could apply to the international market through the analysis of the medical device related technology. Consequently, new standards such as NP (New proposal) or NWIP (New Work Item Proposal) should be developed through international standardization of medical device technology.

• Journal of Internet Computing and Services
• /
• 제22권6호
• /
• pp.59-69
• /
• 2021

Malfunctions and failures linked to medical devices may result in significant damage for human being. Thus, in order to ensure that safety of medical device is achieved, it should be established and applied the international standard. It is required to integrate and customize activities at standards, owing to reference relationship between standards, especially, activities based safety analysis is too expensive. This paper proposes a integration process that integrate activities of development lifecycle and safety process. Additionally, we derived a guidance based on STPA for integration process. As a result, we can be performed systematically from early stage of the development and increased effectiveness of integration process by the guidance.

• Korean Journal of Computational Design and Engineering
• /
• 제13권5호
• /
• pp.362-371
• /
• 2008

Generally, a PLM education program in university consists of lectures of theory, software lab and software development raining as an advanced subject. Most industries want more than these, such as practical problem solving capabilities, teamwork skills and engineering communications including human relationship, rhetoric, technical writing, presentation and etc. Problem-Based Learning is a problem-stimulated and student-centered teaming method, and an innovative education strategy for collaborative and self-directed learning by applying real world problems. Education paradigm changes from "teaching" to "learning" accomplished by team working, and students are encouraged to develop, present, explain and defense their ideas, suggestions or solutions of a problem, and the "cooperative teaming" proceeds spontaneously during team operations. Co-operative education program is an into-grated academic model and a structured educational program combining classroom learning with productive work experience in a field related to a student's academic or career goals. Based on the partnership between academic institutions and industries, students are engaged in real and productive "work" in the industry, in contrast with merely observing. In this paper, PBL with Co-op program is suggested as an effective approach for PLM education, and we made and operated a PBL-based education course with industry co-op program. The Co-op education in industry accompanied with the PBL course in university can improve practical problem solving capabilities of students, including modeling and management of P3R(Product, Process, resource and Plant) using commercial PLM software tools. By the result, we found this to be an effective strategy for helping students, professors and industries succeed in engineering education, especially PLM area.

• KIPS Transactions on Software and Data Engineering
• /
• 제4권3호
• /
• pp.99-110
• /
• 2015

Internet-of-Things(IoT) is the computing paradigm converged with different technologies, where diverse devices are connected via the wireless network, acquire environmental information from their equipped sensors, and actuated. IoT applications typically provide smart services to users by interacting with multiple devices connected to the network and are designed by integrating multiple technologies such as sensor network, communication technologies, and software engineering. Moreover, since the concept of IoT has been introduced recently, most of the researches are in the beginning step, which is too early to be practically applied. Due to these facts, developing IoT application results in unconventional technical challenges which have not been observed in typical software applications. And, it is not straightforward to apply conventional project guidelines to IoT application development projects. Hence, there can be many difficulties to successfully complete the projects. Therefore, for successful completion of the projects, we analyze technical challenges occurring in all phases of the project lifecycle, i.e. project preparation stage and development stage. And, we propose the effective solutions to overcome the issues. To verify identified issues and presented solutions, we present the result of applying the solutions to an IoT application development. Through the case study, we evaluate how reasonable the unconventional technical issues are generated and analyze effectiveness of applying the solutions to the application.