You are viewing a wiki page. You are welcome to join the group and then edit it. Be bold!
The following is a collaborative list of features that define a data-driven web application. (Admittedly, the phrase "data-driven" sounds like some stupid sort of buzzword, but it's the only thing I can come up with that seems to fit.) Such applications can be UI, back-end, or middle-tier features. The current focus is just to get a list started. How can you tell that a web application is "Data-Driven?"
- Ability to create "entities" and relate them to each other ("foreign key relationships")
- Many inputs restricted via drop downs ("code sets")
- Data input validation with potentially complex rules
- Emphasis on easy browsing of large sets of data and finding records ("listing" and "search")
- Reports in a variety of formats
- Export / import
- Interactions with other systems ("integration")
- Potentially complex actions performed as data is entered into system ("workflow")
- Notifications about important events via email, screen alerts, SMS, etc.
- Forms with embedded subforms, that reflect relationships defined by foreign keys.
- This is a wiki page. Log in, click edit, and add more!