Files

T

Tirsvad 1cd27f77ed Plan MIL-007 and UC-002; AGPL-3.0 default only for a public GitHub project

- MIL-006: the AGPL-3.0 default needs GitHub and a public project
- MIL-007: fetch the framework's own submodules (qc); start through a command link; README usage
- UC-002 with SSD, DM, OC, SD and DCD; US-001.07 and US-002
- Reconcile the project DM, DCD, dictionary, use case diagram and traceability matrix
- Review records RC-022 to RC-028

2026-10-07 12:30:58 +08:00

1.7 KiB

Raw Blame History

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	pending

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. 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.

1.7 KiB Raw Blame History