• Journal of Advanced Navigation Technology
• /
• v.12 no.5
• /
• pp.509-515
• /
• 2008

The requirement analysis which is clear essential important matter of the software development which is successful about demand of the user. Influences big in the software configuration which will be developed. With the development where existing the many softwares the Internet are sudden changed together in web base Web Application, complicated termination the demand of the user increases and many expense and manpower are becoming disturbance in development. However, So far Web Application about the justice of the development environment which is accurate is not becoming well. There is to development and stands but does not reflect the requirement of the user not to be able, the user became freely plan of the function which approaches information with difficult. This paper, Amended a software requirement analysis process, analyzed the method will be able to identify proposed a requirement.

• IE interfaces
• /
• v.17 no.3
• /
• pp.261-268
• /
• 2004

The primary goal of the requirement analysis phase during information system development is to identify and document what is really needed, in a form that clearly communicates to the user and to development team members. Presented in this paper is a QFD(Quality Function Deployment)-based requirement analysis method and procedure for developing a large-scale enterprise information system. For the purpose of elicitation of software functional requirements, this paper adopts the method of HOQ(House Of Quality) and proposes a simplified HOQ which is more suitable for the software requirement analysis. As a result of this paper, it suggests desired functionalities for an integrated design &manufacturing information system.

• Proceedings of the Korean Institute of Information and Commucation Sciences Conference
• /
• 2006.05a
• /
• pp.569-572
• /
• 2006

In this paper, we purpose requirement capturing for RSS reader that be able to aggregate and subscribe to a RSS format document and describing for analysis model. We execute requirement analysis and documentation by using analysis model which is adopted use case model. And the method of requirement analysis is based on Responsibility Driven Design. Analysis model that is not premised on special reader is able to use business model.

• Journal of Intelligence and Information Systems
• /
• v.14 no.4
• /
• pp.161-178
• /
• 2008

Development and realization of ubiquitous services in physical space is now in progress to develop ubiquitous smart space (USS). As the development methodologies for USS, scenario development is performed before requirement analysis and design, or vice versa. However, even though lots of redundant elements could be found between scenarios and requirement analysis results, a sort of structural approaches to join them together has been still very rare. Hence, the aim of this paper is to propose a system which generates ubiquitous service senarios and system analysis specifications according to a novel integration methodology. To do so, scenario and requirement analysis are integrated in a structured manner.

• Korean Journal of Computational Design and Engineering
• /
• v.7 no.1
• /
• pp.42-56
• /
• 2002

Presented in this study is a top-down functional requirement analysis procedure and the desired functionalities for PDM system development, and the benefits of top-down approach over a conventional bottom-up approach is also shown. For the purpose of top-down requirement analysis for PDM system, this study proposes 4P modeling view. 4P modeling view is defined as a modeling perspective for classifying functional requirements and integrating product-related information objects that must be man-aged within PDM systems. Based on 4P modeling templates, benchmarking analysis of commercially major PDM products is conducted and as a result of this analysis, this study suggests desired functionalities for PDM system.

• Journal of the Korea Institute of Information Security & Cryptology
• /
• v.14 no.3
• /
• pp.85-100
• /
• 2004

All information system is information security system that enforced security function. To improve qualify of information security system, suity requirement analysis and specification must be Performed by consistently and typically at early requirement analysis step. In this paper, we propose a security requirements analysis and specification model and process by using Misuse Case Model that extends UML's Use Case Model. And, we propose a cost-effective security product selection algorithm that security product is sufficient of all constructed security functional requirements. It may raise quality of information security system that developed through proposed model and process.

• Korean Journal of Computational Design and Engineering
• /
• v.13 no.2
• /
• pp.121-130
• /
• 2008

The concept of integrated product information has been universalized so that many manufacturing industries have applied the concept to their production system. The field of PDM (Product Data Management), which is one of the core components of the integrated product information, is not an exception. Therefore, various PLM (Product Lifecycle Management) software providers are in process of suggesting the PDM solutions. As the PDM solution is widely adopted in the manufacturing industries, the successful application of the solution has been gathering more strength in manipulation of the product information. However, the standardized implementation methodology is stuck in the basic level contrast with the enhanced PDM's functionality and capability. Present study refers to the application of UML (Unified Modeling Language), which is an object oriented modeling description, to PDM system development procedure. The advantage of UML is its efficiency and effectiveness in handling complex requirement often found in PDM implementation works. This paper shows the integration of PDM and UML proposes a philosophy for the support of requirement analysis throughout the full implementation of PDM system.

• Journal of Information Technology Services
• /
• v.8 no.1
• /
• pp.113-124
• /
• 2009

Value-based requirements engineering process, called The ViRE(Value-Innovative Requirement Engineering) was suggested to create an uncontested market using ERRC(Eliminate, Reduce, Raise, Create) requirements analysis. But ViRE did not provides a quantitative data analysis method for ERRC decision so as to make objective decisions for customers. In this paper, to solve this problem, we suggest a quantitative ERRC analysis method by estimating requirements cost. Our method defines user requirements and decides their weight. Then, it makes quality level table for all the identified requirements and function modules and estimate implementation cost based on their quality levels. Finally, assess each requirement's impact and then evaluate ERRC value. We could get the more objective ERRC values by evaluate the requirement weight. functional module weight, and implementation cost. And we proved the efficiency of our model by a case study, smart student ID system.

• Journal of the Society of Naval Architects of Korea
• /
• v.55 no.3
• /
• pp.243-251
• /
• 2018

In the shipyard, a lot of data is generated, stored, and managed during design, construction, and operation phases to build ships and offshore structures. However, it is difficult to handle such big data efficiently using existing data-handling technologies. As the big data technology is developed, the ship and offshore industries start to focus on the existing big data to find valuable information from it. In this paper, the material requirement estimation method of offshore structure piping materials using big data analysis is proposed. A big data platform for the data analysis in the shipyard is introduced and it is applied to the analysis of material requirement estimation to solve the problems in piping design by a designer. The regression model is developed from the big data of piping materials and verified using the existing data. This analysis can help a piping designer to estimate the exact amount of material requirement and schedule the purchase time.

• Journal of KIISE:Computing Practices and Letters
• /
• v.8 no.6
• /
• pp.657-668
• /
• 2002

Software life cycle consists of requirement analysis, design, implementation, and maintenance phases, and the product of each phase has various format. The UML normalizes such products, and the class diagram, use case diagram, activity diagram and collaboration diagram are usually used for the requirement analysis phase. Because most of UML development tools store such diagrams in a file, there nay be some difficulties of information retrieval and co-work among users. To cope with the difficulties, this paper proposes a database supported methodology to store and manage the diagrams produced by the requirement analysis. In this methodology, the constituents of class, use case, activity and collaboration diagram are first analyzed and then transformed in the form of relational fables. The constituents of such diagrams are stored as tables in a database, and can be easily retrieved from the database by using some queries. This database supported methodology provides the concurrent sharing and high reuse of diagrams.