• Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

Comments (2)

1 localhost commented Permalink

When you describe the purpose of models in general (and presumably UML in particular), you start with the proposition that they "help us reason about ... software-intensive systems".Can you please elaborate about the types of reasoning that you would regard as important here. I think this might be helpful in clarifying any real differences of opinion between the Microsoft gang and yourself.

2 localhost commented Permalink

Why guys you are concerned so much about throwing or not throwing away models? Obviously, the main point was that *code* (or *executable product*, logically) is the main deliverable; and models are an [auxiliary] mean to build those deliverables. The phrase about throwing models away was an illustration of that point, and you need to understand it in that context. Not as an advice to throw your models away, or declaration that models are something not important.In this view, you throw away models that you think you don't need anymore (e.g. after code has been generated from them, or analysis has been complete). And you keep those models that you think you'll need (e.g. for future reference or refactoring). And you don't throw code away because it is used to build product, and later change it.

Add a Comment Add a Comment