SCOPE OF THE PROJECT
Programming a website (online shop: FRONT END + BACK END) and making it work at the hosting. I will supply access to the host and to the database.
The scope of the project includes the design of the pages and the scripts behind it.
The site is to be developed in PHP. Database is Mysql.
Find explanation of the Website in attached document
1 Must use Dreamweaver (or at least I must be able to edit the websites with Dreamweaver)
2 Must use CSS,
3 Must use templates.
4. The website will be able to send email to customers to confirm order reception, order executions, etc.
5 Used programs and scripts must be free from copyright and from license payments. If used external code (PERL, Pear, Captcha, etc.) programmer will deliver a list of codes and where it has been sourced
6 System must allow to easily query the database and send promotional emails to users.
7 User register and log in:
7.1 User id must be unique
7.2 Some fields must be validated. (I will tell which ones and the validation logic)
7.3 Webmaster must be able to enable and disable captcha system (for user registration and login)
7.4 Function “I forgot my password”: (Enter email and resend the password):
8 There will be SSL security in place.
9 Pricing of the “tickets” will depend on user’s profile
10 Accepted payments: Paypal + Credit card (I will supply interface with the bank) + Bank Transference + load of excel sheets with users and amounts paid.
11 Web to be multilingual. To be developed in English. (Translations are up to me. What languages are in place must be driven from the webmaster Back End) (I mean that I can say: now functional “en” + “it”. In one month time I will switch on “es”, in another month, I will switch on “fr”. In 4 months time, I can switch off “it”
12 Not all the options (tickets) will be available in all of the languages. The kind of tickets available in each language must be driven for the Back End. This may affect the screen (the main screen) where all the available options for one country are displayed
13 For the database to run quicker, old records will be removed from the production tables and put in the history files
14 After the tickets have been sold, some post processing will be needed.
15 For the most sensitive data, we will keep track of the status (explanation: for the user, I want to keep track of all his addresses along the time)
16 System must be prepared to load data from excel sheets
17 link: “tell a friend”
18 link/button: “add to my favourites / markers” in the browser
19 For one user to be able to invite one friend to take a ticket in the same vehicle, the system must generate a code “A1g8nqefd89522ds” to be sent to the 2nd user. 2nd user will enter the code in the system, and this will trigger some events (will identify both users as friends). I will give full details before programming starts.
20 There will be several banners: To be managed from the Back End. Note that banners in different languages will be different.
21 System will have 4 levels of access (non identified users – identified users – supervising webmaster (no data alteration allowed) - full webmaster (data alteration allowed)
22 User may want to access and alter his data. Also access to his history in the website (I mean past orders, tickets bought, account movement)
23 In the order screen, there will be 2 warnings which will be visible under certain conditions (1 – if non registered user has place orders => must register or log in. 2 – if registered user has not money to pay for tickets he has ordered)
24 Before the trips, we will reserve some seats for our crew. This seats can be sold before or even after the departure of the vehicle.
25 System will account sales and revenues per trip, week, (I will define criteria)
26 Back End: Visitor (screen definition and web browser…) and customer profiling (per country, sales, top ordering one…). System will also update timely statistics of users.
27 Keep track of emails sent to customers.
28 Ability of making discounts (i.e. from a certain date onwards, give a free ticket to a user every 10 trips only for a certain vehicle (i.e. bus): free 10th, 20th, 30th…
29 Promotion to customers: Generate series + sequence number per ticket and give one whenever a ticket is sold. So the number can be used to draw lots for prizes
30 Some of data of sensible fields will not be fully displayed to customers in screen (i.e. bank account details, will show only first 3 and last 3 digits)
31 Customers may define a limit of weekly expenses
32 Must show the steps in the purchasing sequence (1 define preferences – 2 Log in…)
33 System will forecast virtual balance of customer
34 Link / button for customer to be deleted from the database.
35 Webmaster can undo some of the purchases of the customers.
36 Webmaster can accede to customer’s data, and edit it.
37 Webmaster can delete 1 user
Periodically (may be daily or when a trigger works) the system will evaluate the existing Orders of customers with money in the account and what there is available to sell at that time. When available, it will match orders and tickets. Also will take actions
Mysql: I will suggest the tables and the fields.
I am open to study your suggestions both to improve the characteristics of the website and to reduce complexity of your work.
Remark about ITEM 12 – multilingual request. I have 2 concerns about that: 1st is that text in buttons in different languages will have different width: will the buttons self accommodate in width or shall I have to adjust in manually? 2nd question: Since not all the kind of tickets will be available in all the languages, How to accommodate to all the languages the main sheet where all the products are displayed?
I will define the guidelines of the system, I will define triggers (time based or click based), flow charts, the tables, the fields, the working logic, the algorithms, screen shoots and details of the connection to the banks. Thus I pretend that your job is focused on the programming rather in defining the system
I would like a close contact and a timely review of the project at the developing stage so we get things done at the first time, rather than asking you to change things after they are done.
Time frame: Timing is not the priority. I am thinking in make a decision by 15th of June. I do not want the project to last for many months, but 2 weeks more or 2 weeks less does not make a difference for me.
Payment: Will use Pay Pal. If this is not acceptable, I will listen your proposal.
17 freelanceria on tarjonnut keskimäärin %project_bid_stats_avg_sub_26% %project_currencyDetails_sign_sub_27% tähän työhön
Need some sample site for how the design should look. Will provide to mocks to select the design. Will create a prototype of the selected mock. Then all the back end functionality.
Well, minimum 25 days will take to complete you work. we are ready to start the project and confident too...if you have any question , then you can PM me