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 @ 5c61a2b0
......@@ -52,13 +52,13 @@ A simple use case is an upgrade request from Symantec on a tool we had previousl
1. __Performance Sizing__
- __UI Changes__
- Symantec NetBackup Appliance Software version Pulldown will be added after appliance selection. The choices will be 2.5 and 2.6.
- GB changed to TB throughout the sizing interface.
- Performance sizing data collection screens will occur after capacity sizing. These pages will collect the data represented by the blue fields in the spreadsheet supplied by Mario Lukic on 1/27/14.
- GB changed to TB throughout the sizing interface.
- Performance sizing data collection screens will occur after capacity sizing. These pages will collect the data represented by the blue fields in the spreadsheet supplied by Mario Lukic on 1/27/14.
- __Logic Changes__
- After the capacity sizing calculations occur and the required capacity TBs are calculated we calculate the required throughput TBs using the performance sizing inputs and the calculation supplied.
- Mario will supply Digitec with a formula that will allow us to determine whether the capacity TBs are enough to satisfy the throughput TBs. If the capacity TBs satisfy the throughput TBs we simply use the capacity TBs to give the recommendation. If the capacity TBs do NOT satisfy the throughput TBs we then adjust the required TBs and proceed with the recommendation.
- After the capacity sizing calculations occur and the required capacity TBs are calculated we calculate the required throughput TBs using the performance sizing inputs and the calculation supplied.
- Mario will supply Digitec with a formula that will allow us to determine whether the capacity TBs are enough to satisfy the throughput TBs. If the capacity TBs satisfy the throughput TBs we simply use the capacity TBs to give the recommendation. If the capacity TBs do NOT satisfy the throughput TBs we then adjust the required TBs and proceed with the recommendation.
- __General Assumptions__
- If the software choice is 2.6 and sizing is chosen, you MUST use performance sizing.
- The data for recommendations for 2.6 will be submitted in the Digitec specified format.
- There are NO additional SKUs to be added in this update.
- If the software choice is 2.6 and sizing is chosen, you MUST use performance sizing.
- The data for recommendations for 2.6 will be submitted in the Digitec specified format.
- There are NO additional SKUs to be added in this update.
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