SDLC represented through GOAP

This scene showcases a variety of IT workers operating within an office environment and performing a Software Development LifeCycle (SDLC). Their behaviors are driven by a Goal-Oriented Action Planning (GOAP) system, which offers a more dynamic alternative to traditional Finite State Machines (FSMs).

Unlike FSMs—which rely on step-by-step decision-making at each node and can become stuck or inactive due to rigid local logic—GOAP evaluates the desired goal first. It then determines whether that goal is achievable and only activates the necessary actions if all conditions are met to move from the current state to the goal state. This method prevents flow deadlocks and enables more adaptive, purposeful behavior

What am I looking at?

SDLC Role is represented by capsule color:

- Gray: Customer

- Dark Blue: Requirements manager (dev team)

- Yellow: Product owner

- Green: Developer (dev team)

-Light blue: Tester (Dev Test)

Artifacts (items that are processed in this simulation):

- Defined Requirement

- Tasking (JIRA entry)

- implementation

- Testing (deployable)

Workflow Steps that are portrayed

1.  Customer arrives to be collected and interviewed by Req Manager. Req Delivered is incremented by one.

2. Lead takes reqs and builds out tasks (in task room).  Tasks are inc by 1

3. Developer chooses a tasks and works to implement it.  Implemented is inc by 1

4. Tester tests implemented result to confirm the result is in line with the requirement definition.  Delivered is inc by 1.

This is an example of an infinite game (per Simon Sinek).

The content is a video of a running system, that will run indefinitely (no blocks in the logic flow).

3D DYNAMIC

Copyright © 2025 Evan Fraser All Rights Reserved