@startuml
participant User
User -> A: DoWork
activate A
A -> B: << createRequest >>
activate B
B -> C: DoWork
activate C
C --> B: WorkDone
destroy C
B --> A: RequestCreated
deactivate B
A -> User: Done
deactivate A
@enduml
SEQUENCE DIAGRAM
6379109303189504
This is a notefoo1This note is on severallinesand cancontainHTMLCalling the methodfoo()is prohibitedfoo2
ACTIVITY DIAGRAM
6381438920294400
This is a notefoo1This note is on severallinesand cancontainHTMLCalling the methodfoo()is prohibitedfoo2
@startuml
start
:foo1;
note left: This is a note
:foo2;
note right
This note is on several
//lines// and can
contain <b>HTML</b>
====
* Calling the method ""foo()"" is prohibited
end note
stop
@enduml
@startuml
[-> A: DoWork
activate A
A -> A: Internal call
activate A
A ->] : << createRequest >>
A<--] : RequestCreated
deactivate A
[<- A: Done
deactivate A
@enduml
SEQUENCE DIAGRAM
6408443392950272
Materialuid: uuid.UUIDdata: DataContainerdescription: strfrom_material(material: Material): Material {copy}classmethods
CLASS DIAGRAM
6411336321859584
Materialuid: uuid.UUIDdata: DataContainerdescription: strfrom_material(material: Material): Material {copy}classmethods
@startuml
class Material {
uid: uuid.UUID
data: DataContainer
description: str
-- classmethods --
from_material(material: Material): Material {copy}
}
@enduml
CLASS DIAGRAM
6411336321859584
Automatic placement of classesdoesn't look good. This diagramhas to be improved.AuthConfigurableClientListDataSourceClientZoneWriterZoneTableAccessorDataSourceStatusZoneTableIteratorDataSourceInfoZoneTableSegmentCacheConfigZoneTableAccessorCacheZoneTableIteratorCacheZoneDataZoneTableHeaderMemorySegmentLoadActionZoneDataLoaderZoneDataUpdaterRdataSetZoneTableLoadFromFileIteratorLoaderMemorySegmentMappedMemorySegmentLocalZoneTableSegmentMappedZoneTableSegmentLocal1*1*«reset»«create»«create»«create»1*1*1*«create»«create»add/replace1111createcreateadd111111
CLASS DIAGRAM
6413630371266560
Automatic placement of classesdoesn't look good. This diagramhas to be improved.AuthConfigurableClientListDataSourceClientZoneWriterZoneTableAccessorDataSourceStatusZoneTableIteratorDataSourceInfoZoneTableSegmentCacheConfigZoneTableAccessorCacheZoneTableIteratorCacheZoneDataZoneTableHeaderMemorySegmentLoadActionZoneDataLoaderZoneDataUpdaterRdataSetZoneTableLoadFromFileIteratorLoaderMemorySegmentMappedMemorySegmentLocalZoneTableSegmentMappedZoneTableSegmentLocal1*1*«reset»«create»«create»«create»1*1*1*«create»«create»add/replace1111createcreateadd111111
@startuml
title: Single Process Single Thread
package ProcessSonaSpecFile {
package gui {
interface "FileControl" as B
interface "FileData" as B1
interface "Spec" as A
A - [SonaSpec]
B - [File Reader]
B1 - [File Reader]
[SonaSpekFile] --> A : use
[SonaSpekFile] --> B : use
[SonaSpec] -> B1: use
}
}
@enduml
COMPONENT DIAGRAM
6450257852366848
DulaniDulaniVirnaVirnaLogLogAuthentication Requestalt[successful case]Authentication Accepted[some kind of failure]Authentication FailureMy own labelLog attack startloop[1000 times]DNS AttackLog attack end[Another type of failure]Please repeat
SEQUENCE DIAGRAM
6451298039758848
DulaniDulaniVirnaVirnaLogLogAuthentication Requestalt[successful case]Authentication Accepted[some kind of failure]Authentication FailureMy own labelLog attack startloop[1000 times]DNS AttackLog attack end[Another type of failure]Please repeat
@startuml
Dulani -> Virna: Authentication Request
alt successful case
Dulani -> Virna: Authentication Accepted
else some kind of failure
Dulani -> Virna: Authentication Failure
group My own label
Virna -> Log : Log attack start
loop 1000 times
Virna -> Dulani: DNS Attack
end
Virna -> Log : Log attack end
end
else Another type of failure
Dulani -> Virna: Please repeat
end
@enduml