• Journal of the Korea Academia-Industrial cooperation Society
• /
• v.10 no.12
• /
• pp.3668-3674
• /
• 2009

Use case diagram is used for defining inter-action between users and systems in object-oriented modeling. It is very important to defining users' requirements for efficient software development. In this paper, we propose a object-oriented modeling process using hierarchical use case analysis for designing class model. First, We define many use case diagrams by several hierarchical modeling level. And next, we can also design class model using the use case diagrams. Our proposed modeling process provides interaction between use case model and class model. That can make us to check the modeling process during the software development. Using the proposed object-oriented modeling we can develop software based on users' requirements. It is very useful for class modeling.

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

• Journal of Information Technology Applications and Management
• /
• v.12 no.1
• /
• pp.21-34
• /
• 2005

Object-oriented paradigm has required the fundamental changes in the developers' practice and orientation. However. the relevant literature has not still provided the solid practical methodology but created some myths regarding Use Case modeling. In this study. we attempt to 'demythologize' some key aspects of Use Case Modeling by describing what we have observed in our research and practice. In order to identify the developers' perceptions. the survey methodology was utilized. By discussing the differences between what must be done and what has been done. this study provides rich insights into the better understanding of the Use Case modeling and the successful development of object-oriented systems.

• International Journal of Computer Science & Network Security
• /
• v.21 no.6
• /
• pp.127-136
• /
• 2021

In the systems and software modeling field, a conceptual model involves modeling with concepts to support development and design. An example of a conceptual model is a description developed using the Unified Modeling Language (UML). UML uses a model multiplicity formulation approach, wherein a number of models are used to represent alternative views. By contrast, a model singularity approach uses only a single integrated model. Each of these styles of modeling has its strengths and weaknesses. This paper introduces a partial solution to the issue of multiplicity vs. singularity in modeling by adopting UML use cases and class models into the conceptual thinging machine (TM) model. To apply use cases, we adopt the observation that a use-case diagram is a description that shows the internal structure of the part of the system represented by the use case in addition to being useful to people outside of the system. Additionally, the UML class diagram is recast in TM representation. Accordingly, we develop a TMUML model that embraces the TM specification of the UML class diagram and the internal structure extracted from the UML use case. TMUML modeling introduces some of the advantages that have made UML a popular modeling language to TM modeling. At the same time, this approach supplies UML with partial model singularity. The paper details experimentation with TMUML using examples from the literature. Our results indicate that mixing UML with other models could be a viable approach.

• KIPS Transactions on Software and Data Engineering
• /
• v.3 no.7
• /
• pp.255-262
• /
• 2014

Our previous research[1] suggested object extraction and modeling method based on Fillmore's case grammar. This approach had not considered of use case extraction and method. To solve this problem, we adopt Fillmore's semantic method as linguistic approach into requirement engineering, which refine fillmore's case grammar for extracting and modeling use cases from customer requirements. This Refined mechanism includes the definition of a structured procedure and the representation of visual notations for 'case' modeling. This paper also proposes the use case decision matrix to identify use case size from extracted use cases based on goal oriented requirement engineering(GoRE), which related with the complexity of use case, and also prioritizes the use cases with this matrix. It demonstrates our proposal with the bank ATM system.

• Journal of Internet Computing and Services
• /
• v.10 no.5
• /
• pp.153-163
• /
• 2009

It is necessary to identify the use cases of the supplier systems in order to define new service using their functions. Current use case modeling techniques, however, do not represent the external use cases clearly, because the external system is represented only by an actor. This ambiguity of the modeling technique declines the comprehensiveness of the model, and does not limit the scope of the target system explicitly. In this paper, we propose the extended use case modeling technique for service-oriented computing. This modeling technique enables the definition of external use cases and components. They are used to limit the boundary of the target system, and the relationship between them are modeled by the realization of external use cases. The proposed technique uses UML stereotype extension mechanism. so the compatibility with current use case modeling technique is preserved.

• Journal of Advanced Navigation Technology
• /
• v.14 no.6
• /
• pp.900-908
• /
• 2010

Recently, OOM(Object-Oriented Method) access method which begins to apply to software development is emphasizing development cost and time reduction through independent software reuse. But because of planning to the exclusion of the lack of knowledge and expansion or performance for development technology many problems are coming out. Therefore, this thesis suggests Effective Object-Oriented Modeling methods considering the plan for higher productivity enhancement of software in the software development life cycle. Effective Object-Oriented Modeling method includes, methods, Use Case modeling methods, Analysis Modeling methods, Design Modeling methods and others.

• Journal of Korean Institute of Architectural Sustainable Environment and Building Systems
• /
• v.12 no.6
• /
• pp.627-640
• /
• 2018

Submetering electricity consumption data enables more detail input of end use components, such as lighting, plug, HVAC, and occupancy in building energy modeling. However, such an modeling efforts and results are rarely tried and published in terms of the estimation accuracy of electricity demand. In this research, actual submetering data obtained from a university building is analyzed and provided for building energy modeling practice. As alternative modeling cases, conventional modeling method (Case-1), using reference schedule per building usage, and main metering data based modeling method (Case-2) are established. Detail efforts are added to derive prototypical schedules from the metered data by introducing variability index. The simulation results revealed that Case-1 showed the largest error as we can expect. And Case-2 showed comparative error relative to Case-3 in terms of total electricity estimation. But Case-2 showed about two times larger error in CV (RMSE) in lighting energy demand due to lack of End Use consumption information.

• 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 KIISE:Software and Applications
• /
• v.27 no.4
• /
• pp.357-369
• /
• 2000

SMIL(Synchronized Multimedia integration Language) allows integrating a set of independent multimedia objects into a synchronized multimedia presentation. In this paper, I propose modeling rules, formal models, modeling function and an algorithm for SMIL documents using use case diagram and sequence diagram of UML(Unified Modeling Language), It will be used the use case diagram and collaboration diagram for object-oriented visualizing tool to describe the temporal behavior of the presentation. The main contribution of this paper is that developers of SMIL documents easily generate them using this rules and algorithm. And, the formal models and modeling functions provide an environment for processing object-oriented documents.