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 spec process

digitec spec process · Changes

Page history
rcabral created page: digitec-spec-process authored Feb 05, 2014 by Rene Cabral's avatar Rene Cabral
Hide whitespace changes
Inline Side-by-side
digitec-spec-process.markdown
View page @ 0ea5291f
......@@ -68,5 +68,5 @@ A simple use case is an upgrade request from Symantec on a tool we had previousl
The requirement for __GB changed to TB throughout the sizing interface__ has programming work associated with it: calculations need to be changed.
The total time this requirement will take, will be calculated taking the programming work into account. The programming work is not mentioned because the result is never externalized to the user.
The __Logic Changes__ requirements are interesting because the part externalized to the user is just the result. The calculations supplied by Symantec are a key part of the work being done. Note that the specification never goes into detail about the implementation of these, but simply references where the details can be found.
The __Logic Changes__ requirements are interesting because the part externalized to the user is just the result. The calculations supplied by Symantec are a key part of the work being done. The important thing to note is that the specification never goes into detail about the implementation of these, but simply references where the details can be found.
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