• 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.

• KSII Transactions on Internet and Information Systems (TIIS)
• /
• v.8 no.1
• /
• pp.123-144
• /
• 2014

Wireless sensor networks are generally deployed for specific applications to accomplish certain objectives over a period of time. To fulfill these objectives, it is crucial that the sensor network continues to function for a long time, even if some of its nodes become faulty. Energy efficiency and fault tolerance are undoubtedly the most crucial requirements for the design of an information extraction protocol for any sensor network application. However, most existing software agent based information extraction protocols are incapable of satisfying these requirements because of static agent itineraries and large agent sizes. This paper proposes an Information Extraction protocol based on Multiple software Agents with Dynamic Itineraries (IEMADI), where multiple software agents are dispatched in parallel to perform tasks based on the query assigned to them. IEMADI decides the itinerary for an agent dynamically at each hop using local information. Through mathematical analysis and simulation, we compare the performance of IEMADI with a well known static itinerary based protocol with respect to energy consumption and response time. The results show that IEMADI provides better performance than the static itinerary based protocols.

• Journal of KIISE:Computing Practices and Letters
• /
• v.16 no.10
• /
• pp.985-989
• /
• 2010

The near future smart ubiquitous computing oriented system will have to provide the optimal (right) service through interactions between users and the system. To provide the right services what the user needs, we should choose the user-centered development for reflecting the user needs, but not the developer-centered development. To do this, we proposed User Behavior Analysis Based Needs Extraction Method [1]. In this paper, we propose Object Extraction and Modeling Method from the user requirements with Fillmore's Case Grammar.

• Journal of Korea Multimedia Society
• /
• v.14 no.1
• /
• pp.1-14
• /
• 2011

While the circulation of images become active, various requirements to manage increasing database are raised. The content-based technology is one of methods to satisfy these requirements. The image is represented by feature vectors extracted by various methods in the content-based technology. The global feature method insures fast matching speed because the feature vector extracted by the global feature method is formed into a standard shape. The global feature extraction methods are classified into two categories, the spatial feature extraction and statistical feature extraction. And each group is divided by what kind of information is used, color feature or gray scale feature. In this paper, we introduce various global feature extraction technologies and compare their performance by accuracy, recall-precision graph, ANMRR, feature vector size and matching time. According to the experiments, the spatial features show good performance in non-geometrical modifications, and the extraction technologies that use color and histogram feature show the best performance.

• Korean Journal of Computational Design and Engineering
• /
• v.4 no.2
• /
• pp.139-152
• /
• 1999

This paper presents a feature-based approach to extracting machining features fro a feature-based design model. In the approach, a design feature to machining feature conversion process incrementally converts each added design feature into a machining feature or a set of machining features. The proposed approach an efficiently handle protrusion features and interacting features since it takes advantage of design feature information, design intent, and functional requirements during feature extraction. Protrusion features cannot be directly mapped into machining features so that the removal volumes surrounding protrusion features are extracted and converted it no machining features. By utilizing feature information as well as geometry information during feature extraction, the proposed approach can easily overcome inherent problems relating to feature recognition such as feature interactions and loss of design intent. In addition, a feature extraction process can be simplified, and a large set of complex part can be handled with ease.

• Journal of the Korean Society of Systems Engineering
• /
• v.18 no.2
• /
• pp.50-57
• /
• 2022

Along with the development of the 4^th Industrial Revolution technology, artificial intelligence technology is also being used in the field of systems engineering. This study analyzed the development status of artificial intelligence technology in the areas of systems engineering core processes such as stakeholder needs and requirements definition, system requirement analysis, and system architecture definition, and presented future technology development directions. In the definition of stakeholder needs and requirements, technology development is underway to compensate for the shortcomings of the existing requirement extraction methods. In the field of system requirement analysis, technology for automatically checking errors in individual requirements and technology for analyzing categories of requirements are being developed. In the field of system architecture definition, a technology for automatically generating architectures for each system sector based on requirements is being developed. In this study, these contents were summarized and future development directions were presented.

• The KIPS Transactions:PartD
• /
• v.9D no.4
• /
• pp.639-650
• /
• 2002

We have to carry out systematic, definite requirements analysis for the successful development of software. The UML gives the ways to grasp user or customer requirements and decide the boundary of business systems from the use case modeling. This paper presents how to extract use case diagram from the requirements specification systematically by applying the standardized rules as a part of the study for use case modeling. We modify requirements specification by applying $R_{RS}$ (Rules for Requirements Specification) and extract actor, use case, relationship by applying $R_{A}$(Rules for Actors), $R_{U}$(Rules for Use Cases) and $R_{R}$(Rules for Relationships) to the modified requirements specification separately and then become to make out use case diagram in the end. By applying the rules presented in this paper to the requirements specification for personnel management, we can reduce the existing difficulties of extracting use case diagram based on the narrative descriptions without any standardized rules.rules.

• Journal of Information Technology Services
• /
• v.13 no.4
• /
• pp.397-410
• /
• 2014

For mobile service organizations, it is one of the most important tasks to reflect users' opinions rapidly and accurately. In this study, the process is defined to elicit requirements of software/system improvement for mobile application by extracting and refining from users' opinion in mobile app, and detailed activities procession method in this processing are also proposed. The process consists of 3 activities to get requirements of software/system improvement for mobile app. First activity is to transform mobile app to software structure and define term dictionary. Second activity is to elicit simple sentences based on software from users' opinion and refine them. The last activity is to integrate and adjust refined requirements. To verify the usability and validity of the proposed process and the methods, the outputs of manual processing and semi-automated processing were compared. As a result, efficiency and improvement possibility of the process were confirmed through extraction ratio of requirements, comparison of execution time, and analysis of agreement ratio.

• Journal of the Society of Naval Architects of Korea
• /
• v.48 no.3
• /
• pp.207-214
• /
• 2011

Ship design requirements described in the building specification should be reflected in the design process. This paper identifies the configuration of requirements mentioned in the building specification using Ontology Representation Language (OWL). Ontology-based semantic search system specifies the requirement items. Through this extraction, building specifications mentioned for each entry are configured to the tree. Tracking requirements for ship design and a set of procedures to instruct is also used for the V model of systems engineering. The semantic search engine of robot agent and ontology can search the requirements specification document and extract the design information. Thereafter, design requirements for the tracking model that proposes the relationship between the associated BOM(bill of material) and product structure.

• Journal of the Korean Operations Research and Management Science Society
• /
• v.28 no.2
• /
• pp.91-103
• /
• 2003

Use case modeling on UML (Unified Modeling Language) is getting widely used in OOAD and CBD and it is considered a useful technique in dealing with the complexity of the requirements analysis. However, some of the problems with use case modeling are that it is not structured, difficult to handle non-functional requirements, and to analyze impacts among use cases. To alleviate these problems, we propose a scenario-based goal-oriented approach for use case modeling. The proposed approach is to apply a goal-oriented analysis method to use case modeling. Since goal-oriented analysis method is not systematic and many heuristics are involved, we have adopted scenarios as the basis for goal extraction. The proposed method is applied to CBIS (City Bus Information Subsystem) in ITS (Intelligent Transportation System) domain. The proposed approach helps software engineers to analyze the impact among use cases and represent non-functional requirements.