Re:Ispace Announces Results of the “Hakuto-R” Mission 1 Luna...
by macintux on Friday May 26, 2023 @08:15PM
(#36090912)
This is something I’ve long struggled with: how you capture assumptions tied to decisions so you can revisit the decisions when the facts on the ground change.
[ Parent
| on HN ]
Re:Ispace Announces Results of the “Hakuto-R” Mission 1 Luna...
by tuukkah on Friday May 26, 2023 @09:09PM
(#36091157)
(Architectural) Decision Records should explicate assumptions behind the decisions. There will be implicit assumptions too, but at least you can later go back to the records and analyse what was implicit in them.
Re:Ispace Announces Results of the “Hakuto-R” Mission 1 Luna...
by sho_hn on Friday May 26, 2023 @11:09PM
(#36091729)
Yup, we have a strong culture around this at work. Problem statement, decision drivers, decision criteria, alternate options to seriously evaluate. It should be clear why one is recommended over the other, and under what circumstances other options might be preferable.
Re:Ispace Announces Results of the “Hakuto-R” Mission 1 Luna...
by latchkey on Saturday May 27, 2023 @12:48AM
(#36092148)
Neat, how is all of this tracked?
Re:Ispace Announces Results of the “Hakuto-R” Mission 1 Luna...
by svilen_dobrev on Saturday May 27, 2023 @06:13AM
(#36093486)
requirements traceability - dependency tracking/tracing graph, upwards (because of) and downwards (therefore).
It is a very tedious process, Very few companies do it.
But once the graph is built, one can poke questions on it, like what would/might be affected if node X changes. And any assumptions also counts as requirement of sorts