Actually I was not refering to this in terms of security it was just an observation. I think that should have gone to a separate thread. But I agree with you in regard to what leads to an easy to use application. But for training, what does that meaning developers and testers training or user training. I think a dream software would be one that requires no training to use effectively. Operating an iphone for example gives a nice example of what good design is. You need not ask how sth is done, it like comes out automagically.
On Thu, Oct 15, 2009 at 4:37 PM, Rad! <conradakunga@gmail.com> wrote:
I would be of the opinion that ease of use and security has little to do with the underlying engine. You can write insecure, difficult to use software on anything - php, j2EE, .NET, perl.
Ease of use is a direct result of a conscious design effort (use cases, user stories, user monitoring). Security is a result of a combination of factors including design, infrastracture, best practices, security reviews, audit, technology, quality developers and testers and training