Skip to content

Commit 7587e61

Browse files
authored
docs: adds Trinitie's sample user stories (#210)
1 parent 5291dca commit 7587e61

File tree

1 file changed

+36
-0
lines changed

1 file changed

+36
-0
lines changed
Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
# The Astral Compass
2+
This is a fictional system for a fantasy nation that my friends and I created a while back, called the Mayou Kuni.
3+
4+
## User Story 1
5+
6+
***As a*** space pilot, ***I want*** the system to calculate the fastest and safest route ***so that*** I avoid hazards like asteroid fields or black holes.
7+
### Acceptance Criteria
8+
- If a hazard is detected, the system issues an audible and visual alert ASAP.
9+
- The alert identifies the hazard type, like an Asteroid Belt, Enemy Territory, etc.
10+
- The system highlights the hazard location on the compass map.
11+
- If no safe alternative exists, the system displays a warning that the risk is unavoidable.
12+
13+
## User Story 2 (with a fantasy twist)
14+
15+
***As a*** navigator, ***I want*** to align my course with favorable star constellations ***so that*** my journey is blessed and protected.
16+
### Acceptance Criteria
17+
- Navigation map shows constellation alignments for the chosen route.
18+
- Navigator can toggle "favorable path” view.
19+
- If alignment is poor, system recommends an alternate departure time/route.
20+
- Alignments are based on dynamic celestial cycles and updated daily.
21+
22+
## User Story 3
23+
24+
***As a*** ship engineer, ***I want*** the system to calculate fuel and supply requirements for a plotted route ***so that*** I can prepare the ship properly.
25+
### Acceptance Criteria
26+
- When a course is plotted, the system displays estimated fuel and supply needs.
27+
- System shows real-time impact of changes.
28+
- If the power setup could damage the system, the system gives a warning.
29+
- Engineer can increase or decrease power to engines, shields, or weapons individually.
30+
31+
## Definition of “done”
32+
- Test coverage meets the team’s agreed threshold.
33+
- All Acceptance Criteria are met.
34+
- Feature integrates with existing ship systems (navigation map, engineering console, pilot display).
35+
- Alerts, warnings, and logs appear in the correct locations.
36+
- Feature has been tested in simulation (normal conditions, hazardous conditions, emergencies).

0 commit comments

Comments
 (0)