In addition to the recent posts:
If “engineering is producing an artifact to cost”, then how can modelling contribute to it?
By uncovering complexity, since complexity is what causes the cost! Actually, from a management point of view, cost, and thus mainly complexity, is one of the most interesting attributes of a model. Here, with ‘complexity awareness’ in real world software engineering, I do not mean, computing the exact complexity class of a model (may it be descriptive or algorithmic). Rather it means being able to recognise points where complexity ‘suddenly’ increases by ‘just a little bit’ more of functionality (like the undelete function in the state machine from the last post) This already can proof very beneficial, since finally controlling* complexity means controlling cost.
*where ‘controling’ can mean all sorts of decisions, like refusing the feature, increasing the budget (a priori), considering workarounds, …