Starting saturday
by Thomas \"Man of Ice\" Lund · in General Discussion · 01/05/2004 (12:36 pm) · 2 replies
Status from me - I'm over the worst, and ready to kick a$$
I'll start Saturday on the project again. First up will be a review of Bens docs and trying to draft some requirement documents for comments.
I'm missing those a bit at the moment. Simple requirements like e.g.:
* There must be a client for administrating customer accounts
* There must be a management server
* The management server must use the torque netlib
* Client must connect securely to the management server
* Users must authenticate using username and passwords
* Usernames are unique
Etc. etc.
A base to build our design on, that we all agree is the goal of the project (seen from the customer point of view)
It will take a few passes, but I bet its going to help us getting started, as well as keeping focus.
I'll start Saturday on the project again. First up will be a review of Bens docs and trying to draft some requirement documents for comments.
I'm missing those a bit at the moment. Simple requirements like e.g.:
* There must be a client for administrating customer accounts
* There must be a management server
* The management server must use the torque netlib
* Client must connect securely to the management server
* Users must authenticate using username and passwords
* Usernames are unique
Etc. etc.
A base to build our design on, that we all agree is the goal of the project (seen from the customer point of view)
It will take a few passes, but I bet its going to help us getting started, as well as keeping focus.
#2
We could start by putting in some requirements that say:
* There must be an interface for a billing system
* Billing systems must be plugable
* System must contain a simple example billing system
* Example billing system must be available in source for customers to expand
or something.
I believe that stating the requirements will make our solution much much better.
Requirements are as usual 100% seen from customer side of the system, and should never ever contain design. Thats what the design docs are for :-)
01/06/2004 (12:42 am)
Yeh. I agree fully that we need to have some plugable components or example clients.We could start by putting in some requirements that say:
* There must be an interface for a billing system
* Billing systems must be plugable
* System must contain a simple example billing system
* Example billing system must be available in source for customers to expand
or something.
I believe that stating the requirements will make our solution much much better.
Requirements are as usual 100% seen from customer side of the system, and should never ever contain design. Thats what the design docs are for :-)
Associate Ben Garney
I think that a lot of this we should try to leave flexible, if we can do so gracefully.