• Convergence Security Journal
• /
• v.15 no.5
• /
• pp.29-35
• /
• 2015

The network security encryption type is divided into two, one is point-to-point, second method is link type. The level of security quality attributes are a system security quality requirements in a networked environment. Quality attributes can be observed and should be able to be measured. If the quality requirements can be presented as exact figures, quality requirements are defined specifically setting quality objectives. Functional requirements in the quality attribute is a requirement for a service function which can be obtained through the encryption. Non-functional requirements are requirements of the service quality that can be obtained through the encryption. Encryption quality evaluation system proposed in this study is to derive functional requirements and non-functional requirements 2 groups. Of the calculating measure of the evaluation index in the same category, the associated indication of the quality measure of each surface should be created. The quality matrix uses 2-factor analysis of the evaluation for the associated surface quality measurements. The quality requirements are calculated based on two different functional requirements and non-functional requirements. The results are calculated by analyzing the trend of the average value assessment. When used this way, it is possible to configure the network security encryption based on quality management.

• Journal of the Korea Society for Simulation
• /
• v.27 no.2
• /
• pp.61-69
• /
• 2018

As the technology of information and communication has developed over recent years, an embedded system is applied in multiple industries and becomes more complicated. For this reason, embedded system development cost and time are also increased. For decreasing the cost and time, this paper suggests requirement evaluation method for concurrent development of an embedded system based on Discrete Event System(DEVS) Formalism. This paper proposes a method of describing the requirements specification in the form of DEVS atomic model. Also, the paper proposes the evaluator model that compares evaluation target system and the requirements model that is an implementation of requirement specification and proposes the evaluation method using them. In addition, we propose a method to utilize the requirement model created for requirements evaluation in the concurrent development process of the embedded system. As the case study, this paper proceeds requirement evaluation of Kinect depth data processing system.

• Journal of KIISE:Software and Applications
• /
• v.36 no.7
• /
• pp.531-538
• /
• 2009

Domestic software market is struggling with product's low quality and low return-on-investment. The cause for the problems is due to unclear requirements at the early stage of software project. Studies show that, to lessen the problem, the requirements specification must reflect the right project scope and quantifiable quality goal. To achieve such features, this paper describes a standard guideline for SRS (Software Requirements Specification), which helps in defining the scope of project, measuring and quantifying quality, linking and tracing of requirements, and improving usability. The proposed SRS enables separating the requirements analysis activity from implementation activity and thus can improve subcontract management process in software project.

• Proceedings of the Korea Inteligent Information System Society Conference
• /
• 2006.06a
• /
• pp.141-151
• /
• 2006

최근 U-City와 같은 유비쿼터스 지능 공간 (Ubiquitous Smart Space, USS) 개발이 추진됨에 따라 USS 요구 분석 방법론에 대한 필요성이 커지고 있다. 그러나 SDLC, UML 등과 같은 기존 정보시스템 요구분석 등 개발 방법론은 상황인지 에이전트 시스템 등과 같은 USS 특유의 환경을 고려하지 못해 USS 요구 분석 방법론으로 그래도 적용하기에는 한계가 있다. 따라서 본 논문은 USS 개발을 위한 요구분석 방법론으로서 기존 UML에 상황인지, 에이전트 시스템의 특정을 고려하여 수정된 UML(Amended UML)을 제시하는 것을 목적으로 한다. 이를 위해 본 논문에서는 As-Is Space 와 To-Be Space 로 나누어 요구 분석을 하였다. 또한 본 논문에서 제시한 요구 분석 방법론의 활용가능성을 보이기 위해 국내 쇼핑몰 내 실제 USS 서비스 개발에 적용해 보았다.

• Journal of the Korea Society of Computer and Information
• /
• v.6 no.4
• /
• pp.30-37
• /
• 2001

In the conventional development methodologies, requirements are considered to be not changing after the analysis phase. But in the real world requirements can be changed and modified through out the development life cycle according to end-user's more understanding about the target system. new IT technologies, changes of customer environment and market situation, and so on. In this paper, an idea of improving the requirements specification to extend requirements management over the whole development life cycle is proposed to resolve the requirements management problem of development methodologies.

• The KIPS Transactions:PartD
• /
• v.17D no.4
• /
• pp.271-282
• /
• 2010

Insufficient requirement management accounts for 54% ofunsuccessful software development projects and 22% of insufficient requirement management comes from requirement change management. Hence, requirement management activities are important to reduce failure rates and a tracing method is suggested as the major factor in requirements change management. A traceability table is easy to use because of its legibility accurate tracing. However, traceability tables of existing studies have failed to concretely suggest method of change management and effect of traceability. Also, studies of methods to estimate change impact is complex. Hence, this study suggests how to use a traceability table to manage changes in requirements. Together, in comparison to existing studies, this study suggests easier methods to estimate change rate and change impact. Also Fifteen projects were sampled to test the hypothesis that traceability table influences the success of projects and that it decreases the failure rate that comes from the insufficient requirements management.

• The Journal of Korean Institute of Communications and Information Sciences
• /
• v.37 no.1C
• /
• pp.109-117
• /
• 2012

Studying the major wars of the past seventy years, the most fundamental change is the transition of weapon systems to one of convergence and cutting edge / state of the arts technology. Such transition is creating a need for drastic reforms of the weapon systems development process especially in areas of / in regards to effective utilization of IT, reduction of development period, precise establishing of operational concept and, management of required operational capability(ROC). In particular, establishing an accurate operational concept for a new weapon system and efficient management of ROC based on this operational concept is a prerequisite for a low-cost and high-efficiency weapon systems development and in the end, a successful construction of military forces. This paper examines the current management procedure of the ROC of the Korean military and proposes improvements to the procedure while taking into consideration issues of elicitation, analysis and validation of requirements engineering.

• Journal of Korean Library and Information Science Society
• /
• v.44 no.4
• /
• pp.93-122
• /
• 2013

This study purpose to identifying the roles of Health Information Librarian which its role is increasing according to increase recent interest in wellness and health. In other words, this study will present the Education, careen duties and so on, which should be possed by Health Information Librarian, based on the analysis of Job Site. As as result, first, health information professional librarian's name appears very diverse, and consumer health information librarian will be appropriate name for public libraries and medical librarian will be appropriate for medical library and hospital library. Second, education experience required for health information librarian is master's degree of library and information science and bachelor's or more health related degree. Third, at least two years of health-related field experience, particularly health information service experience, is required. Forth, excellent communication skills and interpersonal skills are required, expecially higher knowledge for health-related information resources is required. Fifth, the main duties what health information librarian need to perform, are library management services, training services, research services, access to and sharing of information resources, collection management, information management, information management technology, and advocacy.

• KIPS Transactions on Software and Data Engineering
• /
• v.4 no.4
• /
• pp.161-168
• /
• 2015

It is difficult to provide proper cloud services for cloud users, because the number of cloud services are increasing and the type of cloud services are diversifying. To overcome this problem, the concept of cloud service broker is presented to mediate cloud services between cloud providers and tenant. The most important role of cloud service broker is to finding cloud services that fulfill requirements of tenant. However, current existing cloud service broker conduct passive requirements analysis process with cloud service expert's assistance. In addition, the systematic functional and non-functional requirement analysis is insufficient. Therefore, we need the new methods for requirement analysis to find nearest service that matches with requirement of tenant. In this paper, we apply pairwise comparison from AHP method to analyze requirement automatically and systematically. It calculates score of service by comparing requirement with service specification, calculating importance rate, and so on.

• Journal of KIISE:Software and Applications
• /
• v.30 no.5_6
• /
• pp.503-514
• /
• 2003

In conventional development methodologies, requirements are considered to be not changing after analysis phase, and requirements specifications are used for the next step system design purpose. But in the real world, requirements can be changed and modified throughout the development life cycle according to end-user's more understanding about the target system, new IT technologies, changes of customer environment and market situation, and so on. So there needs a requirements change management process that can extend requirements management over the entire development life cycle and can support managing changes to the requirements after design phase. In this paper, a requirements change management process that can be integrated into conventional development methodologies is proposed to support the extension of requirements life cycle and managing changes to the requirements after design phase. This process was evaluated through an verification test with a widely used development methodology‘MaRMI’.