Joshua makes some great points regarding why the address points are at the ends of driveways but there are ways you can mitigate some of the concerns he brings up.
My former job was with a rural county in Montana with some large lots, long driveways, and structures not even visible from the road. My current job is with a city in Washington State with lots of trees where some homes even on smaller lots are not visible from the street. Different environments but similar issues.
In both of these organizations we created driveway segments for structures where access from the road was not very obvious or simply confusing. And at least in my current job, I created a "Street class" field to classify the streets for better/easier symbology, including completely filtering out certain types of streets. This makes it easy to completely drop the driveways on maps where their inclusion is unnecessary and simply clutters up things. These driveway segments have zero address ranges and a discrete intersection node is NOT created where it connects to the street (no slicing and dicing of the street segments just to accommodate driveways).
Another possible method is for you to create your "analysis-capable" address points as discussed in earlier messages (purely as a means to do what follows), create X,Y fields in the data and calculate the values of the point into those fields. Then add equivalent X,Y fields to the existing 911 address point layer and cross those "analysis X,Y" fields over. Now whenever you need to perform analysis you would create an event layer using the analysis coordinates and then perform your analysis. This would eliminate you needing to maintain two address point layers that must be kept in sync but realistically adds some process overhead, particularly if you plan to do much analysis. I admittedly would not choose this method if at all possible but I understand that some organizations might have some constraints for which this might be the only way to accommodate needs.
You definitely want to gather all of your stakeholders and have a discussion of the pros and cons of various methodologies if your aim is to maintain a single address point layer that will meet everyone's needs.
