Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • D digitec-wiki
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Digitec
  • digitec-wiki
  • Wiki
  • digitec software promises

digitec software promises · Changes

Page history
rcabral created page: digitec-software-promises authored May 02, 2014 by Rene Cabral's avatar Rene Cabral
Hide whitespace changes
Inline Side-by-side
digitec-software-promises.markdown
View page @ edd64282
...@@ -21,6 +21,7 @@ Software promises at Digitec can not be made without two official documents whic ...@@ -21,6 +21,7 @@ Software promises at Digitec can not be made without two official documents whic
- `All Software Architecture requirements 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 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.` - `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. 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.
......
Clone repository
  • alpha beta testing
  • browser testing
  • camtasia licenses
  • code delivery processes
  • coding practices
  • css and sass coding standards
  • database schema standards
  • dependency management
  • development environments
  • digitec agile process
  • digitec gitlab styles
  • digitec software promises
  • digitec spec process
  • gitlab administration
  • gitlab issues tags
View All Pages