-3

my team is starting to work on creating functional and technical requirements for big software. As a part of this assignment we are asked to provide well grounded hardware requirements. I have no idea where to start and how to do it, have you ever seen methodology or any practice that can provide such requirements? how should we decide and state that we need this or that processor? actually the system will work on any modern hardware. please tell me about your experience

Andrei Grb
  • 1

1 Answers1

-2

"big software" is way too broad to explore the hardware options you might have. From the top of my head, you'll have to define:

  • the RAM GB / SMT core ratio [e.g. I go for 2 / 1 ]
  • IOPS
  • HDD / SSD [ HDD for capacity, or SSDs for high IOPS ]
  • client side networking [ 10GbE, 1GbE, low latency ... ]
  • switches [ # ports, # uplinks]
  • blocking factor

Then, based on your internal workflow, plan hardware [or VMs if suitable] for:

  • sandbox system(s) [ QA and DEV ]
  • versioning control
  • backup
  • redundancy [ how much money your company loses if "big software" is down ]

Again, your question is too broad, try discussing the above inside your group then come back with more specific questions.

7y7
  • 108