CLASS DIAGRAM
6243983994912768
@startuml
A --> B
note on link
Association.
The only one that can has number on it.
eg. LineItem has a product
end note
C --|> D
note on link : Extends
E ..|> F
note on link : Implements
G ..> H
note on link
Depends. eg. LineItem depends on Date
(LineItem doesn't store Date but if
Date is missing it cannot be used)
end note
@enduml
CLASS DIAGRAM
6243983994912768
ACTIVITY DIAGRAM
6244412283682816
@startuml
start
if (graphviz installed?) then (yes)
:process all\ndiagrams;
else (no)
:process only
__sequence__ and __activity__ diagrams;
endif
stop
@enduml
ACTIVITY DIAGRAM
6244412283682816
CLASS DIAGRAM
6244667700019200
@startuml
class Usuario
class Entidade
class Categoria
class Necessidade
class Chamado
Categoria "1..*" o-- "0..*" Necessidade
Usuario "1" -- "0..*" Chamado
Chamado "1..*" -- "1" Necessidade
@enduml
CLASS DIAGRAM
6244667700019200
CLASS DIAGRAM
6245697686863872
@startuml
object Object01
object Object02
object Object03
object Object04
object Object05
object Object06
object Object07
object Object08
Object01 <|-- Object02
Object03 *-- Object04
Object05 o-- "4" Object06
Object07 .. Object08 : some labels
@enduml
CLASS DIAGRAM
6245697686863872
SEQUENCE DIAGRAM
6247403325751296
@startuml
hide footbox
actor User
User -> RF: Start of test case
RF->PSTT: Syn
RF<-PSTT: Syn Ack
RF->PSTT: Ack
...
RF<->PSTT: Commands
...
RF -> PSTT: FIN
RF <- PSTT: FIN Ack
RF -> PSTT: Ack
User <- RF: End of test case
@enduml
SEQUENCE DIAGRAM
6247403325751296
CLASS DIAGRAM
6248007305527296
@startuml
class Singleton {
- instance: Singleton
- Singleton(): void
+ getInstance(): Singleton
}
@enduml
CLASS DIAGRAM
6248007305527296
CLASS DIAGRAM
6248694768730112
@startuml
hide members
OResource <|-- OComponent
OResource <|-- OGroup
OGroup <|-- OAccount
OResource <|-- OLease
OResource <|-- OProject
OResource <|-- User
@enduml
CLASS DIAGRAM
6248694768730112
SEQUENCE DIAGRAM
6250233172328448
@startuml
title User Submits a Pull Request
actor User
participant PullRequestClient
participant PsychicOctoRobotServer
note right of PsychicOctoRobotServer
Node.js server which serves the
webpages requested by the user.
end note
User -> PsychicOctoRobotServer : requests page for \n submitting a \n pull request
PsychicOctoRobotServer -> User : web page for \n PullRequestClient
note right
The PullRequestClient is a
Javascript client made of js-git
and our code bundled with browserify
end note
alt Contact GitServer Directly
PullRequestClient -> GitServer : Requests index of \n all branches in \n repos accessible by \n the user
GitServer -> PullRequestClient : Index info
else Get Repo Index through PsychicOctoRobotServer
PullRequestClient -> PsychicOctoRobotServer : Requests index of \n all branches in \n repos accessible by \n the user
PsychicOctoRobotServer -> GitServer : Requests index of \n all branches in \n repos accessible by \n the user
GitServer -> PsychicOctoRobotServer : Index info
PsychicOctoRobotServer -> PullRequestClient : Index info
end
PullRequestClient -> User : Displays branch index \n of remote repos \n user has access to
User -> PullRequestClient : selects branch to \n do a pull request for
PullRequestClient -> User : Displays prompt for \n parent branch for diff
User -> PullRequestClient : Selects parent branch
loop for each branch
alt Contact GitServer Directly
PullRequestClient -> GitServer : Requests latest repo version
GitServer -> PullRequestClient : Repo
else Get Repo Index through PsychicOctoRobotServer
PullRequestClient -> PsychicOctoRobotServer : Requests latest repo version
PsychicOctoRobotServer -> GitServer : Requests latest repo version
GitServer -> PsychicOctoRobotServer : Repo
PsychicOctoRobotServer -> PullRequestClient : Repo
end
end
PullRequestClient -> PullRequestClient : Calculates diffs
PullRequestClient -> User : Displays diffs
User -> PullRequestClient : Accepts changes and makes a comment/message
alt Contact GitServer Directly
PullRequestClient -> GitServer : Submit pull request
GitServer -> PullRequestClient : Confirmation
else Get Repo Index through PsychicOctoRobotServer
PullRequestClient -> PsychicOctoRobotServer : Submit pull request
PsychicOctoRobotServer -> GitServer : Submit pull request
GitServer -> PsychicOctoRobotServer : Confirmation
PsychicOctoRobotServer -> PullRequestClient : Confirmation
end
PullRequestClient -> User : Displays message notifying user of success/failure
@enduml
SEQUENCE DIAGRAM
6250233172328448
SEQUENCE DIAGRAM
6251114177495040
@startuml
title User Merges Branch
actor User
participant MergeClient
participant PsychicOctoRobotServer
note right of PsychicOctoRobotServer
Node.js server which serves the
webpages requested by the user.
end note
User -> PsychicOctoRobotServer : requests page for \n merging a \n branch
PsychicOctoRobotServer -> User : web page for \n MergeClient
note right
The MergeClient is a
Javascript client made of js-git
and our code bundled with browserify
end note
MergeClient -> MergeClient : reads local "git" \n directory to check \n for repositories \n present
MergeClient -> User : Displays documents \n that are tracked \n in repositories and \n are merge-able
User -> MergeClient : selects document \n repository to merge
MergeClient -> User : Displays prompt for \n branch to merge \n and destination branch
User -> MergeClient : Selects merge branches
MergeClient -> MergeClient : Calculates diffs
MergeClient -> User : Displays diffs
User -> MergeClient : Accepts changes
MergeClient -> MergeClient : Begins merging
MergeClient -> User : Displays any merge conflicts
User -> MergeClient : Selects revisions to use for each conflict
MergeClient -> MergeClient : Completes merge and commits locally
MergeClient -> User : Displays message notifying user of success/failure
@enduml
SEQUENCE DIAGRAM
6251114177495040
CLASS DIAGRAM
6252742238535680
@startuml
@startuml
Class01 <|-- Class02
Class03 *-- Class04
Class05 o-- Class06
Class07 .. Class08
Class09 -- Class10
@enduml
CLASS DIAGRAM
6252742238535680
CLASS DIAGRAM
6254676047560704
@startuml
class OwnCode
OwnCode --> TestableFacade
TestableFacade --> ThirdPartyApi
note right of TestableFacade
This was designed to be easy to test
and use :-)
<b>Yay!!!</b>
end note
@enduml
CLASS DIAGRAM
6254676047560704
USE CASE DIAGRAM
6255036287942656
@startuml
title Modèle d'usage\n <b>enflatme</b>
left to right direction
skinparam packageStyle rect
skinparam shadowing false
actor Visiteur as visiteur
actor Colocataire as coloc
actor :Responsable de la colocation: as respColoc
coloc <|-- respColoc
rectangle application {
(S'inscrire) as inscription
(Afficher la colocation) as afficher
(Modifier la colocation) as modifier
(Administrer la colocation) as administrer
(Modifier des tâches) as modifierTaches
(Créer une colocation) .> administrer : extends
(Supprimer une colocation) ..> administrer : extends
(Ajouter des tâches) ..> administrer : extends
(Supprimer des tâches) ..> administrer : extends
(Marquer une tâche commme complétée) .> modifier : extends
modifierTaches ..> modifier : extends
note right of modifierTaches
Exemple : indiquer qu'une tâche
ménagère a été effectuée.
end note
visiteur --> inscription
coloc --> afficher
coloc --> modifier
respColoc -> administrer
}
@enduml
USE CASE DIAGRAM
6255036287942656
STATE DIAGRAM
6255155473285120
@startuml
Design -down-> Development
state Development {
[*] -down-> Project_KickOff_Meeting
--
[*] -down-> Sprint_Planning
Sprint_Planning -down-> Sprint_Development
Sprint_Development -down-> Sprint_Funtion_Test
Sprint_Funtion_Test -down-> Sprint_Demo
Sprint_Demo -down-> Sprint_Review
--
[*] -down-> Bug_Fixing
--
[*] -down-> Project_Release
}
Development -down-> Verification
@enduml
STATE DIAGRAM
6255155473285120
SEQUENCE DIAGRAM
6255542288777216
@startuml
hide footbox
actor User
title Diagramme de séquence d'enregistrement du travail effectué
User->Seance: runTraining(Exercice)
Seance->User: OK
@enduml
SEQUENCE DIAGRAM
6255542288777216
ACTIVITY DIAGRAM
6257159746617344
@startuml
start
:$cache = [[_field_info_field_cache _field_info_field_cache()]];
:return $cache->getField($field_name);
stop
@enduml
ACTIVITY DIAGRAM
6257159746617344
STATE DIAGRAM
6257929216851968
@startuml
Requirement -down-> Design
state Design {
[*] -down-> BluePrint_Design
BluePrint_Design -down-> CoreVisual_Design
--
[*] -down-> Architecture_Design
Architecture_Design -down-> Module_Interface_Design
--
[*] -down-> TestCase_Design
}
Design -down-> Development
@enduml
STATE DIAGRAM
6257929216851968
COMPONENT DIAGRAM
6259555667279872
@startuml
node node1
node node2
node node3
node node4
node node5
node1 -- node2
node1 .. node3
node1 ~~ node4
node1 == node5
@enduml
COMPONENT DIAGRAM
6259555667279872
CLASS DIAGRAM
6260373053243392
@startuml
DbObj <|.. Doc
Doc <|.. DocFam
Doc <|-- WDoc
Doc <|-- DocCollection
DocCollection <|.. Dir
DocCollection <|.. DocSearch
@enduml
CLASS DIAGRAM
6260373053243392
SEQUENCE DIAGRAM
6261340226191360
@startuml
participant User
User -> Xenophile_server: DoWork
activate Xenophile_server #FFBBBB
Xenophile_server -> Xenophile_server: Internal call
activate Xenophile_server #DarkSalmon
Xenophile_server -> B: << createRequest >>
activate B
B --> Xenophile_server: RequestCreated
deactivate B
deactivate Xenophile_server
Xenophile_server -> User: Done
deactivate Xenophile_server
@enduml
SEQUENCE DIAGRAM
6261340226191360
STATE DIAGRAM
6261949306241024
@startuml
Verification -down-> Preview
state Preview {
[*] -down-> Preview_Demo
Preview_Demo -down-> Preview_LUT
Preview_LUT -down-> Preview_Summary
}
Preview -down-> Deploy
@enduml
STATE DIAGRAM
6261949306241024
CLASS DIAGRAM
6262664149860352
@startuml
hide circle
skinparam shadowing false
skinparam classFontStyle Bold
skinparam classFontSize 14
title Class Diagram
note as Title
<b>Class Diagram
Authors:
Ben Cumber
Reviewed By:
Jeff Crocker
end note
class Game{
}
class Character{
}
class Environ{
}
class Unit{
}
class Mission{
}
class Planet{
}
class Possession{
}
class Race{
}
class Stack{
}
Game o-- "*" Stack
Game o-- "*" Planet
Character "*" --o Stack
Character -- "*" Possession: owns
Environ "2-5" --o Planet
Environ -- Race: Inhabits
Unit "*" --o Stack
Stack "*" -- Mission: is assigned
Stack -- Environ: is located
@enduml
CLASS DIAGRAM
6262664149860352