Our approach is lightweight, and models do not get obsolete. You can update the model mechanically.

Eclipse customers were demanding the capability to map their application architecture to the actual code. They now will have the means to test the architecture, detect violations while coding and prevent architectural erosion.

I'm not paid to be a role model, parents should be role models.

People have used models to study permafrost before, but not within a fully interactive climate system model.

Whether it's mechanically or my game plan I'm not sure, but if I'm not executing it's hard to even figure out what you're doing wrong.

The ultimate model that will emerge is going to be one that is a layered authentication approach. You will have risk-based authentication and forms of passive authentication, but, for certain segments of users and certain types of transactions that may be high-risk or high-value, there will be a need for strong credentials like one-time-password tokens.