• Title, Summary, Keyword: Software

Search Result 24,054, Processing Time 0.07 seconds

Design and Implementation of Web-based Software Engineering Tool for Robot (웹 기반 로봇 소프트웨어 공학 도구 설계 및 구현)

  • Hong, Chang-Ho;Park, Hong-Seong
    • Journal of Institute of Control, Robotics and Systems
    • /
    • v.17 no.9
    • /
    • pp.908-915
    • /
    • 2011
  • As the requirement of user for robot functionality, the function and interface for controlling the robot system is more sophisticated and complicated. Accordingly development process of robot is more complicated and it takes much longer time to develop a robot system. Software development using project management tool is more important in software engineering because of the complexity of software, especially robot system. This paper proposes SEED (Software Engineering Equipment for Development), which is a web-based and integrated software engineering tool to provide independent tools for robot software development. SEED includes the document management tool, the software configuration management tool, the software testing tool on developing robot software and provide a functionality of collaborated and remote development due to WEB-based operations.

Development of the Engagement Control Software Architecture Based on UML 2.0 Model (UML 2.0 모델 기반의 교전통제 소프트웨어 아키텍처 개발)

  • Yoo, Myong-Hwan;Bae, Jung-Il;Shin, Jin-Hwa;Cho, Kil-Seok
    • Journal of the Korea Institute of Military Science and Technology
    • /
    • v.10 no.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.

A software reliability model with a Burr Type III fault detection rate function

  • Song, Kwang Yoon;Chang, In Hong;Choi, Min Su
    • International Journal of Reliability and Applications
    • /
    • v.17 no.2
    • /
    • pp.149-158
    • /
    • 2016
  • We are enjoying a very comfortable life thanks to modern civilization, however, comfort is not guaranteed to us. Development of software system is a difficult and complex process. Therefore, the main focus of software development is on improving the reliability and stability of a software system. We have become aware of the importance of developing software reliability models and have begun to develop software reliability models. NHPP software reliability models have been developed through the fault intensity rate function and the mean value functions within a controlled testing environment to estimate reliability metrics such as the number of residual faults, failure rate, and reliability of the software. In this paper, we present a new NHPP software reliability model with Burr Type III fault detection rate, and present the goodness-of-fit of the fault detection rate software reliability model and other NHPP models based on two datasets of software testing data. The results show that the proposed model fits significantly better than other NHPP software reliability models.

A Software Engineering Process for Safety-critical Software Application (Safety-critical 소프트웨어 적용을 위한 소프트웨어 개발 절차)

  • Kang, Byung-Heon;Kim, Hang-Bae;Chang, Hoon-Seon;Jeon, Jong-Sun;Park, Suk-Joon
    • Nuclear Engineering and Technology
    • /
    • v.27 no.1
    • /
    • pp.84-95
    • /
    • 1995
  • Application of computer software to safety-critical systems is on the increase. To be successful, the software must be designed and constructed to meet the functional and performance requirements of the system. For safety reason, the software must be demonstrated not only to meet these requirements, but also to operate safely as a component within the system. For longer-term cost consideration, the software must be designed and structured to ease future maintenance and modifications. This paper present a software engineering process for the production of safety-critical software for a nuclear power plant The presentation is expository in nature of a viable high quality safety-critical software development. It is based on the ideas of a rational design process and on the experience of the adaptation of such process in the production of the safety-critical software for the Shutdown System Number Two of Wolsong 2, 3 & 4 nuclear power generation plants. This process is significantly different from a conventional process in terms of rigorous software development phases and software design techniques. The process covers documentation, design, verification and testing using mathematically precise notations and highly reviewable tabular format to specify software requirements and software design. These specifications allow rigorous, stepwise verification of software design against software requirements, and code against software design using static analysis. The software engineering process described in this paper applies the principle of information-hiding decomposition in software design using a modular design technique so that when a change is' required or an error is detected, the affected scope can be readily and confidently located. It also facilitates a sense of high degree of confidence in the ‘correctness’ of the software production, and provides a relatively simple and straightforward code implementation effort.

  • PDF

(The View Model of Software Architecture for Component Based Software Development) (컴포넌트 기반 소프트웨어 개발을 지원하는 소프트웨어 아키텍처 뷰 모델)

  • 박준석;문미경;염근혁
    • Journal of KIISE:Software and Applications
    • /
    • v.30 no.5_6
    • /
    • pp.515-528
    • /
    • 2003
  • Component Based Software Development has been recognized as a new software development paradigm, and received much attention among researchers. However, it requires software architecture based development to assure component reusability and efficient software development. This paper proposes the Component Based 4+1 View Model of software architecture to support component based software development. It is redefined on the basis of the existing 4+1 view model of software architecture developed by Kruchten. Also, we describe the elements of the view model in detail with UML. This architecture constructs the foundation of component based software such as increasing the understanding of software and providing the information about how the components interact with each other. It can be done by exposing the context for the use of software components to each views.

A Study on Reform Scheme of Software Industrial Promotion Law (소프트웨어산업진흥법의 개선방향에 관한 연구)

  • Choi, Chang-Ryeol
    • Journal of Information Technology Services
    • /
    • v.5 no.1
    • /
    • pp.61-81
    • /
    • 2006
  • It is necessary to systematically explore the reform plans of the Software Industrial Promotion Law to systematically a representative high-added value future knowledge-based industry, software industry. The current Software Industrial Promotion Law provides only one provision on software business contract procedures, and the Civil Code, the National Contract law or Subcontract Fairness Law regulate other things, so the features of software industry are not properly reflected. To the contrary, the Information Communication Construction Law or the Construction Basic Law effectively prevent disputes by providing material and detailed provisions. Therefore the current software industry needs to be shifted from promotion to fundamental one. That is, as the software industry takes up a large portion at present, so the law should have basic procedural provisions. Also the National Contract Law governs only the contract procedures of public sector, so there should be business performance procedural provisions to regulate the software business formalities of civil sector. And the National Contract Law controls the sale, construction and service of articles at separate contract procedures, but software business contains construction and service characters simultaneously, so there should be business performance procedures fit for software business. Thus this study presented the legislative need and bill on the performance procedures of software business.

An Evolution of Reliability of large Scale Software of a Switching System (대형 교환 시스템의 소프트웨어 신뢰도 성장)

  • Lee, J.K.;Shin, S.K.;Nam, S.S.;Park, K.C.
    • Electronics and Telecommunications Trends
    • /
    • v.14 no.4
    • /
    • pp.1-9
    • /
    • 1999
  • In this paper, we summarize the lessons learned from the applications of the software reliability engineering to a large-scale software project. The considered software is the software system of the TDX-10 ISDN switching system. The considered software consists of many components, called functional blocks. These functional blocks serve as the unit of coding and test. The software is continuing to be developed by adding new functional blocks. We are mainly concerned with the analysis of the effects of these software components to software reliability and with the analysis of the reliability evolution. We analyze the static characteristics of the software related to software reliability using failure data collected during system test. We also discussed a pattern which represents a local and global growth of the software reliability as version evolves. To find the pattern of software of the TDX-10 ISDN system, we apply the S-shaped model to a collection of failure data sets of each evolutionary version and the Goel-Okumoto (G-O) model to a grouped overall failure data set. We expect this pattern analysis will be helpful to plan and manage necessary human/resources for a new similar software project which is developed under the same developing circumstances by estimating the total software failures with respect to its size and time.

FAULT TREE ANALYSIS OF KNICS RPS SOFTWARE

  • Park, Gee-Yong;Koh, Kwang-Yong;Jee, Eunk-Young;Seong, Poong-Hyun;Kwon, Kee-Choon;Lee, Dae-Hyung
    • Nuclear Engineering and Technology
    • /
    • v.40 no.5
    • /
    • pp.397-408
    • /
    • 2008
  • This paper describes the application of a software fault tree analysis (FTA) as one of the analysis techniques for a software safety analysis (SSA) at the design phase and its analysis results for the safety-critical software of a digital reactor protection system, which is called the KNICS RPS, being developed in the KNICS (Korea Nuclear Instrumentation & Control Systems) project. The software modules in the design description were represented by function blocks (FBs), and the software FTA was performed based on the well-defined fault tree templates for the FBs. The SSA, which is part of the verification and validation (V&V) activities, was activated at each phase of the software lifecycle for the KNICS RPS. At the design phase, the software HAZOP (Hazard and Operability) and the software FTA were employed in the SSA in such a way that the software HAZOP was performed first and then the software FTA was applied. The software FTA was applied to some critical modules selected from the software HAZOP analysis.

Behavior-Structure-Evolution Evaluation Model(BSEM) for Open Source Software Service (공개소프트웨어 서비스 평가모델(BSEM)에 관한 개념적 연구)

  • Lee, Seung-Chang;Park, Hoon-Sung;Suh, Eung-Kyo
    • The Journal of Distribution Science
    • /
    • v.13 no.1
    • /
    • pp.57-70
    • /
    • 2015
  • Purpose - Open source software has high utilization in most of the server market. The utilization of open source software is a global trend. Particularly, Internet infrastructure and platform software open source software development has increased rapidly. Since 2003, the Korean government has published open source software promotion policies and a supply promotion policy. The dynamism of the open source software market, the lack of relevant expertise, and the market transformation due to reasons such as changes in the relevant technology occur slowly in relation to adoption. Therefore, this study proposes an assessment model of services provided in an open source software service company. In this study, the service level of open source software companies is classified into an enterprise-level assessment area, the service level assessment area, and service area. The assessment model is developed from an on-site driven evaluation index and proposed evaluation framework; the evaluation procedures and evaluation methods are used to achieve the research objective, involving an impartial evaluation model implemented after pilot testing and validation. Research Design, data, and methodology - This study adopted an iteration development model to accommodate various requirements, and presented and validated the assessment model to address the situation of the open source software service company. Phase 1 - Theoretical background and literature review Phase 2 - Research on an evaluation index based on the open source software service company Phase 3 - Index improvement through expert validation Phase 4 - Finalizing an evaluation model reflecting additional requirements Based on the open source software adoption case study and latest technology trends, we developed an open source software service concept definition and classification of public service activities for open source software service companies. We also presented open source software service company service level measures by developing a service level factor analysis assessment. The Behavior-Structure-Evolution Evaluation Model (BSEM) proposed in this study consisted of a rating methodology for calculating the level that can be granted through the assessment and evaluation of an enterprise-level data model. An open source software service company's service comprises the service area and service domain, while the technology acceptance model comprises the service area, technical domain, technical sub-domain, and open source software name. Finally, the evaluation index comprises the evaluation group, category, and items. Results - Utilization of an open source software service level evaluation model For the development of an open source software service level evaluation model, common service providers need to standardize the quality of the service, so that surveys and expert workshops performed in open source software service companies can establish the evaluation criteria according to their qualitative differences. Conclusion - Based on this evaluation model's systematic evaluation process and monitoring, an open source software service adoption company can acquire reliable information for open source software adoption. Inducing the growth of open source software service companies will facilitate the development of the open source software industry.

Exploring the Relationship between Software Capability Level and Software Project Productivity (SW공학 수준과 SW개발 프로젝트의 생산성)

  • Kim, Seung-Gweon;Yoon, Jong-Soo
    • Journal of the Korea Society of Computer and Information
    • /
    • v.17 no.8
    • /
    • pp.123-133
    • /
    • 2012
  • Recently, as IT convergence has seen rapid growth the role and scope of software has been extended. many software companies are trying to improve the software quality and project outcome using software process improvement approach to cope with increasing software demands and software quality. Although software process improvement is difficult task which requires a lot of cost and time, there is still insufficient objective evidence on business benefits by its deployment. The purpose of this study is to analyze the relationship between software process improvement and software project productivity. That is, we investigated whether there is difference in software development productivity depends on software engineering level using statistical methods. We found that the software development productivity is different across the software engineering levels and the higher software engineering level can lead to improved software development productivity.