• Journal of KIISE:Software and Applications
• /
• v.30 no.12
• /
• pp.1193-1207
• /
• 2003

Various web applications are developed as the Internet is popularized in many fields. However, in most cases of web application development, systematic analysis is omitted and developers jump into the implementation. Therefore developers have difficulties with applying the development methods for a large scale project. The approach of creating an analysis models of a web application from a business model is proposed for the rapid and efficient development. The analysis process, tasks and techniques are proposed for this approach. The use case diagram and web page list are created from business modes that is depicted using the notation of UML activity diagram. The page diagram and logical / physical database models are created using the use case diagram and the web page list. These analysis models are refined during the detailed design phase. The efficiency of proposed method has been shown using a practical case study which reflects the development project of the web application for supporting the association of auto repair shops.

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

• Proceedings of the Korea Inteligent Information System Society Conference
• /
• 1999.10a
• /
• pp.355-361
• /
• 1999

An application of case-based reasoning is proposed to build an influence diagram for identifying successful new ventures. The decision to invest in new ventures in characterized by incomplete information and uncertainty, where some measures of firm performance are quantitative, while some others are substituted by qualitative indicators. Influence diagrams are used as a model for representing investment decision problems based on incomplete and uncertain information from a variety of sources. The building of influence diagrams needs much time and efforts and the resulting model such as a decision model is applicable to only one specific problem. However, some prior knowledge from the experience to build decision model can be utilized to resolve other similar decision problems. The basic idea of case-based reasoning is that humans reuse the problem solving experience to solve a new decision. In this paper, we suggest a case-based reasoning approach to build an influence diagram for the class of investment decision problems. This is composed of a retrieval procedure and an adaptation procedure. The retrieval procedure use two suggested measures, the fitting ratio and the garbage ratio. An adaptation procedure is based on a decision-analytic knowledge and decision participants knowledge. Each step of procedure is explained step by step, and it is applied to the investment decision problem in new ventures.

• Asia pacific journal of information systems
• /
• v.11 no.1
• /
• pp.117-137
• /
• 2001

B2B(business-to-business) commerce has become the prime driver of contemporary electronic commerce. Under B2B commerce, corporations often must operate across organizational boundaries to share their business processes. Workflow management was proposed by Aalst(4, 5) to support several business partners that are involved in shared workflow processes in B2B commerce. We designed a messaging system for B2B workflow, where heterogeneous workflow management systems on each organization for trade were integrated. Based on Aalst's example in(4, 5), we analyzed B2B workflow by using class diagram, use case diagram, activity diagram, and statechart diagram of UML, and designed the messaging system, We also demonstrated a prototype system which was implemented by using Java API and XML. To compare with a holistic system such as EDI systems, the messaging system allows the business partners in B2B commerce to communicate with each other by dedicated messages and integrate each B2B interoperable workflow without any restrictions.

• The Transactions of the Korean Institute of Electrical Engineers A
• /
• v.53 no.2
• /
• pp.111-120
• /
• 2004

This paper presents an application of Unified Modeling Language(UML) software technique for developing transmission pricing evaluation package. Also, this paper describes a transmission pricing algorithm applicable to a large-scale power system. The usage-based transmission pricing mechanism is very complex since it requires power flow analysis, fault current analysis, sensitivity evaluation of a transmission line, penalty factors calculation, transmission asset databases, and cost allocation rules, etc. For the efficient and flexible development of the transmission pricing package, a UML. approach is applied, which is composed of a use-case diagram, interaction diagram, class diagram, and package diagram using Rational Rose Unified Process(RUP). The designed transmission pricing package can be efficiently modified and reused as the market environments evolves since it is designed by Object-Oriented Programming(OOP).

• International Journal of Knowledge Content Development & Technology
• /
• v.7 no.2
• /
• pp.5-20
• /
• 2017

The notion of object oriented analysis and design in software engineering has many rewards that aid the programmer to have an understanding of and improve the program efficaciously. Object oriented metrics helps rather a lot to a programmer or developer to comprehend and unravel the thing-oriented trouble readily and exactly. Object oriented metrics helps in examining the usefulness of object oriented applied sciences or in simple phrases Object-oriented metrics depict characteristics of object-oriented programming. The intention of this paper is to have an understanding of concerning the UML, Object oriented evaluation and design and the way it plays in UML.

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

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