Sung-Yul Rhew

Metrics for measuring the consistencies of requirements with objectives and constraints

Requirements engineering (RE) is essential to succeed in software projects. That is, it is important to elicit sound requirements for proper performing of RE. If some requirements are inconsistent with a given objectives and constraints, these requirements may hinder the performance of RE. For this reason, it is necessary to pre-check the consistency of requirements. We propose the metrics for evaluating requirements by considering given objectives and constraints. Our metrics are validated by two sample scenarios: “Payroll and Roster Planning of Hospital” and “Noise Source Location System.” At the result, we expect that these metrics would be helpful when selecting a set of consistent requirements.

Cost Measurement Indicators and Maintenance Cost Estimation Model for Maintenance of Component-based Software

ABSTRACT Most information systems are component-based and developed by outsourcing, and developed software is maintained integrative. However, studies on cost measurement indicators and cost estimation model have not been performed sufficiently, which are foundational to enhance the productivity and efficiency of maintenance. This study suggests indicators to measure maintenance cost for com- ponent-based software and examines maintenance cost estimation model of component software by the measurement indicators suggested. In order to generate the indicators to measure the component-based maintenance cost, the previously proposed indicators are summarized comparatively. To estimate the measurement indicators of component-based software, it makes a comparison of the previously proposed indicators and arranges them. We classify the measurement indicators by how to apply according to maintenance types of component software and then we propose the cost measurement indicators. Moreover, we propose the cost estimation model according to the maintenance types of component software using the suggested measurement indicators suggested. With the suggested estimation model, a case study is performed and its validity is verified.Keywords:Maintenance, Measurement Indicators, Maintenance Cost, Maintenance Cost Estimation Model

Machine Learning Process for the Prediction of the IT Asset Fault Recovery

The IT asset is a core part that supports the management objective of an organization, and the fast settlement of the IT asset fault is very important. In this study, a fault recovery prediction technique is proposed, which uses the existing fault data to address the IT asset fault. The proposed fault recovery prediction technique is as follows. First, the existing fault recovery data were pre-processed and classified by fault recovery type; second, a rule was established for the keyword mapping of the classified fault recovery types and reported data; and third, a machine learning process that allows the prediction of the fault recovery method based on the established rule was presented. To verify the effectiveness of the proposed machine learning process, company A`s 33,000 computer fault data for the duration of six months were tested. The hit rate for fault recovery prediction was approximately 72%, and it increased to 81% via continuous machine learning.

Software Replacement Time Prediction Technique Using the Service Level Measurement and Replacement Point Assessment

ABSTRACT The software is changed according to the changing businesses and the user requirement, it involves increasing complexity and cost. Considering the repetitive changes required for the software, replacement is more efficient than maintenance at some point. In this study, the replacement time was predicted using the service dissatisfaction index and replacement point assessment index by the software group for each task. First, fuzzy inference was used to develop the method and indicator for the user’s service level dissatisfaction. Second, the replacement point assessment method was established considering the quality, costs, and new technology of the software. Third, a replacement time prediction technique that used the gap between the user service measurement and replacement point assessment values was proposed. The results of the case study with the business solutions of three organizations, which was conducted to verify the validity of the proposed prediction technique in this study, showed that the service dissatisfaction index decreased by approximately 16% and the replacement point assessment index increased by approximately 9%.

A Study on Techniques for Measuring Requirement Suitability Considering Project Objectives and Constraints

The suitability of requirements that are developed and changed is a key factor to make a success of project. The key elements of requirement suitability are the objectives and constraints which are decided by scope. To ensure that requirements have suitability, our study proposes the techniques for measuring requirement suitability considering objectives, constraints and requirements. To calculate requirement suitability points, which are quantities calculated by these techniques, we develop indicators and metrics based on relationship among objectives, constraints and requirements, and propose expressions to quantify our indicators using MCDM (Multi Criteria Decision Making) techniques. An interpretation and usage of our techniques are described by statistical analysis.

Requirements Trace Table Expansion and How to Normalization

There are various methods to trace output in software development to verify the consistency and completeness of requirements. Existing studies do present the trace meta-model or automated tools, but fail to list specifically traced output or traced items. Also, in regards to trace tables, which contain traced items, existing studies don‘t consider the whole software development process but merely its sub-process. Given this, the present study suggests an extended requirements tracetable that tracks output from the inception of the project through the architectural design phase to the application delivery, following up on the researcher’s previous study on a tracetable that considered only a sub-process of the whole development process. In addition, in order to address the problem of the tracking process becoming complicated with increased tracefields due to an extended trace table, the researcher suggests a method for normalizing a requirements tracetable that can integrate and separate by development process phase. Apply it to theH system development project of a D company, and this study caseverified application possibility of study, confirmed an effect of a chase to easily find out an error of requirements. Improve precision of a traceto verify consistency of requirements and completeness through this study, and will minimize failure of a software development.

Erratum to: Metrics for measuring the consistencies of requirements with objectives and constraints

Unfortunately, in the original publication, the fourth author’s name (Vijayan Sugumara) and affiliation of all authors have been published incorrectly. The acknowledgment section was also missed. The correct name of the fourth author is Vijayan Sugumaran. The correct affiliation of all authors and the acknowledgment section are given below. Acknowledgments This research was supported by Next-Generation Information Computing Development Program through the National Research Foundation of Korea (NRF) funded by the Ministry of Science, ICT & Future Planning (2012M3C4A7033348).

Mobile Software Architecture Technique and Application for Using Business Logic and View

Mobile application has changed from existing terminal vendor and carrier-oriented service. In particular, smart environment enables various services from Native application to web application. It will take lots of time and cost if mobile application service is developed and provided according to various service needs of mobile application. If existing business logic and view are reused when developing mobile application, it can not only save cost but also reduce development time. In addition, various services can be provided effectively to various platforms. This thesis presents mobile software architecture technique and based on this, develops mobile applications. It is because application should be developed based on well-designed software architecture in order to develop mobile application serving various platforms using business logic and view.

Study on Predictor Measurement for Risk Management in Financial Information System

Financial information system is a nationally and socially important infrastructure, thus risks in such infrastructures constitutes a threat to both the nation and the society. However, the current financial information system risk management is feeble due to lack of research and its focus on after treatment rather than prevention. To increase prevention of defects, measurement of predictors that predict failures and faults in the information system is of utmost importance. This paper established hypotheses and evaluated market factors that cause errors and defects in financial information system such as trading volume, index fluctuation, number of public announcements, number of orders and fills, and number of changing duties. It was shown that trading volume, number of orders and fills, and number of changing duties caused failures and faults while other factors showed no influence.

Rule Based Authorization Management Using User Context and ROLE

A source code included user context is limit of existing RBAC models under personnel changes or business changes. This research proposed the authorization model and design, which is defined the rule based on tabular using user context which was hard coded in source code in order to resolve the limit of RBAC model. The proposed authorization management was defined as the two stages of authorization model and authorization design. An authorization model was modeled rule using RBAC and user context, authorization design was designed as tabular based using User Context. In order to verify the efficiency of authorization management was compared and analyzed other RBAC models.