I am whipping a short specification / requirements document for a small prototype iPhone application. Describing the basic functions and behavior is not a problem for me. But, since my knowledge of mobile applications and the iPhone is very weak, I’m not quite sure what else should be in such a document regarding best practices, etc.
Example: In my programming world (on the server side of Java), when I design a project for outsourcing, I argue that the project must undergo a static error analysis using FindBugs.
Example: I understand that there are API calls. Apple does not want application developers to call. This may be the reason for the application to refuse the application store. But I'm not sure how to say that we want Apple to be respected. (I don’t even know how to verify this.)
What should I include in the two-page requirements and specification document specific to iPhone application development?
source
share