• 한국정보과학회논문지:소프트웨어및응용
• /
• 제35권11호
• /
• pp.653-660
• /
• 2008

최근에 제시된 서비스 기반 컴퓨팅 패러다임에서의 서비스 기반 소프트웨어 개발을 지원하기 위한 체계적인 프로세스 모델에 대한 요구가 대두되고 있다. 기존에 제시된 Unified Software Development Process, UML Components 등의 방법론은 컴포넌트에 초점을 두고 만들어진 방법으로, 서비스의 정의, 바인딩, BPEL(Business Process Execution Language)을 이용한 서비스의 조합등과 같은 서비스 기반의 개발이 가지고 있는 특징을 반영하지 못하고 있다. 또한 서비스 기반의 개발 방법론으로 제시된 SOUP(Service Oriented Unified Process), SOMA(Service Oriented Modeling and Architecture) 등은 개념적인 절차가 위주로 되어 있지, 구체적인 가이드라인, 산출물 및 접근 방법을 명확히 제시하지 않는다. 그러므로 본 논문에서는 서비스 기반의 개발 패러다임을 지원하기 위한 체계화되고, 간소화된 프로세스 모델을 제시한다. 또한 OMG에서 제시한 SPEM(Software Process Engineering MetaModel)을 적용하여 프로세스 모델을 명시적으로 표현한다. 본 논문에서 제안된 프로세스 모델을 실제 서비스 기반의 개발에 적용함으로써 서비스 기반 소프트웨어 개발의 체계성 및 효율성을 증대시킬 수 있게 된다.

• 한국정보처리학회논문지
• /
• 제6권10호
• /
• pp.2680-2692
• /
• 1999

Software quality is classified by quality of process and product. In experience of Quality Management, it is known that quality level of product as it depends on goodness and badness of process and organization. As a result, improvement of software process has been important subject. According as this trends, ISO 12207 is publicated as standard of software life cycle process by ISO. For UML based object oriented development process, it is necessary that we should research detailed definition of activity and task of ISO 12207 process which is added, deleted or tailored in according to organization and project characteristics. In this thesis, by according with ISO 12207 software life cycle process, UML based object oriented development process is proposed. This process is composed of 7 steps and 19 activities including development phase, activity and product to improve quality of reliability. Usefulness of object oriented process for improvement of software quality is proved at three ways, which are comparative analysis of process characteristics, SPICE process evaluation and SPICE rick analysis.

• 디지털콘텐츠학회 논문지
• /
• 제9권2호
• /
• pp.165-175
• /
• 2008

현재 소프트웨어 개발을 위한 방법론은 객체지향에서 컴포넌트지향으로 컴포넌트지향에서 서비스지향 발전되어 오고 있다. 컴포넌트지향 개발 방법과 서비스지향 개발 방법들은 객체지향 UML 모델을 기반으로 분석되어지므로 효율적인 객체지향 분석 방법이 필요하다. 따라서 본 논문에서는 UML 기반의 클래스 식별 및 유스케이스 모델링이 개발자의 직관과 경험에 의존하는 문제점을 보완하여 입력 데이터-처리 프로세스-출력 데이터를 사용한이벤트 기반의 유스케이스 및 클래스 분석 가이드라인과 분석 프로세스를 제안 한다.

• 한국IT서비스학회지
• /
• 제8권1호
• /
• pp.99-111
• /
• 2009

Rapid growth of Management Information System (MIS) and evolution of software system enlarge maintenance necessity and it needs a process to implement information system service in business. This paper proposes service-oriented maintenance process of component software based on service design and implementation provided by existing processes for maintenance, MaRMI-RE and ITIL. The proposed process derives activities and tasks of the process by identifying services according to service guidelines. Service-oriented maintenance process is produced by analyzing correlation between the derived activities and tasks and MaRMI-RE's and adding the tasks to MaRMI-RE. To verify availability of the proposed service-oriented maintenance process, correlation between artifacts is proved.

• 한국디지털정책학회:학술대회논문집
• /
• 한국디지털정책학회 2006년도 춘계학술대회
• /
• pp.197-204
• /
• 2006

This paper tried to develop differentiation strategies of policy process in governance. Firstly, we reviewed model of policy making(output-oriented model and process-oriented model, normative or idealistic approach and realistic or empirical approach, rational model and cognitive model etc). Now gumi city is making the policy based on the process-oriented model, realistic or empirical approach, cognitive model. So gumi city was winner the test of provinces innovation in 2005. Therefore, when we make the policy, consider these factor: citizen and public service personnel participate policy making process and control policy quality.

• 한국멀티미디어학회논문지
• /
• 제6권4호
• /
• pp.736-745
• /
• 2003

Traditional slicing techniques make slices through dependence graphs. They also improve the accuracy of slices. However, traditional slicing techniques require many vertices and edges in order to express a data communication link because they are based on static slicing techniques. Therefore the graph becomes very complicated, and size of the slices is larger. We propose the representation of a dynamic object-oriented program dependence graph so as to process the slicing of object-oriented programs that is composed of related programs in order to process certain jobs. We also propose an efficient slicing algorithm using the relations of relative tables in order to compute dynamic slices of object-oriented programs. Consequently, the efficiency of the proposed efficient dynamic object-oriented program dependence graph technique is also compared with the dependence graph techniques discussed previously As a result, this is certifying that an efficient dynamic object-oriented program dependence graph is more efficient in comparison with the traditional object-oriented dependence graphs and dynamic object-oriented program dependence graph.

• 한국디지털건축인테리어학회논문집
• /
• 제1권1호
• /
• pp.46-50
• /
• 2001

It is known that to automate the quantity take-off process enables you to increase the productivity best among the construction business field. However, the limitation of 2D(Two-dimension) CAD System prevented a cost-estimating system which makes the great effects on the quantity take-off process from being developed. This study aims that you can automate both the itemized statements and the quantity take-off process by using commercially available object-oriented CAD system. The commercially available CAD system today does not give us entire satisfaction. This study shows the deduction of the old boundaries of the object-oriented CAD system and the solution of those problems. And it also studied about the quantity take-off process and the automated cost-estimating system that can be used in the simple and plain repair-maintenance work such as the execution drawing which doesn't need the complicated drawings.

• 품질경영학회지
• /
• 제13권2호
• /
• pp.2-7
• /
• 1985

본(本) 연구(硏究)에서는 품질관리(品質管理)의 추진(推進)을 비용(費用) 지향적(指向的)인 방법(方法)과 공정지향적(工程指向的)인 방법(方法)으로 대별(大別)하고 각각(各各)의 특징(特徵)을 설명(說明)함과 아울러 비교분석(比較分析) 하였다. 또 현장(現場) Q.C 담당기술자(擔當技術者)들이 품질관리(品質管理)를 실시(實施)함에 있어서 방향(方向)을 모색한다거나 현재(現在) 실시(實施)하고 있는 방법(方法)의 부당성(不當性)을 첵크하기 위한 기준(基準)을 비용함수(費用函數)로서 제시(提示)하였다.

• Journal of Computing Science and Engineering
• /
• 제4권4호
• /
• pp.253-275
• /
• 2010

In this article we review the metaphor of service-oriented architecture for enterprise computing. In typical definitions service-oriented architecture appears as a single message and a consistent roadmap for building flexible software system landscapes. But it is not. Different communities have elaborated different SOA (service-oriented architecture) concepts to address different problem areas, i.e., enterprise application integration, business-to-business, business process management, and software productizing. If software architects and software managers are aware of these strands of SOA when talking about SOA in their projects they can avoid misunderstandings and detours better. This article contributes a clarification of the different strands of SOA concepts and technologies and their mutual dependencies and identifies particular SOA concepts as instances of more general software engineering principles.

• 한국정보시스템학회지:정보시스템연구
• /
• 제10권1호
• /
• pp.97-126
• /
• 2001

Object-orientation has been proposed as a promising software process innovation to improve software productivity and quality. It has not been understood clearly, however, what factors influences the diffusion of object-oriented technology in organizations. A research model was formulated and hypotheses were generated based on the literature of information technology implementation and software process innovation. To test the research hypotheses, a questionnaire survey was conducted. The results based on 121 responses from Korean companies revealed that project characteristics, use of external experts, and number of development projects are significantly related to the diffusion of object-oriented analysis and design and object-oriented programming. Innovation champion is positively related to the diffusion of object-oriented analysis and design, whereas it is not related to the diffusion of object-oriented programming language. Only project complexity was significantly related to the diffusion of visual programming language. On the other hand, organizational size was not significantly related to any object-oriented technology in this study.