• 한국멀티미디어학회논문지
• /
• 제20권4호
• /
• pp.660-670
• /
• 2017

In case of auditing of the information system development project applying agile methodology, it is not appropriate to carry out a comprehensive check on the establishment of information system with only the existing check on software. This study considers the characteristics of the agile methodology in terms of Information System Auditing. To improve inspection quality of development project with agile methodology by deriving detailed check items of test activities at each stage, this study proposes a strategy to improve the check on software for the test activities of the supervisory model that is suitable for agile methodology, which emphasizes repetitive work.

• 경영정보학연구
• /
• 제10권2호
• /
• pp.211-234
• /
• 2008

우리나라의 정보시스템 개발 방법론은 1960년대와 1970년대의 정보기술 도입기, 1980년대의 공공부문을 중심으로 한 방법론 도입기, 1990년대 초반의 민간부문을 중심으로 한 방법론 확산기, 1990년대 중반의 정보공학 방법론을 가미한 방법론 내부화기, 그리고 2000년대의 객체지향과 컴포넌트 기반 개발 방법론을 반영한 방법론 관리기로 발전하였다. 우리나라 정보시스템 개발 방법론은 30년이 채 안 되는 짧은 역사를 지니고 있다. 우리나라는 비록 세계적 흐름과 비교했을 때 대략 10년 늦게 출발하였지만 1990년대 빠른 속도로 발전하여 세계적 업체들과 경쟁할 정도의 수준으로 발전하였다. 본 논문은 1980년 초에 시작되어 2007년 말까지 진행된 우리나라 정보시스템 개발 방법론의 역사를 정리한 최초의 논문이라는 점에서 의의가 있다. 이 논문은 관련 산업에 종사하는 실무자들에게 역사적 통찰력을 제공함으로써 현재와 미래의 전략적 청사진을 그리는 데 도움을 줄 것이다. 그리고 학자와 정책 입안자들에게는 정보시스템 개발 방법론이 걸어온 길을 재음미하는 과정에서 향후 국내 정보시스템 개발 방법론의 나아가야 할 방향에 대한 시사점과 다양한 연구 아이디어를 제공할 것이다.

• 예술인문사회 융합 멀티미디어 논문지
• /
• 제6권7호
• /
• pp.389-397
• /
• 2016

디지털 인문학 시스템은 정보기술을 활용하여 인문정보나 지식을 사용자에게 효율적으로 공유 및 확산하는 방안이다. 또한 인문학을 연구하는 연구자들에게는 새로운 연구방법론으로 주목받고 있다. 디지털 인문학 시스템은 기존의 정보시스템과는 차별화된 성격을 가진다. 따라서 시스템 구축 시 기존의 정보시스템 구축 방법론이 아닌 디지털 인문학 시스템에 특화된 개발 절차와 관련 인력을 구성할 필요가 있다. 최근 연구되는 디지털 인문학 시스템은 절차나 방법론 없이 기존의 정보시스템 구축방법론을 통해 구축되는 경우가 대부분이며 이로 인해 시스템 구축 후 사용성이나 효율성이 떨어져 시스템 운영에 실패하는 사례가 발생한다. 이에 따라 본 연구에서는 정보기술의 관점에서 다양한 전문분야와의 협업을 통해 효과적이고 창조적인 '디지털 인문학 시스템' 개발 방법에 대해 연구한다. 세부적으로 소프트웨어 공학 관점에서의 정보시스템 구축방법론을 기반으로 디지털 인문학 시스템에 특화된 구축 방법을 제시하고자 한다.

• 경영과학
• /
• 제19권1호
• /
• pp.197-224
• /
• 2002

Our study focuses on the implementation of IS development methodology as the innovation of IS organization. We have two main research objectives. We Intend to understand the critical factors affecting the implementation process of IS methodology. We also intend to deeply analyze the relationship among the implementation processes of methodology. The whole innovation process is divided into detailed four levels tilth dynamic and evolving Point of clew a cognition level, an adoption level, an acceptance level and an usage level. The results of our study are as follows. The main factors affecting initiation level of the IS methodology are the innovativeness of IS members, the existence of champion manager, training, the existence of IS performance gap, executive supports for IS organization, and the relative advantage of IS development methodology At the Implementation level, It is understood that the existence of champion manager executive supports, training and the relative advantage of innovation are the main factors. However, the complexity of Innovation is a megative factor about the quality of accepting and using the methodology In Innovation process. In performing the Innovation process, the Previous level gives very notable affection to the continuous next level. However it's also understood that positive attitude of adoption level does not directly affect the quality of using Innovation. Therefore, IS managers must pay attention to manacle each level of the Innovation Process to successfully accomplish the Implementation of IS methodology.

• International Journal of Fuzzy Logic and Intelligent Systems
• /
• 제5권3호
• /
• pp.268-273
• /
• 2005

We propose the specialized product-line development methodology for developing the embedded system of an MSDFS (Multi Sensor Data Fusion System : called MSDFS). The product-line methodology provides a simultaneous design between software and hardware, high level reusability. However this is insufficient in requirement analysis stage due to be focused on software architecture, detailed design and code. Thus we apply the business model based on IDEF0 technique to traditional methodology. In this paper, we describe the processes of developing Core-Asset, which are requirement analysis, feature modeling, validation. The proposed model gives the efficient result for eliciting features, and ensures the high level reusability of modules performing on embedded system.

• 품질경영학회지
• /
• 제25권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).

• International journal of advanced smart convergence
• /
• 제9권3호
• /
• pp.59-70
• /
• 2020

There are many limitations in applying agile methodology to projects so far. In fact, projects overlap with other development methodologies and management processes, resulting in confusing progress, while there are often cases where the benefits of agile cannot be embraced due to a lack of understanding of agile processes and the organization's inability to adapt to change. It is an important role of information system development to improve the quality of agile application projects by discovering the problems and improvements in these cases. In this paper, we analyze the differences between existing development and project management methods and agile, and analyze agile processes. The optimal agile methodology was proposed by analyzing and applying methodologies established and applied mainly by large domestic development companies. In addition, the effectiveness was verified through a questionnaire of IT experts, and the result of the questionnaire was verified to be 4.75 points on a 5-point scale.

• ETRI Journal
• /
• 제26권2호
• /
• pp.167-180
• /
• 2004

As component-based development (CBD) rapidly spread throughout the software industry, a comprehensive methodology is needed to apply it more systematically. For this purpose, a new CBD methodology named Magic & Robust Methodology Integrated III (MaRMI-III) has been developed. The purpose of this paper is to present MaRMI-III by its constituent processes and claim that it can be used to support system developers conduct CBD in a consistent manner. First, we review the CBD approach to system development and the role of CBD methodology, and then we explain the several characteristics of MaRMI-III which are considered necessary to the CBD environment. Next, we explain a process model of MaRMI-III which separates the development process from the project management process and prescribes well-ordered activities and tasks that the developer should conduct. Each phase forming the Process Model is explained in terms of its objectives and main constituent activities. Some techniques and workproducts related to each phase are also explained. Finally, to examine the usefulness of MaRMI-III, an analytical comparison with other CBD methodologies and the results of a questionnaire survey are described.

• ETRI Journal
• /
• 제18권4호
• /
• pp.245-264
• /
• 1997

This paper presents a formalism-based methodology and its implemented environment which constitutes a sound framework for real-time systems development. The software and/or hardware systems developed in such a formal manner are well structured and maintainable. We first propose a set-theoretic VSSS (Variable Structure System Specification) formalism. This formalism is the core of the presented methodology which supports a means of formal specification for real-time systems. We then develop the environment, including VSSS language definition, a translator for the language, and supporting libraries for real-time execution. Finally, a demonstration of the methodology in development of a real-time event manager, a subsystem of an ATM-based communication system, shows the correctness and efficiency of the methodology.

• 한국데이타베이스학회:학술대회논문집
• /
• 한국데이타베이스학회 2010년도 춘계국제학술대회
• /
• pp.13-19
• /
• 2010

Information competitiveness accounts for substantial parts of business competitiveness necessary for business management in the knowledge-information society in the 21st century. To improve quality. productivity and competitiveness through information in the fields of SMEs particularly having difficulties under rapidly changing business environment. the government has operated "SME Information Support Project" for the past 8 years. The methodology for developing the standard for this project known as EISDM (Enterprise Information System Development Methodology) provides communication between IT businesses and SMEs participating in this project. and standardized output document formats and how to make out such documents. Infortunately. the number of personnel partaking in the development project for SMEs is no more than 2~4 per site on average. Further. they are required to complete demand analyses. development. testing and operation in about 6 months. which is a very short period. Moreover, there is too much demand for documentation, which is likely to end up being formal work process just for supervision and inspection. That is, the documentation could be for noting but documents. which will prove useless outputs after the project finishes. Therefore, this study proposes an improvement approach as an information system development methodology taking into account SMEs' characteristics and environment so as to relieve developers from such excessive burden of documentation, to save time and resources through efficient management of software development as the original purpose of the methodology, and to produce required quality software.