... | ... | @@ -7,10 +7,21 @@ |
|
|
|
|
|
###### Overview
|
|
|
|
|
|
The first step you must take as a developer BEFORE starting any project and BEFORE writing down any code, is to correctly identify the requirements that need to be fulfilled in order to satisfy the project.
|
|
|
|
|
|
It is worth noting that, as a general rule, implementors are discouraged from creating the specification for a project that they will be working on. Implementation details tend to cloud and weaken the conceptual integrity of a specification. Thus, it is preferred that the project manager be responsible for creating the specification.
|
|
|
|
|
|
|
|
|
###### REF - [Agile Software Development](http://en.wikipedia.org/wiki/Agile_software_development)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
### The Guidelines:
|
|
|
---
|
|
|
For large projects we use an abbreviated form of the IEEE SRS standard which relies on the functional requirements section. This document is also a great overall reference for learning about software specifications.
|
... | ... | |