• Nuclear Engineering and Technology
• /
• v.28 no.6
• /
• pp.594-601
• /
• 1996

To assure quality of safety critical software, software should be developed in accordance with software development procedures and rigorous software verification and validation should be performed. Software verification is the formal act of reviewing, testing or checking, and documenting whether software components comply with the specified requirements for a particular stage of the development phase [1]. New software verification methodology was developed and was applied to the Shutdown System No. 1 and 2(SDS1,2) for Wolsong 2, 3 and 4 nuclear power plants by Korea Atomic Energy Research Institute(KAERI) and Atomic Energy of Canada Limited(AECL) in order to satisfy new regulation requirements of Atomic Energy Control Board(AECB). Software verification methodology applied to SDS1 for Wolsong 2, 3 and 4 project will be described in this paper. Some errors were found by this methodology during the software development for SDS1 and were corrected by software designer. Output from Wolsong 2, 3 and 4 project have demonstrated that the use of this methodology results in a high quality, cost-effective product.

• The Journal of the Korea Contents Association
• /
• v.11 no.7
• /
• pp.80-88
• /
• 2011

It is no simple matter to measure and manage the quality of Software which is invisible. However the importance cannot be ignored as the software development project is getting bigger and complex. This study analyses and compares the methods of software quality improvement. Further it formulates rules for Code Inspection and verifies the efficiency and the effectiveness by applying to practical project. The study get the following results. First, the study organizes theoretical content about the methods of Software review. Second, the study formulates rules for Code inspection and demonstrates the result through the case study. Third, the study performs the quantitative dater management through code inspection.

• Industrial Engineering and Management Systems
• /
• v.10 no.1
• /
• pp.43-53
• /
• 2011

Currently, knowledge within the field of software development is largely implicit and is not formally disseminated and shared. This means that there is little improvement and regeneration of processes, and knowledge gained from previous projects is not necessarily applied to new ones. In order to turn this situation around it is necessary to take an organized approach to sharing job-related information. For this study, the authors constructed "Amalab-Project Planning Navigation System, or A-PPNS", a system for organizing accumulated knowledge related to the field of software development. More specifically, A-PPNS is a business process monitoring system and consists of the following four elements: (i) Optimized estimate support subsystem, (ii) Schedule monitoring system, (iii) QCD optimization diagnostic system, and (iv) Strategic technology accumulation system. The effectiveness of this system has been demonstrated and verified at Company A, a system integration company.

• The KIPS Transactions:PartD
• /
• v.11D no.7 s.96
• /
• pp.1491-1498
• /
• 2004

Successful project planning relics on a good estimation of the manpower required to complete a project, together with the schedule options that may be available. Despite the extensive research done developing new and better models, existing software manpower estimation models are present only the total manpower or instantaneous manpower distribution according to the testing time for the software life-cycle. This paper suggests the manpower estimating models for software testing phase as well as testing process and debugging process in accordance with de-tected faults. This paper presents the polynomial model for effort based on testing and debugging faults. These models are verified by 5 different software project data sets with coefficient of determination and mean magnitude of relative error for adaptability of model.

• Journal of Internet Computing and Services
• /
• v.5 no.2
• /
• pp.85-95
• /
• 2004

The web-based project is seriously not efficient area at software engineering. In order to develop a web-based system, UI(User Interface) designers usually first design display layout and then business logic developers bring to complete the coding of the display layout source. In the case of maintenance, it goes through the same process, This kinds of web-based software development method were proposed by the various methods same as the tag library of JSP, But there are many problems to apply them and they are low productive comparing to the CIS based software development method, WFS(Neb Form System), which is suggested on this thesis, separates UI design from business logic on a web project and offers the better environment to develop web based software, Eventually WFS will improve the productivity to develop web based software.

• International Journal of Computer Science & Network Security
• /
• v.21 no.12spc
• /
• pp.586-596
• /
• 2021

Software organisations follow different methodologies for the development of software. The software development methodologies are mainly divided into two categories, including plan-driven and agile development. To attain project success, it is very significant to consider risk management during whole project. Agile development is considered risk-driven, but many risks are unreported at the industrial level. The risks can be divided into three categories, including (i) development risks, (ii) organisations risks, and (iii) people-oriented risks. This paper deals with Development risks specifically. Several risks related to development are faced by people working in the industry while dealing with agile development. Their management among the industry is a big issue, so this paper emphasises ARMF based on development-related risks by following agile development. This research work will help software organisations to prevent different project-related risks during agile development. The risks are elicited at two-level, (i) literature-based and (ii) IT industry based. A systematic literature review was performed for eliciting the agile risks from the literature. Detailed case studies and survey research methods were applied for eliciting risks from IT industry. Finally, we merged the agile development risks from literature with standard industrial risks. Hence, we established an agile risk mitigation framework ARMF based on agile development and present a groundwork established in light of empirical examination for extending it in future research.

• Journal of Construction Engineering and Project Management
• /
• v.4 no.2
• /
• pp.8-11
• /
• 2014

The interactions and interrelationships between stakeholders largely determine the overall performance of a construction project, and have the crucial responsibility for delivering a project to successful completion. An important component of stakeholder management is stakeholder analysis. Two case studies are conducted within Kerala (India). The main objective was to carry out stakeholder analysis using stakeholder organiser deluxe software, considering the data's collected from the project execution team using questionnaire. During data collection the key stakeholders were identified, to know how to manage them, their interest, power, attitude level etc, for quality improvement. Analyze the results using the software Stakeholder organizer deluxe and modeling of stakeholders is to be done. Finally validate the models of the projects. These findings may mainly reflect the stakeholder management environment in the respective regions of project implementation.

• Journal of Korean Society for Quality Management
• /
• v.25 no.1
• /
• pp.142-155
• /
• 1997

To successfully carry out large scale research projects while su, pp.rting quality assurance of research output, effective and systematic management through utilization of resources such as manpower, time and cost as well as engineering techniques such as component technology and design methodology is required. It is necessary to establish development methodology to su, pp.rt quality assurance. The development methodology covers the contents and procedures of the project, such as division of the project into independently executable units, allocation of resources including researchers, component technology, related know-how and equipment, deployment of research units and integration of the project at the end. In this paper we present systematic development methodology for quality assurance in large scale software development projects by analyzing the contents of the methodology a, pp.ied to the Gigabit Information-processing And Networking Technology development project(GIALT).

• Journal of the Korea Society of Computer and Information
• /
• v.21 no.9
• /
• pp.139-147
• /
• 2016

In recent, android application developments have been done widely that intensify smart phone utilization. In this paper, we propose a curriculum that undergraduate students can improve their mobile programming abilities as well as integrate experiences of application development based on android. And also a series of practices to advance their sense of accomplishment are added by offering an opportunity to carry out a real project to use a variety of sensors embedded in smart phone during the course of study. The project is composed of a series of modules for implementing a trekking App that helpful to people who enjoy spending time in outdoors through their favorite activities such as trekking, cycling, and climbing with their own smart phones. Through practical curriculum operation and project implementation, we show that the proposed curriculum is appropriate to a mobile programming education that combine learning and practice.

• Journal of Digital Convergence
• /
• v.13 no.8
• /
• pp.91-99
• /
• 2015

Reviewing the previous researches related to SW quality, we find that they are mostly quality evaluation models for SW quality improvement and maturity-design models for software project management evaluation. There are few studies for the appropriateness of SW quality management by Quality Control(QC) functions. Moreover, they are bound for government's SW R&D projects in the view of the third party. Therefore, we propose means for the objective evaluation of SW quality management's appropriateness by QC functions. For this reason, there are three research proposes in our study as follows. Firstly, we produce problems for the evaluation of the existing government's SW R&D project management's appropriateness. Secondly, to overcome the drawbacks for the evaluation of the appropriateness of SW quality management, new appropriateness evaluation methods are proposed. Lastly, we investigate the availability and effectiveness of the appropriateness evaluation methods for WBS projects.