• 제목/요약/키워드: Software Development lifecycle

검색결과 49건 처리시간 0.027초

발전설비 최적 정비를 위한 독립형 위험도 평가 소프트웨어 개발 (Development of Stand-Alone Risk Assessment Software for Optimized Maintenance Planning of Power Plant Facilities)

  • 최우성;송기욱;김범신;장성호;이상민
    • 대한기계학회논문집A
    • /
    • 제39권11호
    • /
    • pp.1169-1174
    • /
    • 2015
  • 위험도 평가 기술은 주로 플랜트의 많은 운영설비 중 대형사고나 피해를 유발할 수 있는 위험설비를 선별하는 목적으로 개발되었다. 현재 발전소에 설치되어 있는 설비관리시스템에는 초기 버전의 위험도 평가 모듈이 설치되어 있으나 문진 위주로 구성되어 통계적 기법에 기반을 둔 고장 확률 평가보다는 평가자의 주관적인 판단에 따라 평가 결과가 좌우되었다. 또한 발전회사 서버에 기반하였기 때문에 평가자가 공간 및 시간의 제약을 받을 수 밖에 없고 현장 활용에 한계가 있었다. 본 논문에서는 문진 대신 해석적 분석을 이용한 기본 고장확률을 계산하고 현장 검사 결과 및 검사 효용도를 분석할 수 있는 독립형 위험도 평가 소프트웨어를 개발하였다. 독립형으로 현장 운용이 가능하며 최적 정비주기 예측 및 현장검사 결과에 대한 입출력 기능이 있기 때문에 정비에 직접 참여하는 현장 사용자뿐만 아니라 발전 설비의 수명연장 및 교체를 결정해야 하는 엔지니어에게 유용한 정보를 제공할 것이다.

클래스계층구조의 품질평가척도를 기반으로 하는 재구성기법 (A Metrics-Based Approach to the Reorganization of Class Hierarchy Structures)

  • 황석형;양해술;황영섭
    • 정보처리학회논문지D
    • /
    • 제10D권5호
    • /
    • pp.859-872
    • /
    • 2003
  • 클래스계층구조는 객체지향 소프트웨어의 중심적인 구성요소가 되며, 따라서 이에대한 품질은 매우 중요하다. 좋은 품질을 갖춘 클래스계층 구조를 구축하는 것은 객체지향 소프트웨어 개발에 있어서 매우 중요한 작업이지만, 좋은 품질의 클래스계층구조를 구축하는 작업은 수월하지 않다. 더욱이, 반복 및 점증적인 소프트웨어 개발에 있어서, 요구사양에 적합하도록 개발중인 클래스계층구조를 재구성하거나 세련시키는 작업이 빈번히 발생한다. 따라서, 객체지향 개발자들이 이와같은 클래스계층구조의 재구성 작업을 수행할 경우에 도움이 될 수 있는 기법 및 도구들에 대한 관심이 증가하고 있다. 본 논문에서는, 클래스계층구조의 복잡도를 일정수준 측정가능한 몇가지 평가척도를 제안하고, 이러한 평가척도들을 바탕으로 클래스계층구조를 재구성하는 알고리즘들을 정의한다. 또한, 각 알고리즘들에 대하여, 알고리즘을 적용하기 전과 후의 각 클래스계층구조들로부터 생성할 수 있는 객체들의 집합이 변화하지 알고 보존됨을 증명하였다. 본 논문에서 제안하는 재구성기법은 클래스계층구조의 구축 및 재구성 등의 지침으로서 사용할 수 있으며, 이러한 평가척도들을 기반으로 하는 클래스계층구조의 재구성 알고리즘들은 객체지향 소프트웨어 개발시에 유용한 도구로서 개발자들에게 도움이 될 수 있다.

4-계층 모델 기반의 선박 수명주기관리 시스템 프레임워크 (Framework of Ship PLM System Based Upon Four-Tier Model)

  • 김승현;이장현;이경호;서흥원
    • 한국CDE학회논문집
    • /
    • 제15권5호
    • /
    • pp.362-374
    • /
    • 2010
  • Product Lifecycle Management (PLM) is an integrated business approach to manage the creation and distribution of product information throughout the product development process. From the product perspective, PLM encompasses a holistic approach to product development and product information management. It supports the integrated product information in conjunction with the efficient product structures and BOM (Bill Of Material), user interfaces, proper functions, design processes and enterprise integration. Therefore, PLM should not only satisfy required functions as an enterprise software but also offer a systematic method for the efficient application from the initial stage of its development. Recently, many shipyards have been considering the PLM as a strategic solution to get the efficient management of product information such as 3-D models, BOM, drawings, documents, and the other product data. Though many studies on PLM are performed, most of them are performed in a function-based approach adequate for mass productive assembly industries. It could not help having limitations on applying the proper PLM system to the shipbuilding business since the requirements of shipbuilding PLM are too diverse and huge to design the architecture. This study presents the PLM framework which effectively reflects the diverse requirements of shipbuilding PLM. In order to get the macroscopic architecture of shipbuilding PLM, authors suggest the four-tier architecture model which considers the various requirements collected from shipyards. Entities of ship design data are modeled BOM in terms of product structure and hierarchical class diagram. Applicable functions of shipbuilding PLM are also investigated by analysis of issues of ship design. Finally, by reflecting the design process of shipbuilding, To-Be ship design procedure cooperated with the suggested PLM framework has been summarized.

CIA-Level 기반 보안내재화 개발 프레임워크 (CIA-Level Driven Secure SDLC Framework for Integrating Security into SDLC Process)

  • 강수영;김승주
    • 정보보호학회논문지
    • /
    • 제30권5호
    • /
    • pp.909-928
    • /
    • 2020
  • 미국 정부는 1970년대 초반부터 모의해킹만으로는 제품의 보안 품질을 향상시킬 수 없다는 것을 인지하기 시작하였다. 모의해킹팀의 역량에 따라 찾을 수 있는 취약점이 달라지며, 취약점이 발견되지 않았다고 해서 해당 제품에 취약점이 없는 것은 아니기 때문이다. 제품의 보안 품질을 향상시키기 위해서는 결국 개발 프로세스 자체가 체계적이고 엄격하게 관리되어야 함을 깨달은 미국 정부는 1980년대부터 보안내재화(Security by Design) 개발 방법론 및 평가 조달 체계와 관련한 각종 표준을 발표하기 시작한다. 보안내재화란 제품의 요구사항 분석 및 설계 단계에서부터 일찍 보안을 고려함으로써 제품의 복잡도(complexity)를 감소시키고, 궁극적으로는 제품의 신뢰성(trustworthy)을 달성하는 것을 의미한다. 이후 이러한 보안내재화 철학은 Microsoft 및 IBM에 의해 Secure SDLC라는 이름으로 2002년부터 민간에 본격적으로 전파되기 시작하였으며, 현재는 자동차 및 첨단 무기 체계 등 다양한 분야에서 활용되고 있다. 하지만 문제는 현재 공개되어 있는 Secure SDLC 관련 표준이나 가이드라인들이 매우 일반적이고 선언적인 내용들만을 담고 있기 때문에 이를 실제 현장에서 구현하기란 쉽지 않다는 것이다. 따라서 본 논문에서 우리는 Secure SDLC를 기업체가 원하는 수준에 맞게 구체화시키는 방법론에 대해 제시한다. 우리가 제안하는 CIA(functional Correctness, safety Integrity, security Assurance)-Level 기반 보안내재화 프레임워크는 기존 Secure SDLC에 증거 기반 보안 방법론(evidence-based security approach)을 접목한 것으로, 우리의 방법론을 이용할 경우 첫째 경쟁사와 자사간의 Secure SDLC 프로세스의 수준 차이를 정량적으로 분석할 수 있으며, 둘째 원하는 수준의 Secure SDLC를 구축하는데 필요한 상세한 세부 활동 및 산출해야 할 문서 등을 쉽게 도출할 수 있으므로 실제 현장에서 Secure SDLC를 구축하고자 할 때 매우 유용하다.

자동차 개발 프로세스에서의 보안 내재화 방법론 (A Methodology for Integrating Security into the Automotive Development Process)

  • 정승연;강수영;김승주
    • 정보처리학회논문지:소프트웨어 및 데이터공학
    • /
    • 제9권12호
    • /
    • pp.387-402
    • /
    • 2020
  • 기존의 자동차 개발은 주로 정확성(Correctness) 및 안전성(Safety) 확보에 초점을 맞추어 왔으며, 이에 반해 보안성(Security)은 비교적 소홀하게 다루어져 왔다. 하지만 최근 자동차의 인터넷 연결성이 높아짐에 따라 자동차 해킹 사례가 증가하면서, 유엔유럽경제위원회(United Nations Economic Commission for Europe, UNECE)와 같은 국제기관은 자동차 개발에 대한 보안성을 확보하기 위해 사이버보안 규제를 준비하고 있다. 다른 IT 제품과 마찬가지로 자동차 사이버보안 규제에서 또한 개발 초기부터 보안성을 고려하는 "보안 내재화(Security by Design)"의 개념을 강조한다. 특히 자동차 개발은 생명주기가 길고 공급망이 복잡하기 때문에 개발 이후에 아키텍처를 변경하는 것이 매우 어려우므로, 자동차 개발에 있어 보안 내재화는 기존 IT 제품에 비해 훨씬 더 중요시된다. 그러나 문제는 아직 자동차 개발 과정에 보안을 내재화하는 구체적인 방법론이 제시되지 못하고 있다는 것이다. 이에 본 논문에서는 자동차 보안 내재화를 위한 구체적인 방법론을 제안한다. 본 논문에서 제안된 방법론을 통해 자동차 제조사는 자동차 개발 과정에 있어 기능 안전성과 보안성의 측면을 동시에 고려할 수 있으며, 다가오는 UNECE 자동차 사이버보안 규제에 대한 인증에도 대응할 수 있을 것이다.

PDM 프레임워크 재 정의 도구 구축 (Construction of a Toolkit for Customizing a PDM Framework)

  • 김정아
    • 한국정보과학회논문지:컴퓨팅의 실제 및 레터
    • /
    • 제7권1호
    • /
    • pp.38-47
    • /
    • 2001
  • PDM(Product Data Management)분야는 일반적으로 제조업체에서 제품개발에 필요로 하는 제반정보를 제품기획단계부터 폐기단계까지 제품 생명주기(Lifecycle) 전반에 걸쳐 일원적으로 통합 관리하도록 하는 제품정보 통합관리 솔루션(solution)을 말한다. PDM 어플리케이션은 매우 크고 복잡함 영역이다. 프레임워크의 재사용은 단순한 소스코드나 어플리케이션 일부의 재사용이 아닌 소프트웨어 아키텍처의 재사용을 가능하게 함으로써 생산성 향상을 가능하게 하는 방법이다. 본 연구에서 PDM분야에서 프레임워크를 개발하게된 목적이기도 하다. 즉, PDM 프레임워크는 새로운 PDM 어플리케이션 개발에 드는 시간과 노력을 줄일 수 있게한다. 그러나 프레임워크는 대규모의 클래스들의 집합과 그들간의 복잡한 상호작용을 정의하고 있기 때문에, 프레임워크 기반 재사용 역시 재사용 공정을 지원하는 재사용 환경이 제공되어야한다. 이러한 도구를 바탕으로 큰 규모의 프레임워크를 이해하고 재 정의할 Hot spot을 효과적으로 식별할 수 있게된다. 본 연구에서는 저장소(repository)를 기반으로 컴포넌트와 컴포넌트에 대한 정보를 관리함으로써 컴포넌트를 이해하고 프레임워크에 정의된 hot spot에 새로운 요구사항을 정의하여 새로운 어플리케이션의 개발 과정을 효과적으로 지원하는 도구의 개발하였다.

  • PDF

웹 기반 산불위험지수 표출시스템에서의 UML(Unified Modeling Language) 설계 사례 (Case Study of UML(Unified Modeling Language) Design for Web-based Forest Fire Hazard Index Presentation System)

  • 조윤원;조명희;안승섭
    • 한국지리정보학회지
    • /
    • 제5권1호
    • /
    • pp.58-68
    • /
    • 2002
  • 최근 재해방재 사업에 대한 인식이 고조화 되면서 중앙정부나 지자체에서는 일반 국민들에게 국가에서 시행하는 재해방재 서비스를 웹이라는 공간을 통해 제공함으로서 국민들의 재해방지에 대한 관심을 부각시키려는 노력을 하고 있다. 특히, 사용자 누구든지 접근할 수 있는 웹 환경하에서 대규모의 국가적 재해로 연결될 수 있는 산불의 당일 발생위험지수를 시각화하는 서비스를 제공한다면 산불방지에 대한 국민들의 관심과 인식을 불러 일으켜 산불피해를 조금이나마 최소화하는데 도움을 줄 것이다. 본 연구에서 개발한 산불위험지수 예보시스템은 우리나라의 당일 산불위험지수를 지도상에 시각적으로 표출하고 위험지수산출에 관계되는 자료들을 텍스트 형식으로 서비스하도록 한다. 시스템 개발에 있어서는 컴포넌트를 이용하여 소프트웨어를 생산하는 방식으로 패러다임이 변해 가는 현재의 추세를 반영하기 위하여 UML(Unified Modeling Language)을 이용한 컴포넌트 기반 개발 프로세스를 설계하고 이를 통해 시스템 개발을 체계화하고자 한다. 개발된 시스템은 향후 사용자 요구 사항변경이나 서비스 영역의 확대 시 시스템 유지보수 측면에서 탄력성을 가질 것으로 예상되며 아울러 본 시스템과 유사한 서비스를 제공하는 다른 웹 GIS(Geographic Information System) 애플리케이션 개발에 있어서도 컴포넌트 재사용을 통하여 개발에 소요되는 비용과 시간을 최소화시킬 수 있을 것이라 사료된다.

  • PDF

통합병참지원에 관한 연구 (A Study on Integrated Logistic Support)

  • 나명환;김종걸;이낙영;권영일;홍연웅;전영록
    • 한국신뢰성학회:학술대회논문집
    • /
    • 한국신뢰성학회 2001년도 정기학술대회
    • /
    • pp.277-278
    • /
    • 2001
  • The successful operation of a product In service depends upon the effective provision of logistic support in order to achieve and maintain the required levels of performance and customer satisfaction. Logistic support encompasses the activities and facilities required to maintain a product (hardware and software) in service. Logistic support covers maintenance, manpower and personnel, training, spares, technical documentation and packaging handling, storage and transportation and support facilities.The cost of logistic support is often a major contributor to the Life Cycle Cost (LCC) of a product and increasingly customers are making purchase decisions based on lifecycle cost rather than initial purchase price alone. Logistic support considerations can therefore have a major impact on product sales by ensuring that the product can be easily maintained at a reasonable cost and that all the necessary facilities have been provided to fully support the product in the field so that it meets the required availability. Quantification of support costs allows the manufacturer to estimate the support cost elements and evaluate possible warranty costs. This reduces risk and allows support costs to be set at competitive rates.Integrated Logistic Support (ILS) is a management method by which all the logistic support services required by a customer can be brought together in a structured way and In harmony with a product. In essence the application of ILS:- causes logistic support considerations to be integrated into product design;- develops logistic support arrangements that are consistently related to the design and to each other;- provides the necessary logistic support at the beginning and during customer use at optimum cost.The method by which ILS achieves much of the above is through the application of Logistic Support Analysis (LSA). This is a series of support analysis tasks that are performed throughout the design process in order to ensure that the product can be supported efficiently In accordance with the requirements of the customer.The successful application of ILS will result in a number of customer and supplier benefits. These should include some or all of the following:- greater product uptime;- fewer product modifications due to supportability deficiencies and hence less supplier rework;- better adherence to production schedules in process plants through reduced maintenance, better support;- lower supplier product costs;- Bower customer support costs;- better visibility of support costs;- reduced product LCC;- a better and more saleable product;- Improved safety;- increased overall customer satisfaction;- increased product purchases;- potential for purchase or upgrade of the product sooner through customer savings on support of current product.ILS should be an integral part of the total management process with an on-going improvement activity using monitoring of achieved performance to tailor existing support and influence future design activities. For many years, ILS was predominantly applied to military procurement, primarily using standards generated by the US Government Department of Defense (DoD). The military standards refer to specialized government infrastructures and are too complex for commercial application. The methods and benefits of ILS, however, have potential for much wider application in commercial and civilian use. The concept of ILS is simple and depends on a structured procedure that assures that logistic aspects are fully considered throughout the design and development phases of a product, in close cooperation with the designers. The ability to effectively support the product is given equal weight to performance and is fully considered in relation to its cost.The application of ILS provides improvements in availability, maintenance support and longterm 3ogistic cost savings. Logistic costs are significant through the life of a system and can often amount to many times the initial purchase cost of the system.This study provides guidance on the minimum activities necessary to Implement effective ILS for a wide range of commercial suppliers. The guide supplements IEC60106-4, Guide on maintainability of equipment Part 4: Section Eight maintenance and maintenance support planning, which emphasizes the maintenance aspects of the support requirements and refers to other existing standards where appropriate. The use of Reliability and Maintainability studies is also mentioned in this study, as R&M is an important interface area to ILS.

  • PDF

Information Privacy Concern in Context-Aware Personalized Services: Results of a Delphi Study

  • Lee, Yon-Nim;Kwon, Oh-Byung
    • Asia pacific journal of information systems
    • /
    • 제20권2호
    • /
    • pp.63-86
    • /
    • 2010
  • Personalized services directly and indirectly acquire personal data, in part, to provide customers with higher-value services that are specifically context-relevant (such as place and time). Information technologies continue to mature and develop, providing greatly improved performance. Sensory networks and intelligent software can now obtain context data, and that is the cornerstone for providing personalized, context-specific services. Yet, the danger of overflowing personal information is increasing because the data retrieved by the sensors usually contains privacy information. Various technical characteristics of context-aware applications have more troubling implications for information privacy. In parallel with increasing use of context for service personalization, information privacy concerns have also increased such as an unrestricted availability of context information. Those privacy concerns are consistently regarded as a critical issue facing context-aware personalized service success. The entire field of information privacy is growing as an important area of research, with many new definitions and terminologies, because of a need for a better understanding of information privacy concepts. Especially, it requires that the factors of information privacy should be revised according to the characteristics of new technologies. However, previous information privacy factors of context-aware applications have at least two shortcomings. First, there has been little overview of the technology characteristics of context-aware computing. Existing studies have only focused on a small subset of the technical characteristics of context-aware computing. Therefore, there has not been a mutually exclusive set of factors that uniquely and completely describe information privacy on context-aware applications. Second, user survey has been widely used to identify factors of information privacy in most studies despite the limitation of users' knowledge and experiences about context-aware computing technology. To date, since context-aware services have not been widely deployed on a commercial scale yet, only very few people have prior experiences with context-aware personalized services. It is difficult to build users' knowledge about context-aware technology even by increasing their understanding in various ways: scenarios, pictures, flash animation, etc. Nevertheless, conducting a survey, assuming that the participants have sufficient experience or understanding about the technologies shown in the survey, may not be absolutely valid. Moreover, some surveys are based solely on simplifying and hence unrealistic assumptions (e.g., they only consider location information as a context data). A better understanding of information privacy concern in context-aware personalized services is highly needed. Hence, the purpose of this paper is to identify a generic set of factors for elemental information privacy concern in context-aware personalized services and to develop a rank-order list of information privacy concern factors. We consider overall technology characteristics to establish a mutually exclusive set of factors. A Delphi survey, a rigorous data collection method, was deployed to obtain a reliable opinion from the experts and to produce a rank-order list. It, therefore, lends itself well to obtaining a set of universal factors of information privacy concern and its priority. An international panel of researchers and practitioners who have the expertise in privacy and context-aware system fields were involved in our research. Delphi rounds formatting will faithfully follow the procedure for the Delphi study proposed by Okoli and Pawlowski. This will involve three general rounds: (1) brainstorming for important factors; (2) narrowing down the original list to the most important ones; and (3) ranking the list of important factors. For this round only, experts were treated as individuals, not panels. Adapted from Okoli and Pawlowski, we outlined the process of administrating the study. We performed three rounds. In the first and second rounds of the Delphi questionnaire, we gathered a set of exclusive factors for information privacy concern in context-aware personalized services. The respondents were asked to provide at least five main factors for the most appropriate understanding of the information privacy concern in the first round. To do so, some of the main factors found in the literature were presented to the participants. The second round of the questionnaire discussed the main factor provided in the first round, fleshed out with relevant sub-factors. Respondents were then requested to evaluate each sub factor's suitability against the corresponding main factors to determine the final sub-factors from the candidate factors. The sub-factors were found from the literature survey. Final factors selected by over 50% of experts. In the third round, a list of factors with corresponding questions was provided, and the respondents were requested to assess the importance of each main factor and its corresponding sub factors. Finally, we calculated the mean rank of each item to make a final result. While analyzing the data, we focused on group consensus rather than individual insistence. To do so, a concordance analysis, which measures the consistency of the experts' responses over successive rounds of the Delphi, was adopted during the survey process. As a result, experts reported that context data collection and high identifiable level of identical data are the most important factor in the main factors and sub factors, respectively. Additional important sub-factors included diverse types of context data collected, tracking and recording functionalities, and embedded and disappeared sensor devices. The average score of each factor is very useful for future context-aware personalized service development in the view of the information privacy. The final factors have the following differences comparing to those proposed in other studies. First, the concern factors differ from existing studies, which are based on privacy issues that may occur during the lifecycle of acquired user information. However, our study helped to clarify these sometimes vague issues by determining which privacy concern issues are viable based on specific technical characteristics in context-aware personalized services. Since a context-aware service differs in its technical characteristics compared to other services, we selected specific characteristics that had a higher potential to increase user's privacy concerns. Secondly, this study considered privacy issues in terms of service delivery and display that were almost overlooked in existing studies by introducing IPOS as the factor division. Lastly, in each factor, it correlated the level of importance with professionals' opinions as to what extent users have privacy concerns. The reason that it did not select the traditional method questionnaire at that time is that context-aware personalized service considered the absolute lack in understanding and experience of users with new technology. For understanding users' privacy concerns, professionals in the Delphi questionnaire process selected context data collection, tracking and recording, and sensory network as the most important factors among technological characteristics of context-aware personalized services. In the creation of a context-aware personalized services, this study demonstrates the importance and relevance of determining an optimal methodology, and which technologies and in what sequence are needed, to acquire what types of users' context information. Most studies focus on which services and systems should be provided and developed by utilizing context information on the supposition, along with the development of context-aware technology. However, the results in this study show that, in terms of users' privacy, it is necessary to pay greater attention to the activities that acquire context information. To inspect the results in the evaluation of sub factor, additional studies would be necessary for approaches on reducing users' privacy concerns toward technological characteristics such as highly identifiable level of identical data, diverse types of context data collected, tracking and recording functionality, embedded and disappearing sensor devices. The factor ranked the next highest level of importance after input is a context-aware service delivery that is related to output. The results show that delivery and display showing services to users in a context-aware personalized services toward the anywhere-anytime-any device concept have been regarded as even more important than in previous computing environment. Considering the concern factors to develop context aware personalized services will help to increase service success rate and hopefully user acceptance for those services. Our future work will be to adopt these factors for qualifying context aware service development projects such as u-city development projects in terms of service quality and hence user acceptance.