S. B.

JAIN INSTITUTE OF TECHNOLOGY, MANAGEMENT &

RESEARCH, NAGPUR.

PRE-LAB

Aim: Installation to Software Engineering Star UML software.

Name of Student: Nupur Y. Kuhite

Roll No.: AD22026

Semester/Year: 5th sem / 3rd year

Academic Session: 2024 - 25

Date of Performance:

Date of Submission:

Department of Emerging Technologies, S.B.J.I.T.M.R, Nagpur.

 AIM: Installation to Software Engineering Star UML software.

THEORY:

● Introduction to StarUML:
StarUML is a sophisticated software modeler aimed to support agile and concise modeling.

The main targets of users are:

○ Agile and small development teams

○ Professional persons
○ Educational institutes.

Project:
● Project is a top-level element stored as a single file (.mdj).

● Modeling a software system requires describing multiple models because it is not

enough to describe the system with a single perspective, so we typically make
multiple models such as Use-Case Model, Design Model, Component Model,
Deployment Model, or others in a Project.

● Typically Project is organized as a set of UMLModels, UMLPackages, or

UMLSubsystems. If you want to know more about UML Elements, please refer to
OMG UML Specification.

Model vs View:

Many users are confusing the difference between diagramming or drawing tools such as
Microsoft Visio and modeling tools such StarUML or Rational Software Architect. First you
need to understand a diagram is not a model.

Model or software model is a description of any aspect of a software system such as

structure, behavior, requirement, and so on. A software model can be represented in textual,
mathmatical or visual form. A Model element is a building block of a software model.

A Diagram is a visual geometric symbolic representation of a software model. A software

model can be represented in one or more diagrams with different aspects. For example, a
diagram can focus on class hierarchical structure while another diagram can focus on interaction
between objects. Diagrams consists of view elements, which are visual representations of a
model element.
 Fragment

A fragment is a part of a project saved as a separate file with the extension name .mfj.
Any element can be exported as a fragment, but typically UMLPackage, UMLModel, and
UMLSubsystem are the candidates. Once a fragment is exported as a file, the fragment can be
reused by importing in a project.

See also
Import Fragment - To import a fragment file
Export Fragment - To export an element to a fragment file

● Types of Diagrams:

○ Class Diagram:

Create Class Diagram

To create a Class Diagram:

● First select an element where a new Class Diagram to be contained as a child.

● Select Model | Add Diagram | Class Diagram in the Menu Bar or select Add Diagram |
Class Diagram in Context Menu.

Classifier

Classifier is an abstract element of:

 ​ Class
​ Interface
​ Signal
​ DataType
​ PrimitiveType
​ Enumeration
​ Component
​ Artifact

You can use QuickEdit for Classifier by double-click or press Enter on a selected classifier.

○ Package Diagram:

Create Package Diagram

To create a Package Diagram:

 ● Select first an element where a new Package Diagram to be contained as a child.
● Select Model | Add Diagram | Package Diagram in Menu Bar or select Add Diagram |
Package Diagram in Context Menu.

Package

To create a Package on a diagram:

​ 1) Select Package in Toolbox.

​ 2) Drag on the diagram as the size of Package.

To create a Package (model element only) by Menu:

​ 1) Select an Element where a new Package to be contained.

​ 2) Select Model | Add | Package in Menu Bar or Add | Package in Context Menu.

You can use QuickEdit for Package by double-click or press Enter on a selected Package.

○ Composite Structure Diagram:

Create Composite Structure Diagram

To create a Composite Structure Diagram:

● Select first an element where a new Composite Structure Diagram to be contained as a

child.
● Select Model | Add Diagram | Composite Structure Diagram in Menu Bar or select
Add Diagram | Composite Structure Diagram in Context Menu.

○ Object Diagram:

Create Object Diagram

To create a Object Diagram:

1) Select first an element where a new Object Diagram to be contained as a child.

2) Select Model | Add Diagram | Object Diagram in Menu Bar or select Add Diagram |
Object Diagram in Context Menu.
 ○ Component Diagram:

Create Component Diagram

To create a Component Diagram:

1) Select first an element where a new Component Diagram to be contained as a child.

2) Select Model | Add Diagram | Component Diagram in Menu Bar or select Add
Diagram | Component Diagram in Context Menu.

Component

To create a Component:

​ 1) Select Component in Toolbox.

​ 2) Drag on the diagram as the size of Component.

To create a Component (model element only) by Menu:

​ 1) Select an Element where a new Component to be contained.

​ 2) Select Model | Add | Component in Menu Bar or Add | Component in Context
Menu.
 ○ Deployment Diagram:

Create Deployment Diagram

To create a Deployment Diagram:

​ 1) Select first an element where a new Deployment Diagram to be contained as a child.

​ 2) Select Model | Add Diagram | Deployment Diagram in Menu Bar or select Add
Diagram | Deployment Diagram in Context Menu.

Node

To create a Node:

​ 1) Select Node in Toolbox.

​ 2) Drag on the diagram as the size of Node.

Deployment

To create an Deployment:

​ 1) Select Deployment in Toolbox.

​ 2) Drag from an element (to be deployed) and drop on a Node.

​
 ○ Use Case Diagram:

Create Use Case Diagram

To create a Use Case Diagram:

​ 1) Select first an element where a new Use Case Diagram to be contained as a child.
​ 2) Select Model | Add Diagram | Use Case Diagram in Menu Bar or select Add
Diagram | Use Case Diagram in Context Menu.

Use Case Subject

To create an Use Case Subject:

​ 1) Select Use Case Subject in Toolbox.

​ 2) Drag on the diagram as the size of Use Case Subject.

Actor

To create an Actor:

​ 1) Select Actor in Toolbox.

​ 2) Drag on the diagram as the size of Actor.
 ○ Sequence Diagram:

Create Sequence Diagram

To create a Sequence Diagram:

​ 1) Select first an element where a new Sequence Diagram to be contained as a child.

​ 2) Select Model | Add Diagram | Sequence Diagram in Menu Bar or select Add
Diagram | Sequence Diagram in Context Menu.

Interaction Operand

You can use QuickEdit for Interaction Operand by double-click or press Enter on a selected
Interaction Operand.

​ Guard : Edit guard property

Endpoint

To create an Endpoint:

​ 1) Select Endpoint in Toolbox.

​ 2) Click at the position on the diagram.
​
 ○ Communication Diagram:

Create Communication Diagram

To create a Communication Diagram:

​ 1) Select first an element where a new Communication Diagram to be contained as a

child.
​ 2) Select Model | Add Diagram | Communication Diagram in Menu Bar or select
Add Diagram | Communication Diagram in Context Menu.
 ○ Timing Diagram:

Create Timing Diagram

To create a Timing Diagram:

​ 1) Select first an element where a new Timing Diagram to be contained as a child.

​ 2) Select Model | Add Diagram | Timing Diagram in Menu Bar or select Add
Diagram | Timing Diagram in Context Menu.
​

Time Segment

To create a Time Segment

​ 1) Select Time Segment in Toolbox.

​ 2) Click on a State/Condition area on the diagram.
 ○ Interaction Overview Diagram:

Create Interaction Overview Diagram

To create an Interaction Overview Diagram:

​ 1) Select first an element where a new Interaction Overview Diagram to be contained as

a child.
​ 2) Select Model | Add Diagram | Interaction Overview Diagram in Menu Bar or
select Add Diagram | Interaction Overview Diagram in Context Menu.
​
Interaction Use, Interaction (inline), Initial, Final,
Fork, Join, Merge, Decision,
Control Flow.
 ○ Statechart Diagram:

Create Statechart Diagram

To create a Statechart Diagram:

​ 1) Select first an element where a new Statechart Diagram to be contained as a child.

​ 2) Select Model | Add Diagram | Statechart Diagram in Menu Bar or select Add
Diagram | Statechart Diagram in Context Menu.

1) State 9) Internal Activity

2) Internal Transition 10) Region
3) Initial State 11) Choice
4) Join, Fork 12) Junction
5) Shallow History 13) Deep History
6) Entry Point 14) Exit Point
15) Connection Point
7) Terminate
Reference
8) Final State
16) Transition
○ Activity Diagram:
Create Activity Diagram

To create an Activity Diagram:

​ 1) Select first an element where a new Activity Diagram to be contained as a child.

​ 2) Select Model | Add Diagram | Activity Diagram in Menu Bar or select Add
Diagram | Activity Diagram in Context Menu.

Features

Action
Accept Signal
Trigger
Accept Time Event
Initial Node
Flow Final Node
Activity Final Node
Object Node
Fork Node
Central Buffer
Join Node
Datastore
Merge Node
Activity Parameter Node
Decision Node
Expansion Region
Swimlane (Partition)
Input Expansion Node
Interruptible Activity Region
Output Expansion Node
Structured Activity Node
Control Flow
Input Pin
Object Flow
Output Pin
Exception Handler
Send Signal
Activity Interrupt

​
 ○ Information Flow Diagram:

Create Information Flow Diagram

To create a Information Flow Diagram:

​ 1) Select first an element where a new Information Flow Diagram to be contained as a

child.
​ 2) Select Model | Add Diagram | Information Flow Diagram in Menu Bar or select
Add Diagram | Information Flow Diagram in Context Menu.
​

Information Item, Information Flow

CONCLUSION:
StarUML is a versatile tool used in software engineering for creating UML
diagrams, aiding in the visualization and design of complex systems. It supports
various diagram types such as class, sequence, and use case diagrams, making it
essential for modeling, communication, and documentation in software development
projects. Its use enhances clarity and efficiency in understanding system architecture
and interactions.