• Journal of Information Processing Systems
• /
• v.16 no.6
• /
• pp.1372-1390
• /
• 2020

An attractive user interface (UI) design with a clear user experience (UX) is the key for the success of applications. Therefore software development projects require very close collaboration between SI developers and front-end service developers. However, methodologies for software development only exist with inadequate development processes or work standards for collaboration. This survey derived 13 risk factors in developing UI/UX from 113 risk factors of IT projects through a questionnaire and factor analysis and proposed a collaboration-based UI/UX development model that can eliminate or mitigate six risks with high weights and reliability. To extract risk factors with high reliability, factor and reliability were analyzed to extract 13 major risks, and based on the expert opinions and the results of correlation analysis, UI/UX development stages were classified into planning, design, and implementation. The causal relationships between risks were verified through regression analysis. This study is the first to expertly analyze major risks based on collaboration in UI/UX development and derive a theoretical basis that can be used in project risk management. These findings are expected to provide a basis for research on development methodologies for higher levels of front-end services and to construct rational collaboration systems between SI practitioners and front-end service providers.

• Journal of Korea Multimedia Society
• /
• v.18 no.4
• /
• pp.546-556
• /
• 2015

Since the concept of software engineering was first used in 1968 by NATO Science Committee, a lot of research work and improvements have been made on software development methodology and software quality control, but they still fall short of ensuring successful development of small and medium scale software systems. Under these circumstances, Center for Software Engineering (CSE) at National IT Industry Promotion Agency(NIPA) has been conducting studies on quality control methodologies of software visualization well-suited for small and medium scale software systems, and also working on the systemization and quantification of software quality control. In this paper, we attempt to scope on the software development management of domestic and foreign small and medium-sized enterprises that are lying in the blind spot, compared to large enterprises with well-organized software development systems. In particular, based on software visualization that CSE is pursuing for small and medium-sized developers, we propose a practical quality control methodology well-suited for small and medium scale projects, and a low-cost quality control management tool by combining open-source quality control tools. Our proposal is expected to induce developers' mind change in SI-specialized small and medium-sized software enterprises, increase their profits and improve customer satisfaction through project quality control.

• The KIPS Transactions:PartD
• /
• v.12D no.4 s.100
• /
• pp.601-608
• /
• 2005

It is very important to improve qualify, cost and the necessary period for production in software development project. In order to improve software quality, cost and period, final product as well as a project planning and process itself are concerned. In CMMI of SEI and ISO/IEC 15504 (SPICE), the process for the project management is specified. Recently, as a method of total management - including man power, budget, and schedule - PMBOK is introduced. The detailed and specific management method in PMBOK results in multiple experiments that apply PMBOK to enterprise environment. In this paper, hybrid method of CMMI and PMBOK is proposed to obey CMMI, at the same time, to apply the detailed and specific management method in PMBOK and develop metrics for the method.

• Journal of the Korean Society of Systems Engineering
• /
• v.1 no.2
• /
• pp.63-68
• /
• 2005

This study developed the planning process for technical management of engineering project applying systems engineering process in order to correctly design technical management activities early during the system development projects. The developed process describes a systemic design process of a product to be developed as well as the development process and the personnel team of project organization. As an outcome of the process implemented by a Model-Based Systems Engineering(MBSE) software, a systems engineering management plan(SEMP) and a risk management plan can easily be produced.

• Journal of the Korea Society of Computer and Information
• /
• v.25 no.6
• /
• pp.119-129
• /
• 2020

Software development activities are influenced by stochastic theory rather than deterministic one due to having process variability. Stochastic methods factor in the uncertainties associated with project activities and provides insight into the expected project outputs as probability distributions rather than as deterministic approximations. Thus, successful software projects systematically manage and balance five objectives based on historical probability: scope, size, cost, effort, schedule, and quality. Although software size estimation having much uncertainty in initial development has traditionally performed using deterministic methods: LOC(Lines Of Code), COCOMO(COnsructive COst MOdel), FP(Function Point), SLIM(Software LIfecycle Management). This research aims to present a function point method based on stochastic distribution and a case study based on Monte Carlo Simulation applying on an automotive electrical and electronics system software development. It is expected that the result of this paper is used as guidance for establishing of function point method in organizations and tools for helping project managers make decisions correctly.

• The KIPS Transactions:PartD
• /
• v.13D no.1 s.104
• /
• pp.61-66
• /
• 2006

It is reported that the success ratio of software development projects has been only 30%. Many causes lower project's chance of success, particularly lack of systematic project management. Especially, moving on the next phase of project with unsatisfactory outputs can be very problematic because it can cause much waste of resource, time and even lead to the failure of the whole project. Peer review and inspection are some of the practices designed to prevent such waste and possible failure. When defects are identified through such progress, each developer has to work on the product component again and fix the problem. This process is called rework. In this paper, we propose a method for improving quality of reworked product component to prevent excessive cost and time consumed caused by moving on the next phase of a project with a problematic product component. More specifically, this paper suggests a rework indicator that measures the level of rework based on its complexity and severity and is used to choose appropriate checking method on reworked product component. The research also confirmed the method's usefulness and effectiveness by applying the suggested method on four projects.

• Journal of Aerospace System Engineering
• /
• v.17 no.6
• /
• pp.108-117
• /
• 2023

Thus far, a mission software component of the KT-1 military fixed-wing aircraft for overseas export has been developed through international joint development with foreign companies. The reliability of the software component could be certified by complying with the development environment and procedures of foreign companies based on DO-178B. However, recently, DO-178C certification is required for overseas exports, and reliability tests to comply with the weapon system software development guidelines are required for domestic military forces. In this paper, we describe the problems in obtaining domestic airworthiness certification in the international joint development of a previously developed KT-1 export-typed aircraft system integration project. To this end, we find a solution to comply with both DO-178C and the Weapon System Software Development and Management Manual and provide the optimal software reliability test method.

• Proceedings of the KSRS Conference
• /
• 2004.10a
• /
• pp.39-41
• /
• 2004

This paper demonstrates the in-house development of the subsystem C&DH in a D-SAT satellite project of Astronautic Technology (M) Sdn. Bhd. (ATSB). D-SAT is a non-imaging satellite. It will carry a dosimeter as the payload for scientific objectives. Since one of the D-SAT project establishment intended objectives is to demonstrate the research and development skill of the ATSB engineers on the satellite system building, most of the subsystems of the D-SAT are developed in-house including the C&DH subsystem. C&DH subsystem plays an important role for managing data handling tasks and general operation of the satellite system. The C&DH development includes the research and study on the hardware and software design, the design of both the hardware and software, the development of the software system, the integration between the software and the hardware system and the implementation of the subsystem into the satellite system. This program allows ATSB to accomplish the engineers with expertise not only in the C&DH subsystem but other subsystems too besides developing knowledge in the management of a space project that covers not only on the technical issues but issues relating to the economic, political and legal issues.

• Journal of Korean Society for Quality Management
• /
• v.13 no.2
• /
• pp.61-65
• /
• 1985

The quality of a final SOFTWARE PACKAGE depends on many complicated factors in the software development process. This paper describes ststistical methods for establishing relationships between final quality and development process factors. The final software quality is represented by the number of errors through the system test phase. The data presented here were gathered during the course of a real IS-month development project. Regression theory is used for data analysis. Some of the interesting results include the observation that specification changes during the development process have an adverse effect on final software quality.

• 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.