Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ispace Announces Results of the “Hakuto-R” Mission 1 Lunar Landing

ispace-inc.com

Post reply on HN
Print view View original

11–16 of 16 posts

Re: Ispace Announces Results of the “Hakuto-R” Mission 1 Lunar Landing

#11

Post by latchkey »

sho_hn wrote: post #10
tuukkah wrote: post #8

Earlier quoted context omitted.

(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.

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.

Neat, how is all of this tracked?

Re: Ispace Announces Results of the “Hakuto-R” Mission 1 Lunar Landing

#12

Post by svilen_dobrev »

latchkey wrote: post #11
sho_hn wrote: post #10

Earlier quoted context omitted.

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.

Neat, how is all of this tracked?

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

https://en.wikipedia.org/wiki/Requirements_traceability

Re: Ispace Announces Results of the “Hakuto-R” Mission 1 Lunar Landing

#13

Post by beyondCritics »

noizejoy wrote: post #6

Is there something like penetration testing for projects? i.e. a business unit that is working fulltime on identifying “what could possibly go wrong” in very complex projects.

Of course, since software errors are inevitable there is no other way than to test extensive and systematically. In Europe adaptions of the V-Model [1] are in wide spread use. Even for smallish projects, expensive simulation of substantial cost is completely normal [2]. Hence there should have been a test software component, that can simulate realistic landing data. This component failed to identify the error, which is nothing more than a big blunder of the testing team.

[1] https://en.wikipedia.org/wiki/V-model [2] https://en.wikipedia.org/wiki/Hardware-in-the-loop_simulatio...

Re: Ispace Announces Results of the “Hakuto-R” Mission 1 Lunar Landing

#14

Post by latchkey »

svilen_dobrev wrote: post #12
latchkey wrote: post #11

Earlier quoted context omitted.

Neat, how is all of this tracked?

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 https://en.wikipedia.org/wiki/Requirements_traceability

What tools specifically? Just excel?
Post reply on HN