• Journal of KIISE:Software and Applications
• /
• v.28 no.10
• /
• pp.743-756
• /
• 2001

Component-based software development (CBSD) is a method for building large software system by integrating previously-existing software components. Software development method using components has several advantages such that reducing time to delivery and development costs, and increasing productivity etc. But integrating components developed from multiple vendors is too difficult As a result it is required the understanding on the context of use to develop reusable components. The context of use for software component of determined by software architecture. Therefore, it is possible to develop an application based on components if is based on software architecture. Also, it is essential to consider domain concepts for CBSD. To increase the reusability of components. we should develop components in a domain which is a set of related systems. In this paper, we proposed a domain architecture development methodology that supports component-based software development. Domain architecture that represents components and their relationship is produced through domain analysis and design process. We believe that component development methodology using proposed domain architecture can efficiently develop highly reusable components as well as easily develop and application using information acquired from domain architecture.

• Journal of the Korea Society of Computer and Information
• /
• v.25 no.2
• /
• pp.133-140
• /
• 2020

The IISS(Integrated Interface Storage System) software uses communication methods such as DSS(Data Sharing Service), UDP to perform the function of sending all messages from the Combat Management System to the analytical computer. Because IISS software handles all message used in the Combat Management System, the source code is large and has a highly dependent feature on message changes. Modification of software is a task that requires a lot of labor, such as series of software reliability test. so research has been conducted to reduce software development costs, including minimizing software modifications. In this paper, We study the method of messages receiving and architectural structure improvement to minimize reliance on message changes in the Combat Management System and improve the modifiability. Reduced message dependency by changing the way DSS and UDP protocols are communicated to Packet Sniffing. In addition, Factory Method Pattern were applied to improve the software design. Test comparing existing software and development elements have confirmed that the software has improved its modifiability and reuse.

• Proceedings of the IEEK Conference
• /
• 2002.07c
• /
• pp.1744-1747
• /
• 2002

In late years, the tendency to shift the design language of electronic circuits from HDL to C-based languages of C/C)1 and so on is strengthened. The current of adopting these software languages thrives by necessity to solve the problem peculiar to HDL that verification of design is difficult. When we use C-based languages, we can describe the design by higher abstraction degree, mount the design as both hardware and software finally and so that express the design part which is not made clear at early stage the same one language. Therefore, the flexibility of design very improves, the design work in environment the range of applying the whole systems become possible. This paper introduces example at having applied C-based languages in image processing LSI design and describes that the design technique of C-based languages is effective for the system design.

• Archives of design research
• /
• v.17 no.4
• /
• pp.119-128
• /
• 2004

There is a lack of user centered design methods that support effective collaboration between designers and end-users for designing hardware and software integrated digital products. This paper presents the application of Collaborative Design and a new collaborative design prototyping tool for interactive digital product design projects. The tool consists of STCtools(State Transition Chart tools) software, hardware modeling materials, and physical interface toolkits for integrating software and hardware. STCtools allow users to create and edit States, to compose Events describing transitions between States, and to run intermediate or final results of STC. Using the hardware modeling materials and the physical interface toolkit, designers and end-users can collaborately examine the hardware and software integrated concepts in an early stage of the design process. Three collaborative design workshops of designing a portable digital guide for a theme park were accomplished to examine the feasibility of the tool. The results suggested that the tool supported iterative concept development and interactions between designers and end users. Although several user interface problems of STCtools were identified, the participants gave positive feedback on the role of the tool in collaborative concept generation and deployment. It is expected that the results of this study contribute not only to the collaboration between designers and end users, but also to the collaboration between designers, and between designers and other professionals.

• Proceedings of the Korea Society of Design Studies Conference
• /
• 2001.10a
• /
• pp.32.2-32
• /
• 2001

• Proceedings of the Korea Society of Design Studies Conference
• /
• 2001.10a
• /
• pp.51.1-51
• /
• 2001

• Proceedings of the Korea Society of Design Studies Conference
• /
• 2005.05a
• /
• pp.230-231
• /
• 2005

• Journal of Information Technology Services
• /
• v.5 no.2
• /
• pp.155-168
• /
• 2006

Software product line is a software product or a set of software system, which has common functions. We can develop a specific software product, which satisfies requirements of a particular market segment and a mission in a specific domain by reusing the core asset such as the developed software architecture through the software product line. Software development methodology based on the software product line can develop a software more easily and fast by reusing the developed software core asset. Developed countries of software technology select software product line as a core field of software production technology, and support technology development. In case of USA, CMU/SEI(Carnegie Mellon University/Software Engineering Institute) developed product-line framework 4.0 together with the industry and the Department of Defense. Europe is supporting the development of product line technology through ITEA(IT for European Advancement) program. However, industries in our country understand the necessity of software production technology based on product line concept for the purpose of increasing productivity, it is not sufficient to invest for this technology development. In this paper, we aim to construct the common architecture of software product line for production of the software product line.

• 제어로봇시스템학회:학술대회논문집
• /
• 1986.10a
• /
• pp.409-413
• /
• 1986

This paper deals with a micro computer based CAD(Computer Aided Design/Drafting) software developed by SERI/KAIST. The objectives of this software(hereinafter, CADMATE) development are to develop a low-cost CAD/CAE system, which means the micro-computer based graphic handling software including its geometrical primitives, graphic editor, external interface and output(drawing) control routine.

• Journal of the Korea Safety Management & Science
• /
• v.10 no.1
• /
• pp.83-90
• /
• 2008

Development of human-system interfaces (HSI) supporting the interaction between human and automation-based systems, particularly safety-critical sociotechnial systems, entails a wide range of design and evaluation problems. To help HSI designers deal with these problems, many methodologies from traditional human-computer interaction, software engineering, and systems engineering have been applied; however, they have been proved inadequate to develop cognitively well engineered HSI. This paper takes a viewpoint that HSI development is itself a cognitive process consisting of various decision making and problem solving activities and then proposes a design requirements-driven process for developing HSI. High-level design problems and their corresponding design requirements for visual information display are explained to clarify the concept of design requirements. Lastly, conceptual design of software system to support the requirements-driven process and designers' knowledge management is described.