I have a two way SMS web application at [url removed, login to view] that needs finishing touches (like a sensible navigation) and testing with appropriate changes being made.
The testing that needs to be undertaken is as follows:
There are 3 different levels on the site according to how you log in.
The admin pages are accessed by
You can then see all the other usernames and the associated teams.
I will now write the basic rules the site needs to implement:
Someone sends a team a message
This message is sent to the relevant peoples' email addresses and mobile phones
If a text message doesn't get to the recipient this must be flagged, and a message sent to that recipient's email address informing him the phone number didn't work, and asking him to verify or email the correct mobile number.
The same is true for email's that do not work. i.e. the recipient must be informed via text that his email did not get through and to text his email address starting the text with "Email" followed by his email or NA if he doesn't have one.
If both fail, the captain must be emailed.
This will be a common situation with players changing their details quite often, rendering the captain's team sheets from the beginning of the season incorrect. This method relieves the captain of all the chasing to the databases up to date.
If we get to this stage and test it amoungst ourselves, and the navigation is done as per the previous email, I will release half the funds. We can then get a real team in to test it on. To test amoungst ourselves please go to the site and log in as
this will give you the [url removed, login to view] rfc team! Just 3 players at the moment.
Mess around with our details to emulate the situations above and test, test, test.
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables):
a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment.
b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request.
3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement).