• Journal of Information Technology Applications and Management
• /
• v.21 no.2
• /
• pp.127-147
• /
• 2014

A methodology is often used in solving complex problems. As a typical case of complex problem solving, development of information systems mostly requires a use of system development methodology. However, it is not always easy or smooth for organizations to adopt the methodology and to achieve a positive outcome from their application in real project situations. Although there are a few studies to find out success factors in the implementation of the methodology, they did not take into consideration essential characteristics of the methodology. This study aims to analyze the quality of the methodology as a key determinant to influence the performance of the methodology application.

• IE interfaces
• /
• v.23 no.1
• /
• pp.35-47
• /
• 2010

This paper presents a structured framework for developing the embedded subsystem, called ESDMP (Embedded Subsystem Development Methodology for POP), which is one of core components at the development of POP (Point Of Production) system. It is essential that embedded subsystem development methodology must be closely related to the general information system development methodology from the early stage of system development. Therefore, this paper investigates the PDSM (Production System Development Methodology) that is developed by Korea Technology and Information Promotion Agency for SMEs and widely utilized at the fields of POP system development, and proposes the embedded subsystem development methodology aligned with each step of PSDM. The main characteristics of proposed methodology are as follows : First, it is developed to link each step of embedded subsystem development with relating steps of PSDM from the early stage of feasibility study. Second, it provides the procedure for designing and implementing hardware and software simultaneously. Third, it includes the method of reusability for developed products and modules.

• Journal of Korean Society for Quality Management
• /
• v.25 no.1
• /
• pp.142-155
• /
• 1997

To successfully carry out large scale research projects while su, pp.rting quality assurance of research output, effective and systematic management through utilization of resources such as manpower, time and cost as well as engineering techniques such as component technology and design methodology is required. It is necessary to establish development methodology to su, pp.rt quality assurance. The development methodology covers the contents and procedures of the project, such as division of the project into independently executable units, allocation of resources including researchers, component technology, related know-how and equipment, deployment of research units and integration of the project at the end. In this paper we present systematic development methodology for quality assurance in large scale software development projects by analyzing the contents of the methodology a, pp.ied to the Gigabit Information-processing And Networking Technology development project(GIALT).

• Journal of the Korea Safety Management & Science
• /
• v.20 no.2
• /
• pp.65-76
• /
• 2018

Recently, most of the information system use environment is changing to GUI environment based on windows and web. Most of the development tools for building such a GUI-based information system support object-oriented and event-driven programming concepts. However, there is still a lack of a development methodology that systematically supports event-based information system construction. From a business perspective, an information system is one that supports business processes efficiently and effectively to improve business performance. These business processes are composed of business activities which involve a series of business events. A business event is executed according to a business scenario. Therefore, it is necessary to grasp these events in the requirements analysis stage and to apply it on the system development methodology. However, information systems development methodology which systematically reflect the event processing concept still is insufficient. From this viewpoint, this paper proposes an event-driven scenario-based development methodology that can meet the recent development environment of information systems, and applies the proposed methodology to a small scale information system development case.

• Journal of Digital Convergence
• /
• v.15 no.1
• /
• pp.53-60
• /
• 2017

The time of digital era and the increasing complexity of the management environment have raised uncertainties about the future. Companies have made steady investments in education as a way to prepare for the future. In this study, design and development methodology based on web - based management simulation games (manufacturing, distribution, finance) which author participated in development was presented. The development methodology presented in this study can be roughly divided into business simulation game design methodology and business simulation game development methodology. Since there is no existing research methodology for development methodology, development model is presented based on empirical based on development case. In this paper, we propose an overall content development methodology and propose a detailed methodology of the content.

• The KIPS Transactions:PartD
• /
• v.9D no.6
• /
• pp.1083-1090
• /
• 2002

The software development methodology has not caught up with the rapid change of information technology. Most of the software development projects use structural methodology or information engineering methodology. If established software development methodologies don't reflect technologies applied to the project, the project may be performed ineffectively. This paper describes a model in which we can apply a new information technology to an already existed structural methodology or information engineering methodology. This model uses the technique of the divide and conquer that software development life cycle is divided into phases, each phase is divided into viewpoint- areas and the software development processes of a new information technology are applied to each small area. By using the design phase this paper shows application example, in which I applied web-based development processes to CS@RoadMap Methodology of KCC Information & Communication, a system provider in Korea. The CS@RoadMap Methodology reflecting the Web technology, Web@RoadMap Methodology, has been applied to the public-domain projects.

• Journal of Information Technology Services
• /
• v.13 no.2
• /
• pp.195-217
• /
• 2014

This paper has explored when implementing SW development project of the IT service corporations, what factors affect its productivity in SW development methodology. The importance of the AHP analysis surveyed from the experts in IT service companies and related committee, was shown in the order of the following processes : 1) Deployment process 2) Management process 3) Establishment process. It is measured the methodology levels of establishment, deployment and management in each project using the survey results collected from project execution members and analyzed the productivity of projects that have been executed within 2 years. Using project methodology level, productivity correlation analysis, and regression analysis, this study confirms that the methodology deployment level brings positive effects significantly to SW development productivity. The significance of this study would be not only to research and analyze SW development productivity using the real project execution data but also to underline the necessities and the importance of steady research, deployment and support for SW development productivity improvement.

• Information Systems Review
• /
• v.10 no.2
• /
• pp.211-234
• /
• 2008

The history of information system (IS) development methodology in Korea is less than 30 years. Korea introduced the structured development methodology in the public fields in 1980s, introduced the information engineering methodology in 1990s, and accepted and developed the objected oriented development methodology and the component based development methodology in 2000s. The history of IS development methodology in Korea is shorter than that of the world. Korea's IS development methodology started 10 year later compared with the world level. But it developed rapidly in 1990s and then grew to the world level in 2000s. This paper is the first research that it investigated the history of IS development methodology in Korea. This paper will give the people of IT industry the historical insights about IS development methodology and will help make a current and future strategic plan for IS development methodology. And it will provide researchers and policy makers with the insights and research ideas of future direction of information system development.

• Proceedings of the KIEE Conference
• /
• 2011.07a
• /
• pp.1702-1703
• /
• 2011

MEMS 소자의 Wafer level Package 관련하여 Deep cavity를 가진 Cap Wafer와 Polymer bonding 중 cavity 단차로 인한 Polymer Patterning 및 접합 불량의 어려움을 극복할 수 있는 새로운 공정 flow를 제안하였다. Cavity를 형성할 때 사용하는 Si deep etching Mask인 기존의 Photoresist를 접합용 감광성 Polymer로 대체하고, cavity 형성 후, 별도의 추가 공정 없이 이 Polymer를 이용해 Wafer bonding을 진행하였다. 이를 통해 cavity 단차에 따른 문제를 해결함과 동시에 공정이 단순하고 제작 비용이 저렴하며, 신뢰성 있는 Wafer level Package를 구현하였다.

• Journal of the military operations research society of Korea
• /
• v.22 no.2
• /
• pp.90-112
• /
• 1996

Research issues in software engineering in recent may be object oriented methodology and software quality. Since Halstead has proposed metric-software science in 1977, software quality area has been studied in steady but inactively until 1980s. As international standards such as ISO 9000-3, 9126 were enacted in 1990s early, interest in software quality is increased but many problems such as how to validate metric, measure quality or apply metric are remained. This paper proposes software quality metric methodology which software developer or project manager can use in measuring quality and validating metric during software development. The methodology is classified by several phases: establishment of quality requirement, identification of quality metric, data collection, metric implementation, metric validation. In order to show its applicability, test program, metrics and data are applied to each phase of the methodology. Consideration of this methodology as a methodology for software quality measurement similar to development methodology for software development is needed.