• Title/Summary/Keyword: software life cycle

Search Result 335, Processing Time 0.02 seconds

Development of Environment Assessment Software for Electronic Multiple Unit (EMU) (전동차 환경성 평가 S/W RACE의 개발)

  • Kim, Yong-Ki;Lee, Jae-Young;Lee, Cheul-Kyu;Eun, Jong-Hwan
    • Journal of the Korean Society for Railway
    • /
    • v.11 no.3
    • /
    • pp.211-215
    • /
    • 2008
  • Generally, an EMU (Electronic Multiple Unit) is manufactured by assembling a large number of components and parts with extensive raw materials. Throughout its entire life cycle, much both the complicated system and long operating period. Therefore, it is necessary to the environmental performance of EMUs from raw materials to waste. In this study, RACE (Rail Assessment for Clean Environment) was developed as the software that can analyze the environmental RACE had several LCI (Life Cycle Inventory) database for main components as well as principal materials in EMUs. In the future, RACE can also be used as a tool for environmental communication between manufacturers and operators. Also, we will improve RACE continuously to assess more easily the environment of rolling stocks EMU for user.

Content-based Configuration Management System for Software Research and Development Document Artifacts

  • Baek, Dusan;Lee, Byungjeong;Lee, Jung-Won
    • KSII Transactions on Internet and Information Systems (TIIS)
    • /
    • v.10 no.3
    • /
    • pp.1404-1415
    • /
    • 2016
  • Because of the properties of software such as invisibility, complexity, and changeability, software configuration management (SCM) for software artifacts generated during software life-cycle has been used for guarantee of the quality of the software. However, the existing SCM system has only focused on code artifacts and software development document artifacts such as Software Requirements Specification (SRS), Software Design Description (SDD), and Software Test Description (STD). Moreover, software research-oriented project comes out late the code artifacts and the software development document artifacts. Therefore, there is a need for trace and management of software research document artifacts composed of highly abstracted non-functional requirements like 'the purpose of the project', 'the objectives', and 'the progress' before generation of the code artifacts and the software development document artifacts for a long time. Nevertheless, the existing SCM system cannot trace and manage them. In this paper, we propose content-based configuration management system comprised of the relevance link generation phase and content-based testing phase to trace and manage them. The preliminary application results show applicability and feasibility of the proposed system.

A Software Estimating Model for Development Period (소프트웨어 개발기간 추정 모델)

  • 이상운
    • Journal of KIISE:Software and Applications
    • /
    • v.31 no.1
    • /
    • pp.20-28
    • /
    • 2004
  • Estimation of software project cost, effort, and duration in the early stage of software development cycle is a difficult and key problem in software engineering. Most of development effort and duration estimation models presented by regression model of simple relation function point vs. effort and effort vs. duration instead of considering developer's productivity. But different project have need for different effort according to developer's productivity if the projects are same software size. Also, different duration takes according to developer's productivity if the projects require the same effort. Therefore, models that take into account of productivity have a limited application in actual development project. This paper presents models that can be estimate the duration according to productivity in order to compensate a shortcoming of the previous models. Propose model that could presume development period by various methods based on productivity and compared models' performance. As a result of performance comparison, an estimating model of development period from software size got simple and most good result. The model gives decision-making information of development duration to project management in the early stage of software life cycle.

Research on Financial Regulations Related RPA(Robotic Process Automation) (금융회사 RPA(로봇자동화) 관련 규제 연구)

  • Han, Taek-Ryong;Lee, Kyung-ho
    • The Journal of Bigdata
    • /
    • v.4 no.2
    • /
    • pp.47-59
    • /
    • 2019
  • Recently, the RPA (Robotic Process Automation) solution, which has been spreading in Korea and overseas, allows users to easily automate their tasks with the application GUI (Graphic User Interface), and the number of Korean financial companies which Implemented for automating their business is increasing now. However, as the major supervisory regulations that financial institutions must comply with are based on the existing traditional SDLC (Software Development Life Cycle), it is not proper to be directly applied to RPA that automates end-user works on the level of user's system interface. Therefore, in this paper, we organized the important financial supervisory rules and control items that should be considered for RPA implementation, then surveyed 24 financial companies which have implemented RPA for checking how they applied them. Finally, we would like to present the necessity of revision of related compliance.

  • PDF

A Requirements Management Process to improve the Requirements Management of Development Methodologies (개발방법론의 요구사항 관리를 개선하기 위한 요구사항 관리 프로세스)

  • Sin, Jong-Cheol;Gu, Yeon-Seol
    • The KIPS Transactions:PartD
    • /
    • v.9D no.1
    • /
    • pp.81-90
    • /
    • 2002
  • More than 50% of defects and errors in the software development projects are related to the requirements[14]. But the development methodologies can not provide enough supports to the requirements management and changes. In the real world, the requirements keep changing as the requirements at the early development phase are usually incomplete, the developer′s understanding of the problem will be constantly changed during the software process, and new requirements may emerge with the organizational and environmental changes. In this paper, a requirements management process that can be integrated into the development methodologies is proposed to extend the requirements management over the whole development life-cycle and to support the requirements changes at the design/implementation/test phases. To evaluate the proposed process, it was compared to the existing requirements managements processes and models, and examined through a integration test with a widely used development methodology "MaRMI" to show the expected improvements at each development phase.

Designing Software Architecture for Reusing Open Source Software (오픈 소스 소프트웨어 재사용을 위한 소프트웨어 아키텍처 설계)

  • Choi, Yongseok;Hong, Jang-Eui
    • Journal of Convergence for Information Technology
    • /
    • v.7 no.2
    • /
    • pp.67-76
    • /
    • 2017
  • Along with shortening the life cycle of software utilization and supporting various types of user functions, the importance of software architecture development has been emphasized recently. If a software architecture is developed flexibly and reliably for expansion to support new functionality, it can quickly cope with new market demands. This paper proposes an architecture design method based on design recovery of open source software to reuse the software in the development of sustainable software system. When using open source software to develop a software system based on software architecture, we can develop a software system rapidly and also can improve the reliability of the system because we use the already proven open source software in the development.

Design and Implementation of a CASE Tool Supporting Proof of Consistency between OO Models (객체지향 모형 간 일관성 검증을 지원하는 CASE 도구 설계 및 구현)

  • Lee, Seon-Mi;Jeon, Jin-Ok;Ryu, Jae-Cheol
    • The Transactions of the Korea Information Processing Society
    • /
    • v.6 no.11
    • /
    • pp.2965-2980
    • /
    • 1999
  • There are several models and the corresponding diagrams to express software system in many kinds of viewpoints, but these are supposed to be integrated and implemented into only one system. Therefore, the software modelers should have the models ensuring the consistency between information in software development life cycle. To support the robust models for modelers using OO modeling methods, i.e. UML, and CASE tools, the meta models of the software architecture and the consistency rules between the models are suggested in this thesis. Finally, the rules are implemented in the OO CASE tool, DEBUTO(Design By UML Tool). It supports UML1.1 notations and has visual modeling editors that enable users make their own software model.

  • PDF

The C Language Auto-generation of Reactor Trip Logic Caused by Steam Generator Water Level Using CASE Tools

  • Kim, Jang-Yeol;Lee, Jang-Soo
    • Nuclear Engineering and Technology
    • /
    • v.31 no.1
    • /
    • pp.58-67
    • /
    • 1999
  • The purpose is to produce a model of nuclear reactor trip logic caused by the steam generator water level of Wolsong 2/3/4 unit through an activity chart and a statechart and to produce C language automatically using Statechart-based Formalism and Stalemate MAGNUM toolset suggested by David Harel Formalism. It was worth attempting auto-generation of C language though we manually made Software Requirement Specification(SRS) for safety-critical software using statechart-based formalism. Most of the phases of the software life-cycle except the software requirement specification of an analysis phase were generated automatically by Computer Aided Software Engineering (CASE) tools. It was verified that automatically produced C language has high productivity, portability, and quality through the simulation.

  • PDF

A Study on the Application of an Integrated Management Software for a Petrochemical Plant Project (화공플랜트 프로젝트에서 통합관리 소프트웨어 적용에 관한 연구)

  • Kim, Yoon;Lee, Dong-Eon;Yoo, Ho-seon
    • Plant Journal
    • /
    • v.6 no.2
    • /
    • pp.56-61
    • /
    • 2010
  • In this paper, an integrated management software is developed to promote the business competitive power. The interoperability among the software accounts for an ever growing performance of petrochemical plant project. If the interoperability is built up, company has taken advantages of quality, schedule, cost, and safety by active communication. The advantage of an integrated management software is examined in three aspects. In efficiency aspect, It takes advantage of the saving about the various information and the standard of project performance procedure. In quality, the integration gave aid to a quality improvement through team collaboration and data management within project life cycle. In cost, poor communications between systems waste 30% of project costs. If information could be inputted once and used by all, reductions in delivery time up to 40% were possible. Therefore, 10% savings of engineering cost was also possible.

  • PDF

The Study of Framework Model for Software Productivity Enhancement in Object-Oriented Environment (객체지향 환경에서 소프트웨어 생산성 향상을 위한 프레임워크 모델 연구)

  • Heo, Kwae-Bum;Kim, Young-Gyu;Yang, Dong-Il
    • Journal of Advanced Navigation Technology
    • /
    • v.14 no.6
    • /
    • pp.900-908
    • /
    • 2010
  • Recently, OOM(Object-Oriented Method) access method which begins to apply to software development is emphasizing development cost and time reduction through independent software reuse. But because of planning to the exclusion of the lack of knowledge and expansion or performance for development technology many problems are coming out. Therefore, this thesis suggests Effective Object-Oriented Modeling methods considering the plan for higher productivity enhancement of software in the software development life cycle. Effective Object-Oriented Modeling method includes, methods, Use Case modeling methods, Analysis Modeling methods, Design Modeling methods and others.