I know that there are no set standards or rules for software docuemntation. I am not sure if this is good or bad? I am busy creating my first "Software Document" for my organisations solution. Our solution is pretty standard. It is a mobile application for iPhone, iPad, Apple Watch and Android [Not sure if im allowed to say that here]. The docuemnt is not a user manual but an internal document which will explain the architechture, lifecyle, deployemnt procedures etc.
I have scoured the net looking for resources on best practice, templates, examples and the like. I was wondering if I have missed something but I cant find any sort of standard or commonly defined structure for these documents. It seems to be a company by company type approach with each company writing the document in a way they feel is best.
I hope I am wrong. Can anyone shed some light?
Thank you very much indeed. I must also appologise in advance if I put this request for information in the wrong place. I dont see an applicaple (post deployment) area in the forums.