Sunday, July 19, 2015

2.04. Ensure that any document upon which they rely has been approved, when required, by someone authorized to approve it.

Our client is Mooniak and its a organization that share most of their work under open licenses, even client projects with their approval.Any document we come across regarding design or requirements has been approved by Mooniak with our knowledge and any document we produce is forwarded to Mooniak and with a discussion over Teamspeak we come into conclusions and we add necessary requirements and changes that was altered during the discussion to the document and that final versions of the document will be approved by them.


As developers, it’s always important to have reliable documentation to guide our work. If we are like most developers, we can be supporting multiple applications at the same time, which means that it is even more crucial to have documentation in place to help track all aspects of each application. It’s also helpful for development, maintenance, and knowledge transfer to other developers. The following are some areas in which documentation is especially valuable for a developer and some of my thoughts on what should be included. If possible, the documentation should be focused into the various components that make up an application

No comments:

Post a Comment