2.3 KiB
System Sequence Diagram
Metadata
| Key | Value |
|---|---|
| ID | SSD-002 |
| CrossReference | UC-002, DM-003 |
Version History
| Date | Status | Author | Reviewer | Change | Commit |
|---|---|---|---|---|---|
| 2026-10-07 | Proposed | Jens Tirsvad Nielsen | S02 | Initial version | 1cd27f7 |
| 2026-10-07 | Proposed | Jens Tirsvad Nielsen | S02 | Names the confirmation of a configuration file from the working folder as out of scope | 0ab5006 |
Source Use Case
Start the script as a global command (UC-002) — scenario: main success scenario
Diagram
@startuml
actor Maintainer as A
participant ":System" as S
A -> S : startFromWorkingFolder(configPath, envPath)
S --> A : prompts for project details
A -> S : provideProjectDetails(...)
S --> A : creation summary with the project's full path
@enduml
System Operations
| Step | Message | Parameters | Return | Use case step |
|---|---|---|---|---|
| 3 to 4 | startFromWorkingFolder | configPath (optional), envPath (optional) | prompts for project details whose default directory is under the working folder | 3, 4, 5 |
| 5 | provideProjectDetails | the parameters of provideProjectDetails in [UC-001] |
creation summary that names the full path of the new project | 5, 6 |
Failure flows (extensions 1a, 3a, 4a and 4b of UC-002) are out of scope for this diagram: they end the run with a message and add no system operation. The confirmation of a file from the working folder (extension 4c) is a prompt from the system, out of scope as the consent questions of SSD-001 are. provideProjectDetails is the operation of [UC-001] and is not repeated in OC-002; the only difference is the base of the default directory. Making the command link (step 1) and opening the shell (step 2) are done by the Maintainer outside the system, so they are not system operations.
Lifecycle Notes
One script run, as in [UC-001]. The command link persists between runs; the system keeps no state of it.