Not data access dev, but can share how my team deals with some of this.
1. Create a good looking documentaion of your domain model.
Thank you for your answer.
Depends on what you want. Any .net code documenter can work, such as sharpdoc http://sharpdox.de/en/ or sandcastle https://sandcastle.codeplex.com/. Fancy visual layouts can be generated by Visual Studio or Resharper as well.
Sandcastle isn't developed any more. I'll have alook into Sharpdox. Thanks for the hint.
2. Generate boiler plate code (OData, WCF, implement several interfaces, naming conventions, ...).
Code generation is something I want too. :/ You might just be best off coming up with your own convention based solutions, at least then you have control of the code.
3. Take care of views and stored procedures.
DA still handles arbitrary stored procs the same way on the 'low level' api. http://docs.telerik.com/data-access/developers-guide/low-level-ado-api/executing-stored-procedures/data-access-tasks-adonet-execute-stored-procedure.
If you want nicer more oop style c# methods thats kinda the generator problem again unfortuately.
As a one man show I can't afford developing and maintaining such a selfmade tool. Look at the time I needed to answer to your post. ;)