Software requirements: Difference between revisions

Revision as of 04:52, 10 March 2004

Software requirements are so constrained by hardware requirements, protocol requirements and (especially) performance requirements that we should avoid choosing any programming language, production wiki code or even chat code until the whole healthy buying infrastructure is much better understood. This starts by understanding the healthy signal infrastructure and its low tolerance for e-waste or volunteer labour.

Some questions to keep in mind as these concepts evolve:

audio vs. video as primary presentation of Consumerium buying signal
Python vs. Java - consider mobile device and wiki code issues
response time - is HTTP an acceptable protocol for our purposes? If not, can some similar REST protocol be developed that will be?
PHP - useful tool or slow script-kiddie fluff?

Revision as of 04:27, 10 March 2004 (edit) 142.177.76.153 (talk) No edit summary ← Older edit		Revision as of 04:52, 10 March 2004 (edit) (undo) 142.177.76.153 (talk) No edit summary Newer edit →
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]], [[protocol requirements]] and (especially) [[performance requirements]] that we should avoid choosing any [[programming language]], production [[wiki code]] or even [[chat code]] until the whole [[healthy buying infrastructure]] is much better understood. This starts by understanding the [[healthy signal infrastructure]] and its low tolerance for [[e-waste]] or [[volunteer labour]].

	Some questions to keep in mind as these concepts evolve:		Some questions to keep in mind as these concepts evolve: