How would you handle needed "System" class/table/form in application?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

I'm just curious how you would handle this. In the cable industry, Comcast
is referred to as an "MSO" (multiple systems operator) meaning they own many
cable systems. Therefore a solution must be architected to accommodate
"System" as an entity. This means a table in the database named System, a
class System, a web form System, etc.

Since System is such a reserved word, how should we do this? To rename it
"CableSystem" would bug as isn't consistent/what is desired (should have to
change our business terminology because conflicts with development tool).
For the class, it could be named "System" and just wrapper a namespace
around it named "Classes". But for the web form, while it could be named
System.aspx, you can't just wrap a namespace around it.

Hungarian notation is "out" these days so I'm looking for a good
standardized and consistent approach for all such names that might conflict.

Thanks,
Ron




.