• 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 the Korea Institute of Information and Communication Engineering
• /
• v.13 no.5
• /
• pp.868-876
• /
• 2009

This paper presents a design and implementation of Usecase modeling tool to support integrated usecase diagramming and description writing. It also suggests diagram maintaining based on relationship and it makes UML standard diagramming by providing connection verification between diagram elements. It results in not only user-friendly and effective usecase modeling but it also contributing to integrated and consistent usecase modeling.

• Journal of the Korea Institute of Information and Communication Engineering
• /
• v.13 no.2
• /
• pp.243-252
• /
• 2009

This paper presents an implementing of Use Case Description writing tool to support systematically writing and editing Use Case Description. It also supports both 1 column and 2 column formats of use case scenarios and increases convenience for editing scenario steps with automated step numbering function we presented. It results in not only user-friendly and effective description for use case but also contributing to development of integrated use case modeling tool with use case diagram.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2010.11a
• /
• pp.47-49
• /
• 2010

객체지향 설계에 사용하는 모델링 언어인 UML을 이용하여 유스 케이스 다이어그램을 도출합니다. 도출된 유스 케이스 다이어그램을 바탕으로 생성되는 클래스 다이어그램을 관계형 데이터베이스 스키마로 변환 방법을 소개 합니다.

• Journal of KIISE
• /
• v.43 no.10
• /
• pp.1104-1114
• /
• 2016

Software is continuously changing during development and after development. When a change is required, it is difficult to precisely grasp the scope of impact intuitively. A systematic method is needed to accomplish the required change. The purpose of impact analysis on software change is to avoid missing any information by recognizing the ripple effect that the change might cause. This paper proposes a dynamic method that can easily identify the scope of change request by using the association between use-case scenarios and artifacts of UML modeling in object-oriented development environment. By using this approach, the scope of impact that the change might have on other components such as class diagram and sequence diagram in use-case scenarios can be identified by forward tracing. In addition, analysis of influence of possible further changes due to changes in other components can be identified iteratively through backward tracing. The results of this paper are not limited to impact analysis on artifacts and change type. They can also be used as basic guidelines during impact analysis for various change requests.

• Journal of KIISE:Computer Systems and Theory
• /
• v.35 no.8
• /
• pp.394-406
• /
• 2008

Even though context is the most important feature in context-aware systems, the existing requirements engineering cannot support methodology for elicitation and specification of contexts. In this paper, we propose a requirements elicitation method and a requirements specification method for context-aware systems. Our requirements elicitation method is a 6-stepped, incremental, and iterative process. At the beginning steps in the process, we identify the requirements for business logic. Afterwards, we gather the requirements for context logic, model contexts, and identify subsystems. For requirements specification, we suggest a context-aware use case diagram, a context diagram for context modeling, and a context-type-use-case-dependency diagram for the traceability of use cases on the change of context types. We also introduce a case study that we apply our approaches to a real system, and a qualitative evaluation of our approaches. Our study will help stakeholders to efficiently elicit requirements for context-aware systems and to specify them clearly.

• Proceedings of the Korean Information Science Society Conference
• /
• 2005.07b
• /
• pp.379-381
• /
• 2005

비즈니스 시스템 분석을 위한 비즈니스 모델링에서 사용자와 개발자간의 원활한 의사소통은 프로젝트의 성공을 결정할 수 있는 중요한 요소이다. UML 기반의 유스케이스 모델링은 숙련자의 경험에 많이 의존하고 있으며, 모델링의 수준을 결정하기 어렵고, 또한 사용자가 쉽게 이해하기가 어렵다. 따라서 사용자의 업무를 분석하여 직관적으로 표현할 수 있는 속성구조 다이어그램을 이용한 정보구조 모델링은 사용자와 개발자 모두 쉽게 이해할 수 있는 구조로 사용자의 요구사항을 직관적으로 분석하여 요구사항 분석에서부터 발생되는 사용자의 잦은 변경을 줄일 수 있으므로 유스케이스 모델링을 보완할 수 있는 효과적인 방법이 될 수 있다.

• Journal of the Korea Society of Computer and Information
• /
• v.16 no.11
• /
• pp.25-34
• /
• 2011

In this paper we present an integrated design methodology for relational database based on object-oriented analysis and design. The integrated design methodology is based on business profile and has six phases. In the first phase, business use cases are identified and described by macroactivity diagrams and then the macroactivity diagrams are transformed to detailed business activity diagrams by using objects, object flows and business worker's responsibilities. In the third phase, the detailed business activity diagrams are transformed to business class diagrams that describe the static structure of the entire business system based on detailed business activity diagrams. In the four phase, the business class diagrams are transformed to class diagrams that represent the initial conceptual model of the target relational database. In the five phase, we add additional transformations on the class diagrams with generalization and specialization of associations, roles, activities, additional classes and redundant associations. Eventually, the final class diagrams are transformed to relational database schema. The methodology presented in this paper by applying that proposal for organic connection between object-oriented analysis and design methodology and relational database design methodology. And it will be able to deal with integration management. By the integrated design methodology, we can make more easily software systems based on relational database. In the case study, proposal integrated design methodology applied for a visa issuing system.

• Journal of the Korea Society of Computer and Information
• /
• v.7 no.4
• /
• pp.157-162
• /
• 2002

In this paper, we implement the XML and data modeling by the UML tool, in which the class diagram is constructed from the sequence diagram after making the use case diagram. For the XML modeling. the guiding line will be presented to transform the UML class into the XML document, and then an example to draw the XML DTD from the UML class will be also shown. Furthermore, through the proposed data modeling, the integrated design methods for the transformation of the UML class into relational database schema. object-relational database schema and object-oriented database schema also will be proposed. Finally, we will be presented schema for each database system.

• Journal of the Korea Computer Industry Society
• /
• v.7 no.3
• /
• pp.179-184
• /
• 2006

many corporation introduce information system by method to maximize profit and to reduce expense within flood of information along with development of Information Technology. In this paper, construed AS-IS using UML that is an object intention methodology design tool via process of TO-BE process model design and so on to base Use Case diagram, sequence diagram, component diagram make out that do and this is Microsoft's .NET And wished to raise reusability of component and development productivity of software as that embody smaller enterprise type business administration system that .NET-based relationship extension is possible.