Browse Prior Art Database

Using a transparent cube to denote software model element

IP.com Disclosure Number: IPCOM000170661D
Original Publication Date: 2008-May-26
Included in the Prior Art Database: 2008-May-26
Document File: 3 page(s) / 117K

Publishing Venue

IBM

Abstract

A program is disclosed on modelling IT System using a single transparent cube model for the target system. The transparent cube will have six aspects: 1. business functions aspect The business functions aspect will capture the initial business requirements. It will be in a free text format which typically produced by business users.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 51% of the total text.

Page 1 of 3

Using a transparent cube to denote software model element

The invention is a software system and method to model IT system. It is a visual software modelling system that uses a transparent cube to denote a model element rather than the traditional 2D rectangle. It also aims at using a single model to representing an IT system, rather than the traditional multiple models approach.

The basic model element under this modelling system is a transparent cube, which can represent the overall system, and can be decomposed to low level transparent cubes to represent fine-grained software components. See Fig 1 below for each aspect of the transparent cube:

1: Business Function Aspect

2: Process Logic Aspect


3: Implementation Aspect


4: Policy Constraint Aspect

5: Operational Aspect


6: Infrastructure Aspect

Fig 1 Six Aspects of a Transparent Cube Representing a Model Element

Each side of the cube represents a particular aspect. With the top side (1) represents the business function aspect , the left front side (2) represents the process logic aspect, right front side (3) represents the Implement aspect. The left back side (4) represents the policy constraint aspect. The right back side (5) represents the operational aspect. Finally the bottom side (6) represents the infrastructure aspect.

A system can be further decomposed into components. Each component can be modelled using a transparent cube. The decomposition can go down to the appropriate fine-grained level. Double clicking on a transparent cube allows to display or add low level transparent cubes. A modeller, depending on the role he/she plays, can select the appropriate aspect of the transparent cube to work on. He/she can also gets input from other aspects. Depending on the level of decomposition, the modeller can create artefacts in the relevant aspects. For example, he/she can use BPMN to create business process in the process logic aspect, he/she can also create component diagram artefact using UML in the implementation aspect. In the low level component, he/she can create UML class diagram in the implementation aspect.

Fig2 below illustrates how to select the appropriate aspect to work on. Basically the user can drag a line between diagonal corners to select a particular aspect. For example:

To select business function aspect (1), drag a line between A-C, or B-D,

Same as the rest aspects:

For Process Logic aspect (2): drag a line between D-G, or H-C For Implementation aspect (3): drag a line between C-F, or B-G For Po...