I'm curious about what you consider a BLL. Both the examples you've given, Access Control and Validation, are things I've typically seen implemented elsewhere.
I've seen these implemented either in the presentation layer or in a service layer common to, say, web services and web ui. I can see a BLL using an access control subsystem, but not that access control is part of a BLL. Do you have any examples of that?
Same with validation, depending on what you mean by "validation". Do you mean, "this business object passes all business that it's meant to pass, given its current state?" Or were you referring to UI-style validation, making sure alphabetic characters are not input into a numeric field?
You also mention controls, which are usually thought of as UI artifacts. Could you please give more detail about what you consider a BLL to be? I'd also appreciate any links to examples of what you consider to be a BLL.
Based on your clarifications, I'd point you to the Enterprise Library from Microsoft's patterns and practices group. Some of its components are:
- Caching
- Cryptography
- Data Access
- Exception Handling
- Logging
- Policy Injection
- Security
- Unity - Dependency Injection
- Validation
It's all available on CodePlex in both source and binary formats. The source code comes complete with thorough unit tests.