I actually like some of the ideas from CASE. For example, non-programmers (typically analysts) should be able to change attribute-oriented features without code

I actually like some of the ideas from CASE. For example, non-programmers (typically analysts) should be able to change attribute-oriented features without code changes. Menus, button titles, field titles, field length, required status, etc. should all be update-able without code changes. The idea kind of exists in "Table Oriented Programming" where much of the routine programming, field info, and navigation is controlled by tables, not by code. The problem has been that's hard to tweak such for special or specific needs. I've been working on how to get around this. I've stumbled upon "incremental draft rendering" where the attributes from the tables generate draft handling and markup in stages, which can then be custom tweaked as needed using an event-driven approach. But most programming languages are not designed for event-driven table oriented programming. Experiments continue though...