Browse Prior Art Database

Method or system to split a large UML Component/Class based on behavior conveyed by collaboration diagrams

IP.com Disclosure Number: IPCOM000240294D
Publication Date: 2015-Jan-21
Document File: 4 page(s) / 75K

Publishing Venue

The IP.com Prior Art Database

Abstract

This document proposes to split a large UML Component/Class based on behavior conveyed by collaboration diagrams. If there is a design which comprises of Components/Classes with large number of methods which are designed to perform unrelated services, then splitting for such monolithic components/classifier is important for decoupling of unrelated functionalities or services. This splitting big components based on collaboration diagrams will ensure that the decoupling is based on behavior of service.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 62% of the total text.

Page 01 of 4

Method or system to split a large UML Component /Class based on behavior conveyed by collaboration diagrams

If there is design which comprises of Components/Classes with large number of methods which are designed to perform unrelated services, then splitting for such monolithic components/classifier is important for decoupling of unrelated functionalities or services.

The proposal intends to provide a method or apparatus using which users can split the monolithic UML components/classifiers
The proposal to split a large UML Component/Class based on behavior conveyed by collaboration diagrams. This method of splitting big components will ensure that the decoupling is based on behavior of services.

Proposed method will work as described:
User selects a Component/Class for splitting and selects a set of sequence diagrams which will be

1.


2.

component/class. If there is no lifeline representing the selected component/classifier, the split operation will not be performed.

Otherwise all operations which are being used in sequence diagram for the selected component will be extracted.

The extracted operations will be refactored into a new class/component If the original Class/Component happens to Implement/Extend any Interface/Class and one the implemented/overriden method happens to be part of extracted operations, then the new component/class will Implement/Extend the Interface/Class

Example:

UML Component "Server" as shown in Figure 1, is a typical example of monolithic...