Skip to main content

From UML Activity Diagram to Project Management Software

By Freddy Allilaire (INRIA)
March 2007

This use case shows how to translate between UML Activity Diagrams and MSProject. All transformations code in ATL and metamodels code in KM3 is available from the zoos.

Keywords

UML Activity Diagrams, MsProject, Project Management Software.

Overview

This use case shows the possibility to have interoperability between an UML activity diagram and a project management software like MsProject.

UML Activity Diagrams are typically used for business process modeling, for modeling the logic captured by a single use case or usage scenario, or for modeling the detailed logic of a business rule. Although UML activity diagrams could potentially model the internal logic of a complex operation it would be far better to simply rewrite the operation so that it is simple enough that you don’t require an activity diagram. In many ways UML activity diagrams are the object-oriented equivalent of flow charts and data flow diagrams (DFDs) from structured development.

Project management software is a term covering many types of software, including scheduling, resource allocation, collaboration software, communication and documentation systems, which are used to deal with the complexity of large projects. One of the most common tasks is to schedule a series of events, and the complexity of this task can vary considerably depending on how the tool is used.

Microsoft Project is a project management software program developed by Microsoft which is designed to assist project managers in developing plans, assigning resources to tasks, tracking progress, managing budgets and analyzing workloads.

The aim of this case study is to generate an MSProject project from a UML Activity Diagram. The overall approach is summarized in the following figure:

“From UML Activity Diagram to Project Management Software” Use Case’s Overview

“From UML Activity Diagram to Project Management Software” Use Case’s Overview

The XML extraction phase was done by using XML projector available from the AM3 and ATL toolkit. The Model-to-Model transformation phase was implemented by using ATL model-to-model transformations. Metamodels was created by using KM3 syntax and toolkit. All the metamodels mentioned in the previous schema (and so used within this use case) are available at the Download section.

We provide below a set of screenshots showing the different input/output files provided/created with this use case:

Screenshots of the input/outputs of the use case

Screenshots of the input/outputs of the use case

None at the current time.

References

  1. Hoare, C.A.R Monitors: An Operating System Structuring Concept Communications of the ACM, Vol. 17, No. 10. October 1974, pp. 549-557
  2. Dijkstra, E. W. Cooperating Sequential Processes. In programming Languages (Ed. F. Genuys), Academic Press, New York.

Download

Scenario available in the ATL transformation zoo (with source files).

 

 

 

UML metamodel in MDR XMI 1.2, conforming to MOF 1.4.

 

 

 

MsProject metamodel is expressed in the KM3 textual format.

 

 

 

Acknowledgement

The present work is being supported by the Usine Logicielle project of the System@tic Paris Region Cluster.

Back to the top