"Create, Read, Update, and Delete" ("CRUD") = the four basic operations on a database record. Also, an application which provides only a thin interface over database operations.
From an SQL relational database perspective, "SelectInsertUpdateDelete?."
Some tools and frameworks will automatically generate CrudScreens for you -- AutoGenCrudScreens.
Aka Create, Read, Alter, Purge.
I sure hope there is no Sort Hide Insert Transaction :-)
There is on this page a fixation on AcronymsAboutWasteProducts, do I detect "I have no desire to utilize WastingMyTimeWithGUInterfacesUsedToSelectModularProcesses? aka WebbrowserInterfaceviaMouseSelectablePages
and bias toward CommandLineorKeyboardPressSomeKeysInstead ?
"CRUD" is not descriptive enough in my opinion. I'd instead suggest "SER":
Edit - Includes add, change, and delete
Furtherless, despite all the tutorials teach CRUD, industrial-strength programs often should never Update or Delete. To Update, you add a new record, with a timestamp, that adjusts a previous record. To Read, you look thru a View of some type that rolls up all this auditing trail. And, naturally, you only mark for deletion.That is the only way to preserve consistent auditing and accountability across mistakes and revisions.ThouShaltNotDeleteData
See also: CrudPatternsCategoryInteractionDesign