• The KIPS Transactions:PartB
• /
• v.10B no.5
• /
• pp.575-578
• /
• 2003

SPIHT algorithm is a wavelet based fast and effective technique for image compression. It uses a list structure to store status information which is generated during set-partitioning of zero-tree. Usually, this requires lots of additional memory depending on how high the bit-rate is. Therefore, in this paper, we propose a new technique called MZP-DFS, which needs no additional memory when running SPIHT algorithm. It traverses a spatial-tree according to DFS and eliminates additional memory as it uses test-functions for encoding and LSB bits of coefficients for decoding respectively. This method yields nearly the same performance as SPIHT. This may be desirable in hardware implementation because no additional memory is required. Moreover. it exploits parallelism to process each spatial-tree that it can be applied well in real-time image compression.

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

• The KIPS Transactions:PartD
• /
• v.16D no.5
• /
• pp.767-790
• /
• 2009

Setting up a priorityfor an embedded system is greatly significant because a release plan at the early stage of product developments can properly be established through right decision making procedures based on the priorities. For instance, both dependencies among requirements and the aspects of product developers should be considered into the priorities to improve the embedded system. Especially, trade-offs among the requirements, which are quite different depending on H/W and S/W architecture styles they use, should be acknowledged without exception. However, the selection process on the priority has hitherto been fairly systematic in the existing environment where hardware and software are not being considered at once. Therefore, this paper suggests an dependency and aspect-based model and process for the requirements of the priority. For this, the paper analyzes the trade-offs between the requirements depending on the disparate Architecture styles of H/W and S/W, and it also reflects the viewpoints of the developers. For thelast thing, the model and process suggested will be applied to the case of the development of both cell phones and cameras to gain authenticity and reliability. In conclusion, the danger occurring when the release plan is constructed can be minimized by screening the priorities that optimizes the embedded system more explicitly.

• The KIPS Transactions:PartD
• /
• v.15D no.6
• /
• pp.841-856
• /
• 2008

The priority of requirement is important because the priority is a critical activity of release plan especially in software development which has an open market customer. Also, it is important for stakeholders to select a method and aspects to prioritize requirements. The selection is based on the organizational experience of a priority process, the process model of the product, goals and a type of products, and dependencies between requirements. But, the current researches considered only static dependency between requirements and did not suggest a systematic priority process. In addition, the current researches only suggest limited aspects to prioritize requirements, such as cost and value. Therefore, this paper proposes an adjustable priority process based on a priority model to select a method and aspects for the suitable priority for product and organization. Especially, this paper enhances the completeness of a release plan by a definition of static and dynamic dependency types between requirements. This paper suggests a priority model, which considers the dependencies between requirement and various viewpoint of software development. Based on the priority model, the paper suggests a systematic priority process to promote reasonable decisions to the priority and release plan of requirement.

• Proceedings of the Korea Concrete Institute Conference
• /
• 2008.04a
• /
• pp.125-128
• /
• 2008

Studies for structure design has conducted in many research institutions. A basic concept of Performance-Based Design for structures was presented in seismic fields. Hereafter, Demand were defined to communicate owner's demand to designer by several research institution. Performance-Based Design is guaranteed by an accurate analysis from hazard affected to structures and from social, economical and environmental effects. It is essential to define Performance Level and Performance Objective to grasp accurate demand for structures. In this study, Performance Level and Performance Objective in ATC-40, FEMA-273 and Eurocode were defined to introduce Performance-Based Design.

• Journal of KIISE:Software and Applications
• /
• v.30 no.12
• /
• pp.1185-1192
• /
• 2003

In the component assembly and composition technique of software architecture, It is operated that the existing composition techniques based on architecture, ACME, Wright etc., used in FIFO with the direct connection structure between components through connector's Role. But, when the non-synchronizing request of components that have different characteristics occurs, the FIFO techniques is applied to the connector is difficult to process and operate effectively because of the high performance component waiting the sequence order if the low performance component is allocated first. Thus, the allocated request process according to the priority considering the characteristics of each call components in connector is necessary to improve the operation of assembled component. In this research, we extend the connector part that is available in multiplex connection structure based on existent Wright specification. For service process requested from component, the connector part is designed and implemented to operating with priority sequence through calculating the weight of CPU use rate, bean requesting process time and memory use rate among the efficiency elements of assembled components. To verify the efficiency if this designed connector, we implemented 20 samples EJB components that have different efficiency characteristics and applied these samples components to designed connector. The operating results with this designed connector show that the efficient operation of whole system is possible though the processing time takes 481ms more than the time of the existing FIFO techniques.

• The KIPS Transactions:PartD
• /
• v.13D no.1 s.104
• /
• pp.67-74
• /
• 2006

The security requirements identification in the software development has received some attention recently. However, previous methods do not provide clear method and process of security requirements identification. We propose a process that software developers can build application specific security requirements from state transition diagrams at the security threat location. The proposed process consists of building model and identifying application specific security requirements. The state transition diagram is constructed through subprocesses i) the identification of security threat locations using security failure data based on the point that attackers exploit software vulnerabilities and attack system assets, ii) the construction of a state transition diagram which is usable to protect, mitigate, and remove vulnerabilities of security threat locations. The identification Process of application specific security requirements consist of i) the analysis of the functional requirements of the software, which are decomposed into a DFD(Data Flow Diagram; the identification of the security threat location; and the appliance of the corresponding state transition diagram into the security threat locations, ii) the construction of the application specific state transition diagram, iii) the construction of security requirements based on the rule of the identification of security requirements. The proposed method is helpful to identify the security requirements easily at an early phase of software development.

• Journal of Korean Library and Information Science Society
• /
• v.39 no.2
• /
• pp.355-373
• /
• 2008

The purpose of this study is to find out user's information needs in public libraries based on websites. The data were collected from the user's plaza in public libraries websites. To identify the user's information needs, the works in the public libraries including acquisition, information services, circulation, digital library, reading room, reference services were analyzed.

• Journal of the Korean Society for information Management
• /
• v.17 no.3
• /
• pp.71-91
• /
• 2000

The purpose of this study is to analyze user needs of university libraries for design of user-centered information retrieval system. To do this, 6 kinds of basic system design factors necessary for user-centered information retrieval system design of the university libraries are used. The user needs which should be considered for system design are examined and analyzed through the questionnaires made by user-centered approach according to the design factors.

• Convergence Security Journal
• /
• v.2 no.1
• /
• pp.17-33
• /
• 2002

The major goal of this study is to develop an index that can evaluate the quality of the appropriate network in a series of projections that analyze, design, and then build a network. The existing software engineering and/or the methods of developing a system are limited. The process of defining the requirements in building a network, designing the system, and building the network focuses on arranging the methods of building a network. Based upon this, we tried to develop a necessary index to evaluate the security of a network.