• 한국전자거래학회지
• /
• 제5권1호
• /
• pp.123-134
• /
• 2000

Over the past several decades, several architectural approaches have been applied to develop Information Systems, The software architectural model has been recognized as one of the most important methods for improving productivity. Most conceptual models are difficult to understand and interpret at various system models. As a consequence, conceptual models of many Information Systems fail to represent, exploit, and apply to various aspects, which is needed for reducing development step of the architecture. In this paper, we will explain the architectural model as the 4＋1 View of UML. This model integrates the Knowledge Management System into five views： the Logical View, the Process View, the Deployment View, Implementation View, and the Use-Case View. Moreover, this paper will not only provide information on the application of the software architectural model by stakeholders, but also ultimately improve productivity.

• 한국IT서비스학회지
• /
• 제10권4호
• /
• pp.191-204
• /
• 2011

Recently, many software companies are trying to improve the software quality and project outcome with more costs and efforts in development time. In the software convergence and integration environments, it is required efforts to gain high quality of software. In other words, it is required to utilize software engineering knowledge and technology for higher software quality and better software project productivity. The Software development productivity can be varied by software process capability according to building a framework for software development, selection and use of appropriate technology, human resource management. Software process capability will influence software project outcome which is the general opinion. This study provides empirical evidence about software engineering efforts and investment approach to lead software project performance. We measured the software engineering efforts by SW engineering level and analyzed the corelation between software engineering level and schedule deviation. And, we verified that this performance is affected by the size of software company. As a result, software process capability is important to build a infrastructure and develop systematically software project. The higher software engineering level can lead to improved software project performance.

• 한국경영과학회:학술대회논문집
• /
• 대한산업공학회/한국경영과학회 1993년도 춘계공동학술대회 발표논문 및 초록집; 계명대학교, 대구; 30 Apr.-1 May 1993
• /
• pp.62-71
• /
• 1993

Recently, the computer software technology is not keeping pace with the increasing demand of application software development and rapid changes in business environment. To overcome this "software crisis", many researchers have studied the methodologies to improve the productivity in software development and the flexibility of software usage. Among these methodologies, the most promising and intensively studied methodology is the Object-Oriented Approach The purpose of this study is, therefore, to examine the applicability of the Object-Oriented Approach for improving productivity and flexibility in Management Information Systems development. For an application, we selected a financial planning model, especially focusing on the budgeted income statement. In this thesis, we identified relevent objects in the budgeted income statement, and represented them in the object models. By implementing these object models using C++ language, we evaluated their adaptability in the budget-making process, and showed, by comparing them with the existing Planning '||'&'||' Modeling Languages such as IFPS(Interactive Financial Planning Saystem), their practicability in Management Information Systems. The results of this study are as follows: First, the same object models can be used in making the budgeted income statement both in the department level and in the corporate level. Second, the object models provide the flexibility and extensibility of an application program in case of the changes in business environment. Third, the Object-Oriented Approach is a practical methodology to improve the productivity and cut down the maintenance cost of application software development.t.

• 디지털융복합연구
• /
• 제10권3호
• /
• pp.137-142
• /
• 2012

본 논문은 동일한 경량 컨테이너 구조 환경에서 스프링 2.5와 EJB 3.0의 개발 생산성에 대한 지침과 평가 지표를 제공하는데 목적이 있다. 스프링은 경량 컨테이너 아키텍처로 성공적인 오픈 소스 모델로 알려져 있으며, EJB는 엔터프라이즈 환경에서의 표준 프레임워크로 현업에서 가장 많이 사용되고 있다. 그러나 동일한 플랫폼 상에서 스프링 2.5와 EJB 3.0 프레임워크에 대한 성능 평가 연구는 부족하였다. 또한 정량적 분석도 일부분의 LoC(Line of Code) 분석만 시도함에 따라 새로운 사양이 발표됨에도 구체적인 평가 지표와 지침이 부족하여 소프트웨어 생산성의 평가와 프로젝트의 새로운 시도에 제한이 있었다. 따라서 본 연구에서는 동일한 개발 플랫폼 환경을 기반으로 파일럿 시스템을 스프링 2.5와 EJB 3.0 프레임워크에서 설계하고 구현한 후, 개발 플랫폼 환경별 객관적인 소프트웨어 개발 생산성을 비교하고, 표준화에 따른 평가 지표를 제공하고자 한다.

• 디지털융복합연구
• /
• 제12권3호
• /
• pp.263-268
• /
• 2014

본 논문은 EJB 3.0과 EJB 3.1에 연관된 객체 지향 소프트웨어 개발 생산성에 대한 정량적인 평가 지표를 제공하는데 목적이 있다. N-Tiers 엔터프라이즈 아키텍처가 가지고 있는 문제점을 해결하고 장점들을 지원하기 위하여 새롭게 등장한 아키텍처가 경량 컨테이너 아키텍처이다. 이 구조는 EJB(Enterprise JavaBeans) 아키텍처와 같이 무겁지 않으면서도 EJB 컨테이너의 모든 기능을 제공하는 구조이다. 그러나 동일한 플랫폼 상에서 EJB 3.0과 EJB 3.1에 대한 성능 평가 연구는 부족하였다. 또한 정량적인 분석도 일부분의 LoC(Line of Code) 분석만 시도함에 따라 새로운 사양이 발표됨에도 구체적인 평가 지표와 지침이 부족하여 소프트웨어 개발 생산성의 평가와 프로젝트의 새로운 시도에 제한이 있었다. 따라서 본 연구에서는 동일한 개발 플랫폼 환경을 기반으로 영화예매시스템을 EJB 3.0과 EJB 3.1에서 설계하고 구현한 후, 개발 플랫폼 환경별 객관적인 소프트웨어 개발 생산성 비교 및 표준화에 따른 평가지침을 제공하고자 한다.

• 한국군사과학기술학회지
• /
• 제10권4호
• /
• pp.20-29
• /
• 2007

The engagement control software embedded in the weapon control computer of the fire control center for air defense missile system is large-scale real-time software. The use of typical software development methodologies is not appropriate to develop such large-scale embedded software in terms of reusability, reliability, and productivity for the reason that it is significantly complicated, and highly dependent on hardware platforms and developers. In this paper, a model-based software architecture using components based on UML 2.0 for the engagement control software is presented in order to solve these problems. This software architecture is verified using the black-box test, the scenario-based test, and the Ethernet packet monitoring test methods. The results demonstrate that the developed software architecture can be employed to enhance reusability, maintainability, and productivity of large-scale embedded software.

• Journal of Information Technology Applications and Management
• /
• 제9권3호
• /
• pp.113-127
• /
• 2002

The effort for software process improvement is lately surging its interest though it does not satisfy both developer and receiver In terms of low productivity, quality, delay and increasing cost. According to current research, software process improvement contributes to improvement of productivity, its Duality, reduction of development time and cost, and the prediction of the time limit for delivery, which means software process improvement affects competitive advantage among developers. The latest research is whether the investment for information technology substantially had effect on improvement of productivity. That is, software process improvement and maturity of software industries has influence upon economic efficiency and as a result, it plays an important role in whole industries. This research is that how does software process improvement using CMM (Capability Maturity Model) and SPICE (Software Process Improvement and Capability dEtermination) have a effect on factors of software engineering, and how does it have influence upon competitive advantage among SI firms. For this research, reusability, customizability, participation, and review & inspection are set to independent variable and process flexibility and process predictability are set to mediate Variable. Finally, competitive advantage among SI firms Is set to dependent variable. The targets for survey are laborers who work for SI firms. The result of this research is as follows: 1 ) Reusability, Customizability and participation is not rejected but review and Inspection is rejected in process flexibility which has significant level 0.05. 2) Reusability, Customizability and participation is not rejected but review and inspection Is rejected in process predictability which has significant level 0.05. 3) Process flexibility is not rejected and process predictability Is rejected in the competitive advantage of 51 industries which has significant level 0.05

• Asia pacific journal of information systems
• /
• 제2권2호
• /
• pp.15-30
• /
• 1992

Computer-Aided Software Engineering or CASE is the technology for automating the software development and maintenance process. Many firms are turning to CASE in hopes of realizing improvement in productivity and system quality. Although expenditures on CASE were reported to be rapidly rising, the performance gains have been very difficult to measure. The empirical results in this article are intended to provide some evidence about (1) the major objective of using CASE, (2) the gains from CASE, (3) the difference in productivity among CASE tools. They are based on an analysis of data collected from 61 software engineers from five corporations who have the experience of using CASE.

• 한국컴퓨터정보학회논문지
• /
• 제16권9호
• /
• pp.35-43
• /
• 2011

하나의 소프트웨어를 개발하기 위해서는 개발조직의 생산성, 투입되는 노력, 개발일정, 소프트웨어 규모 간에 관계가 있다. 이들 관계를 유도한 식이 소프트웨어 공식이다. 소프트웨어 공식은 근본적으로 규모-노력, 규모-일정 관계가 적용되었다. 이 관계가 적절하지 않을 경우 소프트웨어 공식으로부터 유도되는 비용-일정 타협 공식, 투입인력 프로파일 등의 효용성이 없어진다. 본 논문에서는 이러한 문제점을 해결하고자 수정된 소프트웨어 공식을 유도하였으며, 수정된 소프트웨어 공식에 기반하여 소프트웨어 규모별로 비용-일정을 타협하는 모델들을 제안하였다. 소프트웨어 개발 성공률을 향상시키기 위해 제안된 모델을 적용하면 계약 협상이나 입찰에 도움이 될 것이다.

• 한국항행학회논문지
• /
• 제14권6호
• /
• pp.900-908
• /
• 2010

최근 소프트웨어 개발에 적용하기 시작한 객체지향 방법(OOM:Object-Oriented Method)은 독립적인 소프트웨어의 재사용을 통한 개발 비용과 시간의 단축을 강조하고 있다. 그러나 개발 기술에 대한 지식 부족과 확장성 및 성능을 배제한 설계로 많은 문제점이 나타나고 있다. 따라서 본 논문에서는 소프트웨어 개발 생명주기에서 소프트웨어 생산성 향상을 위한 효율적인 객체지향 모델링 방법을 제안하고자 한다. 제안 방법은 Use Case 모델링, 분석 모델링, 그리고 설계 모델링 방법들을 포함하고 있다.