• Title/Summary/Keyword: Software Component

Search Result 1,204, Processing Time 0.025 seconds

A Design Version Control System of Component using UML (UML를 이용한 컴포넌트 버전 제어 시스템 설계)

  • 김홍진;오상엽;김영선
    • Journal of the Korea Society of Computer and Information
    • /
    • v.8 no.1
    • /
    • pp.69-75
    • /
    • 2003
  • The Development of software Puts component of software made in advance to use to improve productivity Reuse of component can cut down on the development costs of software and reduce the development Period. By reusing component needed for software development, it can minimize risk factors from the software design to implementation We are going to Proposal the method which can promote efficiency of reuse by introducing with skill to implement the software and managing the specification using UML with version through the version management systems. The object of this study is that when the software is developed, we make software used effectively through the version management of component using UML.

  • PDF

Component-based Partner Management System Architecture on .NET Environment (닷넷 환경에서의 컴포넌트 기반의 파트너 관리 시스템 아키텍처)

  • Bae, Sung-Moon;Lee, Sang-Cheon;Choi, Jeong-Tae
    • IE interfaces
    • /
    • v.16 no.spc
    • /
    • pp.127-131
    • /
    • 2003
  • Component-based development approach is used in modern software system development projects that are very complex and large-scale. Technical components are more effective rather than business components in software development. However, on the Microsoft .net environment, the technical component-based development issues are not adopted. Moreover, software architecture on the .net environment is not studied yet because the development platform is recently used in the development of enterprise-level system. This paper proposes a technical component-based software architecture on .net environment. Seven technical components - configuration, data access, exception, file I/O, log, message, and paging - are contained in the architecture. The proposed architecture enables developers to reduce development time and to concentrate business logic rather than architectural issues. To verify the proposed architecture and the components, a partner management system is developed based on the architecture.

A Method of Domain Analysis and Design for Component-based Software Development (컴포턴트 기반 소프트웨어 개발을 위한 도메인 분석 및 설계 방법)

  • Ha, Hyunju;Moon, Mikyung;Yeum, Keunhyuk
    • Journal of KIISE:Software and Applications
    • /
    • v.28 no.10
    • /
    • pp.743-756
    • /
    • 2001
  • Component-based software development (CBSD) is a method for building large software system by integrating previously-existing software components. Software development method using components has several advantages such that reducing time to delivery and development costs, and increasing productivity etc. But integrating components developed from multiple vendors is too difficult As a result it is required the understanding on the context of use to develop reusable components. The context of use for software component of determined by software architecture. Therefore, it is possible to develop an application based on components if is based on software architecture. Also, it is essential to consider domain concepts for CBSD. To increase the reusability of components. we should develop components in a domain which is a set of related systems. In this paper, we proposed a domain architecture development methodology that supports component-based software development. Domain architecture that represents components and their relationship is produced through domain analysis and design process. We believe that component development methodology using proposed domain architecture can efficiently develop highly reusable components as well as easily develop and application using information acquired from domain architecture.

  • PDF

A Study on the XML-based Software Components Specification Method and Supporting Tool Design (XML 기반 컴포넌트 명세서 생성을 위한 지원 도구 설계에 관한 연구)

  • 박준범;오수열
    • Journal of the Korea Society of Computer and Information
    • /
    • v.7 no.2
    • /
    • pp.34-39
    • /
    • 2002
  • This paper proposed a kind of software component specification method based on XML. We define a document type definition(DTD) of software component specification for the XML representation of a component. The semantic relationship of the component elements in diagrams of component specification must be Presented by the XML tag. This paper also designs the supporting tool for the representation of the software component specification.

  • PDF

Unit Testing for the AUTOSAR Software Component (AUTOSAR 소프트웨어 컴포넌트의 유닛 테스트 방법)

  • Kum, Dae-Hyun;Lee, Seong-Hun;Park, Gwang-Min;Son, Byeong-Jeom
    • Journal of KIISE:Computing Practices and Letters
    • /
    • v.16 no.11
    • /
    • pp.1061-1065
    • /
    • 2010
  • AUTOSAR, a standard software platform for automotive, has been developed to manage software complexity and improve software reuseability. However Automated and standardized testing is needed to improve reliability and reduce time and effort on testing. Fundamental functionality of AUTOSAR RTE and basic software modules is guaranteed by using an AUTOSAR tool, but application software components have to be tested thoroughly. In this paper, we suggest a test system for the AUTOSAR software component using TTCN-3, a standardized testing language. Test execution system and test cases for the software component are generated automatically from AUTOSAR XML containing software design information. With the proposed testing techniques we can reduce time and effort to build the testing system.

Cost Measurement Indicators and Maintenance Cost Estimation Model for Maintenance of Component-based Software (컴포넌트 소프트웨어의 유지보수를 위한 비용 측정지표 및 비용 추정 모델)

  • Jo, Ju-Yeon;Rhew, Sung-Yul
    • The KIPS Transactions:PartD
    • /
    • v.16D no.3
    • /
    • pp.353-360
    • /
    • 2009
  • Most information systems are component-based and developed by outsourcing, and developed software is maintained integrative. However, studies on cost measurement indicators and cost estimation model have not been performed sufficiently, which are foundational to enhance the productivity and efficiency of maintenance. This study suggests indicators to measure maintenance cost for component-based software and examines maintenance cost estimation model of component software by the measurement indicators suggested. In order to generate the indicators to measure the component-based maintenance cost, the previously proposed indicators are summarized comparatively. To estimate the measurement indicators of component-based software, it makes a comparison of the previously proposed indicators and arranges them. We classify the measurement indicators by how to apply according to maintenance types of component software and then we propose the cost measurement indicators. Moreover, we propose the cost estimation model according to the maintenance types of component software using the suggested measurement indicators suggested. With the suggested estimation model, a case study is performed and its validity is verified.

Extraction and Specification Technique of Java Components for Reuse of Java Programs (자바 프로그램의 재사용을 위한 자바 빈즈 컴포넌트의 추출 및 명세화 기법)

  • Lee, Seong-Eun;Kim, Yeong-Ik;Ryu, Seong-Yeol
    • The Transactions of the Korea Information Processing Society
    • /
    • v.7 no.5
    • /
    • pp.1388-1400
    • /
    • 2000
  • An important technical issue in recent software development is to make needed software by the composition of components that are assemblable, and configurable, and independently extracted. The main advantage of component-based software development is reducing development time and cost. It is more cost-effective in development time to use components that are already developed than developing from scratch. There are two ways of component-based software development: one is to compose self-developed components, and the other is to by the components developed by third-parties and compose them. In the second case, existing non component programs must can be used for reuse in the component development. In this paper, we approach two methods for increase of reusability of Java program. First, we suggest the technique of extracting the elements suitable for the Beans component model from Java program, and then we show a process and a guideline of converting the extract elements into the Beans component model. Second, we suggest a technique of automatically extracting component information from the Java Beans component, expressing them in XML, its is possible to reuse the efficient component environment.

  • PDF

A Study on the Design and Analysis of Component based Game Development (컴포넌트를 이용한 게임 개발의 분석 및 설계에 관한 연구)

  • Jung, Hae-Ryong;Jung, Kwang-Ho
    • Journal of Korea Game Society
    • /
    • v.1 no.1
    • /
    • pp.73-79
    • /
    • 2001
  • The objective of this paper is to systematically establish the development of game software through the fusion of game implementation and component methodology. The development of game software has inconsistently accomplished without the consistent frame for the analysis and design of game development in the domestic environments. Therefore in case of the development of game software based on game component, although a lot of resources were required in the initial the accumulation of experience and the technology of reuse lead to the efficiency of the maintenance ultimately.

  • PDF

Software Component Reusability Metrics (소프트웨어 컴포넌트 재사용성 측정 메트릭)

  • 박인근;김수동
    • Journal of KIISE:Software and Applications
    • /
    • v.31 no.6
    • /
    • pp.760-772
    • /
    • 2004
  • Component Based Development(CBD) Methodology is widely used in software development lifecycle to improve software quality. The Component Based Development(CBD) results to improve software reusability and reduce development term and cost. For this reason, lots of Enterprises are trying to make their processes to components. But, there has been few quality assurance or reusability testing action to those components. Most software component users can not know how their components are reusable and what extent their components satisfy to th eir quality requirements. For this reason, this paper suggests that software components can be measured their reusability by metrics proposed by this paper. We propose that in measuring software component reusability, there are direct metrics and indirect metrics. The results made by direct metrics are suggested to measure indirect metrics, so results to obtain reusability metrics.

Component Specification-based GPS Applications Development Process (컴포넌트 명세기반의 GPS 애플리케이션 개발 프로세스)

  • Lee, Sang Young;Lee, Yoon Hyeon
    • Journal of Korea Society of Digital Industry and Information Management
    • /
    • v.8 no.3
    • /
    • pp.11-22
    • /
    • 2012
  • GIS have expanded the use-range to the various application area with the advantage of interface environment, the various geographical operation. topological analysis by the friendly user. Early GIS software was developed as monolithic tool in which all functions packed in the same software. But, these GIS software have the problems of the high cost of constructing system, closely related system architecture and the reusability. And there is a lack of interoperability between them because most of them have their own unique data format according to their practical application fields. So Component is a unit that it is cohesive software package which is able to be developed and arranged independently and connected with another component for necessary system composition. In this paper, we analyze the requirements for component design and component specifications based on the extracted components. Commonly used to extract components from the requirements of the GPS component-based development process is presented. These components extracted by the process can be used to assemble components only. In particular, applications for developers to add features specific case without affecting the other components that can be modify the component.