Comment by theappsecguy

Agreed; typically (especially if a client is involved) I’ve seen creative and dev define and articulate spec and expected behavior, and BA documents it. Then, when it inevitably evolves, BA’s job is to capture the changed spec. The artifact is simply documentation as a client deliverable that’s then often never referenced or used for anything outside of maybe complaining that a feature doesn’t do what the spec claimed, or maybe as context when the client takes their whole project to another vendor to be rebuilt from scratch lol