• The Journal of Korean Association of Computer Education
• /
• v.9 no.4
• /
• pp.43-54
• /
• 2006

In general, user requirements in web-based learning systems are divided into functional and non-functional requirements. Developers are responsible for the verification of quality related requirements, which is known to be difficult to perform. This paper suggests a verification method that can be applied in the area where the conformance of implementation for non-functional requirements is required. The paper performs tests for non-functional requirements by using the information extracted from quality related features that have imposed constraints on design activities.

• Journal of Korea Multimedia Society
• /
• v.8 no.5
• /
• pp.715-720
• /
• 2005

In a software development process, it is necessary to have a method which verifies and satisfies users' requirements in their point of view. This allows the system developer to design a high qualify software system and have it developed and used in an effective way since users' requirements have well been shown through it. In this paper, we propose the RV-UI model system that can verify users' requirements a step ahead of system implementation step. This RV-UI model system has standardized user interface which is in practical use into functional model for each process and it is designed to satisfy users' requirements and manage configuration of them through the interface which has the Kano model.

• Korean Journal of Construction Engineering and Management
• /
• v.5 no.3 s.19
• /
• pp.88-96
• /
• 2004

Recently, client requirements concept is an important issue related to many effects of firms. Especially, if we think that apartment is given a great deal of national construction industry, it is requested that we should try to improve apartment quality with various methods of client requirements survey and reflecting those on apartment project. The technique searching and applying client requirements to apartment project is requested for that and ROQ(Return On Quality) process connected to QFD(Quality Function Deployment) is a technique which is used in manufacturing industry and help to make money by rising client satisfaction with searching clients requirements, and applying this to quality improvement program. In this study apartment quality management development is suggested through using ROQ process. For this customer interview research and FGI(Focus Group Interview) was carried out and clients requirement was analyzed with this. Then quality improvement program applicable to developing a new apartment product was established with specialist monitoring. A new apartment quality management development plan is prosed with this process.

• Journal of KIISE:Software and Applications
• /
• v.33 no.8
• /
• pp.655-667
• /
• 2006

This paper proposes a method for counting function point using goal and scenario based requirements. Function Point is a software sizing method and widely used as a basis to estimate software development cost. Requirements elicitation and analysis should be performed before function point analysis but function point analysis method doesn't deal with requirements elicitation and analysis. For that reason, Function point extraction method from existing requirements method is needed and if the requirements method has advantage for traceability and elicitation, it is suitable for managing cost. Goal and scenario method is widely used as requirements elicitation and analysis. It has also good traceability. Therefore, this paper discusses a method for extracting function point from requirements text gathered using the goal and scenario based requirements elicitation technique. The proposed method aims to establish and maintain traceability between function point and requirements text. Text based function point extraction guidance rules have been developed. The proposed methodology has been applied to Order Processing System development.

• Journal of KIISE
• /
• v.44 no.9
• /
• pp.893-907
• /
• 2017

In safety-critical systems, software defects may have serious consequences. Therefore, defects should be considered during the requirements specification process, which is the first step of a software development lifecycle. Stakeholder requirements that are usually written in natural language are difficult to derived, and there may also be defects due to ambiguity and inaccuracy. To address these issues, we propose a requirement specification method using a standardized Boilerplate and a GSN Model. The Boilerplate is a semi-standard language that follows a predefined format. Due to its ability to provide a consistent representation of the requirements, boilerplate helps stakeholders avoid ambiguities about what they mean and to define the exact meaning of the requirement. Meanwhile, GSN is recognized notation to prepare a Safety Case to prove to authorities that a system is safe. It can be expressed as a functional goal, e.g., Safety Evidence, etc. The proposed study allows an analyst to easily identify a fault from the early stage of the software development lifecycle. The Boilerplate and GSN Model are designed to specify the requirements of safety critical systems and to prove safety conformity through a connection with Safety Evidence. In addition, the proposed approach is also useful to develop secure software by correcting deficiencies in the requirements found during this process.

• Journal of the Korea Society of Computer and Information
• /
• v.17 no.11
• /
• pp.149-161
• /
• 2012

In the customer-centered world, which is used internet and social network services actively, it is important that their needs should be embraced into systems. Our study proposes a technique to normalize and select 1,800 customer's needs at C company. In order to normalize the requirements, we have specified requirements by considering a standard for requirements specification, have identified a set of keywords of requirements and have constructed a relation-graph of requirements. The graph presents objectives to design and build a system, and shows a degree of relative importance for each requirement. And then, we propose a techniques for requirements selection according to their contribution points, which are calculated using relative degree. We demonstrates our techniques by a case study of C company.

• Journal of the Korea Institute of Information and Communication Engineering
• /
• v.3 no.4
• /
• pp.715-722
• /
• 1999

This paper was studied on developmental direction of Telecommunications system for aged welfare policy. The results of this study is as follow: An economic needs must development of home shopping system, home banking system and telecommuting system. A medical needs must development of medical support system, medical information system and telemedical support system. A house needs must development of home automatic system, internet system. A culture needs must development of event system, leisure information system. A traffic needs must development of automatic traffic geographical system, automatic operating system. An education needs must development of teleeducation system, knowledge studying support system.

• Journal of Digital Convergence
• /
• v.12 no.12
• /
• pp.477-484
• /
• 2014

This study was examined relation to comprehensive needs and the quality of life in cancer patient. The Study period was 15 to 24 October 2012. The participants were 100 cancer patients more than 20 years old with cancer. Information and educational requirements are the highest need, and social support is the lowest one in patients with cancer. The longer survival time after diagnosis of cancer was, the higher social support requirements were needed. The Information and education requirement about healthy life showed higher in a family history of cancer. The cancer patients with stage IV ask higher service requirement significantly. and showed that physical and psychological requirements were getting higher, the quality of life became lower. As a result of this study, Physical and Psychological requirements were the most significant factors that affect the quality of life in cancer patients. Therefore, it is necessary to develop the physical and psychological supporting system and to provide appropriate Intervention for them.

• The Journal of the Institute of Internet, Broadcasting and Communication
• /
• v.16 no.1
• /
• pp.263-271
• /
• 2016

Software requirement analysis is necessary for successful software development project. Specially, incomplete requirement is the most influential causes of software project failure. Incomplete requirement can bring late delay and over budget because of the misunderstanding and ambiguous criteria for project validation. Software requirement patterns can help writing more complete requirement. These can be a reference model and standards when author writing or validating software requirement. Furthermore, when a novice writes the software scenario, the requirement patterns can be one of the guideline. In this paper proposes an automatic approach to identifying software scenario patterns from various software scenarios. In this paper, we gathered 83 scenarios from eight industrial systems, and show how to extract 54 scenario patterns and how to find omitted action of the scenario using extracted patterns for the feasibility of the approach.

• The Journal of Society for e-Business Studies
• /
• v.12 no.3
• /
• pp.33-47
• /
• 2007

The requirements have been changed during development progresses, since it is impossible to define all of software requirements. These requirements change leads to mistakes because the developers cannot completely understand the software's structure and behavior, or they cannot discover all parts affected by a change. Requirement changes have to be managed and assessed to ensure that they are feasible, make economic sense and contribute to the business needs of the customer organization. We propose a feature-oriented requirements change management method to manage requirements change with value analysis and feature-oriented traceability links including intermediate catalysis using features. Our approach offers two contributions to the study of requirements change: (1) We define requirements change tree to make user requirements change request generalize by feature level. (2) We provide overall process such as change request normalization, change impact analysis, solution dealing with change request, change request implementation, change request evaluation. In addition, we especially present the results of a case study which is carried out in asset management portal system in details.