Re: AS9100 Rev. D - When and what? • First AS9100:2016 certificate issued, March 2017
AS9100D doesn't require documented procedures for design and development, but I still think it's a good idea. If you already have documented procedure(s) describing your D&D process, I would take what you have and see if there is anything missing. If there are gaps with the new standard, look at what needs to change, how to best implement the changes, and then modify the procedure to match.
If you don't already have a procedure, I would map your current process first in a flow diagram. Again, if you need to change anything to meet the requirements, add steps in as appropriate. Then write a procedure around your process. Or you could just use the flow diagram as the procedure supplemented with responsibilities and authorities and use forms to capture inputs, reviews, and outputs.
I wouldn't start with someone else's procedure because their D&D process may be very different. But it probably would help to look at other D&D procedures to get an idea of what kind of content is useful. The Post Attachments List at the top of each page in the forums here is useful to find things that people have posted over the years. I don't see a lot of procedures, but here's a quick search to start with:
Just change the keyword to search using other terms (like procedure, template, development, etc.)