4 ms·
Analyzing code in terms of "function points" was something done back in the day. Maybe it still is; in my mind it's part of the same general dustbin as UML et a
by finnh 4y ago
Analyzing code in terms of "function points" was something done back in the day. Maybe it still is; in my mind it's part of the same general dustbin as UML et al.
- dtgriscom 4y agohttps://en.wikipedia.org/wiki/Sequence_point https://en.wikipedia.org/wiki/Sequence_point
- CoastalCoder 4y agoThe concept is still fundamental to static code analysis.
- morelisp 4y agoHowso, given that function point analysis comes from requirements and doesn't even need code to exist? (Are you sure you know what function point analysis is? It sounds a lot like "sequence points" or "branching points", but in reality it's more like "story points"...)
- CoastalCoder 4y agoSorry, you may be right. Based on context I assumed "function point" was synonymous with static analysis' "code point". I should have checked before commenting.
- aaaaaaaaaaab 4y agoNope, that’s something totally different. Function point analysis is some handwavy enterprise bullshit that noone takes seriously anymore. https://en.m.wikipedia.org/wiki/Function_point https://en.m.wikipedia.org/wiki/Function_point
- astrange 4y agoImpressive that it made it to ISO standards. What kind of person lacks the capacity for boredom enough to get through that?
- aaaaaaaaaaab 4y agoThree letters: IBM. People in the 90s were still believing that software engineering could become similar to other engineering disciplines.