星UML 5.0入门教程：构建与API应用

需积分: 9 60 浏览量更新于2024-07-23 收藏 3.31MB PDF 举报

本教程详细介绍了StarUML 5.0，一款功能强大的统一建模语言（UML）工具，旨在帮助用户理解和掌握其使用方法。StarUML 5.0 Developer Guide由Minkyu Lee、Hyunsoo Kim、Jeongil Kim和Jangwoo Lee共同创作，遵循GNU Free Documentation License 1.2或更高版本，允许用户自由复制、分发和修改文档。教程内容分为五个章节： 1. **简介**： - **星型统一建模语言概览**：介绍StarUML的基本概念，以及它在软件开发中的作用，特别是作为UML建模平台的价值。 - **为什么选择UML/MDA（模型驱动架构）**：讨论UML作为标准建模语言的优势，以及星型UML如何支持模型驱动开发的方法论。 2. **StarUML架构**： - **平台架构**：深入解析StarUML软件架构的设计，包括各个组件的功能和它们之间的协作。 - **模块组织**：指导用户如何组织项目结构，确保高效地利用星型UML的各项功能。 - **OpenAPI概述**：讲解星型UML的开放应用程序接口（OpenAPI），它为高级定制和扩展提供了可能。 3. **Hello, World! 示例**： - **创建脚本**：通过一个简单的例子展示如何使用StarUML来创建基础模型，如绘制基本的类图或序列图。 - **菜单扩展文件**：介绍如何编写和部署自定义菜单项，提升用户体验。 - **插件部署与注册**：步骤详解如何安装和注册插件，以便集成额外的功能到星型UML环境中。 - **验证与执行添加的插件**：确保新功能正常工作的方法和流程。 4. **使用OpenAPI**： - **项目API应用**：教授如何通过API操作整个项目的生命周期，如创建、编辑和管理。 - **元素API操作**：涉及如何处理UML模型中的各种元素，如类、接口和关系等。 - **应用对象API**：针对与应用程序交互的对象进行操作，如工具栏、视图等。 - **元对象API**：深入理解并利用星型UML中的元数据和元模型功能。 5. **编写策略**： - **B**：这部分可能是对特定编程风格或最佳实践的探讨，例如面向对象设计原则，或者是如何有效地利用API进行代码生成或自动化过程。通过阅读和遵循这个教程，学习者可以全面掌握StarUML 5.0，无论是为了个人项目开发，还是希望成为该工具的开发者或扩展者。每个章节都注重实用性和深入理解，确保用户能够灵活运用星型UML进行软件建模和工程。

StarUML5.0DeveloperGuide(UsingOpenAPI)

http://staruml.sourceforge.net/docs/developer-guide(en)/ch04.html

varprjmgr=app.ProjectManager;

prjmgr.NewProjectByApproach("UMLComponents");

Opening Project

To open a project file (.UML), acquire reference for the IProjectManager

object and then use the

OpenProject

method.

varapp=newActiveXObject("StarUML.StarUMLApplication");

varprjmgr=app.ProjectManager;

prjmgr.OpenProject("C:\\MyProject.uml");

Saving Project

To save the project currently open in StarUML™, acquire reference for the IProjectManager object and then use

the SaveProject method. Use the SaveProjectAs method to save with a different name, and use the

SaveAllUnits method to save all units under the project.

varapp=newActiveXObject("StarUML.StarUMLApplication");

varprjmgr=app.ProjectManager;

prjmgr.SaveProject();

prjmgr.SaveProjectAs("MyProject2.uml");

prjmgr.SaveAllUnits();

Closing Project

To close a project, acquire reference for the IProjectManager

object and then use the

CloseProject

method.

varapp=newActiveXObject("StarUML.StarUMLApplication");

varprjmgr=app.ProjectManager;

prjmgr.CloseProject();

Unit Managment

Separating New Unit

To separate a new unit for managing a package, model, or subsystem as a separate file, acquire reference for the

IProjectManager

object and then use the

SeparateUnit method.

varapp=newActiveXObject("StarUML.StarUMLApplication");

varprjmgr=app.ProjectManager;

varpkg=...//Assignreferenceforthepackagetoseparateasanewunit.

varnew_unit=prjmgr.SeparateUnit(pkg,"NewUnit.unt");

Merging Unit

If a separated package, model, or subsystem unit does not need to be managed as a separate file and needs to be

merged, acquire reference for the

IProjectManager

object and then use the

MergeUnit

method.

StarUML5.0DeveloperGuide(UsingOpenAPI)

http://staruml.sourceforge.net/docs/developer-guide(en)/ch04.html

varapp=newActiveXObject("StarUML.StarUMLApplication");

varprjmgr=app.ProjectManager;

varpkg=...//Assignsreferenceforthepackagethatwillnolongerbemanagedasaunit.

prjmgr.MergeUnit(pkg);

Accessing Sub-Unit

Units can be organized hierarchically. A project can have many units under it, and each unit can have many

sub-units. The following example illustrates accessing the sub-units within a unit.

varunit=...//Assignsreferencefortheunitthatcontainssub-unitstoaccess.

for(vari=0;i<unit.GetSubUnitDocumentCount();i++){

varsub_unit=unit.GetSubUnitDocumentAt(i);

...

}

Model Fragment Management

Making Model Fragment from Package

Package, model, or subsystem can be saved as a separate model fragment file. Acquire reference for the

IProjectManager

object and then use the

ExportModelFragment method.

varapp=newActiveXObject("StarUML.StarUMLApplication");

varprjmgr=app.ProjectManager;

varpkg=...

//Assignspackagetomakeasamodel.

prjmgr.ExportModelFragment(pkg,"MyFragment.mfg");

Importing Model Fragment

A model fragment file can be added to a package, model, or subsystem. Acquire reference for the

IProjectManager

object and then use the

ImportModelFragment method.

varapp=newActiveXObject("StarUML.StarUMLApplication");

varprjmgr=app.ProjectManager;

varpkg=...//Assignspackagetoaddamodelfragment.

prjmgr.ImportModelFragment(pkg,"MyFragment.mfg");

Using APIs for Elements

This section introduces interface types that are modeling elements of

StarUML™ external API, and describes their

usage. Modeling elements refer to the UML model, view, and diagram el

ements that are used when modeling

software. Model elements such as package, class, and actor, view elements that correspond to each model element,

and diagram elements such as class diagram and use case diagram are e

xamples of modeling elements. Model,

view, and diagram elements can be created, deleted or modified using external API for modeling elements.

Note: Please refer to

"Appendix B. List of UML Modeling Elements"

for a complete listing of UML modeling

elements.

Modeling Element Structure

Modeling elements are organized in the following logical groups.

StarUML5.0DeveloperGuide(UsingOpenAPI)

http://staruml.sourceforge.net/docs/developer-guide(en)/ch04.html

Core Elements: The Core Elements group defines the top interface for model, view, and diagram elements.

ExtCore Elements

: The ExtCore Elements group defines the common top interface for extensible model

elements.

ViewCore Elements

: The ViewCore Elements group defines the core types for view elements.

UML Model Elements: Defines the UML model elements. The UML standard modeling elements fall into this

category.

UML View Elements

: The UML View Elements group defines the UML view elements.

Modeling elements are largely divided into

model

, view, and diagram

types. However, the diagram type is

actually a part of the model or view types, and thus it is more accur

ate for the division to be made into

model

type

and view

type. Model is the element that contains actual information for the s

oftware model, and view is a visual expression

of information contained in a specific model. One model can have multiple views and a view generally has reference

to one model.

Simple Example of Using Modeling Elements

Before introducing the external API interfaces for modeling elements, let us look at a simple example of using

modeling elements. Suppose we want to track StarUML™ application’s top-level project element through

namespace type elements like package, class, and interface, all the way down to the sub-elements of each

namespace type element. In this case, the modeling element structure must be utilized. The following is the Jscript

code for utilizing the modeling element structure.

varapp,prj;

app=newActiveXObject("StarUML.StarUMLApplication");

prj=app.GetProject();

VisitOwnedElement(prj);

functionVisitOwnedElement(owner){

varelem;

for(vari=0;i<owner.GetOwnedElementCount();i++){

elem=owner.GetOwnedElementAt(i);

...

if(elem.IsKindOf("UMLNamespace"))VisitOwnedElement(elem);

}

}

In this example, all sub-elements that are in "OwnedElement" relationships with the top project element are

recursively obtained. The most crucial part of this code is the user-

defined function called

VisitOwnedElement

This function takes an IUMLNamespace type element (which is a modeling element) as an argument and uses

GetOwnedElementCount and GetOwnedElementAt, which are IUMLNamespace

interface methods.

Information required for structuring the

VisitOwnedElement

function can be obtained from the relationships of the

StarUML5.0DeveloperGuide(UsingOpenAPI)

http://staruml.sourceforge.net/docs/developer-guide(en)/ch04.html

Information required for structuring the

VisitOwnedElement

function can be obtained from the relationships of the

modeling elements. The following diagram illustrates the relationship

s between StarUML™ external API interface

types that are related to the IMULNamespace interface example above.

The

IUMLNamespace

interface is inherited from IUMLModelElement

, which is a shared upper type for

IUMLPackage, IUMLClass, and IUMLInterface

types.

IUMLNamespce

also has an association called

Namespace-OwnedElement

. The diagram illustrates that the

IUMLNamespace

type modeling elements like

IUMLPackage, IUMLClass, etc. have IUMLModelElement type elements below them known as

OwnedElements.

As such, external API modeling elements interfaces are defined according to the relationships between the modeling

elements.

Note: Modeling element names that fall into the category of standard UML elements start with an "

UML

" prefix

before the standard UML element names. For example, the name of a UML element called Actor is UMLActor

. And

for external API, the prefix "I" is used according to coding procedures, as in IUMLActor. Please refer to "Appendix

B. List of UML Modeling Elements"

for a complete listing of UML modeling elements and their names.

Convention for Expressing Association for External API

The diagram above illustrates that IUMLModelElement and IUMLNamespace

interface types have an

OwnedElement-Namespace association. Such associations are expressed a

s references in StarUML™'s external API

interface. For example, Namespace association in the IUMLModelElement interface is expressed as below.

IUMLModelElement

Namespace: IUMLNamespace

Further,

OwnedElement

association in the

IUMLNamespace

interface is expressed as below. This is because the

Multiplicity attribute of the metamodel is * and groups or list struc

tures are used in the internal implementation of

the program. As all associations in external API interface definition are expressed using the same convention, this

applies to all other interfaces as well as IUMLModelElement-IUMLNamespace.

IUMLNamespace

function GetOwnedElementCount(): Integer;

function GetOwnedElementAt(Index: Integer): IUMLModelElement;

Core Elements

Core Elements are top parent interfaces for modeling elements.

IElement

IModel

, IView, IDiagram, and

IDiagramView

interfaces fall into this category, and they are organized as illustrated in the diagram below. The organization below

should be given special attention as core group interface types are quite frequently used and they play critical roles.

Associations between the interfaces should be given special emphasis

here.

StarUML5.0DeveloperGuide(UsingOpenAPI)

http://staruml.sourceforge.net/docs/developer-guide(en)/ch04.html

Associations between the interfaces should be given special emphasis

here.

Interface name Description

IElement Interface type that defines the top shared element for all modeling elements.

IModel Interface type that defines the shared parent element for model elements.

IView Interface type that defines the shared parent element for view elements.

IDiagram Interface type that defines the shared parent element for diagram mod

el elements.

IDiagramView Interface type that defines the shared parent element for diagram view elements.

IElement

interface defines the top shared type for all modeling elements, and provides the following main methods.

Main method Description

GetGUID(): String

Function that returns the GUID (Global Unique Identifier) of

modeling elements. GUID is encoded as Base64.

GetClassName(): String Function that returns class names of modeling elements. Return

value example: "UMLClass"

IsKindOf(ClassName: String): Boolean Function that verifies whether the modeling element is the same

type of element received as an argument. Argument value

example: "UMLClass"

IsReadOnly(): Boolean Function that verifies whether the modeling element is read-only.

Attributes of read-only modeling elements cannot be modified.

MOF_GetAttribute(Name: String): String Returns in strings the default type attribute values of modeling

elements as defined by arguments.

MOF_GetReference(Name: String): IElement

Returns the reference type attribute (object reference) values of

modeling elements as defined by arguments.

MOF_GetCollectionCount(Name: String):

Integer

Returns the count number of items in reference collection as

defined by arguments.

MOF_GetCollectionItem(Name: String;

Index: Integer): IElement

Returns the attribute value (object reference) of the 'index' order

item in the reference collection of modeling elements as defined

by arguments.

Among the methods of

IElement

interface, the

MOF_

XXX

methods provide consistent ways to access the attribute

values of each modeling element by string names. For instance, IUMLModelElement, a sub-type of IElement

has an attibribute called "Visibility". In general, the expression IUMLModelElement.Visibilty is used to get the

value of this attribute. But the

IElement.MOF_GetAttribute

method can be used as illustrated below to get the

剩余122页未读，继续阅读

Julian_Huang

粉丝: 13
资源: 26

星UML 5.0入门教程：构建与API应用

Marvell推出超薄型基于PCIe的88NV8120 NAND闪存控制器

Marvell推出基于PCIe的超小型NAND闪存控制器88NV8120

staruml用户手册 pdf格式 和staruml5.0软件——第2部分

staruml5.0使用教程

StarUML5.0.rar

starUML 5.0操作指南

StarUML5.0汉化版

StarUML5.0汉化补丁，绝对可用

StarUML5.0真多绿色版UML建模工具

StarUML 5.0 使用教程：快速上手与进阶指南

最新资源

staruml用户手册 pdf格式和staruml5.0软件——第2部分