Software requirements: Difference between revisions
typo |
questions |
||
| Line 1: | Line 1: | ||
'''Software requirements''' are so constrained by [[hardware requirements]] and [[protocol requirements]] that we should avoid choosing [[wiki code]] or even [[chat code]] until the whole [[healthy buying infrastructure]] is much better understood. This starts by understanding the [[healthy signal infrastructure]]. | '''Software requirements''' are so constrained by [[hardware requirements]] and [[protocol requirements]] that we should avoid choosing [[wiki code]] or even [[chat code]] until the whole [[healthy buying infrastructure]] is much better understood. This starts by understanding the [[healthy signal infrastructure]]. | ||
Some questions to keep in mind as these concepts evolve: | |||
*[[audio]] vs. [[video]] as primary presentation of [[Consumerium buying signal]] | |||
*[[Python]] vs. [[Java]] | |||
*[[response time]] - is [[HTTP]] an acceptable protocol for our purposes? If not, can some similar [[REST]] protocol be developed that will be? | |||
Revision as of 04:26, 10 March 2004
Software requirements are so constrained by hardware requirements and protocol requirements that we should avoid choosing wiki code or even chat code until the whole healthy buying infrastructure is much better understood. This starts by understanding the healthy signal infrastructure.
Some questions to keep in mind as these concepts evolve:
- audio vs. video as primary presentation of Consumerium buying signal
- Python vs. Java
- response time - is HTTP an acceptable protocol for our purposes? If not, can some similar REST protocol be developed that will be?