crystal-facet-uml Architecture

MOF::Class C0115

MOF::Feature C0116

MOF::Association C0117

This diagram shows some example classes of the MOF Meta Model.

MOF (M3) C0111

--> MOF::Class R0153

--> MOF::Feature R0154

--> MOF::Association R0155

UML (M2) C0112

--> UML::Image R0690

--> UML::Comment R0157

--> UML::Relationship R0158

--> UML::DirectedRelationship R0159

--> UML::Element R0156

--> UML::Classifier R0177

--> UML::Feature R0178

UML::Element C0118

ownedComment --> UML::Comment R0160

ownedElement --> UML::Element R0161

UML::Comment C0119

--> UML::Element R0162

annotatedElement (0..*) --> UML::Element R0439

UML::Relationship C0120

--> UML::Element R0163

UML::DirectedRelationship C0121

--> UML::Relationship R0164

UML::Classifier C0125

UML::Feature C0129

featuringClassifier --> UML::Classifier R0176

UML::Image C0441

--> UML::Element R0691

SysML (M2) C0190

--> ConstraintProperty R0250

ConstraintProperty C0191

data_database C0037

- wraps the sqlite database
- knows the current status and filename
- opens and closes the database
- manages the list of listeners and notifies changes

data_database _reader C0038

- reads data from the database

has --> data_database R0028

data_database _writer C0039

- writes changes to the database
- ensures low-level consistency of the database, e.g. all foreign keys point to existing rows (referential integrity)
- retrieves the old, changed values for the undo/redo list

uses --> data_database _reader R0027

has --> data_database R0029

data/storage C0004

- provides read access to ctrl, pencil and gui components
- provides write acccess to only the ctrl component
- ensures low-level consistency of database: all referenced objects exist.
- sends notifications on changes

--> data_database _writer R0040

--> data_database _reader R0041

--> data_database R0042

data C0235

--> data/storage R0313

thread-1 C0241

open --> data_database R0320

init(:data_database) --> r1 :data_data base_reader R0326

init(:data_database, r1) --> data_database _writer R0324

get_diagram --> r1 :data_data base_reader R0332

get_classifier --> r1 :data_data base_reader R0333

set_feature --> data_database _writer R0334

destroy --> data_database _writer R0325

destroy --> r1 :data_data base_reader R0329

close --> data_database R0321

thread-2 C0242

init(:data_database) --> r2 :data_data base_reader R0327

get_diagram --> r2 :data_data base_reader R0330

get_classifier --> r2 :data_data base_reader R0331

destroy --> r2 :data_data base_reader R0328

data_database C0037

- wraps the sqlite database
- knows the current status and filename
- opens and closes the database
- manages the list of listeners and notifies changes

data_database _writer C0039

- writes changes to the database
- ensures low-level consistency of the database, e.g. all foreign keys point to existing rows (referential integrity)
- retrieves the old, changed values for the undo/redo list

get_feature --> r1 :data_data base_reader R0335

get_database_ptr --> data_database R0340

--> thread-1 R0337

r1 :data_data base_reader C0244

get_database_ptr --> data_database R0338

--> data_database _writer R0336

r2 :data_data base_reader C0245

In the current implementation, the software runs single-threaded.
If running multiple threads, a possible implementation is that the data_database object exists just once and provides an sqlite3 connection object in SQLITE_CONFIG_SERIALIZED mode (see https://sqlite.org/threadsafe.html ) Every thread gets its own readers and writers (to separate the statements-with-bound-variables and statement-string-buffers)
There is a chance that thread-2 performs multiple independant queries while thread-1 performs a write transaction. This is expected to not cause a problem, given the current sequences of statements.

get_database_ptr --> data_database R0339

Locks needed here C0425

The data_database_writer can handle only one client-thread at a time.

--> data_database _writer R0659

ctrl_controller C0040

- changes the database contents
- maintains the undo redo list

has --> ctrl_consistency_checker R0030

has --> ctrl_undo_redo_list R0213

has --> ctrl_ classifier_ controller R0216

has --> ctrl_ diagram_ controller R0218

ctrl_consistency_checker C0041

- checks and repairs a database

ctrl C0003

- provides write access to the database
- ensures consistency of the uml-model, e.g. no circular contains-relations, no lifelines if no corresponding diagramelement exists

--> ctrl_controller R0043

--> ctrl_consistency_checker R0044

--> ctrl_multi_step_changer R0605

--> ctrl_ classifier_ trigger R0221

--> consistency R0732

--> ctrl_ diagram_ controller R0217

--> ctrl_ classifier_ controller R0215

--> ctrl_undo_redo_list R0211

--> ctrl_ diagram_ trigger R0212

ctrl_undo_redo_list C0153

manages a list of actions to be undone or/and redone.
When performing undo or redo operations, this is done directly to the data_database_writer_t, not to the ctrl_controller which could start an endless-recursion.

db_writer: F0113

db_reader: F0114

ctrl_ diagram_ trigger C0154

ensures that application level policies on the model are adhered whenever diagrams are modified.

post_update_diagram_type: F0109

post_create_diagramelement: F0110

post_delete_diagramelement: F0111

--> consistency R0733

ctrl_ classifier_ controller C0155

performs changes on classifier, feature and relationship tables

calls --> ctrl_ classifier_ trigger R0738

ctrl_ diagram_ controller C0156

performs changes on diagram and diagramelement tables

calls --> ctrl_ diagram_ trigger R0219

ctrl_ classifier_ trigger C0157

ensures that application level policies on the model are adhered whenever classifiers are modified.

post_delete_feature: F0112

after deleting a lifeline, all references from diagramelements have to be removed.

--> consistency R0734

ctrl_multi_step_changer C0407

performs multi-step operations:

- delete a set of objects
- try create either with proposed or with auto-generated id

calls --> ctrl_ diagram_ controller R0606

calls --> ctrl_ classifier_ controller R0607

consistency C0469

calls --> ctrl_ classifier_ controller R0735

pencil_diagram_maker C0032

- coordinates layouting and drawing of a diagram
- implements kind of front controller pattern: all requests from gui to pencil are addressed to the pencil_diagram_maker

uses --> pencil_xxx_layouter R0023

uses --> pencil_xxx_painter R0024

pencil_xxx_layouter C0033

- layouts multiple elements within the bounds of a diagram
- can convert abstract order-values to x/y coordinates and vice versa

modifies --> pencil_layout_data R0022

asks for sizes --> pencil_xxx_painter R0034

pencil_xxx_painter C0034

- knows the bounding boxes of single elements
- draws single graphical elements

requires --> pencil_layout_data R0025

use --> pencil.draw R0702

data_visible_set C0035

- caches data from the database needed to draw a diagram

pencil_layout_data C0036

- stores locations of layouted elements (in the current diagram)

references --> data_visible_set R0021

pencil C0002

- renders diagrams to cairo drawing contexts
- highlights uml-elements as requested by the gui module

pencil_diagram_maker: F0084

--> pencil.draw R0282

--> pencil_diagram_maker R0049

--> pencil_xxx_painter R0051

--> data_visible_set R0052

--> pencil_layout_data R0053

--> pencil_xxx_layouter R0056

--> pencil.layout R0265

--> pencil_diagram_maker R0651

pencil.layout C0196

pencil.draw C0205

Encapulates drawing routines for
- geometric objects
- labels
- symbols/icons

pencil::start C0269

--> gui/io select operations R0371

pencil::draw C0270

--> pencil::finish R0377

pencil::define grid C0271

implemented in pencil_diagram_maker

--> pencil::layout elements R0375

pencil::layout elements C0272

implemented in pencil_diagram_maker

--> pencil::draw R0376

gui/io select operations C0273

layout and draw everything --> pencil::define grid R0372

while dragging, layout and draw --> pencil::layout elements R0373

if layout know, draw only --> pencil::draw R0374

pencil::finish C0274

pencil::activities C0312

--> gui/io select operations R0440

--> pencil::start R0441

--> pencil::draw R0442

--> pencil::layout elements R0443

--> pencil::define grid R0444

--> pencil::finish R0445

layouting:start C0353

--> propose processing order R0498

layouting:finish C0354

propose processing order C0355

For the list of elements to be layouted, define the processing order.

--> propose solutions R0501

propose solutions C0356

This step creates a set of possible solutions for 1 element to be layouted.

--> select solution R0499

select solution C0357

This step selects the most promising of solutions for 1 element to be layouted.

--> end of list? R0509

Layouting Algorithm C0358

--> end of list? R0508

--> propose processing order R0502

--> propose solutions R0503

--> select solution R0504

--> layouting:finish R0505

--> layouting:start R0506

end of list? C0359

finished --> layouting:finish R0510

more elements --> propose solutions R0511

io C0195

file output: IF: F0075

file input: IF: F0095

clipboard in: IF: F0074

clipboard out: IF: F0096

export_trigger: F0085

--> image_format_writer R0283

--> io_data_file R0631

--> documents R0419

--> io_exporter R0285

--> io_importer R0369

start export --> io_exporter R0368

paste --> io_importer R0370

cut/copy --> io_exporter R0566

import/sync --> io_importer R0567

image_format_writer C0206

io_exporter C0208

cases about
- file names
- traversing the diagram tree

--> image_format_writer R0287

--> documents R0423

io_importer C0268

documents C0306

documents implements several strategies to traverse the model and diagram trees. For each found element, an element writer is called.

io_data_file C0416

database: F0101

controller: F0102

xhtml_element_writer (and xml/docbook) C0209

cares about
- writing output-format specific meta data
- using right "writer" class to encode data

5.) document artifacts --> md/txt/xmi/xml/json R0413

md/txt/xmi/xml/json C0282

6.) character stream --> Output Stream R0414

Output Stream C0305

data_database _reader C0038

- reads data from the database

1b) diagram data --> io_exporter R0417

3b) diagrams and model --> io_export_diagram_traversal R0438

io_exporter C0208

cases about
- file names
- traversing the diagram tree

1a) query diagrams --> data_database _reader R0416

2.) trigger --> io_export_diagram_traversal R0435

io_export_diagram_traversal C0307

This class traverses the model in the database. The diagram traversal walks along the diagram tree starting at the root. There are other traversal classes implementing other strategies.

3a) query diagrams and model --> data_database _reader R0436

4.) model data --> xhtml_element_writer (and xml/docbook) R0437

gui_main_window C0042

- represents an application window

has --> gui_toolbox R0226

has --> gui_attributes_editor R0228

--> gui_search_request R0354

has --> sketch R0545

--> gui_simple_message_to_user R0640

gui_window_manager C0045

- starts and stops application windows

has (1..3) --> gui_main_window R0033

gui C0001

- allows a user - to select the database - to export diagrams - to modify the uml-model

--> gui_search_request R0353

--> sketch R0349

--> gui_simple_message_to_user R0639

--> gui_toolbox R0225

--> gui_attributes_editor R0227

--> gui_window_manager R0045

--> gui_main_window R0046

gui_toolbox C0159

controller for the buttons in the tool bar:
- performs the callbacks when the user presses buttons
- switches between search, nav, edit and create mode

notify_listeners: F0087

set_selected_tool: F0086

--> gui_toolbox R0533

--> gui_toolbox R0534

gui_attributes_editor C0160

This class manages 5 widgets.
It reads the data of the currently focused object into cache, it writes back changes to the database (via the controller), it updates the visible widgets when the focused object or the data changes.
A challenge for implementation is, that on one hand, it implements the callback functions for 5 gtk widgets (which look independant if ignoring the internal implementation), on the other hand, it manages just one cached focused object (update on user-interaction, reload on change events).

name_entry: GtkEntry *: F0039

stereotype: GtkEntry *: F0042

type_combo_box: GtkComboBox *: F0040

description_text_view: GtkTextView *: F0041

commit_button: GtkButton *: F0043

object_changed: F0088

--> gui_attributes_editor R0535

sketch C0257

This component is the view and controller for the central sketch widget.
This includes the tree navigation bar and the search result list on the left.

gui_search_request C0258

This class manages
- a text entry widget so that the user can enter a search text
- a button that starts the search.
When a search is started, the gui_search_runner is triggered to execute it.

search_runner: gui_search_runner_t: F0083

gui_simple_message_to_user C0419

This class is the controller for the status bar widgets

search C0263

navigate C0264

edit C0265

create C0266

Widget States C0321

--> data available R0458

--> not-yet-layouted R0463

--> uninitialized R0457

--> layouted R0459

uninitialized C0322

load data --> data available R0460

data available C0323

--> invalid layout R0466

--> layouted R0464

--> not-yet-layouted R0465

invalidate --> uninitialized R0469

layouted C0324

draw (drawing context) --> layouted R0462

not-yet-layouted C0325

do layout (drawing context) --> layouted R0468

invalid layout C0326

--> not-yet-layouted R0467

u8stream/ C0030

provides small, generic utility classes that are independant of the project

--> Simple Random R0554

--> Utf8 Writer R0550

--> u8stream R0405

--> u8list R0700

u8stream C0302

--> Output Stream R0408

--> Input Stream R0547

Output Stream C0305

Input Stream C0375

Utf8 Writer C0378

--> Output Stream R0553

Simple Random C0379

Pseudo random number generator, not suitable for security appliances.

u8list C0412

This package is a collection of functinos to handle variable-length lists in statically allocated fixed-sized buffers.

--> Array List R0624

--> Array Index Sorter R0625

Array List C0267

Array Index Sorter C0058

utf8stringbuf C0194

String library

--> utf8:codepoint iterator R0661

--> utf8:string R0662

--> uft8:stringview iterator R0665

--> storage classes R0667

--> view classes R0668

--> utf8:stringview R0664

--> utf8:stringview tokenizer R0666

--> utf8:stringbuf R0663

--> utf8:codepoint R0660

utf8:codepoint C0426

utf8:codepoint iterator C0427

provides --> utf8:codepoint R0677

iterates on --> utf8:string R0681

utf8:string C0428

The methods of this string take an instance as parameter, which is kind of a pointer to the underlying character array.

utf8:stringbuf C0429

The methods of this stringbuf take an instance as parameter, which is kind of a pointer to the underlying character array.

consumes / produces --> utf8:string R0676

use --> utf8:stringview R0683

utf8:stringview C0430

The methods of this stringview take an instance as parameter, which is kind of a pointer to the underlying character array.

selects --> utf8:string R0678

uft8:stringview iterator C0431

iterates on / provides --> utf8:stringview R0679

utf8:stringview tokenizer C0432

iterates on / provides --> utf8:stringview R0680

storage classes C0433

--> utf8:stringbuf R0669

--> utf8:codepoint R0674

--> utf8:string R0675

view classes C0434

--> uft8:stringview iterator R0670

--> utf8:stringview R0671

--> utf8:codepoint iterator R0672

--> utf8:stringview tokenizer R0673

test_fw C0017

Test framework
- runs test cases
- reports test results

--> test_suite R0301

--> test_assert R0304

--> test_fixture R0305

--> test_runner R0302

--> test_result R0303

test_suite C0227

test_case: [list]: F0054

setup(): F0055

tear_down(): F0056

call --> test_assert R0309

test_runner C0228

aggregate --> test_result R0308

run_suite --> test_suite R0311

test_result C0229

test_assert C0230

test_fixture C0231

The set of preconditions and cleanup-routines

--> test_suite R0306

--> test_suite R0307

ERROR C0386

Error-Categories by Reaction C0387

--> CONTINUE R0575

--> USR_ERROR R0576

--> LOGIC_ERROR R0579

--> OP0_ERROR R0580

--> OP1_ERROR R0577

--> USR_ERROR R0578

--> OP1_ERROR R0573

--> NO_START R0581

--> TERMINATE R0582

CONTINUE C0388

--> ERROR R0569

NO_START C0389

--> ERROR R0568

TERMINATE C0390

--> ERROR R0570

USR_ERROR C0391

notify user: in statusbar: F0097

OP1_ERROR C0392

notify operator: via log: F0098

--> CONTINUE R0574

OP0_ERROR C0393

notify operator: F0099

--> NO_START R0572

LOGIC_ERROR C0394

notify developer: F0100

--> TERMINATE R0571

LOGIC_ERROR C0394

notify developer: F0100

Error-Categories by Reaction C0387

--> LOGIC_ERROR R0579

STATE C0400

--> LOGIC_ERROR R0596

PARAMS C0401

--> LOGIC_ERROR R0595

DATA_CORRUPT C0402

--> LOGIC_ERROR R0594

Error-Categories by Cause C0399

--> PARAMS R0592

--> STATE R0591

--> DATA_CORRUPT R0593

Error-Categories by Reaction C0387

--> OP0_ERROR R0580

--> OP1_ERROR R0577

--> OP1_ERROR R0573

OP1_ERROR C0392

notify operator: via log: F0098

OP0_ERROR C0393

notify operator: F0099

Error-Categories by Cause C0399

--> ENV_RUN R0603

--> SYSTEM_ACCESS R0602

--> TIME/SYNC R0601

--> ENV_START R0604

TIME/SYNC C0403

Timeout of remote calls or cyclic events

--> OP1_ERROR R0597

SYSTEM_ACCESS C0404

--> OP1_ERROR R0598

ENV_RUN C0405

Runtime Envionment

--> OP1_ERROR R0599

ENV_START C0406

Startup Envionment

--> OP0_ERROR R0600

INPUT /SOURCE C0395

--> USR_ERROR R0584

OUTPUT /SINK C0396

--> USR_ERROR R0583

USER_ACCESS (r/w/x) C0397

--> USR_ERROR R0585

WRONG_MODE C0398

The request is not valid in the current situation.

--> USR_ERROR R0586

USR_ERROR C0391

notify user: in statusbar: F0097

Error-Categories by Reaction C0387

--> USR_ERROR R0576

--> USR_ERROR R0578

Error-Categories by Cause C0399

--> USER_ACCESS (r/w/x) R0588

--> INPUT /SOURCE R0590

--> OUTPUT /SINK R0589

--> WRONG_MODE R0587

relationships C0081

id: int64_t: F0014

main_type: enum: F0021

name: F0022

description: F0023

from --> classifiers R0096

to --> classifiers R0097

from --> features R0205

to --> features R0206

classifiers C0080

id: int64_t: F0012

main_type: enum: F0017

stereotype: F0018

name: F0019

description: F0020

--> features R0210

features C0083

id: int64_t: F0013

main_type: enum: F0024

key (name): F0025

value (type): F0026

description: F0027

Simple data structure C0088

The data is structured with focus on simplicity.
pro: Simple data structure. There are similarities to UML (M2 Meta-Model) and MOF (M3 Meta-Model).
con: takes into account that some things of UML cannot be represented

--> relationships R0106

--> classifiers R0107

--> features R0108

relationships C0081

id: int64_t: F0014

main_type: enum: F0021

name: F0022

description: F0023

from --> classifiers R0096

to --> classifiers R0097

from --> features R0205

to --> features R0206

classifiers C0080

id: int64_t: F0012

main_type: enum: F0017

stereotype: F0018

name: F0019

description: F0020

--> features R0210

features C0083

id: int64_t: F0013

main_type: enum: F0024

key (name): F0025

value (type): F0026

description: F0027

diagrams C0084

id: int64_t: F0015

diagram_type: enum: F0028

name: F0029

description: F0030

parent --> diagrams R0099

diagramrelationships C0095

for diagrams that show options/alternatives/scenarios

--> relationships R0126

--> diagrams R0130

Classifier or Relationship selection def. view C0092

Depending on the diagram type, either classifiers determine what is visble or relationships determine what is visible.
pro: similar concept for diagrams that show options/alternatives/scenarios to diagrams that show invariants.
con: Bigger extension to existing structure in version 1.0.0 Algorithm to distinguish used from unused elements gets complicated

--> diagramrelationships R0121

--> diagramelements_simple R0712

diagramelements_simple C0152

id: int64_t: F0034

display_flags: F0035

--> diagrams R0207

--> classifiers R0208

Classifier selection defines view C0090

Diagramelements define which classifiers are visible in which diagram. All features of a visible classifier are shown. All relationships are shown that have visible classifiers at both ends.
pro: simple selection rule
con: Problematic for diagrams that show possible scenarios and alternatives (e.g sequences). This solution assumes that the model is invariant for all diagrams, therefore all diagrams showing examples/scenarios have to show own instances of classes, not generic classes that are used in other diagrams.

--> diagramelements_simple R0209

diagrams C0084

id: int64_t: F0015

diagram_type: enum: F0028

name: F0029

description: F0030

parent --> diagrams R0099

relationships C0081

id: int64_t: F0014

main_type: enum: F0021

name: F0022

description: F0023

from --> classifiers R0096

to --> classifiers R0097

from --> features R0205

to --> features R0206

classifiers C0080

id: int64_t: F0012

main_type: enum: F0017

stereotype: F0018

name: F0019

description: F0020

--> features R0210

features C0083

id: int64_t: F0013

main_type: enum: F0024

key (name): F0025

value (type): F0026

description: F0027

diagramelements_simple C0152

id: int64_t: F0034

display_flags: F0035

--> diagrams R0207

--> classifiers R0208

features C0083

id: int64_t: F0013

main_type: enum: F0024

key (name): F0025

value (type): F0026

description: F0027

classifiers C0080

id: int64_t: F0012

main_type: enum: F0017

stereotype: F0018

name: F0019

description: F0020

--> features R0210

relationships C0081

id: int64_t: F0014

main_type: enum: F0021

name: F0022

description: F0023

from --> classifiers R0096

to --> classifiers R0097

from --> features R0205

to --> features R0206

diagrams C0084

id: int64_t: F0015

diagram_type: enum: F0028

name: F0029

description: F0030

parent --> diagrams R0099

diagramelements C0082

id: int64_t: F0016

display_flags: F0031

--> diagrams R0100

--> classifiers R0101

focused_feature --> features R0204

to select one of possibly several lifelines

lifelines C0466

--> features R0726

DATA_CLASSIFIER _TYPE_INTERACTION C0455

Diagramelements define which classifiers are visible in which diagram. All features of a visible classifier are shown. All relationships are shown that have visible classifiers at both ends. In contrast to Classifier and Port/Lifeline selection def view, this solution links lifelines (which are features) to both: their classifier and also to their interaction.
pro: similar simplicity as Classifier and Port/Lifeline selection def view. The model encodes all information even when ignoring the view classes. The solution is closer to the UML proposal The xmi export would not require exceptional handlings for interactions
con: Idea for this solution popped up after Classifier and Port/Lifeline selection def view was already implemented. There would be 1 more implicit object to manage automatically More error cases have to be handled

--> interaction classifier R0715

--> diagramelements_simple R0714

diagrams C0084

id: int64_t: F0015

diagram_type: enum: F0028

name: F0029

description: F0030

parent --> diagrams R0099

classifiers C0080

id: int64_t: F0012

main_type: enum: F0017

stereotype: F0018

name: F0019

description: F0020

--> features R0210

relationships C0081

id: int64_t: F0014

main_type: enum: F0021

name: F0022

description: F0023

from --> classifiers R0096

to --> classifiers R0097

from --> features R0205

to --> features R0206

features C0083

id: int64_t: F0013

main_type: enum: F0024

key (name): F0025

value (type): F0026

description: F0027

diagramelements_simple C0152

id: int64_t: F0034

display_flags: F0035

--> diagrams R0207

--> classifiers R0208

interaction classifier C0456

--> classifiers R0716

---> has lifeline /. <--- context --> lifelines R0727

lifelines C0466

--> features R0726

sort classifiers by number of parents C0301

traverse the list of classifiers, not the diagrams; export classifiers without parents first; export each classifier together with all children
pro: allows to export the expected xmi structure
con: difficult to implement, diagram descriptions are lost

How to generate the Interactions? C0315

Interactions are
- Sequence,
- Timing,
- Communication and
- Interaction Overview Diagrams

--> sort classifiers by number of parents R0452

Create an new "Interaction" Classifier C0316

This solution is in line with the UML specification: An interaction classifier encapsulates all messages belonging to this interaction. The interaction classifier can be referenced from multiple diagrams.

--> How to generate the Interactions? R0453

Traverse the corresponding diagram C0317

Traverse the corresponding diagram when encountering lifelines. This solution sticks to what the current gui can manage in an understandable way for the user.

--> How to generate the Interactions? R0454

planned solution C0318

pro:
- simpler to implement
- less redundancy in database con:
- less UML like
- no clear separation of model and diagrams
- no solution for interaction fragments

--> Traverse the corresponding diagram R0455

Performance of User Interface C0286

Reliability of Program operation C0287

Degradation Mode Scenario C0288

If memory resources are low, a degradation mode is acceptable if
- no data from the database is lost
- the focused diagram is displayed correctly
- the data export works reliably
- 3 undo operations are possible
In degradation mode, the following shortcomings are acceptable:
- not all diagrams on a screen are drawn completely
- the list of search results may be truncated
- the number of simultaneous open windows may be limited

--> Reliability of Program operation R0395

explains --> Degradation Mode R0396

Degradation Mode C0295

In case of low memory, the base functionality of crystal-facet-uml shall still work reliably.

--> Reliability of Program operation R0397

Aesthetics of Auto-layouted diagrams C0291

Compatibility of Export-Formats C0293

Data migration at SW Updates C0294

Program Start and About Window C0345

--> When starting, if not enough memory, stop R0490

When starting, if not enough memory, stop C0335

When starting, if not enough memory is available to operate, the program shall inform the user and stop.

Open a Model Database C0346

Export (Model and/or Diagrams) C0347

Navigate and Search and Open multiple Windows C0348

--> When opening a new window, if low-mem, cancel R0529

--> When searching, if low-mem, show only parts R0492

--> When navigating, if low-mem, show placeholders R0493

When searching, if low-mem, show only parts C0337

When searching, if not enough memory available for storing the search result list, the program shall indicate that some results are omitted and show only parts of the result list.

When navigating, if low-mem, show placeholders C0342

When navigating, if low-mem, the program shall show placeholder rectangles where rendering of diagrams is not possible.

When opening a new window, if low-mem, cancel C0336

When opening a new main window, if low-mem, the program shall inform the user and cancel the operation.

Modify / Create / Delete Diagrams and Element C0352

Undo and Redo C0350

--> When undoing, allow at least 3 undo operations R0494

When undoing, allow at least 3 undo operations C0343

When undoing/redoing past actions, the program shall perform at least 3 undo/redo operations before informing the user that undo/redo is not possible anymore.

Check and Repair Database C0351

icon C0327

An icon is a small picture representing an element-type

--> symbol R0473

contour C0328

A contour is an outer line around an element. The exact shape of it depends on the elements type. Some elements do not have a contour.

--> symbol R0474

top-right-icon --> icon R0682

label C0329

A label is the text attached to the visual representation of an element. It consists of its name and optionally an stereotype.

symbol C0330

A symbol is a drawing/picture representing the type of an element

envelope C0333

the rectangular outer bounds of symbol, label and space

--> symbol R0478

--> space R0479

--> label R0480

space C0334

the rectangular area of all contained compartments (except the label-compartment)

image C0435

The image of a stereotype. This may replace either the stand-alone icon or the icon in the top right corner of a contour.

Label Compartment C0331

The rectangular area containing label and possibly an icon. It is the top-most compartment.

--> Compartment R0475

may have 0..1 --> icon R0476

has 1..1 --> label R0477

Compartment C0332

A compartment is an area in a classifier showing features of the classifier, e.g. tags, methods, attributes, use-cases

icon C0327

An icon is a small picture representing an element-type

label C0329

A label is the text attached to the visual representation of an element. It consists of its name and optionally an stereotype.

space C0334

the rectangular area of all contained compartments (except the label-compartment)

has 1..n --> Compartment R0481

Class C0443

standalone-icon C0444

<path d=" M 3,0 h 4 v 4 h -4 v -4 "/> <path stroke="#0088ff" fill="#cceeff" d=" M 1,4.5 h 8 v 2 h -8 v -2 "/> <path d=" M 2,7 h 2 m 2,0 h 2 v 2 h -2 m -2,0 h -2 v -2 "/>

--> Class R0695

--> icon-img R0697

contour-and-icon C0445

<path d=" M 1,2 h 8 v 6 h -8 v -6 M 6.5,3 h 1.5 v 1.5 h -1.5 v -1.5 "/> <path stroke="#0088ff" fill="#cceeff" d=" M 2,3 h 4 v 2 h -4 v -2 "/> <path d=" M 2,5.5 h 2 m 2,0 h 2 v 2 h -2 m -2,0 h -2 v -2 "/>

--> Class R0696

--> contour-img R0698

icon-img C0446

contour-img C0447