3.7 KiB
3.7 KiB
Stakeholder Analysis
Metadata
| Key | Value |
|---|---|
| ID | SA-001 |
| CrossReference | BC-001 |
| Language | en |
| Domain | it |
Version History
| Date | Status | Author | Reviewer | Change | Commit |
|---|---|---|---|---|---|
| 2026-10-13 | Accepted | Claude (AI) for S01 | AI as stand-in for S01 | Initial version; review RC-002: Go | pending |
Purpose
Identify who is affected by the U.S. States Game project, who decides and who reviews, so each artifact can cite stable IDs. Method: Mendelow power/interest grid, concerns mapped to FURPS+.
Stakeholder Summary Table
| ID | Name | Role/Title | Organization | Power Level | Interest Level | Quadrant | Primary Concern (Business Language) |
|---|---|---|---|---|---|---|---|
| S01 | Jens Tirsvad Nielsen | Course participant; Product Owner, developer and reviewer | Tirsvad | HIGH | HIGH | Manage Closely | A finished, correct, well-documented exercise delivered through a reviewed process |
| S02 | Udemy coursists | Course participants who share code and compare solutions | Udemy 100 Days of Code community | LOW | HIGH | Keep Informed | Readable, runnable code that keeps the assignment's function names, with README instructions to run it |
| S03 | GitHub viewers | Visitors who browse the repository for ideas | Public | LOW | LOW | Monitor | A clear repository description, topics and README, and no runtime dependencies to install |
Power/Interest Classification Rationale
- Manage Closely (S01): decides scope, reviews and accepts every artifact.
- Keep Informed (S02): cannot change scope but is the main consumer; their needs shape code naming and README.
- Monitor (S03): casual consumers; served by the public repository surface.
Primary Concerns and FURPS+ Mapping
| ID | Concern | FURPS+ attribute |
|---|---|---|
| S01 | Game behaves as in the lectures | Functionality |
| S01 | Work traceable through plan, review and pull requests | Supportability |
| S02 | Readable code with the assignment's function names | Supportability |
| S02 | Easy to run from README instructions | Usability |
| S03 | Clear description, topics, README | Usability |
| S03 | No runtime dependencies to install | Supportability |
Communication Requirements
| ID | Channel | Frequency | Deliverable | Phase / Milestone |
|---|---|---|---|---|
| S01 | Chat session | At plan acceptance and at the final summary | Plan, review records, run summary | All milestones |
| S02 | README, wiki (en, da, ms) | Once per release | Run instructions, screenshots | MIL-004 |
| S03 | Repository description, topics, README | Once per release | Repository surface | MIL-004 |
Conflicting Interests and Mitigations
| Conflict | Stakeholders | Mitigation |
|---|---|---|
| The assignment uses pandas, but viewers want no runtime dependencies | S02, S03 | Record the choice in an ADR; keep the assignment's function and variable names regardless of the library |
| Full process documents add weight to a small exercise | S01, S03 | Keep documents short; the repository surface (README, wiki) stays the first thing viewers see |
Traceability Analysis
Business Goal Alignment
| Stakeholder | Concern | Business Case objective |
|---|---|---|
| S01 | Correct game | BC-001 Objectives 1, 3 |
| S01 | Process and traceability | BC-001 Objective 4 |
| S02 | Comparable, runnable code | BC-001 Objectives 1, 2 |
| S03 | Clear repository surface | BC-001 Objective 4 |
Sign-Off
| Role | Stakeholder | Date | Decision |
|---|---|---|---|
| Product Owner | S01 | 2026-10-13 | Accepted in chat as part of the plan; reviewed by AI as stand-in for S01 (RC-002) |