| Description : |
Coder needs to create an EventInvitation web page
fully functional and database to store details of
its users. You can find many web pages where this
functionality had been built in:
www.socializr.com, www.evite.com.
We are looking for a working system and are not
much focused on graphics at this stage.
There are three main functional requirements of
the system. Please keep in mind that at this stage
we are only looking to develop the main logic
based on user recognition, friends recognition and
event invitation.
1. User recognition and data storage in the
database
EventInvitation needs to be able to recognise the
EvenInvitation user.
Only logged-in users can use the EventInvitation
system.
Recognition based on Email address and password.
All details of the person should be kept in a
database.
We are looking to collect the following data here:
First Name, Last Name, Email Address, Password,
Gender, Date of Birth, Region, City, Company
User needs to verify the email address by
confirming code sent to his email address, ect
If required we may be looking to add additional
data into the database.
Data from the database need to be linked to the
Friends and Event functionality.
Once logged in the user should be linked to the
main page having two Tabs: Friends and Events.
2. Friends. Find and store your friends which you
can invite to your events.
Once logged-in the user shall be able to see a
list of his friends (other EventInvitation users
that he knows) with all data (birthday, company,
photo).
User should be able to invite a friend to the
EventInvitation friends list.
Add a new friend functionality. This should work
by cross checking the email addresses with those
stored in the database.
If it is an EventInvitation user – add to the
friends list
If it is not an EventInvitation user – please
invite him to this web page. System should send an
email to the person. User would have to register
into the system. Once the friend registers it
would be automatically added to the friends list.
You should be able to upload your address book
from the main email providers (lets say 8 of
them). People in your address book who are the
system users should appear as your friends.
3. List Events and Invitation for an event
This tab should have two functions:
User should be able to see:
- all events to which he/she has invited people
(with their answer status) – user can click on
them and revise the invitations sent. User needs
to be able to manage its invitations.
- all events to which he/she has been invited by
other people (requiring user action) – user can
click on them and create responses
- Create a new event and invite friends to this
event.
At this stage graphics does not matter. All plain
and white background, but ready to have graphics
implemented when delivered by our graphics person.
Event Name, Hosted by, When, Start Time, Location,
Address, City, Region, Zipcode, Phone, Email,
Description, Event Type, Options
Once an event is created it should be able to
email the event information to the people selected
and friends and see it on the main Event page once
logged in.
It may sound complicated, please see
www.socializr.com, where such a logic (friends and
events) had been implemented. We are also more
than happy to explain all details.
Additional conditions:
1. We expect the EventInvitation to be
significantly expanded in the future, it needs to
have optionality for the database and the system
to develop it in any direction if required
2. You will develop the system in English
language, but it shall be easy to switch from
English into another language after the creation
of the system is finished
3. Graphics (especially the event graphics) needs
to be downloadable and exchangeable. Although
there are no graphics at this stage it is
important to keep in mind that we have a person
working on graphics and you have to make a system
that will accept the format of our graphics.
4. System needs to be able to handle huge amount
of log-ins (many accounts)
5. User friendly and quick to operate
6. We need to have the ability to check the system
pre finish
|
