This paper describes how the technical debt concept widely used in the software domain—-rework deferred to the future for expediency-—needs to be modified to the domain of descriptive models. To illustrate the model technical debt concept, several examples of modeling principles pertaining to model purpose and implementation are described along with their implications on model technical debt.
Members-Only Content
This content is restricted to members only.
You must be logged in with an active membership to access this page.
Please click the link below to log in. If you do not have an account or your membership is inactive, you may need to register or renew it.