Browse Prior Art Database

Generation and Management of Configuration Management artifacts from information attached to the modeling elements Disclosure Number: IPCOM000129262D
Original Publication Date: 2005-Oct-04
Included in the Prior Art Database: 2005-Oct-04
Document File: 3 page(s) / 38K

Publishing Venue



Background: There are different stages in the software development lifecycle; customers create requirements, architects design the product based on the requirements (draw business process model and assign different components to different groups), developers code the components based on the design (drawing UML diagrams. writing code), testers create test cases based on the design etc. Current approach for project development: 1. The architectural model is defined using a business process model. 2. Documents are written to highlight domain specific information. Domain specific information includes, the technology that needs to be used for implementing the different components specified in the business process model, team members for completing the project, the version control system, the bug tracking tool, team-room for discussion of various issues, RUP standards to follow etc. The document is used as a base to manage the different systems. 3. Disparate systems are used to manage related artifacts. System administration tasks include creating components in different applications, managing the access list of different users in the system etc 4. Changes in one system require changes to other systems. For e.g. when a developer moves from one group to another, all the software development artifacts like UML diagrams, test cases and code owned by the developer should be reassigned to another developer. Limitations of current software development approaches: 1. Need to keep the data at different systems in sync. For instance depending on the product users have to be created in CMVC and ClearQuest. 2. Inspite of the relationship between systems to mange software artifacts, there is no mechanism to manage these systems. 3. Absence of a mechanism to generate domain specific artifacts from the business and UML models. 4. No provision for attachment of domain specific RUP concepts on the model.

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 48% of the total text.

Page 1 of 3

Generation and Management of Configuration Management artifacts from information attached to the modeling elements

Main Idea

1. Background: What is the problem solved by your invention? Describe known solutions to this problem (if any). What are the drawbacks of such known solutions, or why is an additional solution required? Cite any relevant technical documents or references.

A mechanism to attach domain specific information to the modeling entities. The attached information can then be used to generate and manage the different artifacts in the software development lifecycle.

Scope of the publication

1. Applicable to software development space (analysis, design, development and maintenance).

2. Modeling entities are created in UML or a business model

3. There is no mechanism to attach domain specific information to UML modeling entity. In this disclosure, we assume a modeling application like RSM or RAD provide a feature to add domain specific information to modeling entities. 4. The information attached could be in plain english or generic format like XML

2. Summary of Invention: Briefly describe the core idea of your invention (saving the details for questions #3 below). Describe the advantage(s) of using your invention instead of the known solutions described above. see 3

3. Description: Describe how your invention works, and how it could be implemented, using text, diagrams and flow charts as appropriate.

Problems listed in section 1 are illustrated with an example below. After the problem we discuss how this disclosure solves the problem.

Component A

Component B

Component C

Fig 1: Component Hierarchy

Consider the example shown above, where software component B extends component A and at the same time depends on C.


[This page contains 1 picture or other non-text object]

Page 2 of 3

In the absence of a mechanism to attach information, and the ability to generate and manage the artifacts from the information attached to the model:
1. The different components (A, B and C) need to be created in ClearCase, ClearQuest, teamroom and other software development applications.
2. Need to create an enhancement request for constructing the different components in a bug tracking database like ClearQuest.
3. Managing Access List for an Individual -> Who all can access the code base, design documents etc. What happens when a person moves from one department to another?
4. Manage security aspects of all the components in different software development lifecycle applications.

UML is a standard to model the components. UML does not support attaching domain specific information to the model. But the different modeling tools can add this support on top of UML. Shown below is a view of how information can be attached to modeling entities in RAD or other modeling tools. The different modeling entities have list of domain specific attributes attached to it.

Version control = ClearCase

Technology = W eb Based, JFace

Bug Tracking = ClearQ uest