• Journal of Information Technology Applications and Management
• /
• 제19권2호
• /
• pp.135-147
• /
• 2012

Software architecture, as a blueprint for the system, should provide a robust foundation for design, implementation, and maintenance, for communication and documentation, and for reasoning about important system properties. Software architecture plays a central role during the whole software life-cycle. There are so diverse definitions of the software architecture, however, and there is no common agreement about what software architecture is. Examining 27 'published' definitions of software architecture, we synthesize an extensive model on the essential elements of software architecture, which consists of components, interaction among components, well-formed structure, reasons, and various perspectives. Further, we explore the possibility of unifying diverse software architecture definitions into a software architecture life-cycle model.

• Journal of Information Technology Applications and Management
• /
• 제22권3호
• /
• pp.143-167
• /
• 2015

This paper addresses the issue how the total life cycle cost may be minimized and how the cost should be allocated to the acquirer and developer. This paper differentiates post life cycle change (PLCC) endeavors from PLCC activities, rigorously classifies PLCC endeavors according to the result of PLCC endeavors, and rigorously defines the life cycle cost of a software product. This paper reviews classical definitions of software 'maintenance' types and proposes a new typology of PLCC activities too. The proposed classification schemes are exhaustive and mutually exclusive, and provide a new paradigm to review existing literatures regarding software cost estimation, software 'maintenance,' software evolution, and software architecture from a new perspective. This paper argues that the long-term interest of the acquirer is not protected properly because warranty period is typically too short and because the main concern of warranty service is given to removing the defects detected easily. Based on the observation that defects are caused solely by errors the developer has committed for software while defects are often induced by using for hardware (so, this paper cautiously proposes not to use the term 'maintenance' at all for software), this paper argues that the cost to remove defects should not be borne by the acquirer for software.

• Journal of Information Technology Applications and Management
• /
• 제20권3호
• /
• pp.1-18
• /
• 2013

Software architecture is the blueprint for a software system and should provide consistent guidelines for design, implementation, and maintenance throughout the entire lifecycle of the system. Components, interactions between the components, well-formed structure, reasons, and various perspectives reflecting various stakeholders' concerns changing through the phases of software lifecycle are the key elements of software architecture. The architect identifies and engages the stakeholders, understands and captures stakeholder's concerns including those regarding life cycle, and lets the concerns reflected in the architecture. To do so, architect should take into consideration various contextual elements regarding the system too. We make an extended list of the elements, especially those of business application software architecture, that the architect should take into consideration and construct a model of the relationships between the elements.

• Journal of Information Technology Applications and Management
• /
• 제20권2호
• /
• pp.69-87
• /
• 2013

The expanded spiral model in this paper consists of five processes of architecture design, architectural construction, architectural maintenance, operation, and architectural management. The former four processes are executed alternatively, while the latter architectural management process is executed continuously interacting with the other processes during the whole life cycle of the system. The expanded spiral model provides a conceptual framework to sort discussions of architectural degeneration into those of product-oriented processes and those of management processes, making it possible to incorporate the models and body of knowledge about project and program management especially those of Project Management Institute, into discussions of architectural degeneration. A good architecture decomposes the software-intensive system into components mutually interacting in a well-formed structure. The architecture design process and the architectural construction process together create the object system with well-designed architecture. The architectural maintenance process prevents the implemented architecture deviate from the designed architecture. The architectural management process monitors the changes of requirements including architecturally significant requirements, supports the other processes to be executed reflecting various perspectives of stake-holders, and creates and documents the reasons of architectural decisions, which is considered as a key element of the architecture.

• 한국철도학회:학술대회논문집
• /
• 한국철도학회 2005년도 추계학술대회 논문집
• /
• pp.1033-1038
• /
• 2005

As a global effort to conservate the environment, life cycle assessment(LCA) which considers the environmental impact through the life cycle of a product, from acquiring of resources to scrapping, has been actively applied. The LCA is a tool to calculate quantitatively the environmental impacts caused by products or services through their life cycles. The list of numerous data should be analyzed, stored and conducted in order to assess the environmental impacts. Therefore, it is necessary to develop a software for LCA, which can perform the interpretation as well as the environment impact assessment to execute the analysis of such a large number of data effectively. At this time, for the existing some kinds of general LCA softwares, the information about all of input and output should be fed directly and the conclusion is deduced by linking to the database from the public authorized organizations. That makes it possible to evaluate the environmental grades accurately, but it is too slow and difficult for general users to operate and applied it into an electric motor unit(EMU). Therefore, in this research, the basic model was designed, which is based on construction of database structure of the software and organization of architecture, to develop an advanced software for EMU according to user and purpose of it by benchmarking of domestic and international softwares. The result of this study would be applied to develop the LCA software in the future.

• 정보화연구
• /
• 제10권3호
• /
• pp.323-334
• /
• 2013

사업기획, 프로젝트 관리, 품질 등 정보시스템의 구축에 관한 연구는 많이 수행되었다. 정보시스템의 수명주기에서 신규투자는 20%의 자원 비중을 차지하고 있고, 유지보수와 인프라가 자원 비용의 80%를 차지하고 있어 유지보수에 대한 관심과 연구가 매우 필요하다. 그동안의 정보시스템 경제적 수명주기 연구는 유지보수 비용을 활용하여 진행되었으며, 인프라 비용의 반영이 정보시스템의 경제적 수명주기에 어떤 영향을 주는지에 대한 연구가 없었다. 본 연구는 정보시스템 수명주기 비용의 40%를 차지하고 있는 인프라 비용을 경제적 수명주기 산정에 어떻게 반영해야 하는지, 그리고 인프라 비용 반영에 따른 정보시스템의 경제적 수명주기 변화에 대하여 살펴보았다.

• 융합정보논문지
• /
• 제7권2호
• /
• pp.67-76
• /
• 2017

소프트웨어 활용의 수명주기가 단축되고, 다양한 형태의 사용자 기능을 지원하기 위하여 소프트웨어 아키텍처 개발의 중요성이 부각되고 있다. 소프트웨어 아키텍처가 새로운 기능을 갖도록 확장에 유연하고 안정적으로 개발된다면, 새로은 시장의 요구에 빠르게 대응할 수 있다. 본 연구에서는 새로운 기능 개발의 수명주기가 짧아지고 있고, 안정적인 소프트웨어 시스템 개발을 위하여 오픈 소스의 설계 복구를 통한 재사용을 고려하는 아키텍처 설계 기법을 제안한다. 소프트웨어 아키텍처를 기반으로 소프트웨어 시스템을 개발하기 위하여 오픈 소스를 사용하는 경우, 매우 신속한 개발이 가능해 질 뿐만 아니라, 이미 검증된 오픈 소스를 사용함으로써 개발 시스템에 대한 신뢰성도 증진시킬 수 있다.

• 한국정보처리학회논문지
• /
• 제7권6호
• /
• pp.1803-1809
• /
• 2000

With the wide usage of the Internet, there use of pre-developed software is becoming important more and more in the development of various communication software. In this paper, the architecture to reuse the communication software is proposed. It is applied to the development of MIB-II system group of SNMP agent software for reusing. If Communication software is developed using this architecture, the software development life cycle will be abridged and the development cost will be reduced.

• 한국지능정보시스템학회:학술대회논문집
• /
• 한국지능정보시스템학회 2001년도 The Pacific Aisan Confrence On Intelligent Systems 2001
• /
• pp.249-255
• /
• 2001

Different kinds of information are used when solving tasks that arise in the life cycle of an applied knowledge based system (KBS). Many of these tasks are still under investigation. Their solving methods are often researched independently of each other due to complexity of the tasks. As a result, systems that realize these methods turn out to be incompatible and therefore could not be used together in the lifecycle of a KBS. The following problem arises here: how to support the full life cycle of a KBS. This paper introduces a class of computer knowledge banks that are intended to support the full life cycle of KBSs. Primary tasks that arise in the full life cycle of a KBS are analyzed. The architecture of a knowledge bank of the introduced class is presented, including an Information Content, a Shell of the Information Content and a Software Content. General requirements on these components are formulated on the basis of the analysis. These requirements depend on the current state of understanding in the life cycle of KBSs.

• 정보처리학회논문지D
• /
• 제12D권3호
• /
• pp.395-408
• /
• 2005

유비쿼터스 컴퓨팅은 매우 광범위한 기술 분야에 적용될 수 있고 완벽한 사용자 요구를 필요로 하며, 많은 시나리오와 기술들을 포함하고 있으므로 이러한 요구를 충족시켜주는 새로운 소프트웨어 개발 툴과 방법론이 필수적이다. 이를 위한 새로운 기술로써 소프트웨어 프로덕트 라인은 공통의 유사한 기능을 가지고 있는 소프트웨어 제품 혹은 소프트웨어 시스템 집합으로 특정 영역의 시장과 용도의 요구사항에 따라 재사용 가능한 아키텍처 및 컴포넌트를 구성함으로써 생산성과 품질을 향상시킬 수 있다. 특히, 시스템을 분할하고 구조화하여 시스템의 성능과 효율성을 향상시킬 수 있는 소프트웨어 아키텍처 개념이 중요시되면서 아키텍처의 개발과 평가에 대한 체계적인 연구가 필요하다. 본 논문에서는 CBD(Component Based Development)를 기반한 소프트웨어 프로덕트 라인(PLD : Product Line based Development)을 도입하여 모바일 비즈니스 도메인에 적합한 모바일 응용 시스템 아키텍처(MASA. Mobile Application System Architecture)를 제시한다.