| ... | ... | @@ -16,11 +16,11 @@ Software promises at Digitec can not be made without two official documents whic |
|
|
|
|
|
|
|
### The Guidelines:
|
|
|
|
---
|
|
|
|
The only binding documents for software production are the SRS and the Time Estimate related to that SRS.
|
|
|
|
`All SRS must be approved by a Senior Software Engineer.`
|
|
|
|
All Software Architecture requirements must be approved by a Senior Software Engineer.
|
|
|
|
All Server Deployment Architecture requirements must be approved by a Senior Software Engineer.
|
|
|
|
All UI Mockups and interactions that must be realized through software (CSS, HTML, Javascript), require an SRS and its related Time Estimate.
|
|
|
|
- `The only binding documents for software production are the SRS and the Time Estimate related to that SRS.`
|
|
|
|
- `All SRS must be approved by a Senior Software Engineer.`
|
|
|
|
- `All Software Architecture requirements must be approved by a Senior Software Engineer.`
|
|
|
|
- `All Server Deployment Architecture requirements must be approved by a Senior Software Engineer.`
|
|
|
|
- `All UI Mockups and interactions that must be realized through software (CSS, HTML, Javascript), require an SRS and its related Time Estimate.`
|
|
|
|
---
|
|
|
|
Words matter, especially when you are legally binding yourself to the delivery of services. The language you use in the specification should observe a criteria that ensures clarity for both the developer (writer of the specification) and the client. As a rule both the developer and the client need to sign off on the specification before work begins.
|
|
|
|
|
| ... | ... | |
