• Title/Summary/Keyword: Software components

Search Result 1,387, Processing Time 0.038 seconds

Applying Software Reuse to Improve Software Quality and Productivity

  • Lai Sen-Tarng
    • Proceedings of the Korean Society for Quality Management Conference
    • /
    • 1998.11a
    • /
    • pp.43-50
    • /
    • 1998
  • The cause of software crisis is that software quality and productivity can not meet the requirement of software market. In order to resolve the software crisis, there are many approaches to be proposed. Software reuse is one of the high potential approaches to improve software quality and productivity. Some high-tech countries (like USA, Japan) have proposed and studied the topics of software reuse in 1970 and got several results. In software development procedure, the products of detailed design and implement phases are simple, definite and suitable for reuse. In this paper, the necessary documents of reusable software component will be proposed, and how to select and evaluate the software components with high reuse potential and high quality will be discussed and recommended.

  • PDF

Domain Analysis and Component Extraction for Defence Software (국방 소프트웨어의 도메인 분석과 컴포넌트 추출)

  • Song, Ho-Jin;Choi, Eun-Man;Jeon, Byung-Kook;Kim, Young-Chul
    • The KIPS Transactions:PartD
    • /
    • v.11D no.1
    • /
    • pp.123-132
    • /
    • 2004
  • Defense software has short of interoperability due to the vertical development method which is dependent heavily on application area and development environments. In order to prevent from lack of reusability and operability in application domain software development technology needs component concept and makes shift to the trend of domestic software component industry. This paper covers the research topics such as domain analysis and component architecture to improve and extend reusability and inter-operability for defense information system by two approaches, i.e. CBW (Command Based Work flow) analysis and UML components identification.

A Development of The Dynamic Reconfigurable Components based on Software Product Line : Guided Weapon System (소프트웨어 프로덕트 라인공학을 적용한 동적 재구성 컴포넌트 개발 : 유도무기체계)

  • Lee, Jae-Oh;Lee, Jae-Jin;Suk, Jee-Beom;Seo, Yoon-Ho
    • Journal of the Korea Society for Simulation
    • /
    • v.19 no.4
    • /
    • pp.179-188
    • /
    • 2010
  • The concern of Software Product Line(SPL) engineering is spreading widely because the program or product developers are able to satisfy the customer's demands quickly and give a way to handle maintenance efficiently. SPL is a reuse paradigm that reuse common parts and adopts variable parts optionally to form a differentiated product by analyzing domains. Purposes of this paper are to design an architecture which has a dynamic reconfiguration function and to develop basic components which are the basic unit of reconfiguration to raise the reuse level of the guided weapon system using the SPL. Initially we design an architecture and define basic components for developing a dynamic reconfigurable components based on SPL. Then we develop the composer for physical components and behavior components referenced by behavior models of OneSAF.

Defining of Architectural Patterns through Formalization of Architectural Styles (소프트웨어 구조스타일의 정형화를 통한 조립형 구조패턴의 정의)

  • Kung, Sang-Hwan
    • The KIPS Transactions:PartD
    • /
    • v.9D no.5
    • /
    • pp.877-886
    • /
    • 2002
  • The problem of software reuse is dealt in two approaches. One is to build a new software by composing of the built-in components, and the other is to reuse architectural patterns that most of software system is generally composed of. Although the two approaches are important in design of software architecture, we could find outstanding difference in what kind of building blocks they use. The component based software design makes uses of building blocks whose contents are filled in by someone, on the other hand, the architectural pattern based software design is not interested in the contents of building blocks, but in the framework for building blocks including relationship of the building blocks. The paper purposes to find architectural patterns which are commonly found in diverse applications and help software architects reuse them in the software design process. We refine the architectural styles which is the well-known concept for software architecture design, and refine them as architectural components or templates which can be parts of software architecture.

Preliminary design of control software for SDSS-V Local Volume Mapper Instrument

  • Kim, Changgon;Ji, Tae-geun;Ahn, Hojae;Yang, Mingyeong;Lee, Sumin;Kim, Taeeun;Pak, Soojong;Konidaris, Nicholas P.;Drory, Niv;Froning, Cynthia S.;Hebert, Anthony;Bilgi, Pavan;Blanc, Guillermo A.;Lanz, Alicia E.;Hull, Charles L;Kollmeier, Juna A.;Ramirez, Solange;Wachter, Stefanie;Kreckel, Kathryn;Pellegrini, Eric;Almeida, Andr'es;Case, Scott;Zhelem, Ross;Feger, Tobias;Lawrence, Jon;Lesser, Michael;Herbst, Tom;Sanchez-Gallego, Jose;Bershady, Matthew A;Chattopadhyay, Sabyasachi;Hauser, Andrew;Smith, Michael;Wolf, Marsha J;Yan, Renbin
    • The Bulletin of The Korean Astronomical Society
    • /
    • v.46 no.1
    • /
    • pp.39.1-39.1
    • /
    • 2021
  • The Local Volume Mapper(LVM) project in the fifth iteration of the Sloan Digital Sky Survey (SDSS-V) will produce large integral-field spectroscopic survey data to understand the physical conditions of the interstellar medium in the Milky Way, the Magellanic Clouds, and other local-volume galaxies. We are developing the LVM Instrument control software. The architecture design of the software follows a hierarchical structure in which the high-level software packages interact with the low-level and mid-level software and hardware components. We adopt the spiral software development model in which the software evolves by iteration of sequential processes, i.e., software requirement analysis, design, code generation, and testing. This spiral model ensures that even after being commissioned, the software can be revised according to new operational requirements. We designed the software by using the Unified Modeling Language, which can visualize functional interactions in structure diagrams. We plan to use the SDSS software framework CLU for the interaction between components, based on the RabbitMQ that implemented the Advanced Message Queuing Protocol (AMQP).

  • PDF

Component-Z: A Formal Specification Language Extended Object-Z for Designing Components (Component-Z: Object-Z를 확장한 컴포넌트 정형 명세 언어)

  • 이종국;신숙경;김수동
    • Journal of KIISE:Software and Applications
    • /
    • v.31 no.5
    • /
    • pp.677-696
    • /
    • 2004
  • Component-based software engineering (CBSE) composes reusable components and develops applications with the components. CBSE is admitted to be a new paradigm that reduces the costs and times to develop software systems. The high quality of component designs can be assured if the consistency and correctness among the elements of a component are verified with formal specifications. Current formal languages for components include only some parts of contracts between interfaces, structural aspects and behavioral aspects of component, component-based system, component composition and variability. Therefore, it is not adequate to use current formal languages in all steps of a component design process. In this paper, we suggest a formal language to specify component designs Component-Z. Component-Z extends Object-Z, adds new notations to specify components. It can be possible to specify interfaces, the inner structure of a component, inner workflows, and workflows among interfaces with Component-Z. In addition, Component-Z provides the notations and semantics to specify variability with variation points, variants and required interfaces. The relation between interfaces and components is defined with mapping schemas. Parallel operator is used to specify component composition. It can be possible to describe deployed components with the specifications of component-based systems. Therefore, the formal specification language proposed in this paper can represent all elements to design components. In the case study, we specify an account management system in a bank so that we show that Component-Z can be used in all steps of component design.

Classification and Retrieval of Object - Oriented Reuse Components with HACM (HACM을 사용한 객체지향 재사용 부품의 분류와 검색)

  • Bae, Je-Min;Kim, Sang-Geun;Lee, Kyung-Whan
    • The Transactions of the Korea Information Processing Society
    • /
    • v.4 no.7
    • /
    • pp.1733-1748
    • /
    • 1997
  • In this paper, we propose the classification scheme and retrieval mechanism which can apply to many application domains in order to construct the software reuse library. Classification scheme which is the core of the accessibility in the reusability, is defined by the hierarchical structure using the agglomerative clusters. Agglomerative cluster means the group of the reuse component by the functional relationships. Functional relationships are measured by the HACM which is the representation method about software components to calculate the similarities among the classes in the particular domain. And clustering informations are added to the library structure which determines the functionality and accuracy of the retrieval system. And the system stores the classification results such as the index information with the weights, the similarity matrix, the hierarchical structure. Therefore users can retrieve the software component using the query which is the natural language. The thesis is studied to focus on the findability of software components in the reuse library. As a result, the part of the construction process of the reuse library was automated, and we can construct the object-oriented reuse library with the extendibility and relationship about the reuse components. Also the our process is visualized through the browse hierarchy of the retrieval environment, and the retrieval system is integrated to the reuse system CARS 2.1.

  • PDF

A 4D Process for Service Oriented Software Development (서비스 기반 소프트웨어 개발을 지원하는 4D 프로세스)

  • Park, Joon-Seok;Moon, Mi-Kyeong;Nam, Tae-Woo;Yeom, Keun-Hyuk
    • Journal of KIISE:Software and Applications
    • /
    • v.35 no.11
    • /
    • pp.653-660
    • /
    • 2008
  • Recently, Service-oriented computing is the emerging computing paradigm. In this paradigm, we require the practical process model to support service oriented software development. The well-known development methods e.g., Unified Software Development Process, UML components have been proposed focused on component. So, these methods cannot support service-oriented computing concepts such as service definition, binding and composition concepts using Business Process Execution Language (BPEL). Also, a few proposed service-oriented approach, for example Service Oriented Unified process (SOUP), and Service Oriented Modeling and Architecture (SOMA) have appeared. However, these approaches do not explicitly represent detailed guideline, artifacts and approach. Therefore, in this paper we propose a practical and simple process model to support service oriented software development. Also, we explicitly represent process model and artifact using Software Process Engineering Metamodel (SPEM) which is proposed by OMG. By using our approach, it can enhance systematization and effectiveness for service-oriented software development.

A Study on the Construction and Improvement of Software Process Infrastructure for Software Firms In Korea (국내 소프트웨어 사업자의 프로세스 기반구조 구축 및 개선 방안 연구)

  • Ahn, Yeon-Shick;Moon, Song-Chul;Kim, Dong-Soo
    • Asia pacific journal of information systems
    • /
    • v.14 no.4
    • /
    • pp.23-47
    • /
    • 2004
  • This study was tried for the improvement of software process ability of the software firms, and analyzed empirically the impact that a software process infrastructure level influences on the software process level and process performance. The questionnaire were developed and data were collected from the process improvement correspondences or project quality managers of the 78 software firms. The result was shown that management-organization infrastructure was composed of software process improvement organization's role and activity, process standard and education, management system and supporting, management guides and procedures. And organization's standard development procedure or criteria, process asset, process support tools were included in technical infrastructure. This study provides that some components of software process infrastructure had an significant influence on the process level, process infrastructure management level, and software process performance.

Visual Component Assembly and Tool Support Based on System Architecture

  • Lee, Seung-Yun;Kwon, Oh-Cheon;Shin, Gyu-Sang
    • ETRI Journal
    • /
    • v.25 no.6
    • /
    • pp.464-474
    • /
    • 2003
  • Component-based development leverages software reusability and reduces development costs. Enterprise JavaBeans (EJB) is a component model developed to reduce the complexity of software development and to facilitate reuse of components. However, EJB does not support component assembly by a plug-and-play technique due to the hard-wired composition at the code level. To cope with this problem, an architecture for EJB component assembly is defined at the abstract level and the inconsistency between the system architecture and its implementation must be eliminated at the implementation level. We propose a component-based application development tool named the COBALT assembler that supports the design and implementation of EJB component assembly by a plug-and-play technique based on the architecture style. The system architecture is first defined by the Architecture Description Language (ADL). The wrapper code and glue code are then generated for the assembly. After the consistency between the architecture and its implementation is checked, the assembled EJB components are deployed in an application server as a new composite component. We use the COBALT assembler for a shopping mall system and demonstrate that it can promote component reuse and leverage the system maintainability.

  • PDF